Kenn Michael
Well-known member
- Joined
- Dec 28, 2006
- Messages
- 708
- Reaction score
- 0
- Points
- 0
So now that we have the Adobe suite reading R3Ds natively, I thought I'd try out a workflow experiment that I've been thinking about ever since I found out that Premiere Pro CS4 can now import XMLs from Final Cut.
Well it worked, and here's how to cut in FCP and get to a complete 4K conform in After Effects for DPX output (or anything else you want to export from AE)
1. Use RedRushes to transcode your footage to 1K for an offline edit in FCP. (Make sure to have all your transcoded files in one main directory. For this example we'll call this directory - FOOTAGE)
2. Edit normally in FCP.
3. Export an XML from your offline edit.
4. Open the XML in the wonderful app Clipfinder.
5. Use Clipfinder to 'convert MOV to R3D'.
6. Select all the clips in the Clipfinder window, then Cmd-C (to copy the list)
7. Create a new folder in the finder which you can call your 'Neg Pull' (name doesn't matter for the moment)
8. Cmd-V (to paste the list of just the used shots in the cut to the new folder)
9. Create a folder called 'FOOTAGE - Offline' and MOVE the 1K offline QT movies to it. Your 'FOOTAGE' folder should now be empty.
10. Use the spotlight function in the finder to find the .R3D files in the 'Neg Pull' folder. You should now just have a bunch of .R3D files in a list.
11. Move that list of .R3D files into the 'FOOTAGE' folder.
12. Open up the offline XML in a text editor and do a 'Find/Replace' where you find every instance of ".mov" and replace it with "_001.R3D".
13. Open PremierePro and import this altered XML.
If everything goes right, you'll now have a sequence that instead of pointing to 1K ProRes files, it will connect to the folder of R3D files in the 'FOOTAGE' folder.
Now, you can do the new Adobe workflow to preview the cut and make sure that everything came over correctly, copy/paste into a 4K sequence, change your resolution settings to Full on all R3D files, import into AE and adjust to taste before exporting to glorious 4K DPXs!
Whew, that was a lot, and I hope it made sense. I'm sure that someone will write a brilliant little app or plugin to do all this automatically, but the above workflow works today and works great!
Well it worked, and here's how to cut in FCP and get to a complete 4K conform in After Effects for DPX output (or anything else you want to export from AE)
1. Use RedRushes to transcode your footage to 1K for an offline edit in FCP. (Make sure to have all your transcoded files in one main directory. For this example we'll call this directory - FOOTAGE)
2. Edit normally in FCP.
3. Export an XML from your offline edit.
4. Open the XML in the wonderful app Clipfinder.
5. Use Clipfinder to 'convert MOV to R3D'.
6. Select all the clips in the Clipfinder window, then Cmd-C (to copy the list)
7. Create a new folder in the finder which you can call your 'Neg Pull' (name doesn't matter for the moment)
8. Cmd-V (to paste the list of just the used shots in the cut to the new folder)
9. Create a folder called 'FOOTAGE - Offline' and MOVE the 1K offline QT movies to it. Your 'FOOTAGE' folder should now be empty.
10. Use the spotlight function in the finder to find the .R3D files in the 'Neg Pull' folder. You should now just have a bunch of .R3D files in a list.
11. Move that list of .R3D files into the 'FOOTAGE' folder.
12. Open up the offline XML in a text editor and do a 'Find/Replace' where you find every instance of ".mov" and replace it with "_001.R3D".
13. Open PremierePro and import this altered XML.
If everything goes right, you'll now have a sequence that instead of pointing to 1K ProRes files, it will connect to the folder of R3D files in the 'FOOTAGE' folder.
Now, you can do the new Adobe workflow to preview the cut and make sure that everything came over correctly, copy/paste into a 4K sequence, change your resolution settings to Full on all R3D files, import into AE and adjust to taste before exporting to glorious 4K DPXs!
Whew, that was a lot, and I hope it made sense. I'm sure that someone will write a brilliant little app or plugin to do all this automatically, but the above workflow works today and works great!