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

REDrushes crashes with ProRes export

Nick Meyer

Member
Joined
Feb 6, 2009
Messages
10
Reaction score
0
Points
0
Hi everyone,

did anyone experience REDrushes crashing after a couple of files when exporting to ProRes 422 files? It usually happens after like 20 files.

I tried several other export options (DVCpro HD, MJPEGA, ...) with no crashes - even after 40 or more files.

Is this a known bug somehow? What else could I use to export my r3d-files over night in a batch?

Cheers

Nick
 
Maybe a workaround: Is there any way to change the size of the transcoded files in Final Cut Pro when I use "log & transfer". So that Log & Transfer doesn't create 4K ProRes Files, but maybe 1280x720 files?
 
I personally haven't experienced that and I have RedRushes batch processing regularly on two systems. What are your system specs, OS version, QT version, what type of volume are you writing to, etc..
 
Hey.

2x 3.2 Ghz Quad Core, Mac Os 10.5.6, QT 7.6...I'm writing to the same drive (software raid-drive) where my r3d-files are located.
 
How many clips are you trying to do in 1 single batch,
how do you have your settings set up number of clips at 1 time and processors.

I have had problems when i do to many clips i try to keep it under 80 clips in 1 single batch.
 
Seems that rendering to a different drive where my r3d-files are NOT located is the solution. So far no crashes...
 
Should be faster too…
 
Seems that rendering to a different drive where my r3d-files are NOT located is the solution. So far no crashes...

...not!

:angry01:

Tried to render over night on a different drive...in the morning my Mac welcomed me with a crash report. Really have no idea what else to do.
 
The next "funny" thing: I'm doing another (maybe the hundreth :blink: ) test of converting with REDrushes and right now the batch looks like frozen. By accident I clicked on the RED logo in REDrushes and then the batch refreshes to the actual status. REDrushes and me don not really make a good team.
 
Are you sure you don't have some bad RAM in your machine? RR is using it to it's full extent.

What's happening to you looks so unpredictable, and RR is working well here…
 
Uli,

maybe you got a point there. I'm gonna test my RAM with Memtest now.

Thank you so far.
 
Which Memtest? Apple's is not very capable, try the one in Applejack.
Or take some RAM out in pairs.
 
Memtest showed no errors. Still don't know what causes the crashes of REDrushes.
 
Back
Top