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 3 ... 5
Chronos User Discussion / Re: Introducing Chronos 2.1 HD!
« on: January 08, 2020, 02:22:00 PM »
I see that the 2.1HD is now listed as "If you buy one unit today. expect to receive it by April 2020." - Does this apply if I ordered it last year? I'm guessing so, sadly.

It's best to contact for general and sales inquiries.

Software Dev / Re: Chronos V0.3.2-RC1 and RC2
« on: November 07, 2019, 10:25:00 AM »
Is the full version of 0.3.2 any better?

Software Dev / Chronos V0.3.2 full release
« on: November 04, 2019, 05:02:04 PM »
   ++                                  ++
   |     Chronos V0.3.2 Changelog       |
   ++                                  ++

Notable Changes:
 - Automatic ADC calibration during black calibration, which should reduce column banding across a wider temperature range.
 - Add a storage tab to the util menu to view, eject and format the attached storage devices.
 - Speed boost at most resolutions, with a top speed of 1069fps at 1280x1024, and 40420fps at 320x96.
 - Configurable automated power-on and off depending on the AC adaptor status.
 - Option to disable the ring buffer when in segmented recording mode.

 - Factory black calibration is now user accessible from the Factory tab of the util window.
 - The software update button has been moved to the storage tab of the util window.
 - Shipping mode to disable power-on by battery until an AC adaptor is attached.
 - Add a watchdog to reboot the camera in case of a power-on boot failure.
 - Display descriptive error strings instead of number on failure.
 - End of recording from lack of free space generates a warning dialog.
 - Revert to a valid resolution when focus is lost while editing the H/V resolution widgets.

Fixed Bugs:
 - Gated burst record mode may lock up after several trigger edges.
 - Gated burst record mode unreliable when trigger debounce is enabled
 - Memory leak in the M3 video coprocessors which could lead to a crash after lots of H.264 encoding.
 - Ignore video which was recorded during zero-time black calibration (which happens after changing resolution).
 - Stuttering issue on the playback window on new production LCD modules.
 - Fixed deadlock in camera when restoring user settings from external media.
 - Corrupted overlay text at narrow resolutions.
 - Video stream would remain in playback when starting recording via auto-record.
 - Opening and closing the white balance menu can lead to an unexpected change of the custom preset.
 - Bug in calculating the trigger delay on boot (segmented mode only).
 - Ensure a minimum of 0.25 bits/pixel when encoding h.264 video.
 - Crash can occur when saving extremely short videos.
 - After rebooting a camera, focus aid and zebras are sometimes not restored even if they were enabled before the reboot.
 - Restore white balance correctly after reboot

Fixed since V0.3.2-RC2:
 - monochrome cameras being detected as color
 - zombie process when restarting app after reverting settings to defaults.
 - Util window - Auto Power Mode was always shown as Disabled after reentering the Util window, even if it is set to something else

Fixed since V0.3.2-beta-6:
 - Changes to focus aid or exposure aid (zebra stripes) would have no effect until resolution is changed.
 - Changes to exposure may be overwritten during black calibration.
 - Bad image quality at 336x120 resolution
 - Util window, storage tab - bottom of text cut off if device has multiple partitions
 - Factory black cal (black cal all resolutions) would get overridden by old user black cal, if a user had done their own black cal, even before.
 - Fix frame stuttering when focus peaking is enabled.

Known Bugs:
 - The second frame of videos saved in all formats is not from the correct location in the selected region.
 - The first frame of videos saved in formats other than H.264 format is corrupted.
 - Very rare crashes of the video system, causing the camera to lock up on the playback/save window; MTBF seems to be somewhere in the 2-5k recordings at present.
 - Gated Burst record mode only: Live display does not appear to be buffered correctly when the trigger signal is inactive.
 - Speckles in image when recording below 60fps
 - Black cal makes the image look very dark at low framerates when recording below about 45fps
 - Saved videos will have a date modified of 7 or 8 hours earlier than what is set on the clock in the Util menu.


Software Dev / Re: Chronos V0.3.2-RC1 and RC2
« on: October 18, 2019, 05:52:26 PM »
I can confirm the lag issue is gone now. The "Tab is only highlighted and not selected" issues might have gotten a bit worse, but it's hard to tell. I have an estimated "errorrate" of about 1 in 4. This is close to the point where it gets annoying. I did not put the old screen back jet to test the source of the issue though.
According to foobar, we may need to update calibration data for the new LCD panel to fix this:
The response of the touch screen may not be in perfect alignment with the LCD display. Normally this would be fixed using calibration software to align the touch inputs with the underlying LCD. On the old panel, the geometry was close enough that we have never really needed to perform that step, we may need to update the tslib calibration data for the new panel.

Chronos User Discussion / Re: Introducing Chronos 2.1 HD!
« on: October 16, 2019, 07:38:49 PM »

I just saw in the 2.1 manuel that there is no mention about the 100.000 fps as the max framerate as it was said as the camera was introduced. In fact the max framerate is now shown lower as that of the 1.4. did you change that by purpose or is it just not up to date?

The 2.1 and 1.4 both have require a minimum frame height of 96 pixels because the H.264 encoder needs at least that many pixels to work correctly.
This will eventually be worked around by adding black bars above and below the footage at the time of saving the video, if the H.264 format is being used. Once we get around to implementing that, the 2.1 will have a max framerate around 100kpfs.

Software Dev / Re: Chronos V0.3.2-RC1
« on: October 10, 2019, 08:49:05 PM »
V0.3.2-RC2 has been added to the OP, along with the changes since V0.3.2-RC1.

Chronos User Discussion / Re: vnc or other remote desktop possibility?
« on: September 30, 2019, 05:16:48 PM »
You'll have to wait until we have the 0.4 beta software release. That is when the ethernet API will be available.
The next best thing that we've put out is the get_latest_video python script.

Are you using the C to CS adapter that came with the camera?

Chronos User Discussion / Re: Trigger Switch Cable
« on: September 18, 2019, 01:21:45 PM »
To use a pushbutton trigger with IO 1 (BNC), choose Record End trigger and enable one or both of the Pullups and Debounce.
After applying these settings, IO 1 should change between Hi and Lo; the status is just above and to the left of Apply on the IO Settings screen.

Chronos User Discussion / Re: Upgrading the 1.4 to the 2.1
« on: September 17, 2019, 03:15:47 PM »
We are working on a plan for trade-ins. Details are not ready just yet. You can sign up for the newsletter here so you will know when we do have details ready:

Chronos User Discussion / Re: Maze artifact with 1.4
« on: September 17, 2019, 01:29:40 PM »
Which of the RAW save formats was used - 12 bit or 16 bit?

Chronos User Discussion / Re: Maze artifact with 1.4
« on: September 10, 2019, 02:31:09 PM »
I've downloaded a few applications including GIMP and Raw Therapee to try and repair two usable shots captured earlier this year that were corrupted in this way.   I'm not having any luck.  Does the repair need to be performed on the raw file or each of the DNGs separately?   Is there any kind of workflow description or tutorial on how to do this? 

In Raw Therapee, I managed to get rid of the maze artifact using the VNG4 demosaicing selection, but it makes the image monochrome (color information is lost).

How important is it to recover the shots?
The process to recover them will be a lot of work. The python raw2dng script will need to be modified to unpack the DNG files twice - once as normal and then once with the assumption that the first pixel was lost(this messes up the colors because applications that process DNGs expect certain colored pixels to be in certain locations, and the loss of the pixel affects the location of every pixel in the image). Then manually look at each resulting frame to see which looks right and keep the good one of the two.

Software Dev / Re: Chronos V0.3.2-RC1
« on: September 03, 2019, 02:15:40 PM »
Another small bug:
In the Util Menu, sometimes "clicking" the tabs does not change to them but only highlights them.
See the following image of an example:
"About" is selected but the "Kickstarter" Tab still displayed.
Do you know if this only started when the screen was upgraded?

General high-speed discussion / Re: Shadowgraph Troubleshooting
« on: September 03, 2019, 01:46:39 PM »
Which raw format are you saving in? If the brightness in the mp4 videos from the camera look good, the then the TIFF format should too (but not TIFF Raw)
Some changes were made to the "raw 12bit" format in software v0.3.1, but I doubt that would cause the brightness issue seen here.

Software Dev / Re: Chronos V0.3.2-RC1
« on: September 03, 2019, 12:55:07 PM »
Thanks, I've added this to the list of known issues as "Lag when focus peaking or zebra stripes (focus and exposure aids) are enabled"

Pages: [1] 2 3 ... 5