Red Rushes Problem: not starting render

[Dan Carew]

I'm having a problem with RedRushes:

Details:
I shot test footage with Build 16 (production build). Using RedAlert 3.50.

I add my R3D clip(s) to RedRushes but when I try to render by hitting the RedRushes "Start" button, the blue "progress" bar zips to the right, but the actual progress (in the "Progress" column) remains stuck at 0%. (screenshot below). Nothing happens, even after a long wait.

I'm trying to render out to ProRes422HQ 1920x1080, but this problem happens no matter what my settings are. I have no problem outputting the same file to ProRes422HQ 1920x1080 using RedAlert. I've tried uninstalling RedAlert, RedRushes and deleting Redline, then re-installing RedAlert--but this doesn't help. I have a relatively new 2.6GHz MacBook Pro with Intel chip with 4Gb RAM, running latest version of Leopard (OSX 10.5.5). I've used RedRushes many times successfully in the past (but not sure if I've used it since I upgraded to RedAlert 3.50 last week).

Has anybody seen this? Anybody have any ideas? Thanks!

 

[Deanan]

Can you export a script from red rushes and email it to me?
(d e a n a n - a t - r e d)

 

[Dan Carew]

Thanks a lot for your speedy reply, Deanan. I've just sent you the RedRushes script, as requested.
cheers,
Dan

 

[Dan Carew]

For everyone else's information: Deanan just gave me the solution to my problem. (Thanks Deanan!)

You cannot have the character "&"(ampersand) in the name of of the folder in which your R3D clip resides (and, I think, also can't have "&" in the name of any of the folders, all the way back to the root directory, in which that folder resides).

 

[Deanan]

For everyone else's information: Deanan just gave me the solution to my problem. (Thanks Deanan!)

You cannot have the character "&"(ampersand) in the name of of the folder in which your R3D clip resides (and, I think, also can't have "&" in the name of any of the folders, all the way back to the root directory, in which that folder resides).

Yeah, non alphanumeric characters can cause problems. It's generally safest to stick to alphanumeric and underscores.