Chronos > Software Dev

Software V0.3 RC2 (Updated June 11, 2018)

(1/6) > >>

tesla500:
Update (June 11 2018): RC2 posted

Here is the release candidate for V0.3, for those of you who want to try the latest and greatest. An updated manual is also attached to this post.

Keep in mind this software is still a release candidate. It has not gone through full validation yet, this software is generally stable but we don't recommend using this for any critical applications where it's not possible to recreate your shot. We recommend waiting for the final release for any applications that require guaranteed stability.


    ┌──────────────────────────────────┐
   ┌┘                                  └┐
   │     Chronos V0.3 RC2 Changelog     │
   └┐                                  ┌┘
    └──────────────────────────────────┘

Notable Changes (from V0.3 RC1):
- White balance can be selected from 5 common presets in addition to taking your own as you could previously.
- Colour calibration (via Set White Balance) now works as expected, and produces vastly more realistic colours.
- Fixed bug where corrupted frames would occur randomly (only on some cameras)
- 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.)
- Saving doesn't change the marked region of video. (Previously, it would advance video marks to the end of the recorded area.)
- Changes to video saving settings are now applied as they are made, not just when the popup is closed.
- Added a visual button to add more pre-record slider time in the trigger delay window.


Notable Changes (from V0.2.5):
- Colour reproduction is greatly improved, especially reds
- Keyboard behavior improved, text is now selected when you tap an edit box
- UI can be flipped, or set to display the main screen menu on the left side
- You can configure the "Unsaved video in RAM" popup 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".
- Fixed bug in 0.2.5 beta that resulted in a small portion of saves failing (about 2%)
- Fixed bug where segmented record mode would produce many invalid segments

More notable changes (from V0.2):
- Trigger I/O's Trigger delay input was moved to the Trigger Delay screen.
- Added Trigger Delay screen and Record Modes screen, accessible from Record Settings.
- Black cal duration reduced by 10s to 15s or so at max resolution. (We still hope to make this much, much faster in a future beta.)
- 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 auto-save after recording. This can loop.

Minutiae:
- Mark In and Mark Out have been renamed to Mark Start and Mark End, probably just until the video seek bar is made horizontal.
- Playback screen has 'region to be saved' marked. Each region saved is marked in a different color.
- The Enter key has been changed to say Apply, since you have to press it to apply your changes.
- The sliders on main screen the play screen have been made larger for ease of grabbing.
- There is now a Settings tab in the Util pages.
- Trigger IO window: The ratio between post-trigger frames and record length in frames is kept constant between resolution and framerate changes.
- 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.

RC1/RC2 known bugs:
-The first few frames in saved videos are from the end of the recording


Installation instructions:

* Unzip the Zip file into the root directory of a FAT32 formatted USB stick
* This should result in a camUpdate folder in the root directory of the stick
* Boot up the camera and insert the USB stick
* Backup your calibration data. Tap "Backup calibration data" and wait for this to complete (about 5 seconds). The cal data is now backed up on the USB drive as cal_[serial number].tar
* To install the update, tap Apply Software Update
* A message box should pop up indicating the software update was found. Tap Yes to install the update.
* The screen will go black, you may see a screen saying "updating", and the update will be installed. This will take about 30 seconds, potentially longer depending on the speed of the USB drive. There's no feedback that anything is happening, just give it time. The camera will restart at the end of this process
* Done!
As always, let us know of any bugs you find, we'll get them sorted out as quickly as possible. We anticipate the fully validated V0.3 release in about a month.

gamerdonkey:
I got the 0.3rc1 update and was playing with my Chronos and RAW output over the weekend. I've come across two issues that I didn't notice when I was running 0.2.5.

The first (and more minor) issue is that the first frame of all the videos that I output looks like the image below. I didn't do any in-camera h.264, so I don't know if it would appear in those. I also didn't notice it in preview or playback while working with the camera.



My second problem is that random frames in recordings are coming out corrupted like the ones below:





Frames before and after look fine. These also seem to be showing up in the preview and playback screens on the camera, though the picture below is from when I was able to reproduce the issue today and it looks a little different.



The problem seemed to arise when I changed resolution from 1280x720 to 800x480 after the camera had reached a warm temperature. That is how I was able to reproduce the issue today.

Thanks for your continued hard work on this project. The 0.3rc1 update has significant improvements! I have been able to work around these issues by manually deleting the problem frames, but I look forward to resolving the bugs more permanently.

John Delonghi:
I got the same first frame issue with 0.3 RC1, but it's no big deal to edit out for now.

I haven't seen the corrupted random frames yet, but I did notice a colour shift in a few frames in one sequence I was unable to explain, so maybe that's related?

JamesB:
Got the same start frame corruption and occasional frames garbled.  I reverted back to the previous release as I need all frames to be free of artifacts for a shoot I'm working on.  Hopefully, this bug can be fixed soon so I can continue testing.

tesla500:
Confirmed, duplicated it here as well. Looking into it now, will post an update in the main post above when we've fixed it.

Navigation

[0] Message Index

[#] Next page