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

Crimson proxie VS whitepaper...

Lewis-M Soucy

Well-known member
Joined
Mar 21, 2007
Messages
1,412
Reaction score
0
Points
0
Age
58
Location
Paris
Website
www.lewis.pro
I'm currently cutting a MV and tried the Crimson way. Thing is my P_ proxies need rendering and it's very long... Strange too, they worked in playback when my canva window was scaled 100% only?! Otherwise, I got the grey screen... The M_ worked better, but still needed rendering (instead of the red line, they had an "orange sort of color" line above, like half rendered???)

I decided to try the whitepaper way, with log and transfer, and this seems much better, besides the fact that the process is very long. Less longer than rendering all through Redcine, but still... The only sad side is I now cut in 2K when I have to go back to SD... But the rushes are in much better quality than with the proxies though...

So in short, I have to render all the rushes instead of having Crimson render only the selected cuts. I used Crimson a couple of months ago and it worked perfectly. I wonder what is going on with proxies and FCP... I always tought they didn't need to be rendered...
 
Crimson is still working for me without problems .Check RT settings ,
with Unlimite RT yit must work without render with M proxies . Proxy quality is very bad in FC , but for first edit it is ok .
In my situation it is deppends on Director , if director can work with proxies i need to L&T footage for him .
But also with this workflow i still can use crimson to go back in RedCine .
 
I'm currently cutting a MV and tried the Crimson way. Thing is my P_ proxies need rendering and it's very long... Strange too, they worked in playback when my canva window was scaled 100% only?! Otherwise, I got the grey screen... The M_ worked better, but still needed rendering (instead of the red line, they had an "orange sort of color" line above, like half rendered???)

I decided to try the whitepaper way, with log and transfer, and this seems much better, besides the fact that the process is very long. Less longer than rendering all through Redcine, but still... The only sad side is I now cut in 2K when I have to go back to SD... But the rushes are in much better quality than with the proxies though...

So in short, I have to render all the rushes instead of having Crimson render only the selected cuts. I used Crimson a couple of months ago and it worked perfectly. I wonder what is going on with proxies and FCP... I always tought they didn't need to be rendered...

Hmmm... well Crimson works with both camera proxies and transcoded media. As long as the quicktime file has a frame to frame correspondence with the Raw file, you should be in bussiness.

The reason you need to render may have something to do with your timeline settings. For example a 2K timeline (_H proxies) will still need rendering if you are mixing 4K and 3K footage for example. I only work with camera reference files for very small projects and on set cut previews. In general I still transcode _H or _M proxies to ProRes using compressor or RedRushes.
The rendering times to transcode _M reference files are very reasonable and
you have the advantage of being able to scale all of your footage to one size and take down rendering load in FCP.

I hope that is helpful.

IBloom
 
Back
Top