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
Software Dev / Re: Question about SD card wear.
« on: June 14, 2019, 01:50:26 PM »
In what way did it fail?
The OS and camera application don't write enough the SD card to cause failures for a very, very long time.

Chronos User Discussion / Re: Segmented recording problem
« on: June 07, 2019, 07:57:36 PM »
Yes, mine operates the same way. As foobar explained, this is operating as intended.
But, we do want to add an option to disable the ring buffer.  Disabling the ring buffer means the camera will stop recording after the final trigger.

Chronos User Discussion / Re: Segmented recording problem
« on: June 06, 2019, 08:25:50 PM »
I have v0.3.1
Resolution: 1280x1024 1057 fps
I select 4 segments, 2183 frames each.  Pretrigger 1490, post trigger 693 (behaviour is the same for several different trigger delays I tried)

Started recording & triggered 4 times.
2nd segment is frames 1-2183
3rd segment is frames 2184-4366
4th segment is frames 4367-8732
1st segment is lost - appears to have been overwritten by 4th segment which is twice as long as it should be.

What if you press the trigger 1 less time than the number of segments? Even after all the segments are filled, the camera continues to record until the red shutter button on the top of the camera is pressed. If you set the number of segments to 4 and press the trigger 4 times, the camera will overwrite the first segment.  But, pressing it only 3 times, the first will not be overwritten because the recording ends right then. This behavior is probably unintuitive and I'll look into whether it can/should be changed.

Also, how are you checking where each segment ends? The Text Overlay on the save settings window gives useful data about current and total number of segments and frame within the current segment, so it is probably the best way to check.

Chronos User Discussion / Re: Segmented recording problem
« on: June 03, 2019, 01:11:35 PM »
Subtracting 8-10 frames from the length of each buffer may fix this wraparound issue.  So, with 4 segments, you might try subtracting about 64 to 80 frames from the total Record Length.

Chronos User Discussion / Re: Segmented recording problem
« on: May 27, 2019, 02:32:56 PM »
Is the latest software, v3.1, on the camera?
If so, what resolution and trigger delay are being used?

Chronos User Discussion / Re: SSD rig parts list
« on: April 15, 2019, 01:22:11 PM »
All -
I just ordered and received the previously linked SSD and eSATA cable.  Is there a special incantation that I need to get the drive to be recognized by the camera?

Thanks in advance -
Did you format the drive? If so, what format? The camera supports FAT32, EXT2 and EXT3.

Chronos User Discussion / Re: Type of RAM
« on: April 04, 2019, 11:15:13 AM »
If a camera has had its RAM upgraded, and you later need to send the camera back for repair under warranty, you'll first need to reinstall the RAM that it was shipped with.

Chronos User Discussion / Re: Autosave feature
« on: April 03, 2019, 01:25:40 PM »
I'm not sure how you plan to trigger a camera from 550m away, but if you want to use radio to trigger the camera, get a device that turns that radio signal into a TTL signal, and send that TTL signal to one of the 3 triggers on the side of the camera.
Alternatively, coax can be run 550m.

The camera can be set to record any time relative to the trigger - for example, start recording 4 seconds after, or finish recording 4 seconds after. I'm not sure which you want, but the Chronos supports both. You can also reduce resolution and/or framerate to get a longer record time.

Chronos User Discussion / Re: Problem saving No storage device found
« on: April 01, 2019, 08:44:56 PM »
I've had a similar issue at least once before with a fat32 SD card - it would either take a very long time to show up, or never show up at all.  I just had to reformat the card.  I chose ext3, but a reformat as fat32 might have worked too.

Software Dev / Software V0.3.1 full release
« on: March 31, 2019, 01:31:57 PM »
Software V0.3.1 is now available!

   ++                                  ++
   |     Chronos V0.3.1 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 window to edit the color correction matrix.
 - New video memory recovery tool to download video (slowly) in the event of a software crash.

 - 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.
 - Add crosshairs to the white balance window.
 - Add Qt stylesheet to improve UI focus visibility.
 - Main window displays exposure time in microseconds and shutter angle.
 - The 'close' button on the soft keyboard now also applies the entered text.
 - Reorganization of the numeric soft keyboard to include a negative key.
 - Animate the status window text while a file save is in progress.
 - When updating from v0.3.1-RC1 or later, camera can now be updated from an SD card in the top slot. Previously, it only supported updates on USB.

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.
 - Black areas of the UI become transparent after HDMI hotplug.
 - HDMI hotplug while on the playback window would revert to live display.
 - Add missing ColorMatrix1 and CalibrationIlluminant1 tags to CinemaDNG encoding.
 - Fix a possible crash of the video system when aborting a file save.
 - Fix a possible crash of the UI when rapidly aborting and re-starting a file save.
 - Fix a possible deadlock of the video system when switching resolutions.
 - Fix color correction math so that saturating the image sensor tends towards white.
 - Fix bug causing crash when opening both the full and numeric keyboards at once.
 - Camapp crashes or fails to save if directory not writable
 - Exposure drops every time user cancels on record settings
 - Minimum exposure was around 1.2us instead of 1.0us.
 - Maximum exposure wasn't quite attainable with the shutter slider on the main screen.
 - Focus peaking color resets after rebooting camera, or pressing OK on Record Settings.
 - Segmented record mode only: Invalid data would sometimes appear at the end of the recording.
 - Gated burst record mode only: recordings would be corrupted and/or incorrect length.
 - White balance doesn't work so well when framerate and gain are high
 - White balance having the opposite effect as intended, the FPGA mixed up red and blue
 - Focus peaking color would get reset after reboot or changing resolution
 - "Restore Settings from backup" not working
 - Prerecord box not showing on Record Modes if gated burst is enabled before that screen was opened.
 - Minor UI issues

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.
 - After saving hundreds or thousands (usually thousands) of videos, the camera may lock up on the playback/save window.
 - After rebooting a camera, focus aid and zebras are sometimes not restored even if they were enabled before the reboot.
 - Gated Burst record mode only: Live display does not appear to be buffered correctly when the trigger signal is inactive.
 - Gated burst record mode only: Trigger stops responding after multiple triggers until the recording is stopped and restarted.

Bugs fixed in V0.3.1 relative to V0.3.1-RC1:
 - Camapp crashes or fails to save if directory not writable
 - Overlay not showing on first save if either autosave was enabled, or if save tapped quickly after opening playback window
 - Stability issues after large numbers of saves. The camera can now save at least 2000 saves on average before the video pipeline has issues.
 - Overlay not showing on first save if either autosave was enabled, or if save tapped quickly after opening playback window
 - Segmented record mode only: Invalid data would sometimes appear at the end of the recording.
 - Gated burst record mode only: recordings would be corrupted and/or incorrect length.
 - White balance having the opposite effect as intended, the FPGA mixed up red and blue
 - White balance doesn't work so well when framerate and gain are high
 - Maximum exposure wasn't quite attainable with the shutter slider on the main screen.
 - Exposure drops by a degree after reboot, or pressing OK or cancel on record settings
 - "Restore Settings from backup" not working correctly
 - Prerecord box not showing on Record Modes if gated burst is enabled before that screen was opened.
 - Focus peaking color resets after rebooting camera, or pressing OK on Record Settings.
 - Minor UI fixes

   ++                                  ++
   |      Chronos V0.3 Changelog        |
   ++                                  ++

Features added and bugs fixed since 0.2:

Notable Changes:
- White balance can be selected from 5 common presets in addition to taking your own as you could previously.
- Custom White Balance calibration (via Set White Balance) now works as expected, and produces vastly more realistic colours.
- Colour reproduction is greatly improved, especially reds.
- Set White Balance now calculates against 80% brightness white instead of 100% brightness white.
- File size warning when saving are generally more reliable now. (eg., 4+GB file warning now FAT32-only, since only FAT32 has a 4GB file size limit.)
- Changes to video saving settings are now applied as they are made, not just when the popup is closed.
- Keyboard behavior improved; text is now selected when you tap an edit box.
- UI can be flipped upside-down, or set to display the main screen menu on the left side.
- You can configure the "Unsaved video in RAM" popup that appears when you hit the record button with an unsaved video in memory. It can be set to "Always", "If not reviewed" (default), or "Never". The previous behavior was always "If not reviewed".
- The sliders on main screen the play screen have been made larger for ease of grabbing.
- Trigger I/O's Trigger delay input was moved to the Trigger Delay screen. A slider has been added as a visual aid and an alternate way to adjust the trigger delay. The ratio between post-trigger frames and record length in frames is kept constant between resolution and framerate changes.
- Added Trigger Delay screen and Record Modes screen, accessible from Record Settings. Selectable modes are Normal, Segmented, and Gated Burst.
- Black cal duration reduced by 10s to 15s or so at max resolution.
- Use any SD card. Previously, a class 10 SD card was required. You can now use slower cards. Of course, using a slower SD card means that videos save slower too.
- You can now auto-record after saving and/or auto-save after recording. This can loop if both are used at the same time.

- Playback screen has 'region to be saved' marked. Each region saved is marked in a different color.
- There is now a Settings tab in the Util pages. This can be used to backup, restore, or reset settings, which does not include black calibration.
- Play -> Settings: bitsPerPixel, maxBitrate, saved file framerate, format, filename and save location are now saved as soon as they are changed instead of when the Close button is pressed.
- Mark In and Mark Out have been renamed to Mark Start and Mark End, probably just until the video seek bar is made horizontal.
- The Enter key has been changed to say Apply, since you have to press it to apply your changes on the record settings window.

Known bugs:
-The first few frames in saved videos are from the end of the recording.
-The camera will freeze after saving approximately 45 videos.  Make sure to reboot before saving approximately 40 videos to ensure the camera does not freeze.
-The camera will freeze when saving a video that is over 4GB onto a FAT32 partition, or when storage is full.
-If auto-record is enabled, but auto-save is not, a new recording will not be started.  However, the camera will still auto-record after booting the camera.
-Warnings about filesize (over fat32 limit, or insufficient free space) can still be shown even if autosave is enabled (if autosave is enabled, the user is unlikely to be there to press Yes for the camera to continue saving)

   ++                                  ++
   |     Installation Instructions      |
   ++                                  ++

 - Extract the `.zip` file into the root directory of a FAT32 formatted USB drive.
    - This should result in a camUpdate folder in the root directory of the stick.
 - Turn on your camera and insert the USB drive into the USB/eSATA combo port.
 - 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.
    - This should take about 5 seconds. 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 may be displayed.
- After approximately 30 to 60 seconds, the update will be complete and the camera will restart.

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:

Pages: [1] 2