I have tried it and Vegas is getting a bit better. This is somewhat of an old topic for me but just to repeat some of my basic dialog:

Back in the SoFo days one of the "sell" points that brought me to Vegas Video was the key word "EDL". It was not *the* main reason for trying Vegas Video but it helped to stear me to it. It took only a short while to figure out that SoFo's term of EDL was not what most editors considered an EDL. Sony's use of the term is the same except over time there has been an ever so slight mod of it - if dig around you can find "Vegas EDL" as a savbe format. The "sell points" are now a bit more focused with "Capture/Export/Hardware Features" listing EDL export, which is true (with the newest versions of Vegas there is a "built in" script that will export a project to a CMX EDL) but Vegas has never called itself an "online" NLE so one has to keep in mind that things like tape/reel numbers as well as locations of media on various hard drives are null. So, IMO, it is somewhat still a misleading "sell point" Not only that but even if Vegas did handle EDL's well it reads time code info in a different way than other NLE's so, for example, exporting a project from Premiere 6.5 (or lower) and/or Premiere Pro 1.5 (or higher) via EDL won't work well because Vegas will not read the time code info from the files captured in Premiere. On top of that Vegas will try and open up any CMX EDL however there are many "but(s)..." involved. Such as "There is no problem with taking a CMX EDL and importing into Vegas. But all media must be in the same folder as the EDL. But it will only work on a cuts only project." and so on.

This is where AAF trys to come in. I guess one could say it is the computer version of the old tape based EDL. And to a point it does work a bit better, my eyes somewhat sparkled when I tried an AAF export of a porject and it opened up in the demo of Vegas...well, I should say it opened up much beeter than a CMX EDL of the same project did. On a bit further research it seems that AAF format is a lot more open ended than an EDL is. So Vegas reads and exports certian things using "keywords", as do other NLE's, and these "keywords" may not match up.

Bob and I had an interesting thread right before Vegas 6 came out talking about EDL's and such. It is at http://www.sonymediasoftware.com/forums/ShowMessage.asp?MessageID=373059. As for AE specific - there is a plug-in available, I think it is 5 bucks, that will convert a Vegas project into one readable in AE. However it was based on an earlier verison of Vegas so chances are unless it has been updated it won't work well with Vegas 6, and may not work with AE 6.5 all that well either.

Now to be fair many people have claimed that they can export/import EDL's and AAF's between Avid NLE's and Vegas. EDL wise I am still waiting for an answer to a question I asked maybe two years ago where someone said there was not any issues doing this. As a test I exported a CMX EDL from Vegas and sent it off to someone with an AVID and said "Here, rebuild this". Of course they could not because none of the tape/reel info was exported, only captured media file names were, meaning the EDL was usless. My question was asked along the lines of "What trick did you use to export tape names and numbers from Vegas?" As I say - still waiting on that answer, because really as far as I can tell you can not do this and no one has come up with a thrid party script or plug-in that will do this.

*EDIT - added links to time code thread.

Integration with other programs would certainly be nice. A lot of programs claim to work with EDL, XML, AAF, etc. but oftentimes it doesn't work, or you can only transfer very basic information across (i.e. speed changes don't translate).

Thanks for the info guys,

SONY should really consider this issue because I know other NLE's offers project export to AE which works better, and I do know there are a lot of AE users using Vegas and this forum, myslef included

We have heard from quite a few people now who are successfully moving complex projects in or out of AVID, Protools, FCP, Premiere and other AAF capable apps. Most of the issues we have seen are related to proprietary codecs (one app can read a certain codec, another can't)

If you are encountering problems with moving an AAF file into, or out of, Vegas 6.0c, we would like to know:

What exact problem(s) are you encountering?

What is the other app (including version #) you are using for AAF interchange?

We're always interested in feature requests but we also want to know about actual bugs you may have run into.