Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Komodo firmware 1.8.3 record error after booting between RED RAW and ProRES

Last edited:
A few more results from today, I got the error with
- all sensor formats except 6k 2:1, 6k 2.4:1 and 2k 17:9
- more likely with higher frame rates but no error with 4 fps in 10 tests
- with both ProRes 422 and 422 HQ
- error condition persists even with power unplugged during reboot
- the error can appear not only after switching from R3D to ProRes, but also after rebooting ProRes several times as long as I made no changes to the project settings
 
A few more results from today, I got the error with
- all sensor formats except 6k 2:1, 6k 2.4:1 and 2k 17:9
- more likely with higher frame rates but no error with 4 fps in 10 tests
- with both ProRes 422 and 422 HQ
- error condition persists even with power unplugged during reboot
- the error can appear not only after switching from R3D to ProRes, but also after rebooting ProRes several times as long as I made no changes to the project settings

Great tests Alex.
Just to be clear, were the errors strictly in ProRes mode or did you get some errors while in R3D as well?
Also, were you able to produce errors in UHD/4K ProRes at all?

So far my errors seem to still be strictly in 2K/HD ProRes though I admittedly have not tested across sensor formats and frame rates the way you have.

Brian Timmons
BRITIM/MEDIA
 
Only in ProRes 2k, not in 4k nor anthying in R3D. I guess it's time for a ticket before I run out of disk space with all the log files...
 
Only in ProRes 2k, not in 4k nor anthying in R3D. I guess it's time for a ticket before I run out of disk space with all the log files...

Ok- that’s actually good to hear.
Yes I can imagine the amount log files that generated and the time it took to generate them.

I’m leaning on this being a coding issue but of course have to keep all possibilities open.

Brian Timmons
BRITIM/MEDIA
 
Back
Top