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 1.8.3 record error after booting between RED RAW and ProRES

B

Brian Timmons

Well-known member
Joined
Apr 29, 2007
Messages
1,553
Reaction score
331
Points
83
Location
NJ
Website
www.britim-media.com
I'm already in contact with RED but seeing if others experienced this issue.

Was on a recent shoot for a client that requires me to boot back and forth between RED RAW to ProRES.

After the camera initially shot several clips in RED RAW I had to boot into ProRES and started getting
"Hardware Error 105" and a "Record Error" screen.

After several of these errors I shutdown the camera, pulled the battery, let it sit for a minute, and also
changed the CFast card. After rebooting my Komodo started to record normal again for several shots.

I again had to switch back to RED RAW where the errors started to occur again.

I eventually rolled the firmware back to the older 1.7.5 version where my Komodo worked like normal and finished the shoot day.

Back home, I reinstalled 1.8.3 but still encountered the issue.

I reached out to RED where they suggested a hardware reset which is part of the normal troubleshooting protocol.
Even after hard reseting I still get the issue.

It's odd because it seems to occur more when in ProRES mode and in RED RAW if it occurs it seems to clear
up after shutting down and letting it sit for a few minutes and booting back up.

Anyone else experience anything like this on the new 1.8.3 firmware?

Brian Timmons
BRITIM/MEDIA
 
Last edited:
Am I right that you're shooting ProRes 2k?

When I boot ProRes with that, I get the error very reliably on all cams, but not when I either boot to 4k right away if this was set before or toggle from 2k to 4k and back before shooting. So, it looks like an initialization problem during boot, not a real or fake "hardware error".
 
Alex Zeder said:
Am I right that you're shooting ProRes 2k?

When I boot ProRes with that, I get the error very reliably on all cams, but not when I either boot to 4k right away if this was set before or toggle from 2k to 4k and back before shooting. So, it looks like an initialization problem during boot, not a real or fake "hardware error".
Click to expand...

Thanks for checking and passing this along Alex. This helps a bit.
Yes I was booting into ProRes 2K and that's the mode that I seem to experience the issue the most in.
I have seen the hardware error when in RED RAW but that seemed to always occur after initially experiencing the issue in ProRes.
The problem also seems to go away in RED RAW but is more persistent in ProRes.

I will follow up with RED tech support and include your notes.

You mentioned multiple cameras in your post. Curious how many Komodos you experienced the issue occurring.
Thank again for your response.

Brian Timmons
BRITIM/MEDIA
 
Last edited:
Brian Timmons said:
You mentioned multiple cameras in your post. Curious how many Komodos you experienced the issue occurring.
Click to expand...
At first I tested it with one and didn't have any problem, so I tried another one and it showed the error. The third one again did not... and I ended up with five and all using different cards some of which were in the drawer for weeks, batteries/power plugged, lens cap shots with nothing else attached, until I recognized the pattern with 2k vs. 4k. But after I switched them to 2k, all five showed the same error very reliably.
 
Alex Zeder said:
At first I tested it with one and didn't have any problem, so I tried another one and it showed the error. The third one again did not... and I ended up with five and all using different cards some of which were in the drawer for weeks, batteries/power plugged, lens cap shots with nothing else attached, until I recognized the pattern with 2k vs. 4k. But after I switched them to 2k, all five showed the same error very reliably.
Click to expand...

Again, this is very helpful and thanks.
I have a 2nd Komodo but held off on installing 1.8.3 until I knew it was solid.
Your post helps a bit in showing a pattern across multiple cameras.
Log files with the error were already sent to RED but they seemed to want more info regarding the conditions that created the issue.
This info should help a bit in troubleshooting.

I have a shoot tomorrow with both cams and will unfortunately have to downgrade back to 1.7.5 (will miss user pages and horizon line.).

Will follow up on this.

Brian Timmons
BRITIM/MEDIA
 
To follow up with an update, RED wanted me to send my camera in for evaluation.

My camera has been filming fine after downgrading to 1.7.5 and is tied up with current and upcoming shoots.

I told RED support that I'll consider sending it in once I get through this leg of filming but asked that they
still take a look at the latest 1.8.3 firmware.

If anyone else experiences hardware 105 issues record issues (specifically in 2K ProRES) please report here.

Brian Timmons
BRITIM/MEDIA
 
I wonder whether anyone has a Komodo that does NOT run into this error with these steps?

1. Prepare ProRes settings:
2. Set Sensor Format to 6k 17:9 (lower res might not error).
3. Set Resolution to 2k / 422 HQ (no error with 4k).
4. Switch to R3D
5. Switch back to ProRes
6. Hit Record
 
I've been testing this issue after installing the latest Komodo beta firmware 1.8.4.

KOMODO FIRMWARE (Beta) VERSION 1.8.4beta (5/15/2025)

https://www.red.com/download/komodo-firmware-beta SIGNIFICANT CHANGES SINCE BUILD 1.8.3 Improved lens compatibility Fixed GIO Scope behavior Fixed Apple ProRes resolution switching after Playback
reduser.net

The issue with the error is seemingly fixed with one lingering problem.

The record error can be reproduced when booting (or re-booting) directly into HD ProRes
but if I just switch to UHD in the menu and switch back to HD ProRes the record errors
seem to consistently go away and the records look fine.

If I shut down the Komodo or reboot into R3D and back into HD ProRes sometimes the
record is fine with no issue and it remains this way until the next re-boot.

Other times I might initially get the error message but again if I go into the menu and briefly
switch to UHD then back to HD the recording is fine again with no error message.

RED has made a bit of progress with fixing the issue (where it occurs less and there is sort of a fix)
but the fix is still not functionally consistent or within expected operation.
While I seem to be able to get HD ProRes to record without the errors I have to perform
an odd ritual of toggling the ProRes resolution setting HD to UHD and back to HD for the HD ProRes
to record with no errors.

Frustrating.

Will send an update email to RED.
If anyone else still experiences this issue please send a message to RED support
as they do not seem to read this board.

Will update more if I observe more.

Brian Timmons
BRITIM/MEDIA
 
Confirmed, it only happens when you boot right into 2k ProRes (#3 in my steps above) and have it at full sensor resolution, no longer after switching to anything else. While that is a work around. it's still annoying if you forget to perform this extra dance. And not very impressive if I have to explain this when I hand the cam over to someone else.
 
Thanks for the checking and confirming Alex.
You seem to have very good observational skills and it brings some relief when you bring
needed analysis to a given situation.
Yes- this is an annoying issue RED seems close to solving but there are a few more things
that have to get worked out in the code.

Will send them an update shortly.

Brian Timmons
BRITIM/MEDIA
 
As you said, 1.8.4beta at least improved it because I don't get the error most of time now. Not sure whether it's the timing after the reboot until you hit record or anything else plus cosmic rays entering from the side, but will test this out a bit more.
 
Last edited:
Yes it actually seems pretty usable though the workaround is not quite so elegant for a cinema camera much less a RED.
I have to test more myself. I only have a few clients that press filming in ProRes but I originally encountered this problem on
a gig and tech issues like that are never fun.

I am thankful though that RED is staying on top of these bugs and still working on Komodo.
It's been a while that firmware is developed at this pace.

Brian Timmons
BRITIM/MEDIA
 
Last edited:
Another difference to 1.8.3 is that I only get the "ERROR - Record error" message now and can continue after pressing OK but no more Error: 105 "A possible hardware error was detected" which requires a reboot. Did you get this 105 still?
 
Alex Zeder said:
Another difference to 1.8.3 is that I only get the "ERROR - Record error" message now and can continue after pressing OK but no more Error: 105 "A possible hardware error was detected" which requires a reboot. Did you get this 105 still?
Click to expand...

Actually I was able to get the error 105 screen if I kept trying to record in HD Prores without toggling to UHD.
It took something like 4-5 times trying to record after the initial "ERROR-Record error" screen for the error 105 screen to come up.

After rebooting and toggling the HD/UHD setting it still seemed to work fine in HD ProRes.
I'm going to test more over the weekend to come to stronger conclusions.

I wish I picked up on this issue during the earlier betas released late last year/early this year.

Brian Timmons
BRITIM/MEDIA
 
I can answer my own question: I just got this Error: 105 now after the "Record error". Log file saved.
 
Even at the risk that the audience here is already bored, some more facts about the error test results:
  • Nothing connected besides batteries and/or plugged in (lens cap shots)
  • Cards used:
    Angelbird 1 TB
    Sandisk 256 GB
  • Cards formatted in camera
  • Camera factory resetted and fresh calibrated

Sequence of four "Record error" followed by a finalizing 105:
https://alexzeder.net/k184/
 
Alex Zeder said:
Even at the risk that the audience here is already bored, some more facts about the error test results:
  • Nothing connected besides batteries and/or plugged in (lens cap shots)
  • Cards used:
    Angelbird 1 TB
    Sandisk 256 GB
  • Cards formatted in camera
  • Camera factory resetted and fresh calibrated

Sequence of four "Record error" followed by a finalizing 105:
https://alexzeder.net/k184/
Click to expand...

The summation and video are excellent Alex.
It clearly shows the sequence of reproducing the problem.
TBH, the video alone saves a lot of typing.
Have you sent this ti RED?

Brian Timmons
BRITIM/MEDIA
 
Not yet, I too want to get more details and a clearer picture over the weekend before I open the ticket. For example, just once so far I got an error 107 instead of 105, so there is probably more to discover... where is error 106?? :)
 
Alex Zeder said:
Not yet, I too want to get more details and a clearer picture over the weekend before I open the ticket. For example, just once so far I got an error 107 instead of 105, so there is probably more to discover... where is error 106?? :)
Click to expand...

I never saw an error code 107. It's hard to tell what circumstance a particular error code can be triggered.

Brian Timmons
BRITIM/MEDIA
 
You must log in or register to reply here.
Back
Top