Luca Immesi
Well-known member
- Joined
- Apr 13, 2008
- Messages
- 878
- Reaction score
- 0
- Points
- 0
- Location
- Italy
- Website
- www.esperimentocinema.com
Update4! Please consider only this update:
So thanks to Nick Shaw, Hans and Rowland now the workflow is really easy:
1 Shoot 4k/2k 16:9 or 2:1
2 Drag the RDM folder in Clipfinder
3 Choose M proxies for 4k and H proxies for 2k
4 Drag the clips to FCP bin and make your edit with M (for 4k) proxies and with H (for 2k) proxies
5 When you finish your editing duplicate the sequence, put all the clips on the first video track and remove all the effects
6 Send to Color
7 Close Color project
8 Open COLORFIXER and choose the color project you want to fix
9 Reopen color project
10 Enjoy
Update3! Please consider only this update:
1 Shoot 4k/2k 16:9
2 Drag the RDM folder in Clipfinder
3 Choose M proxies for 4k and H proxies for 2k
4 Drag the clips to FCP bin and make your edit with M (for 4k) proxies and with H (for 2k) proxies
5 When you finish your editing duplicate the sequence, put all the clips on the first video track and remove all the effects
6 Export the EDL
7 Make a new color project and import the edl
8 Put the right frame rate, resolution (what ever you want), put the right files path, if needed resize the clips in the geometry room
9 When you finish with you color correction render to one of these different formats:
Uncompressed 10 bit, Aja 10-bit RGB codec, Dpx, Prores HQ and send back to FCP and export FCP sequence (file-export to quicktime movie). If you export to dpx you have to manually wrap every clip with aja dpxtoquicktimetraslator and rename it 1_g1.mov and so on in the same folder of the dpxs, then send it back to FCP and it will relink to your dpx wrapped quicktime files.
About the gamma issue: I've tested all the codec above and I can say (with that codecs) it's only the way FCP reads the footage. If you export the sequence outside FCP you will notice that you have the same quicktime (uncheck final cut compatibility) that you have imported before from Color. If I'm wrong please correct me.
Remember to set in FCP sequence settings "render all YUV material in high precision YUV". It's crucial.
Here's the link to a very good source:
http://www.coremelt.com/support/workflow/codec-and-effects-limitations-for-10-bit-online-workflow-with-final-cut-pro-6.0.2.html
and here a podcast with Graeme Nattress
http://www.fxguide.com/modules.php?name=redcentre&pa=listen&path=redcentre-004.mp3
OMG it's 7 P.M. and I have to buy some gifts.
I have to go!!! Merry Christmas everybody!!!
So, I' ve tested this workflow really a little but it seems to work with spanned R3D files. Yes color seems to be able to read correctly r3d spanned files through an EDL. I hope I'm right.
I used for test 4k 16:9 build 16 files I'll test with 17 soon with other resolutions.
For now what I know is:
Shoot 4k 16:9
1 Make your edit in fcp with P or M proxies
2 reconnect P or M with H proxies
3 change fcp sequence settings to 2048x1152
4 export the EDL
5 make a new color project
6 import the edl
7 put the right frame rate, resolution (2048x1152), files path
8 enjoy
Update! It seems that it is not required to reconnect the P or M with H proxies. So the workflow should be:
1 Shoot 4k/2k 16:9
2 Make your edit in fcp with P or M proxies
3 export the EDL
4 make a new color project
5 import the edl
6 put the right frame rate, resolution (what ever you want), files path
7 resize the clips in the geometry room (if needed)
8 enjoy
Update2! So I tried with b17 4k spanned files, it works smooth!
Also I experimented exporting an xml from fcp and importing into color, it works but I noticed a better playback in color with edl method than xml.
But for people can't load the edl they can try exporting the xml and importing in color. Although I highly recommend the edl route.
So thanks to Nick Shaw, Hans and Rowland now the workflow is really easy:
1 Shoot 4k/2k 16:9 or 2:1
2 Drag the RDM folder in Clipfinder
3 Choose M proxies for 4k and H proxies for 2k
4 Drag the clips to FCP bin and make your edit with M (for 4k) proxies and with H (for 2k) proxies
5 When you finish your editing duplicate the sequence, put all the clips on the first video track and remove all the effects
6 Send to Color
7 Close Color project
8 Open COLORFIXER and choose the color project you want to fix
9 Reopen color project
10 Enjoy
Update3! Please consider only this update:
1 Shoot 4k/2k 16:9
2 Drag the RDM folder in Clipfinder
3 Choose M proxies for 4k and H proxies for 2k
4 Drag the clips to FCP bin and make your edit with M (for 4k) proxies and with H (for 2k) proxies
5 When you finish your editing duplicate the sequence, put all the clips on the first video track and remove all the effects
6 Export the EDL
7 Make a new color project and import the edl
8 Put the right frame rate, resolution (what ever you want), put the right files path, if needed resize the clips in the geometry room
9 When you finish with you color correction render to one of these different formats:
Uncompressed 10 bit, Aja 10-bit RGB codec, Dpx, Prores HQ and send back to FCP and export FCP sequence (file-export to quicktime movie). If you export to dpx you have to manually wrap every clip with aja dpxtoquicktimetraslator and rename it 1_g1.mov and so on in the same folder of the dpxs, then send it back to FCP and it will relink to your dpx wrapped quicktime files.
About the gamma issue: I've tested all the codec above and I can say (with that codecs) it's only the way FCP reads the footage. If you export the sequence outside FCP you will notice that you have the same quicktime (uncheck final cut compatibility) that you have imported before from Color. If I'm wrong please correct me.
Remember to set in FCP sequence settings "render all YUV material in high precision YUV". It's crucial.
Here's the link to a very good source:
http://www.coremelt.com/support/workflow/codec-and-effects-limitations-for-10-bit-online-workflow-with-final-cut-pro-6.0.2.html
and here a podcast with Graeme Nattress
http://www.fxguide.com/modules.php?name=redcentre&pa=listen&path=redcentre-004.mp3
OMG it's 7 P.M. and I have to buy some gifts.
I have to go!!! Merry Christmas everybody!!!
So, I' ve tested this workflow really a little but it seems to work with spanned R3D files. Yes color seems to be able to read correctly r3d spanned files through an EDL. I hope I'm right.
I used for test 4k 16:9 build 16 files I'll test with 17 soon with other resolutions.
For now what I know is:
Shoot 4k 16:9
1 Make your edit in fcp with P or M proxies
2 reconnect P or M with H proxies
3 change fcp sequence settings to 2048x1152
4 export the EDL
5 make a new color project
6 import the edl
7 put the right frame rate, resolution (2048x1152), files path
8 enjoy
Update! It seems that it is not required to reconnect the P or M with H proxies. So the workflow should be:
1 Shoot 4k/2k 16:9
2 Make your edit in fcp with P or M proxies
3 export the EDL
4 make a new color project
5 import the edl
6 put the right frame rate, resolution (what ever you want), files path
7 resize the clips in the geometry room (if needed)
8 enjoy
Update2! So I tried with b17 4k spanned files, it works smooth!
Also I experimented exporting an xml from fcp and importing into color, it works but I noticed a better playback in color with edl method than xml.
But for people can't load the edl they can try exporting the xml and importing in color. Although I highly recommend the edl route.