Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - skronstein

Pages: [1] 2
Chronos User Discussion / Re: HDMI support
« on: March 18, 2019, 09:04:22 PM »
What software are you running? HDMI is supported in v0.3.1-RC1.

Chronos User Discussion / Re: SSD rig parts list
« on: March 18, 2019, 09:03:04 PM »
I just saw that the Chronos store now has a SSD that is all ready to go:!/SanDisk-250GB-SSD/p/133345530/category=24447029

Ordered one :)
You'll still need an eSATAp cable with any SSD.  I don't think it's included with the SSD.  Here's the one from our store:!/eSATA-to-SATA-Cable/p/133345541/category=24447029

Chronos User Discussion / Re: Chronos 1.4 RAW conversion tool - pyraw2dng
« on: February 11, 2019, 04:47:38 PM »
I can't decode 12 bit compressed RAW format.
When trying to convert it the output DNG files contain color noise and sometimes something similar to out-of-sync frames.

Tested both options '-d' and '--oldpack'; resolution specified correctly; RAW files saved with firmware 0.3

Are you able to use 0.3.1-RC1 instead? It can natively record videos in CinemaDNG format.

What do you mean by color noise?

The readme says that the old RAW 12bit format has bugs that cause color corruption:
The --oldpack option will attempt to decode the raw file as a 12-bit packed format generated from software versions v0.3.0 and older. However due bugs in this encoding format, there may be off-by-one pixel errors in the encoded files. This is most noticeable as colour corruption after demosiac.

Chronos User Discussion / Re: frame rate stored in saved video?
« on: February 08, 2019, 08:08:07 PM »
Some media players allow you to view metadata.  For example, in VLC, it's listed under Tools-->Codec Information.

Chronos User Discussion / Re: Fixing corrupt files
« on: January 08, 2019, 03:26:21 PM »
This page has a guide and tool that should help to recover your mp4 files:


latest beta, v0.3.1 beta 9.

And I adjusted the cameras clock beforehand, but can't say for sure if only the FAT32 tests were done after (but I think so).

Thanks for your help!!
All the best

The latest software is actually v0.3.1 RC1, available here:
Could you retest on RC1 and see if that can save multiple DNG sequences and with folders correctly named?

Chronos User Discussion / Re: Fixing corrupt files
« on: January 03, 2019, 06:11:10 PM »
Hi. I have a couple of Chronos videos that will not play. While saving the files, the camera froze, showing a negative frame value, and required a restart to recover. V0.3.1-RC1 software is installed. Both files are 2147483647 bytes long, the maxed out value of 31 bits. Is there anything to try to recover any part of the files? I've tried various online mp4 recovery tools without success. VLC has not been able to fix the files. The SD card is formatted one of EXT formats. Should large files be avoided and known to cause the Chronos to freeze? Thank you and Happy New Year!
Large files shouldn't be a problem for the Chronos when using any of the EXT filesystems, as they support files over 2gb. Files over 2gb are only a problem on the FAT32 filesystem.

At what point did the camera freeze - at the beginning, middle or end of the save?
At what point did the negative frame number show?
Was the Abort Save button working?
What kind of storage device are you using - SD, USB, or eSATA?
Has this camera and/or storage device successfully saved videos before?
Are you sure that was saving in h264 format, not RAW16 or RAW12? On h264 saves, it shouldn't even be possible to exceed 2GB due to compression, at least with the size of that marked region, which is about 13800 frames long.

Greetings, these question are for the developers:

- Is there a folder naming bug when exporting to eSATA when the drive is Fat32 formatted?

After doing some eSATA export tests yesterday, using ext3 filesystem, today I tried to redo some tests using the same drive, Fat32 formatted (it's an old WD Raptor 10k drive, 74Gbytes in size, Clustersize is set to 64 sectors == 32Kbytes).

While saving to the SD card always resulted in folders named e.g. "vid_2018-12-31_16-22-09" (and I assume the ext3 folders were named like this as well, didn't check them, but never got an error like this), with Fat32 I can save only once!
The second export always cancels with "Recording failed: File exists", the reason being the raw-file folder wasn't named with the current date/time, it's simply named "vid_2018" (reboots, replugs, etc didn't change this).

The first video is also lost in that moment, the folder only contains the first .dng-file afterwards, 0-byte sized. All .dngs from the first, successful save are gone.

What software version are you using?

Software Dev / Re: Can't fine the overlay feature
« on: November 27, 2018, 08:21:42 PM »
Thanks for reporting the bug. I've replicated it and I'll try try to get the overlay to display with autosave in the next release candidate.

Software Dev / Re: Can't fine the overlay feature
« on: November 26, 2018, 06:50:15 PM »
It's fine that you skipped beta 4 - there is no need to apply updates in a sequence.

Software Dev / Chronos V0.3.1-RC1
« on: November 19, 2018, 07:15:50 PM »
Here is Chronos 1.4 Software V0.3.1-RC1. Do not use this software version if you are capturing something that is not easily replicated.

   ++                                  ++
   |   Chronos V0.3.1 RC1 Changelog     |
   ++                                  ++

Changes from beta-9 to RC1

Notable Changes:
 - Recording speed boost! Save up to about 90fps on h264 saves at full resolution.
 - Revert to 8-bit gamma for monochrome TIFF to improve software compatibility.
 - Split the TIFF encoding into two use cases: "TIFF" for easy editing and software compatibility and the option to display the overlay in the saved images, and "TIFF Raw" for getting at the full 12-bit encoding (linear raw data) for scientific uses.

 - Future updates can be applied from the SD card, and there should no longer be problems with the camera not finding updates that are present on USB sticks after this update is applied.
 - Save settings window: enlarge buttons for easier use, and save location dropdown for longer names
 - Animated dots during saving and aborting to indicate that progress is being made.
 - When autosave is enabled, always use autoname (name by date and time) to avoid naming conflicts

Fixed bugs:
 - Trigger/IO settings window: If exposure trigger or shutter Gating were selected on IO2, it would revert from IO 2 back to to IO 1, though the choice between Exposure Trigger and Shutter Gating would remain.
 - Bad white balance when factory cal is absent.
 - "File already exists" warning not showing up when autosave is disabled

Also, some bugs that were introduced in beta-9 but now fixed:
 - Improve compatibility of CinemaDNG sets of images saved from monochrome cameras.
 - corrupted video with low resolutions are used
 - Trigger/IO settings window had a bug preventing exposure and shutter inputs on IO2 and 3.

More changes (from beta-4 to beta-9)

  ++                                          ++
    |   Chronos V0.3.1.9 Changelog   |
  ++                                          ++

Notable Changes:
 - New Demosaic algorithm based on AHD, which should improve color reproduction and reduce edge noise.
 - Standalone daemon to operate the video system, with DBus API.
 - External HDMI displays are supported at 1080p and 720p resolutions.
 - Recording speed improvements.
 - Add CinemaDNG and TIFF as save file formats.
 - Deprecate Raw 16-bit right-justified save format in favor of CinemaDNG.
 - Add a demo mode to replay a section of recorded video in a loop.
 - Add option to overlay frame statistics onto processed video formats (H.264 and TIFF).
 - Jog wheel can be used to adjust the exposure, and navigate the settings menus.
 - New video memory recovery tool to download video (slowly) in the event of a software crash.
- Redesign of the white balance window, including a new dialog to edit the color matrix.

 - Add whitebalance preset for 3200K/Tungsten lighting.
 - Adjust highlighting of text when selecting text boxes.
 - Auto-record and auto-save modes independant of one another.
 - Improved algorithm to estimate framerate during file save.
 - Date format in the Utility window changed to shorten the Month string.
 - Display separate version strings for both the Application and Filesystem/Release.

Fixed Bugs:
 - Crash causing the video to freeze after approximately 45 recording attempts.
 - Trigger delays would scale incorrectly when using segmented recording mode.
 - Abort recordings when the free space drops below 20MB to avoid crashing when the disk is full.
 - UI bug causing the selected save location to always select the first mounted disk.
 - First frame of a raw recording would contain corrupted NV12 image data.
 - First pixel of a Raw 12-bit packed frame was sometimes being dropped.
 - Corrupted pixels at the end of a Raw 12-bit packed frame.
  - Add crosshairs to the white balance window.
  - Add Qt stylesheet to improve focus visibility.
  - Main window exposure now shown in microseconds and shutter angle.
  - Jog wheel now adjusts exposure logarithmically, or by degrees when pressed.
  - The 'close' button on the soft keyboard now applies the entered text.
  - Reorganization of the soft keyboard to include a negative key.
 - Black ares of the UI become transparent after an HDMI hotplug.
  - HDMI hotplug while on the playback window would revert to live display.
  - Add missing ColorMatrix1 and CalibrationIlluminant1 tags to CinemaDNG files.
  - Fix possible crash of the video system when aborting a file save.
  - Fix possible carsh of the UI when rapidly aborting and re-starting a file save.
  - Fix color correction math so that saturating the image sensor tends towards white.
Also, some bugs that were introduced in beta-4 but now fixed:
  - Monochrome TIFF now pads the pixel values with least-significant zeroes.
  - H.264 bitrate setting was being ignored and defaulting to 0.25 bpp.

Compatibility Issues:
 - The pixel packing order in Raw 12-bit mode has been changed for the v0.3.1 release.
   Given a pair of two 12-bit pixels in hexidecmal as (0x123, 0xabc), the bytes produced
   by the Raw 12-bit packing mode changes as follows:
     v0.3.0 and earlier: (0xab, 0xc1, 0x23)
     v0.3.1 and later: (0x23, 0x1c, 0xab)

Known Bugs:
 - The first frame of an H.264 recording is erroneously copied from the display buffer before the recording starts.
 - Cal and settings data sometimes don't want to be backed up.

Please let us know what you think of the updates. And most importantly, let us know the bugs and things you do not like about the update. If there are any serious issues, please email

Updating Your Camera
 - Extract the `.zip` file into the root directory of a FAT32 formatted USB drive.
 - Turn on your camera and insert the USB drive into the USB/eSATA combo port, not the one labeled 'OTG'.
 - From the main window, tap the `Util` button to open the utility window.
 - As a precaution, tap the `Backup Calibration Data` button on the utility window before starting the update.
    - When the backup is completed, a pop-up window will be displayed.
    - Tap the `Done` button to close the pop-up window.
 - From the utility window, tap the `Apply Software Update` button to begin the software update.
    - A warning message will be displayed, tap the `Yes` button to confirm and begin the update.
    - If a pop-up that says 'No software update found' is displayed, even when a USB stick containing the update in the correct location is connected, reboot the camera and try again.
 - During the update, the screen will go blank and an `Applying Update` message will be displayed.
 - After approximately 60 seconds, the update will be complete and the camera will restart.

Chronos User Discussion / Re: Chronos 1.4 RAW conversion tool - pyraw2dng
« on: November 06, 2018, 04:44:11 PM »
Hi all,

I really want to try out the raw footage on the Chronos but I am struggling to edit the footage. I am a Mac user, can anyone explain how I can create the dng's on a Mac or will I have to use a PC to transcode them?



The 0.3.1-beta-9 version of the camera software can save directly to dng format, no need to transcode. Are you using a monochrome or color camera? DNG's saved directly from a monochrome cameras currently have compatibility issues with some software.  We're working on a fix for this.
If you have to convert a raw file that has already been saved, you can just follow the directions for linux, as they should work on a Mac too.

Chronos User Discussion / Re: transfer video to computer via code
« on: August 28, 2018, 12:02:10 PM »
The last number in the IP address should be 1, not 21. So, the whole address should be

Chronos User Discussion / Re: Connect to Chronos 1.4 via Ethernet
« on: August 09, 2018, 12:46:41 PM »
A python script that automatically copies files over the network was explained and posted here

Chronos User Discussion / Re: Trigger can just stop recording
« on: July 12, 2018, 04:12:53 PM »
It's fine to have the camera start a new recording automatically after a save.  Just check both the "Auto Record" and "Auto Save" checkboxes in the Util menu.  This means the camera will be recording all the time, except for when it is saving, but that does not stress the camera any more than starting the recording just before the event occurs.  It does not even increase the camera's power usage.
Before using the auto save option, make sure that you have enough free space to save the videos.  They could be large depending on your save settings.

Pages: [1] 2