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

FCP Workflow

Dave Beard

Well-known member
Joined
Feb 19, 2009
Messages
125
Reaction score
0
Points
16
Age
40
Hello, I was hoping I might be able to get some help with my FCP workflow. I tried to use the search function on REDuser, but it's a bit lame.

I had very high hopes for Storm, but I'm thinking about throwing in the towel. What are people using now to have RCX and FCP talk to each other. I used clipfinder back in the day, but I understand Hans has somewhat abandoned ship. I understand that RCX may have the ability now to ingest an FCP xml? Am I able to round trip to FCP? I know this is a very noob question, but any help would be greatly appreciated.

Thanks

Dave
 
why abandon storm? seems to have great functionability with xml back and forth with FCP.
My workflow is: RCX or Storm one light; then transcode to Prores422HQ or 4444, then take into FCP and grade with 3 way color and cut with prores. like the ability of storm and xml to FCP as well.
 
I'm just exploring my options.
 
RCX 454 will take a FCP XML (I edited using ProRes 422 proxies transcoded from RCX) and re-link to the R3D's - but your edit must be only on one video track and nothing can be time-remapped.
In the preferences pane (which should pop up whenever you import an xml) you navigate to the folder that contains your RED footage and it will re link everything for you. Once imported you can grade and finsh as you see fit.
I would love to hear what your beef with Storm is - I personally find the ability to bin and tag, do a quick one light and jump into Final Cut pretty convenient!

-Carl
 
Hi Dave,

Currently Build 454 has the following capabilities related to FCP XML:

1. Import. You can import relatively simple single sequence FCP XML's. Any effects will be ignored. Transitions will be compensated for and empty space will be filled with a slug.

2. Export. When you export a sequence with "Timeline (Separate Clips)" and are doing QT wrappers or R3D Trim, you have the option of including an FCP XML with the export.
You can also export an FCP XML from the menu, but this only references R3D's, and thus is only suitable for import into Premiere for example.

Future builds of RCX will let you put out an XML with Quicktimes.

Let me know if you have any more questions. Feel free to shoot me an email. redcinex at red dot com.

David
 
FCP-X is 2 months away (hopefully) might be worthwhile to hold out a bit on that end... there is a lot they haven't revealed yet, might solve any workflow issues you might have.
 
Is anyone still using clipfinder, or is that old news?
 
Is anyone still using clipfinder, or is that old news?

Depends on your workflow. If you are going back to RCX then really no need for Clipfinder. If you want to replace ProRes with Proxies for Color, or to address the Color R3D looping bug then maybe.

In my opinoin, RCX is a great way to bring your edit back and work with R3Ds.
 
So no XML export back to FCP with Quicktime references from RCX yet? I'm curious how people are using this XML functionality to roundtrip back to FCP at the moment.
 
me too...
 
Back
Top