FCP XML into Smoke

[schmoop]

Hi everyone,
There’s been some talk around the shop about switching out our Avids for FCP. If anyone has experience with an XML workflow into Smoke, your two cents would be much appreciated. We’re looking for any and all points of view. Does XML really speed up the process that much, or is it like OMF, where the offline cutter has to be careful about using specific efx so they xfer over in the metadata? Any other caveats? Traditionally, we’ve been using CMX 3600 edls to conform.
Thanks,
Steve

p.s. we’re on SMOKE 7.0.13 tezro

[Scott]

For the most part XMLs work well. The offline editor still has to be careful with fx and what not. The only reason we still use EDLs is the ability to change frame rate from 29.97 to 23.98. I’ve yet to find a comparable tool for XMLs.

md

[cyril conforti]

Also, with tether, you can drag your FCP XML directly into a library, and it will transfer all associated material directly into the smoke, .mov, aiff, mp3, image sequences, any thing that was in the timeline. You can then easily re-link the clips to the XML in Smoke. This is incredibly hand for P2 workflow or anything that is not traditionally tape based.

http://www.tether.it

[Dan Carr]

If you drag your fcp project but the codec are not supported? Do you think it’s possible to conform the project into fcp (for P2 and non tape based project ) in SGI sequence and then ship it to Smoke?

[cyril conforti]

With tether, if your Mac can read it, then it can be sent straight into StoneFS. So if you have already captured the P2 or any other material with FCP, then yes, it will go directly into the Smoke.

@forilou 23553 wrote:

If you drag your fcp project but the codec are not supported? Do you think it’s possible to conform the project into fcp (for P2 and non tape based project ) in SGI sequence and then ship it to Smoke?

[Author]

Posts