KronTalk
Chronos => Software Dev => Topic started by: sanjay on February 08, 2021, 06:16:40 PM
-
Hey everyone,
We're happy to announce a new release of software for both the Chronos 1.4 and 2.1 cameras. This version should especially be helpful to Chronos 2.1 owners, as our engineering team has spent even more time improving image quality and attempting to reduce vertical banding.
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/ (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.
New Features and Improvements
- Chronos 2.1 models benefit from an improved sensor driver configuration. The analog gain values of the LUX2100 sensor have been modified to reduce noise at higher levels of analog gain (also referred to as ISO), such as 6dB, 12dB, and 18dB. This translates to less vertical banding than in prior software versions. Adequate lighting is still highly recommended.
- Chronos 2.1 models no longer require special factory calibration files. All calibrations required to use the camera with the best possible image quality can be performed by a customer in the field within 5 minutes via the Util -> Factory -> Column Gain Calibration function.
- Chronos 2.1 models benefit from newly generated Color Matrix presets, as found in White Bal -> Color Matrix. Previous software versions had color matrices that were optimal for the LUX1310 sensor in the Chronos 1.4, instead of the LUX2100 sensor found in the Chronos 2.1.
- A list of saved files on external media can now be browsed via Util -> Storage -> List Files. The same functionality exists to make it easier for users to select the save destination in Play -> Settings -> Pick Folder. The file browser also allows for users to delete files on external storage devices. This functionality is mirrored in the web page.
- Monochrome cameras can no longer open Color Matrix settings. This was mistakenly enabled in 0.5.0.
- Frame counts are no longer cut-off on the right-hand side of the display when in the Play screen when frame counts are six-digits long.
Known Issues, Updating, Calibration
Please see the PDF contained in the link above.
Chronos 2.1 Image Quality Change Demo
I've made a short video showing a before (0.5.1) and after (0.6.0) at HD with various analog gain levels. The main thing to note is the banding along the left and right sides of the frames in each shot, especially at 12dB. Please excuse the few spots of dirt on my engineering camera.
Download the video here: https://www.dropbox.com/s/urq1qmnsjv9kwcn/Chronos%202.1%200.6.0%20Update%20Demo%20%284%29.mp4?dl=0 (https://www.dropbox.com/s/urq1qmnsjv9kwcn/Chronos%202.1%200.6.0%20Update%20Demo%20%284%29.mp4?dl=0) (I recommend downloading instead of viewing online because of the compression/loss of detail from streaming)
0.6.0 User Manual
We've also updated our user manual to reflect this update, as well as some general semantics. See: https://www.krontech.ca/wp-content/uploads/2021/02/Chronos-1.4-and-2.1-User-Manual-Software-Version-0.6.0.pdf (https://www.krontech.ca/wp-content/uploads/2021/02/Chronos-1.4-and-2.1-User-Manual-Software-Version-0.6.0.pdf)
As always, please feel free to reach out to us at [email protected] for more urgent support inquiries. Thanks!
-
"With software version 0.6.0, Kron Technologies is pleased to announce that there are no longerany special factory files that must be generated at our facilities. Both Chronos 1.4 and 2.1models may be fully calibrated by owners within 10-15 minutes."
.
"Wait for 15 minutes to let the camera and image sensor reach their operating temperatures, then press Yes. This procedure can be redone at any time via the Util ->Factory screen."
.
.
.
Very Nice! Thanks for this new Update!
-
Thanks for this update!!
One question to calibrate the camera - is it necessary to use a lense cap in step 1 too?
-
i Blocked the Lens while doing that, which worked, not sure about if its nessercary, there is no mention about it in the PDF.
-
Did a bit of Testing on my 2.1, nothing too Serious or Methodical, just played around a bit without really Recording, Saving, Grading anything (havent touched Gain settings yet, all at 0dB), and for Higher Framerates (250+fps) and Full Resolution/ 720pHD Resolutions there is a Huge Improovement in Image Quality overall and also a LOT less of those Vertical Lines, even in the Really underexposed Areas of Frame (yes, even at the Lower sides.). This however seems to come at the Cost of a bit lower Overall Light Sensitivity, means it feels like it needs more Light now, which is a Fair Price To pay for this Improovement in Image Quality.
Produces Some Really Nice, even Almost Film-Like Looking Footage (had a Vintage Lens on there, so maybe the overall look of that makes me a bit nostalgic or something, idk....Whatever it is, looks very good)
.
But for Lower Framerates (24-250fps) and Lower Resolutions (below 1280px Horizontal Resolution), the Unstable Build and Even the Last Version did a Much better Job. 800x600px just looks Broken, Brightest Spots on the Frame Meassure about 50% on the HDMI-Out, no matter how bright i Expose is, to the Point where its even obviously Clipping. 100fps/ Full Resolution and Below also looks pretty rough, Way more Vertical Banding than ever in the Shadows, Mids And Highlights look OK-ish but also overall way lower sensitivity on those Settings overall.
.
In Summary a huge Update, which i will definately use for Full-Resolution/ 720pHD Shooting with 250+fps, but at least for now, i will still use the latest Unstable Build on an Second SD-Card for everything else than that, as its still somehow better for everything except that.
This Update is a big Step forward for High-Quality Footage on the 2.1, but i Feel it still needs some more Work to make me want to run it as the Only Software Version on there.
Still need to do further Testing however, maybe this will proove me otherwise.
-
This is working really well for me. Thanks!
-
I am so glad to see this improvement, I will install the patch and test it out. This really changes things as the banding was really problematic in my initial testing. Thank you greatly! ;D
-
Did some tests and also a comparison between 2.1 and 1.4 with the new version 6.0 and the vertical banding is nearly dissapeared.
At the moment the 2.1 needs much more light than the 1.4 and there is somting strange with the video signal level (tested with an external monitor portkeys BM5II). Its not possible to get a video level more than 90 IRE and at lower resolutions the level declines at 30 IRE @ 640x360.
On the other hand the 1.4 allowed a level to 100 IRE and with the same lens and at the same time the level was at 55 IRE @ 640x360.
it seems, that the new software reduces the dynamic range a lot, so that it isnt possible to use the full video level from 100 IRE.
Has someone made a similar observation?
-
Did some tests and also a comparison between 2.1 and 1.4 with the new version 6.0 and the vertical banding is nearly dissapeared.
At the moment the 2.1 needs much more light than the 1.4 and there is somting strange with the video signal level (tested with an external monitor portkeys BM5II). Its not possible to get a video level more than 90 IRE and at lower resolutions the level declines at 30 IRE @ 640x360.
On the other hand the 1.4 allowed a level to 100 IRE and with the same lens and at the same time the level was at 55 IRE @ 640x360.
it seems, that the new software reduces the dynamic range a lot, so that it isnt possible to use the full video level from 100 IRE.
Has someone made a similar observation?
Yes, can confirm, same for me, allready wrote a bit about it above:
[...] 800x600px just looks Broken, Brightest Spots on the Frame Meassure about 50% on the HDMI-Out, no matter how bright i Expose is, to the Point where its even obviously Clipping. 100fps/ Full Resolution and Below also looks pretty rough, Way more Vertical Banding than ever in the Shadows, Mids And Highlights look OK-ish but also overall way lower sensitivity on those Settings overall.
[...]
-
I also noticed some Horizontal "Banding" (or whatever one would call that?) when Overexposed Areas are In Frame right next to dark areas. Dont remember them to be this visible in the Last Version, but will double Check, if i find time for that. I also dont really know, if this is just a Flaw of the Sensor itself, or if this is a software thing. Still way more organic looking than the Vertical Lines from the Last version, but if this could be improoved would sure be neat. Here is two DNGs in a .Zip, from me trying to reproduce this Banding.
.
#EDIT#: Forgot to put the Settings that this was shot at here: 35mm 2.8 Russian Lens, 12dB gain, 359° 1kfps
-
Been using it for a bit now, and i really miss the "Play" Button in the Playback Screen? Is there a specific reason, why it had been removed in this Version? The Play button was very nice Way to view/review footage or to just have a loop playing. Still works with the Forward / Backwards buttons, but is kind of annyoing to allways need to hold the Button down and so on. Would love to see this Play Button come back in future Revisions if possible. The File Browser /List Files option is Great though, finaly a way to check the Footage Without needing to have a PC right there.
-
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.
-
Thanks for the feedback so far, everyone. Below are a few replies to various items:
Thanks for this update!!
One question to calibrate the camera - is it necessary to use a lense cap in step 1 too?
It isn't necessary to cover the lens in Step 1, as the sensor is running in a bypass/test mode, so it doesn't do anything with the light coming in.
Been using it for a bit now, and i really miss the "Play" Button in the Playback Screen? Is there a specific reason, why it had been removed in this Version? The Play button was very nice Way to view/review footage or to just have a loop playing. Still works with the Forward / Backwards buttons, but is kind of annyoing to allways need to hold the Button down and so on. Would love to see this Play Button come back in future Revisions if possible. The File Browser /List Files option is Great though, finaly a way to check the Footage Without needing to have a PC right there.
This wasn't removed, but your default preferences were reset, which is why it was hidden again. It can be re-enabled by going into Util->Main, then checking the One-touch Playback option box.
Horizontal Banding: In cases where this occurs, it may help to black-cal a few times, especially after changing the shutter position. Will take a look, and have seen those sample DNGs, thanks Nikon.
Issues with 800x600: I've noticed this recently too, seems like changing the offset away from center moves the position of the vertical stripe. Also looking into it.
Lowered Dynamic Range: This is likely a side-effect of the sensor driver configuration. Some tweaks were made to the analog gain voltages to handle the vertical banding. Overall, we've been trying to work within the limitations of the sensor, and the tradeoff between the banding mitigation and light sensitivity hasn't been trivial. I'll keep an eye out for more info on this thread, as it is helpful in determining which areas still need improvement.
-
Thanks for the feedback so far, everyone. Below are a few replies to various items:
[...]
Been using it for a bit now, and i really miss the "Play" Button in the Playback Screen? Is there a specific reason, why it had been removed in this Version? The Play button was very nice Way to view/review footage or to just have a loop playing. Still works with the Forward / Backwards buttons, but is kind of annyoing to allways need to hold the Button down and so on. Would love to see this Play Button come back in future Revisions if possible. The File Browser /List Files option is Great though, finaly a way to check the Footage Without needing to have a PC right there.
This wasn't removed, but your default preferences were reset, which is why it was hidden again. It can be re-enabled by going into Util->Main, then checking the One-touch Playback option box.
Horizontal Banding: In cases where this occurs, it may help to black-cal a few times, especially after changing the shutter position. Will take a look, and have seen those sample DNGs, thanks Nikon.
Issues with 800x600: I've noticed this recently too, seems like changing the offset away from center moves the position of the vertical stripe. Also looking into it.
Lowered Dynamic Range: This is likely a side-effect of the sensor driver configuration. Some tweaks were made to the analog gain voltages to handle the vertical banding. Overall, we've been trying to work within the limitations of the sensor, and the tradeoff between the banding mitigation and light sensitivity hasn't been trivial. I'll keep an eye out for more info on this thread, as it is helpful in determining which areas still need improvement.
Thanks a lot, really glad, that Play button is still there :D .
.
About the Banding, just wanting to say, i have seen Some Situations, where it gets WAY worse than the DNGs i posted above, and i dont think Black Calibration helps with that, but will test to do that. I ordered myself a bunch of 32GB Micro SD-Cards to keep the 0.6.0 and an older Version as well as The unstable Build on them without needing to Reflash them all the Time when Changing Versions, so i can directly compare the thing about the Banding there. Hope i get around to test it soon.
-
Given the Fact, that the 0.6.0 now can generate Calibration files on its own, is it possible to export them and use them with other versions, like the latest Unstable Build?
-
I also noticed some Horizontal "Banding" (or whatever one would call that?) when Overexposed Areas are In Frame right next to dark areas. Dont remember them to be this visible in the Last Version, but will double Check, if i find time for that. I also dont really know, if this is just a Flaw of the Sensor itself, or if this is a software thing. Still way more organic looking than the Vertical Lines from the Last version, but if this could be improoved would sure be neat. Here is two DNGs in a .Zip, from me trying to reproduce this Banding.
.
#EDIT#: Forgot to put the Settings that this was shot at here: 35mm 2.8 Russian Lens, 12dB gain, 359° 1kfps
So i tried to reproduce the Banding in the 0.5.037 Unstable Build, and i CAN still see it there in some Extreme Lighting Situations, but it is WAY less obvious to even Barely noticeable depending on what else is in frame. In fact, i didnt even really notice it was there bevore this new 0.6.0 Software really. In the New software however, most extreme i seen was about 1/3 of the Whole Area of Frame Blacking out (Areas Horizontally next to Large Overexposed Area in an overally pretty dark overall frame) Completely. On the Older Software it at worst just affects Brightness Value of the Whole Horizontal Area next to Over Exposed areas a tiny bit, which is mostly hard to notice, unless you are Specifically looking for it; Most visible on the Older Versions are the "Edges" of Square Overexposed Areas/ the Horizontal Lines that Produces at the Edges (those are still very faint tho). Will Upload some Kind of Comparison, if i manage to get a good recording of that.
.
The whole thing reminds me a lot of the Vertical Smear Phenomenon of old CCD-Sensor Cameras somehow. There Was Some really good full Article about it, what is going on and why, sometime ago; but i cant find it, best thing i found about it rn is this Publication on Page 4, where they talk about it a little bit:
.
https://www.researchgate.net/publication/315944464_Stroboscope_Based_Synchronization_of_Full_Frame_CCD_Sensors
-
I also noticed some Horizontal "Banding" (or whatever one would call that?) when Overexposed Areas are In Frame right next to dark areas. Dont remember them to be this visible in the Last Version, but will double Check, if i find time for that. I also dont really know, if this is just a Flaw of the Sensor itself, or if this is a software thing. Still way more organic looking than the Vertical Lines from the Last version, but if this could be improoved would sure be neat. Here is two DNGs in a .Zip, from me trying to reproduce this Banding.
.
#EDIT#: Forgot to put the Settings that this was shot at here: 35mm 2.8 Russian Lens, 12dB gain, 359° 1kfps
I can confirm this. In addition, i made another observation - if the white areas decline at 50 IRE it looks like they get pink....
-
Managed to finally set up three MicroSD´s to test all the Versions. Here is a Test for banding at 250fps, 360°, 0+0 dB Gain; 15mm @ f/0,9 with the Camera well warmed up.
.
Software Version 0.5.1 (This file was Run through AE CS6 to compress it from 108MB down to now just 46MB, apart from the Bitrate untouched Footage):
-
And here another one from the New 0.6.0 (also untouched, straight from the Camera):
.
all Three where shot at exactly the same settings with Whitebalance set to the 4600K Preset (Lamp beeing 4000K Color). I did pan not quite at the same Speed every time, so they show different amounts of Motion blur and Ghosting (yes, Ghosting is visible on all Three Software Versions, seems about unchanged across them, might could cause problems for More Technical / Research kind of applications i assume), but should give a pretty good idea of how visible the Banding can be. Didnt quite manage to record some of the more Extreme Light setting with this yet, but it clearly shows here. As Light and Camera/ Lens Settings are unchanged, this test also confirmes, that there is indeed quite a noticeable difference in Light Sensitivity with the New Software compared to recent versions. the Unstable Build is ever so slightly more sensitive than the Stable 0.5.1 Build from what i can tell, and the 0.6.0 Version is quite a bit darker, like half a Stop of Light or so, or even more. Also Highlights tend to be more Pink when Overexposed, as Bian allready said.
.
#EDIT#: Did also shoot the Same thing with the 0.5.037 Unstable Version, but couldnt upload all Three, because Space on the Server was full or something, got an Error Message when trying to upload. So i just uploaded the old and the New Version, as the Unstable and Stable 0.5.xxx Versions looked about the same.
-
After my limited testing, it is clear the banding has been reduced a whole lot. It will still show up in the shadows and under exposed areas severely (Shows up as red and cyan vertical bands in shadows mostly). However, given enough light and taking care to overexpose a bit it is fairly well reduced. I was able to get Topaz Video Enhance AI to almost completely eliminate the shadow vertical banding after processing which really saved the day.
I can't attest to the DR loss since I went straight to v6 for my testing but it will be good to try to preserve more of it. All in all very stable release, no issues with saving multiple clips for about 4hrs. I was also pleasantly surprised by the good quality h.264 output with lots of detail from the 2.1 camera which is in my view an order of magnitude better than what the 1.4 was able to achieve. Of course, shooting DNG RAW remains unmatched. ;D
-
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
(http://vergleich.jpg)
In my opinion the 1.4 picture looks well - the 2.1 picture is very flat....
-
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
-
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?)
-
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.
-
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
-
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/ (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.
-
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.