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

Red Rushes Crashes New 2.26ghz MacPro

J

joe hedge

Well-known member
Joined
Mar 19, 2009
Messages
604
Reaction score
0
Points
0
Location
Burbank, Ca
On a just-out-of-box today 2.26ghz 8-Core with stock 6gig RAM config, RedRushes crashes machine less than one minute into render. Have RR set to Half-res standard, color space rec709, scale to 2048, ProRes 422HQ, coming from and outputting to separate eSata drives, R3D's are 4k 2:1.

Have tried configuring the Settings menu to both 1 and 2 clips at once and 3, 4, and 8 cores per clip...same results, machine goes crash. Also tried coming from and rendering to internal drive, same result. Any ideas? Thanks
 
The best idea I can offer is to download Clipfinder and use it instead. RedRushes has consistently been unreliable on long renders. Clipfinder hasn't crashed once.
 
Thanks, meanwhile I just found out the sata card they sold me, Sonnet Tempo Sata E2P, is incompatible with the new Mac Pro's...switching to FW800 now...
 
joe hedge said:
On a just-out-of-box today 2.26ghz 8-Core with stock 6gig RAM config, RedRushes crashes machine less than one minute into render. Have RR set to Half-res standard, color space rec709, scale to 2048, ProRes 422HQ, coming from and outputting to separate eSata drives, R3D's are 4k 2:1.

Have tried configuring the Settings menu to both 1 and 2 clips at once and 3, 4, and 8 cores per clip...same results, machine goes crash. Also tried coming from and rendering to internal drive, same result. Any ideas? Thanks
Click to expand...

Joe,

did you find a solution or what was causing this?
I got a new MacPro just like yours today and experiencing the same issues.
I know that Redrushes is not the most stable piece of software, but this is really weird...

Best,
Fredrik
 
I must recommend to follow editblog's tip to use Clipfinder.
Such a nice app. And a lot more stable. I will definitely donate some $$ to Hans-Georg Daun, this is just so much better than Redrushes.
 
second that

second that

Just flipped my workflow from Red Rushes (crashed randomly as well) to clipfinder. Genius app. I just wish I had a little more control over how many cores it uses...

Early 2009, 2.26 octo, btw.
 
Patrick,

There is a parameter in REDline that supposedly controls how many cores to use per render task and I have tried to use that, but it does not seem to have any effect.
Same thing for the "cores per clip" setting in REDrushes.
It looks like there is nothing I can do at the moment.

Cheers,
Hans
 
Hey, thanks for the reply.

Yeah, I found that the only way to max the cores was to let it do 4 concurrent files, or jobs at the same time. I know that the R3D Datamanager, so far, is the only tool that allows you to specify up to 32 cores, and it seems to actually do it. It pushes all 16 (virtual included) to max on one file.

Clipfinder is great though, the red rushes crashing bug was driving me crazy. I love that it actually uses the ram available too, usually one gig per file it works on.

Great app, I'm a huge fan.

-Patrick.
 
ReMaster allows multiple clips and the CineForm decoder will also use up to 32 cores. You still need to process multiple clips to convert from R3D in ReMaster since the decode from the R3D files does not take advantage of multiple cores.
 
You must log in or register to reply here.
Back
Top