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

issues using proxies generated by RCX from scarlet

Joesef o.

Well-known member
Joined
Aug 6, 2012
Messages
246
Reaction score
0
Points
0
Ok so I decided to try using proxies instead of rendering out 2K files (I like to do online edits instead of offline)

I'm testing this on a 2010 MBP with 2.26 intel core 2 duo, 8gigs ram

I can work with 2K prores HQ files in real time with my online editing with this computer but...


When I just make the proxies (quicktime wrappers) from REDCINE-Xpro I have all 4 quality levels... I drop them into my FCP timeline and not even the lowest resolution proxy will play back in real time without rendering. I try playing them in quicktime and same thing, even the lowest resolution proxy file is very skippy...

Am I doing something wrong here?

I have 2K DPX sequences that playback about real time on this computer, but these super low res proxy files are more jittery in playback than the huge online files... What gives?:banghead:
 
Playing back from proxies/raw needs a lot of realtime computing compared to dpx's

Decrypting/debayering/linear to rec compared to just playback on the dpx's.

And i often found the proxies to play better in qt, than in fcp.

From the epic I never had any functioning/practical results from the proxies.. From R1 they worked for short projects.
 
There are reasons that what you are doing is exactly what everyone, especially Red, recommends you not do. It is not an elegant workflow. It causes way more problems than it solves. Relinking to the original files within DaVinci, as well as other grading programs, is simpler now than ever before. Really, you should be editing either with the actual R3Ds (in Adobe Premiere or similar with the appropriate hardware) or using ProRes or DNxHD proxies.

Anything else is precisely what everyone will tell you not to do as it will make you want to slam your head into a wall.
 
I have a msi quad laptop with a gtx670m tha cost me 1.5k and I only edit with R3Ds in RT 1/4.
No issues at all. After cs6, you only use proxies if you want to, really.
 
Hmm well I guess those proxies are useless then... Whats a quicker more streamlined way to get projects going?

What I've been doing is rendering out 2K Quicktime Prores HQ files and just working with those directly and thats it. Takes a lot of overnight rendering for all the clips... I know thats the most ridiculous and longest way to do things, but I like the simplicity of just working with your master online files right there, I can color it if needed and all and just export it out of FCP when I want.

Whats a good workflow that can get me to skip the 2K renders?
 
Using ProRes proxies is still mostly the Standard for working with Red files. It's the way everyone has done it for the past 3 years.

Just now, things are starting to shift over to using the actual .R3D files instead. In that case, using Adobe Premiere along with NVIDIA hardware with enough CUDA cores is the way to go, for the most economical setup anyway.
 
ok thanks, at least I know I was doing roughly the right thing, I started with the prores proxy way but had wanted to skip sending back and forth so I just did the big renders right away and kept it all in fcp.
 
Back
Top