Welcome to our community

Be a part of something great, join today!

Register Log in
  • 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 (Beta) VERSION 1.8.5 beta (7/24/2025) & 1.8.6 Release version

Do anyone know if the FPS in the metadata of the Komodo-X has been fixed (when shooting 80fps in a 25p project it indicates 25fps).

Thanks

Patrick
 
I shot for a few hrs on v1.8.6 and no black screens or other errors so far. Booted between r3d and ProRes and seems OK, too
 
Steve Sherrick said:
@Brian Timmons The GIO Scope behavior issue. I must have missed that in the past. What was fixed? Thinking I might bump up to 1.8.6 if it seems stable.
Click to expand...

Sorry Steve I missed this message.
I have to check the GIO scope issue but I have a feeling it remains the same in the update.

Brian Timmons
BRITIM/MEDIA
 
Last edited:
Ugh. Just commented on that thread. Considering rolling back to 1.8.3. How do you send a bug report to Red? I was only able to start a service request last time…
 
An update... I encountered the issue again and updated the menu toggle work around from my original post.
It should be MENU> IMAGE/LUT > OUTPUT COLOR SPACE> and toggled between DCI-P3/REC709/REC2020/REDWideGamutRGB

Despite encountering the black screen, toggling the Output Color Space settings once again bought the image back.

I tried recreating the issue with various reboots from different User setting profiles I have but could not get the black screen again.

I think this is a somewhat rare phenomena that is hard to consistently reproduce.
I do remember going from ProRes 422 UHD to a 2K 120fps R3D setting I have when it happened but I could not reproduce the black screen again with those same settings.

Considering there is a quick work around and that everything else on this build is stable, I still plan to use 1.8.6.

Unfortunately I forgot to generate another log file when the black screen occurred.

Brian Timmons
BRITIM/MEDIA
 
scorsesefan said:
Thanks for your work on this issue, Brian. Odd that even with your input Red hasn’t been able to rectify the issue…
Click to expand...

The Komodo firmware updates are in much better place than 3 months ago so there is progress.

Not sure if there were under the hood changes or perhaps changes to the firmware team that is at the heart of some of
these recent issues but at least they are getting fixed. I'm trying to stay on top of these bugs as I really want to avoid dealing with
this stuff in the middle of a shoot. Opens the door to FUD and other shenanigans that have nothing to do with filmmaking.

I do think that RED might consider having a more official presence on some of these RED user forums and discussion groups.
In the past there was extremely excellent representation from RED. In fact, perhaps the best I've seen considering the owner of the company and President would be on here regularly.

Of course life changes but it would be good if at least a few tech associates at RED scoured these groups for potential issues in addition to users submitting tech support inquiries. It seems like RED is in the usual corporate bubble and that seems to slow things down a bit when addressing these type of bugs.

Brian Timmons
BRITIM/MEDIA
 
Last edited:
Brian Timmons said:
The Komodo firmware updates are in much better place than 3 months ago so there is progress.

Not sure if there were under the hood changes or perhaps changes to the firmware team that is at the heart of some of
these recent issues but at least they are getting fixed. I'm trying to stay on top of these bugs as I really want to avoid dealing with
this stuff in the middle of a shoot. Opens the door FUD and other shenanigans that have nothing to do with filmmaking.

I do think that RED might consider having a more official presence on some of these RED user forums and discussion groups.
In the past there was extremely excellent representation from RED. In fact, perhaps the best I've seen considering the owner of the company and President would be on here regularly.

Of course life changes but it would be good if at least a few tech associates at RED scoured these groups for potential issues in addition to users submitting tech support inquiries. It seems like RED is in the usual corporate bubble and that seems to slow things down a bit when addressing these type of bugs.

Brian Timmons
BRITIM/MEDIA
Click to expand...
Yeah, I think this is one of the consequences of a boutique camera company being bought by a major multinational. Although I did find Red support to be very responsive and far more helpful than Canon, with whom dealing with is a nightmare... Yes, I recall Jared being a presence here and on dvxuser...
 
Well, first hiccup for me. "Unapproved battery warning" even though I'm using Canon OEM 955s. Removed battery and camera shut down even though there was another battery in the second slot. Contacted Red and sent a bug report.
 
Last edited:
RED is aware of the black screen in live view issue and was able to reproduce it on their end.

I also found another bug where the scrolling in 1:1 magnification does not seem to work on the Top LCD.

I did manage to find a workaround where just opening up RED Control seems to activate the scrolling in 1:1 magnification on the Top LCD.

I sent a support ticket to RED about this latest bug so hopefully it will also get addressed soon.

RED mentioned to continue sending these tech support inquiries to them so they can make sure the problems are related and not different issues that might look similar.

Brian Timmons
BRITIM/MEDIA
 
Last edited:
Installed 1.8.6 and encountered black screen. External monitor showed correctly. Reboot returned to normal op.
 
You must log in or register to reply here.
Back
Top