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,409
Reaction score
246
Points
63
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
 
You must log in or register to reply here.
Back
Top