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

Best Settings for Redrushes?

munchausen

Member
Joined
Sep 19, 2008
Messages
9
Reaction score
0
Points
0
Hi all,

So I'm about to embark on a mass-transcode of 3.2Tb worth of footage to some sort of more manageable codec and, based on advice from several directions, it appears the best method will be to use a batch function in Redrushes.

Now the next question is: if I'm using a Macbook Pro, what settings should I use to optimize "editability" and resolution?

Thanks in advance,

T
 
I would advise:

1.
Do not transcode at all. Use the 1024x512 QT proxies.
Divide the project in 2 or 3 parts, if you do not have a harddrive system, that has the capacity.
Create "onelights" with the the following RED ALERT trick:
http://www.reduser.net/forum/showthread.php?t=19019&highlight=heaven

2.
Transcode for offline:
1024x512 ProRez, Debayer to half, ColorSpace Camera, GammaSpace, Redspace.


Both solutions are very editable even on a MacBook or MacMini. In both cases you need external firewire drives to feed the data, as the internal drives are too slow.

I would avoid transcoding for offline. There is no real benefit in not using the proxy files. If you want a high quality offline (720p, ProResHQ), you might end up with even more space requirements, than the original r3d files.

It makes much more sense to me, to edit first in proxies, and then keep going only with the data, that did not fell down the editing table.
 
You should read my post from yesterday concerning this. As I mention - the first time I tried this it all worked well. But when I tried to guide someone over the phone to do exactly the same it wouldn't work at all. It is probably a something in the install of the codecs or the settings in FCP that we have overlooked. I'm looking into this right now and will post my result as soon as I know anything.

It might be best for such a huge amount of files to start transcoding right away. As you allready know - it will take very long time ;)
 
Back
Top