FCP/ Avid/ Premier for doc post producion houses?

[Andy Field]

not that difficult to transfer the project to FCP 7 or Premiere pro – read this…also once you get it into FCP or Premiere – there are excellent tools to transfer back and forth to AVID as well (AUTOMATIC DUCK – now free)

https://wolfcrow.com/blog/the-sony-vegas-pro-export-guide-part-two-external-workflows/

Andy Field
FieldVision Productions
N. Bethesda, Maryland 20852

[Pam Picard]

I agree with Andrew – I would not pick the editor based on the NLE, but rather the other way around. FCPX, Avid, Adobe – they all can do the job but finding an editor you can work with, communicate with, collaborate with – that is really the most important thing.

[Jari Innanen]

It is worth mentioning, that Sony Vegas supports fcpxml.

[Charlie Austin]

[Jari Innanen] “It is worth mentioning, that Sony Vegas supports fcpxml.”

Interesting isn’t it… Vegas, Smoke, Davinci and a bunch of other post support apps read and write fcpxml. Avid and Adobe need to get with it. lol

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[James Henson]

Thank you very much for the considered responses! I really appreciate it!

firstly, Vegas does not export to fcp/fcpx, that is simply incorrect, i have spent too many hrs trying to do so. If you google how to do so, there are perhaps three sites that superficially cover how you do this. Anyway, I would be grateful to be proved wrong if you could provide a link to pages detailing how this is to be done without fcp/fcpx aborting the footage

[Andrew Kimery]

[Charlie Austin] “Interesting isn’t it… Vegas, Smoke, Davinci and a bunch of other post support apps read and write fcpxml. Avid and Adobe need to get with it. lol”

PPro can import and export FCPXMLs (I think that was added 2 or 3 versions ago). Avid, from my limited understanding of programing, is an entirely different beast under the hood though, as previously mentioned, Automatic Duck exists as a possible bridge.

I’ve only used the Duck once though and it didn’t go very smoothly. While reading up on it I learned that the final version of Automatic Duck was released when Avid’s AMA functionality was very new so there are a lot of shortcomings of using the Duck with tapeless workflows.

[Charlie Austin]

[james henson] “firstly, Vegas does not export to fcp/fcpx, that is simply incorrect, i have spent too many hrs trying to do so. If you google how to do so, there are perhaps three sites that superficially cover how you do this.”

Seems fairly straightforward:

https://www.sonycreativesoftware.com/webhelp/vegaspro/12/ENU/Content/Importing_and_Exporting_Projects.htm

From the File menu, choose Export, and then choose a project type from the submenu:

Pro Tools AAF File
Media Composer AAF
Premiere/After Effects
Final Cut Pro 7/DaVinci Resolve
Final Cut Pro X
EDL Text File

I guess whether it works is another question… 😉

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Andrew Kimery] “PPro can import and export FCPXMLs (I think that was added 2 or 3 versions ago). Avid, from my limited understanding of programing, is an entirely different beast under the hood though, as previously mentioned, Automatic Duck exists as a possible bridge.

I’ve only used the Duck once though and it didn’t go very smoothly. While reading up on it I learned that the final version of Automatic Duck was released when Avid’s AMA functionality was very new so there are a lot of shortcomings of using the Duck with tapeless workflows.”

Pr C imports/exports FCP 7 XML, not FCP X xml. And MC imports neither. Auto duck still works OK for picture… You lose a lot of info, but the cuts come over OK. But that requires FCP 7 or Pr, so, like Adobe.. no X to MC straight shot.

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Andrew Kimery]

[Charlie Austin] “Pr C imports/exports FCP 7 XML, not FCP X xml.”

Ah, thanks for the clarification.

[Charlie Austin]

[Andrew Kimery] “[Charlie Austin] “Pr C imports/exports FCP 7 XML, not FCP X xml.”

Ah, thanks for the clarification.”

It actually works pretty well in the latest CC versions. It would be nice if Adobe and Avid would read FCPXML, it’s a moving target, but the documentation is available. I guess they have no desire to work with the competition in this arena. And Apple probably doesn’t care one way or the other… 😉
Would make my life easier though. X to 7 to whatever or vice versa is like a game of telephone. What you end up with isn’t necessarily what you began with…

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~