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

RELEASED: BETA REDAlert! (v3.4.2)

Hey guys,

Same error here.. I've tried every checkbox and codec, plus DPX/TIFF output instead of QT..

Latest QT codec and RedAlert .. on new Mac Pro

Same software versions work fine on my Macbook Pro.

Weird..
 
Yup.. B16 v3.2.5

Rendering out of Redcine on a 8-Core, 16GB RAM Mac Pro to 1080P Prores instead right now .. 1.5 hours wants to take 42 hours to transcode..

Aiiiiirrggg.. .I love you so dearly RED but I'm crying on the inside
 
One more note ..

Redline doesn't work for me when I try 'render in command line' from RedAlert!.

I get an error like "error: resolution must be 1 or 2" .. or something similar (not at the machine right now). I'm assuming this is casing the problem with RedRushes?
 
If only PRORES wasn't mac only, I'd be able to use our SCRATCH to render out the rushes. Instead I spent 8 hours trying to work around this issue this evening only to end up wishing that I'd started that 42hour Redcine render 8 hours ago..

drat.. oh well :wink:
 
Seth Larney said:
Yup..

Rendering out of Redcine on a 8-Core, 16GB RAM Mac Pro to 1080P Prores instead right now .. 1.5 hours wants to take 42 hours to transcode..

Aiiiiirrggg.. .I love you so dearly RED but I'm crying on the inside
Click to expand...

Sounds like you're using Full debayer and also not setting the display to Full High. Three questions:
1. Am I correct?
2. Assuming I might be, do you **really** feel you need Full debayer for 1080 output?
3. If you have the display at anything other than full and you're using Full debayer, change the screen display to Full. You should find a dramatic increase in render speed. Note: This also holds true for Standard (set to Half High) and draft (set to Quarter high). For the fastest good results on what you seem to be doing, try Standard debayer and Half High display. On an 8 proc Mac, this should reduce the render time to less than 4:1 for pre-B16 footage, higher for B16, provided your storage (both for the source and render directories) is fast (i.e., fast local array or fast SAN). For even faster results, try rendering to DPX rather than QT files if you can handle DPXs through post. Rendering to DPX with pre-B16 footage using the same settings I mentioned above should get render speeds of a little over 2:1. At least that's what I've found...
 
mmost said:
Sounds like you're using Full debayer and also not setting the display to Full High. Three questions:
1. Am I correct?
2. Assuming I might be, do you **really** feel you need Full debayer for 1080 output?
3. If you have the display at anything other than full and you're using Full debayer, change the screen display to Full. You should find a dramatic increase in render speed. Note: This also holds true for Standard (set to Half High) and draft (set to Quarter high). For the fastest good results on what you seem to be doing, try Standard debayer and Half High display. On an 8 proc Mac, this should reduce the render time to less than 4:1 for pre-B16 footage, higher for B16, provided your storage (both for the source and render directories) is fast (i.e., fast local array or fast SAN). For even faster results, try rendering to DPX rather than QT files if you can handle DPXs through post. Rendering to DPX with pre-B16 footage using the same settings I mentioned above should get render speeds of a little over 2:1. At least that's what I've found...
Click to expand...

Hey Mike,

Thanks for the input mate :)

To answer your questions :

1) Actually I am already set to Full and High as this is what I have found as well, but I can see why you might think this is the case.. thanks for the heads up!
2) I do feel like I need full debayer as I find that the noise size (what little there is) is dramatically reduced with a full debayer, even when downconverting to 1080. I'm from the "anything less than the absolute best isn't good enough' school (unfortunately for me sometimes) :whistling:
3) Thanks mate, this is what I have found as well.. right now I am set to Full Debayer and Full view. Funnily, this is not usually the case, but if I try to set 'Standard' Debayer and 'Half' View, then my render time INcreases to 49hours. Weird, but doesn't really matter for me now as I'm pretty set on a full debayer.

I must add, that after the render settled a little, it went down to 36hours, so that's a "little" better.

:ninja:

I think what I really need is for RedRushes to work.. oh well, the gods don't want me to have efficient multithreaded happiness today.
 
Just a reminder for Deanan to take a look at the question posed a few posts ago.

Thanks,

Nick.
 
Seth

Strange, RedRushes work on my PB as well. And not on my 8-core Power Mac.
 
Suede said:
I normally use RedCine, but thought I'd give RedRushes a go but I've encountered problems. In attempting to render out, my progress indicator goes to "error" almost immediately. I'm taking 2K 16:9 24fps R3D files and attempting to convert them into ProRes HQ 720. I'm attempting to use a single RSX file from the first clip in the batch on all other clips. The RSX file is in the first clip's folder. I'm attempting to output to a completely different directory. Any help would be greatly appreciated.

Nick.
Click to expand...

Shouldn't you use the R3D files?
 
You must log in or register to reply here.
Back
Top