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 hangs

Jeremy Morrison

Active member
Joined
Sep 10, 2008
Messages
30
Reaction score
0
Points
0
I'm really hoping someone might be able to shed some light on a reoccurring issue I've been having with Redrushes. We've just wrapped week one on a feature and each night I've been running the R3D files through Redrushes to create the ProRes files I'll be editing with later. On average, I've been attempting to batch about 45 - 50 clips for the day.

Unfortunately, Redrushes seems to hang before finishing. Sometimes it's after the first hour or so of crunching away or sometimes when it's on the last few clips. There doesn't seem to be any consistency on when it decides to screech to a halt.

I just purchased a brand new MacPro Quad (18gb, 2.5tb internal drive space) last week to handle this workflow. I've disconnected all external drives before running Redrushes to rule out any interference from them but without any luck.

Does anyone have any ideas on what might be causing this problem? Are there log files somewhere that might provide a hint?

Any help on this would be very much appreciated since, at this time, it takes me several attempts to get a full batch of clips to complete.
 
Any clips that generated a record error in camera (and which will have a green QT reference file screen) will crash Red Rushes. When it crashes check the first unrendered clip in the list. Uusally this is the one to stall the render engine. Remove the offending clip and try again.

Regards
Jeff Brown
RED 708 "Ruby"
 
Hey Jeff, thanks for the reply.

Unfortunately the hang up of Redrushes does not appear to be due to a bad clip. In fact, just to explain a little bit more clearly, I can get all the clips to process through Redrushes, it just takes several batch sessions wherein I restart the machine (for good measure), load in the remaining clips that did not complete all the way or start at all, and process again.

Any other thoughts?
 
Hey Jeff, thanks for the reply.

Unfortunately the hang up of Redrushes does not appear to be due to a bad clip. In fact, just to explain a little bit more clearly, I can get all the clips to process through Redrushes, it just takes several batch sessions wherein I restart the machine (for good measure), load in the remaining clips that did not complete all the way or start at all, and process again.

Any other thoughts?

What version of the OS are you running?
 
Hi Deanan, thanks for the reply. I just purchased this MacPro Quad last week and have run all the software updates. I am running OSX 10.5.4.

Also, just to let you know, we are shooting 4k 16:9 and in Redrushes I am using the Half Debayer (Full or High Quality) and resizing to 1080p ProRes files.

Any thoughts?
 
Hi Deanan, thanks for the reply. I just purchased this MacPro Quad last week and have run all the software updates. I am running OSX 10.5.4.

Also, just to let you know, we are shooting 4k 16:9 and in Redrushes I am using the Half Debayer (Full or High Quality) and resizing to 1080p ProRes files.

Any thoughts?

Are you using version 3.5.0?

How long are your clips?

I've done tests with 100s of clips going for a few days and not seen any problems.
 
Deanan,

I'm not at that machine now so I can't check but I downloaded and installed Redrushes last week so if 3.5.0 was the version available then, I am using it.

Most clips are under 1 minute.

I suppose my only solution is to install OSX fresh onto one of my other internal drives, and only install Redrushes under that, then run some tests. If it works, the problem is software related on my end. If it doesn't work, then I guess it's a hardware issue.

Are there any sort of Redrushes or System log files that might narrow down the specific problem?
 
You might also want to try deleteing REDline and REDrushes manually and reinstalling. (REDline is in /usr/sbin)

Another option could be to output a script and run the script in the shell.
 
Crashes here to

Crashes here to

Hi all we are seeing the same experience on 3 different mac,
running the latest os update. and the lates redrushes,
and it is a pain since one normally set it of for rendering over night. and then it is crashed in the morening, or hanging.

is there a fixe for this, i am very shure it is not hardware related. can reproduce this on 3 - 4 machines...

Lars
 
Hi all we are seeing the same experience on 3 different mac,
running the latest os update. and the lates redrushes,
and it is a pain since one normally set it of for rendering over night. and then it is crashed in the morening, or hanging.

is there a fixe for this, i am very shure it is not hardware related. can reproduce this on 3 - 4 machines...

Lars

Hmmm, quite a bit puzzling because I know others are running overnight renders no problem with RR and I've run it for two days with no problems.

Can you verify that both versions are the latest by looking at the version number in RR and the version when you type REDline in terminal. There's a small chance it didn't get installed properly.

Also, how many clips are you generally running?
What type of machine?
How much ram?
What OS version?

Thanks.
 
It is 3.5 the latest version. is there anyway one can select lets say 20 lines and only execute the selected items, have just seen that it is hung again overnight.
 
can you also answer me some question about if one use the hi res, half option extracting out to dpx frames. whith fith turned on. will this extract a clean 2 k image without resizing.
 
What happens to the processor usage when it stops?

Does the activity monitor show any REDline processes running
that aren't using any cpu?
 
can you also answer me some question about if one use the hi res, half option extracting out to dpx frames. whith fith turned on. will this extract a clean 2 k image without resizing.

"whith fith" ?

half high will get you a very clean 2k image which is close to doing a 4k with a scale down.

half normal is a faster render that is more aliasy but perceptually sharper than half high.
 
Hey Deanan,

Ok, we just wrapped week 2 of our 5 week feature shoot and Redrushes is still hanging on me when I batch process the days shots. Here is what I am running:

Brand new MacPro Dual Quad 3.2GHz
Mac OS X 10.5.4
3 internal drives, 500mb, 1tb and 1tb
18 GB RAM
Redrushes version 3.50 (1)

Here is what I have tried:

1. As you suggested, deleting Redrushes and Redline manually and reinstalling. I thought this fixed this issue because the next batch I did after that (about 40 clips) went through without a hitch. But the following batch hung.

2. Reinstalled OS X on another one of my internal drives and ONLY installed Red Alert, Redcine, Red Codec for Quicktime and Final Cut Studio 2. No luck. The last 2 batches I have run both froze during the first 6 clips or so it was processing

One thing that is interesting. After Redrushes hangs, I will quit the app (no need to force quit or anything), and if I attempt to access the drive Redrushes was reading / writing to, the OS will pinwheel forever. I thought this might be an indication of a bad drive but it seems to happen no matter what drive I use.

Any additional suggestions? As our shoot continues, I'm really starting to get behind processing these clips.
 
Do you have any spaces in the drivenames and/or foldernames?

e.g.:
"/redproject/card 1"

If so, please change them to underscores:
"/redproject/card_1"

and avoid any kind of other "funny" characters.

This fixed an issue with redline for me. (I also completely reinstalled the system and appz and upgraded to latest OS/QT, but that did not help.)
 
The drive name and the folder name I copy all the r3d data to, do infact have spaces. I'll change these before I try another batch tonight. Thanks for the tip.
 
Is it possible that the energy saver or screen saver is stopping RED Rushes?

Deanan-We have had incredibly long render times, but I think it is stopping every time a screen saver kicks on. Is this possible?
 
Back
Top