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

Red Rushes Manual...

It's starting 6 threads, but they found that this is giving the best load balance. Remember, there'll be also a lot of I/O going on.
 
Here's what I'm seein'...The program is wonderful in it's simplicity. The ease of use and complete lack of bells and whistles makes this program a delight to use, however I have yet to notice a great difference in speeds. I've been getting roughly 18:1 render times on dpx 2k qt-Pro Res 422 HQ at Full Dbyr with an 8 core. Is this the same sort of times that other users have been getting? Is there anything I can do outside of Redrushes to get it to go faster while keeping the same settings?
 
18:1 render times is this a little slow ?

18:22 minutes to render 1:02 minute? It's not that bad I guess, but it's not substantially different from Redcine.

Another thing that I noticed about Redrushes, is that if you're trying to make slightly different renders of the same file, give them each a completely different folder otherwise it'll just render over the one you just did and you'll be left saying "Why do I only have one file here when I've just rendered out 5 different times??"
 
It's called REDrushes... 1/2 debayer should be what you use. Quality is plenty good and speed is fine. If you are using for some other higher quality purpose, then expect longer times.

Jim
 
That's what we are discussing here.

You cannot "save as preset" though, because that generates an RLX file.

You can only use the autosaved RSX file.

Haven't tried RedRushes yet, but it's nice to have Dylan be the one speaking the geek greek for once! :-) (this camera has changed you, man!)

Has anyone tried renaming an RLX to an RSX?
 
Back
Top