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

Sending Proxy from FC to Color . Is it right workflow .

Joined
May 2, 2007
Messages
1,288
Reaction score
0
Points
0
Age
42
Location
Tbilisi , Georgia
Website
sarke.ge
Good day . My basic Red Workflow is still FC-CRIMSON-REDCINE-Color ,
but i found that if i will just send proxy files to color i can manage
my footage in Color. Without LOG and Transfer and etc .


1. Edit in FC with M proxy files
2. Send To Color
3. Change Project setting to 1920x1080
4. Change Geometry for 2K footage
5. Grade in Color
6. Render in Prores
7. Send back to FC .

For me this workflow is working for small projects without some super
cc job , in Primary in i have RED tab , sow i
can manage my metadate . Everything looks like working fine .
I have question , did some body test this workflow for quality and
etc, can not found difference in files from Color and from RedCine .



Thanks.
 
Yes, that works just fine, same quality output as the RED Whitepaper L&T method. You'll want to run "color fixer" http://www.daun.ch/software/ to avoid the color loop-bug error when doing this. But yes, that method gives great results.
 
Yeah, color doesn't deal very well with speed changes. One option is to make a separate sequence that has all you speed-change clips on it back at regluar speed, then you can drop them back into the correct timeline once you've gotten back to FCP.

The loop bug happens when you have clips that are spanned across multiple R3D files. Color doesn't like that, but if you run that utility, it keeps it from happening. If you ever see the error, you will know what it is.
 
  • Thread starter
  • Banned
  • #5
Yeah, color doesn't deal very well with speed changes. One option is to make a separate sequence that has all you speed-change clips on it back at regluar speed, then you can drop them back into the correct timeline once you've gotten back to FCP.

The loop bug happens when you have clips that are spanned across multiple R3D files. Color doesn't like that, but if you run that utility, it keeps it from happening. If you ever see the error, you will know what it is.

Thanks.
 
  • Thread starter
  • Banned
  • #6
One more bug in this workflow.
When working with Key you can not change keys setting for RED
metadate. For exsampe if you will change saturation in RED TAB for 1 key
and then for 2 change , transaction will have no effect . And 2 key
parameters will be applied to full shoot.
 
Back
Top