Welcome to our community

Be a part of something great, join today!

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 :)

Prores Proxy Buffer Overflow

J

Joel Voelker

Well-known member
Joined
Nov 9, 2013
Messages
1,015
Reaction score
0
Points
36
Location
U.S. of A.
Had this error last week. Camera was recording, recording stopped, error popped up, second message said camera was going to shut itself off. Powered back up and all was fine but this makes me nervous. I'm submitting a log file to RED but curious if anyone has had similar.
 
The new firmware still hasn't fixed this problem for me. It's scarey when it happens, camera is unresponsive and you have to basically have to do a hard restart (with the camera complaining about improper shutting off when it comes back) I just had this error twice yesterday during a shoot and I'm currently at 6.3.78.
 

Attachments

  • image1.jpg
    image1.jpg
    43.8 KB · Views: 0
The solution is to format the card as UDF
I had this issue before, it's a firmware issue where the file corrupts on a FAT32 formatted (default) SSD mag. It's corrupting right when it's writing to the next file, you'll notice that you recorded the maximum amount of 31.9GB, and then you'll see the corrupt file on the next one. That's when I realized it's a writing issue with the FAT32. So if you updated to the latest beta firmware and you record 2K ProRes, you will inevitably get this error if you left the card as FAT32. RED tech is aware and currently working on the issue
 
This issue happenedto me llast week, I lost footage of a live event and lost a client as a result. Why isn’t every single owner notified of this fault... stupidly unprofessional of RED.
 
Has this been properly fixed yet? I had this happen during a live event recording with my Raven on a 120 mag.

Even formatting the card as UDF didn't save me - it recorded for a far longer period of time (about 45-50 minutes) before crapping out. Any further attempts to record on the same mag without formatting quickly resulted in more corrupt files. Fortunately the event was a performance with several runs during the week so I didn't lose the client. I just had one less show to have on hand. Still, it was disconcerting since I wanted to use ProRes for quick client work that didn't require the full power of .R3D files.

I chalk it up to ProRes being finicky. The .R3D recordings were fine by comparison. I'll have to do more tests to see if I can figure out why it fails even on UDF-formatted mags.
 
You must log in or register to reply here.
Back
Top