Greetings all-
We've had quite a few people asking about EDLs, OMF, AAF, Vegas-to-whatever project interchange, as well as broader questions about application scripting in general, so I'd like to bring the Vegas user community up to speed and tell you where we're headed with all this.
As of right now (1.17.03) the scripting api and documentation is still being worked on. While still in progress, the architecture is in place to allow project data to be exported and imported, and in addition, many processes will be also able to be automated.
You can get a taste of the automation by running the sample scripts posted on the Vegas 4 beta download page- these scripts will allow some basic process automation, like still image export, adding/removing the timecode filter from all media files, batch rendering and a few more. These samples should give you an idea of the possibilities that application scripting will open up.
-------------------------------
As far as EDLs/OMF/project interchange is concerned, this is important and needs to be stated clearly: Vegas 4.0.0 WILL NOT be shipping with a CinemaTools/AVID EDL manager/Automatic Duck-type plug-in or companion tool. Vegas 4.0.0 will not ship with an OMF or AAF importer/exporter.
Equally important: If you poke around Vegas 4, you'll see that source TC i/o is now in edit details, the TC window plug-in is greatly improved, the media pool has been beefed up significantly, and the scripting engine will allow all of this info (and lots more) to be imported or exported. This means that edls/omf/aaf or whatever will be possible from Vegas 4...but some work needs to be done.
So, a proposition:
If you are....
a) familiar with jscript
b) familiar with EDLs, OMF, AAF
c) familiar with Vegas
d) are possibly interested in discussing working with us on an EDL/OMF/AAF plug-in
...SF would like to talk to you. Contact me directly at drdropout@sonicfoundry.com.
-------------------------------
More about scripts:
Scripting docs will be posted on our website when they are ready.
More sample scripts will be posted on our website when they are ready.
There will be a Vegas scripting forum on sonicfoundry.com when Vegas 4 ships. This will be the go-to place for scripting info. The cool part is, because scripts are really just text, you'll be able to copy/paste scripts right from the forum threads, so script sharing and debugging will be easy.
We will keep a close eye on the scripting forum and help people get up and running with scripts- like the other Vegas forums, once a critical mass of expertise by the user base is achieved, you'll likely be able to get an answer, if not a complete solution, in a short period of time.
Finally, we are very excited about the potential that application scripting brings to Vegas 4. We hope you are too. It'll take awhile to get rolling, but within a few months I think you'll all be amazed at what application scripting brings to the table.
-------------------------------
Sincerely, SF Engineering
ps: If you disseminate the info above, please post all of it, unmodified.
We've had quite a few people asking about EDLs, OMF, AAF, Vegas-to-whatever project interchange, as well as broader questions about application scripting in general, so I'd like to bring the Vegas user community up to speed and tell you where we're headed with all this.
As of right now (1.17.03) the scripting api and documentation is still being worked on. While still in progress, the architecture is in place to allow project data to be exported and imported, and in addition, many processes will be also able to be automated.
You can get a taste of the automation by running the sample scripts posted on the Vegas 4 beta download page- these scripts will allow some basic process automation, like still image export, adding/removing the timecode filter from all media files, batch rendering and a few more. These samples should give you an idea of the possibilities that application scripting will open up.
-------------------------------
As far as EDLs/OMF/project interchange is concerned, this is important and needs to be stated clearly: Vegas 4.0.0 WILL NOT be shipping with a CinemaTools/AVID EDL manager/Automatic Duck-type plug-in or companion tool. Vegas 4.0.0 will not ship with an OMF or AAF importer/exporter.
Equally important: If you poke around Vegas 4, you'll see that source TC i/o is now in edit details, the TC window plug-in is greatly improved, the media pool has been beefed up significantly, and the scripting engine will allow all of this info (and lots more) to be imported or exported. This means that edls/omf/aaf or whatever will be possible from Vegas 4...but some work needs to be done.
So, a proposition:
If you are....
a) familiar with jscript
b) familiar with EDLs, OMF, AAF
c) familiar with Vegas
d) are possibly interested in discussing working with us on an EDL/OMF/AAF plug-in
...SF would like to talk to you. Contact me directly at drdropout@sonicfoundry.com.
-------------------------------
More about scripts:
Scripting docs will be posted on our website when they are ready.
More sample scripts will be posted on our website when they are ready.
There will be a Vegas scripting forum on sonicfoundry.com when Vegas 4 ships. This will be the go-to place for scripting info. The cool part is, because scripts are really just text, you'll be able to copy/paste scripts right from the forum threads, so script sharing and debugging will be easy.
We will keep a close eye on the scripting forum and help people get up and running with scripts- like the other Vegas forums, once a critical mass of expertise by the user base is achieved, you'll likely be able to get an answer, if not a complete solution, in a short period of time.
Finally, we are very excited about the potential that application scripting brings to Vegas 4. We hope you are too. It'll take awhile to get rolling, but within a few months I think you'll all be amazed at what application scripting brings to the table.
-------------------------------
Sincerely, SF Engineering
ps: If you disseminate the info above, please post all of it, unmodified.