XML to Discreet/AutoDesk?

[Oliver Peters]

Scott,

I tested this path for the Videography article I just did on Smoke (Linux). It worked fine, but there are some guidelines. You can get a “white paper” from Autodesk about the FCP DOs and DON’Ts. Effects don’t come across, but the clips are put in the right places with Smoke functions applied, just no parameters adjusted. For example, I did a simple quad split on 4 tracks. These were properly placed on the TL with Smoke axis effects applied. Smoke dealt with speed effects and I was told ramps are also supported. Nests are, of course, a no-no.

Sincerely,
Oliver

Oliver Peters
Post-Production & Interactive Media
Orlando, FL
http://www.oliverpeters.com

[Scott Witthaus]

Thanks, Oliver –

I have been told that while the parameters are not applied on the effect, the metadata (easily read by XML) details the effect parameters. True?

Is your article out yet?

Scott Witthaus
Senior Editor/Post Production Supervisor
Greybox, LLC
Richmond, VA USA
http://www.greybox.cc

[Michael Buday]

The XML output from FCP should, from what I’ve heard, contain everything about the project, including the keyframe metadata you’re interested in. More likely is that Disceet is ignoring that data during import except for the placing the closest effect type – in its default state – on to the clip.

All the best,

Michael Buday