Chronos V0.6.0 Full Release

A little comparison between 1.4 and 2.1 - both with V0.6.0
Outdoors, no clouds.
Framerates: 17391 (1.4) and 16191 (2.1) recorded as TIFF



In my opinion the 1.4 picture looks well - the 2.1 picture is very flat....

 

Attachments

  • vergleich.jpg
    vergleich.jpg
    215.5 KB · Views: 2,213
I have a 2.1 but update doesn?t work here.  Using balenaEtcher, W10, W7, MacPro and different SDs. After balena is finished I have only a e:/boot 35 MB partition (!) and nothing else. WINrar doesn?t work either. Do I probably need a  NEW completely unformated card to proceed?
 
did you unpack the File First? i used 7Zip, if you just put the File as is from the Downloader into the Etcher, it wont work.
 
Yes, I did.

Chronos-20210205_manualBuild.img  >>>>>> Etcher ... and here is what I got:

Boot E:/  35MB - and nothing else, although another windows says "Flash complete"!

Allright....

But when I inserted the card into the cam and started it nothing happens, no ?column gain calibration sign,? no update
 

Attachments

  • boot1.jpg
    boot1.jpg
    5.5 KB · Views: 2,119
  • boot2.jpg
    boot2.jpg
    10.9 KB · Views: 2,091
  • boot3.jpg
    boot3.jpg
    14.1 KB · Views: 2,093
Thats normal so far, you cant easily see the other Partition on Windows. Only the Small Boot one will show up, but there is an invisible other one too. Does the Camera start up with that card however, meaning, you see an Krontech Logo/ Animataion after a bit and later a User interface you can interact with, or is something along the Boot-Process broken?
 
Everything is clear now  The microSD card on the bottom, NOT the SD card on the top! 

Thanks to Mostafa Azarbar (opening my eyes).

Read quick, be blind ;)
 
The linked instructions say that special factory calibration files are no longer needed for both the 1.4 and the 2.1, while the first post here only mentions the 2.1 ? can anyone please clear this up? Can the 1.4 generate it's calibration entirely on its own or is this limited to the 2.1?
Also, as the update currently cant be done "in place" but requires an SD-Card update, is the existing "factory" calibration data still relevant ion some way (like providing better results?)
 
NiNeff said:
The linked instructions say that special factory calibration files are no longer needed for both the 1.4 and the 2.1, while the first post here only mentions the 2.1 ? can anyone please clear this up? Can the 1.4 generate it's calibration entirely on its own or is this limited to the 2.1?
Also, as the update currently cant be done "in place" but requires an SD-Card update, is the existing "factory" calibration data still relevant ion some way (like providing better results?)

Thats right - the 1.4 generate its calibration internally - only the 2.1 needed their own factory data. For a new calibration both cameras need te same process now.
 
NiNeff said:
The linked instructions say that special factory calibration files are no longer needed for both the 1.4 and the 2.1, while the first post here only mentions the 2.1 ? can anyone please clear this up? Can the 1.4 generate it's calibration entirely on its own or is this limited to the 2.1?
Also, as the update currently cant be done "in place" but requires an SD-Card update, is the existing "factory" calibration data still relevant ion some way (like providing better results?)

A few notes to help clear things up (thanks for the help, Bian!):

Chronos 1.4
  • Fully self-calibrating from software versions 0.3.2 onwards
  • The old factory cal files aren't required/relevant anymore

Chronos 2.1
  • Fully self-calibrating from software versions 0.6.0 onwards
  • Required special factory files up until version 0.6.0, aka. factory cal
  • The old factory cal files can be kept in case you aren't satisfied with how the image quality works for your preferred resolution/framerate/gain settings, in which case you can safely revert to 0.5.0

Both Cameras
  • All calibration data generated by the camera itself can be backed up or restored via the Util -> Storage screen
  • It's possible to import calibration data between unstable and stable releases, but we recommend calibrating again after each update, since it's a short and automatic process
 
Hello,

I've updated my Chronos 1.4 cam from v.0.3.2 to the v.0.6.0. Now I have a problem because my 256 GB SD card is not detected by the camera. Card is formatted as FAT32 and was detected by the camera for previous firmware with no problem.  I've noticed that the same SD card connected to USB/SATA input through SD/USB adapter works fine. After detection as USB/eSATA input device, I've formatted the SD card using camera software. But after this the SD card is still not recognized when installed into the dedicated SD card slot in the camera. From USB/eSATA slot everything works fine.
 
Hi,
Another issue I've noticed after updating to v0.6.0 firmware my Chronos 1.4 is the problem with authomatic camera shut down after disconnecting from the power supply. I've investigated the problem and I see that this occurs only when camera is connected to LAN interface and SMB share file transfer is configured. When this setup is made then camera has a problem with authomatic shut down. Waking up after connecting the power supply is always ok. It is interesting that when the file saving destination is changed from SMB share to USB drive then the camera shut down properly, even if LAN cable is connected. Have you any suggestions how to resolve this?
 
I currently using the 0.5.1 version. When I let the camera check for updates it says that no updates have been found :(

Any ideas what to do?

PS: ahh maybe it's better to first read the entry post. Then I will wait until I can update via network :'D
 
sanjay said:
Something that's a bit different for this update is that you'll need to create an sd card image. We're having some issues with the package server, so the Util->Storage->Apply Software Update via network will not work for this update, but I still wanted everyone to have it instead of waiting for me to fix it. I'll come back and post when this update is also available via network update.

See http://debian.krontech.ca/manualBuilds/ for the update file, checksum, and a PDF of the release notes. Also contained in the PDF are instructions on how to update, and how to calibrate your camera, so hopefully that works as a start-to-finish guide for everyone. Please let me know if anything is unclear.
.
Reread the first post in this thread from sanjay, for 6.0 you need to do an manual update. They wanted to fix it, so automatic updates would work, but i guess they didnt yet do that, so you still need to manually update it.
Hope this works for you.
 
Nikon1 said:
Here is an untouched DNG Sequence (Heavily Compressed With 7Zip) directly from the 2.1, that shows this Banding i talked about above in Motion. Watch for the Reflection on the Hammer and how it affects the Background. Shot at 0db 1kfps, 180? on an Schneider-Kreuznach Tele-Xenar 75mm/2.8 (was a bit stopped down, not exactly sure where i put the Apperture at...). This Short bit of Footage also shows Ghosting, where the Hammer Moves Fast, there is a "Ghost" Exposure of the Overexposed Highlight Visible, which disappears, when it suddenly stops. The Ghosting was allready there in the Previous Version, and wasnt really a Problem Ever for me, but still wanted to point it out, as i now finaly have footage which shows it very well; but the "Horizontal Banding" isnt that nice, and i dont remember it beeing that visible bevore.
Ran into this Ghosting issue again last Weekend, when i had a Shoot, where we Tried to Shoot a Water Drop Silhouette on a Black Background. There it was a pretty big Problem.
Requirements for the Final Shot were a Black Seamless Background, and only the Drop (/spot where the Drop hits the Surface/ resulting Waves) or its silhouette visible.
Did a Proof of Concept shot on the 0.6.0 Firmware @1kfps, and it just looked completely unusable, immediately switched to 0.5.1Unstable, and it was about as bad.
Ghosting was about the same or a bit less on the Unstable 5.1 Build, but at least the banding was way less visible.
Ghosting seems to become really nasty and bad, if Image is basically solid Black and some Overexposed or at least extremely bright spots moving very fast relative in comparison to Framerate (what that shot was all about).
Did the Rest of that shoot on the 5.1 Unstable Firmware, and eventually switched to 2.1kfps, as Motion blur was a bit much anyways, where it was still noticeable there, but way less prominent/ distracting.
As Ghosting seems to be about the Same on both Versions and thus still relevant, i thought i might as well share it here for future improvement.
.
Attached is an Render of the First Proof-Of-Concept Shot i did (sadly cant share any final Shots here, lighting was changed a bit later) on 5.1 Unstable, and some Untouched DNG Frames from the Same Shot.
For the Render i didnt even Bother to do any further editing, grading or denoising, its mostly just an DNG-Conversion to MP4, to be small enough to be posted here as an Entire Sequence.
.
Settings Must have been 1000fps/0dB and something between 180? and 130? Shutter, but i didnt take any notes about it that day, so cant say for sure about the Shutter Speed.
 
Back
Top