Found a script that allegedly converts Vegas-EDL to FCP-EDL, at http://forums.creativecow.net/thread/24/880627 (as 2008-07-04) Anyone tried that? I suppose in principle a project could be exported as a bunch of EDLs (one for each track) but don't know whether FCP could import them cumulatively (to separate tracks).
However I understand (from a recent FCP course) that EDL is outmoded by XML, for example EDL is only for one track. In that case I suppose what we really want is to exchange XML between Vegas & FCP. I appreciate that XML is a meta-language and not anything as specific as a NLE interchange format. Then what we are talking about in an ideal world is the ability for Vegas to import & export FCP-XML and/or FCP to import& export Vegas-XML. A third party "Translator" app is possible in principal but I only know of Automatic Duck which has no plans for Vegas. Not aware of any 'Geese etc.
Possibly it is mostly in Vegas's interest to become multi-lingual, since we are used to scripts, even if only to approximate cuts and dissolves and to handle the different ways that tracks are laid out (between Vegas & FCP). Perhaps a Vegas script could be developed to output a simplified subset of Vegas-XML for just these aspects.
Maybe then there is some way to use an open-source PC & Mac based database to hold the objects and do the translation, rather than an unwieldy script. Could lead to lots of other kinds of automation too.
Either way, would need a definition of each product's XML (or subsets thereof). FCP-XML format is published in great detail with example apps at http://developer.apple.com/referencelibrary/AppleApplications/idxFinalCutProFinalCutExpress-date.html. Is there / could there be anything like this for Vegas? I wonder how much of the Project definition is represented in the Vegas-XML.
However I understand (from a recent FCP course) that EDL is outmoded by XML, for example EDL is only for one track. In that case I suppose what we really want is to exchange XML between Vegas & FCP. I appreciate that XML is a meta-language and not anything as specific as a NLE interchange format. Then what we are talking about in an ideal world is the ability for Vegas to import & export FCP-XML and/or FCP to import& export Vegas-XML. A third party "Translator" app is possible in principal but I only know of Automatic Duck which has no plans for Vegas. Not aware of any 'Geese etc.
Possibly it is mostly in Vegas's interest to become multi-lingual, since we are used to scripts, even if only to approximate cuts and dissolves and to handle the different ways that tracks are laid out (between Vegas & FCP). Perhaps a Vegas script could be developed to output a simplified subset of Vegas-XML for just these aspects.
Maybe then there is some way to use an open-source PC & Mac based database to hold the objects and do the translation, rather than an unwieldy script. Could lead to lots of other kinds of automation too.
Either way, would need a definition of each product's XML (or subsets thereof). FCP-XML format is published in great detail with example apps at http://developer.apple.com/referencelibrary/AppleApplications/idxFinalCutProFinalCutExpress-date.html. Is there / could there be anything like this for Vegas? I wonder how much of the Project definition is represented in the Vegas-XML.