Hello SonicPJM


You have mention something about macro recording while before
And its definitely a grate Idea
Qoute:
"Without specifics, I can't give too many how-to details here. But one
general concept I've toyed with for performing macro operations is to
extend on the idea of exporting and importing XML. There's a sample
script that exports an entire project as XML. Something similar can
be done to export just a selected event. Then, perhaps the XML could
be edited to form a template to be used by an import script. The
import script could read the template and "apply" it to any selected
event. The application of the template could be enhanced/customized
by event-specific parameters or be given a GUI to set specific
variables."

Its looks like a very good Idea to start
Maybe as experimental feature
You surly have an access to an all events, why not dump em as xml !!!!
to let as write the script easier

Also I have a question about
Interop.VegasCOM.dll
Interop.VegasCOM.tlb
they are com base ( not DOT.NET )
could they be scriptable? ( if yes how, if no why not )
By the way if you need .chm file for those files
let me know, (very cleanly outlined methods, and very clean doc)

One last question:
Why did you choose DOT.NET framework vs Com
what is particular reason for it?
couz for "com" you could get a third party scripting engine
with all "blows and wisles" ( I think sax have very nice one )

Thanks for your product
Its should I say a very best in its kind.....
I think if you will do it right you can start the next revolution
just like a Micromidia did.....

craziedde

I'm in production of E-learning content delivery and Vegas 4 has been a huge plus for our daily production process. Here's my wish list:

1. in the Capture app, we'd like to b able to place markers on the fly in our capture file. Similar to the way it works in Soundforge including an option to save them as a text file.
2. be able to upload output files to FTP server (if it's not already scriptable).

Thanks.

Thanks for your feedback.

My ExportXML script needs a few updates to be current with the
complete scripting API but I will try to post on the web it soon along
with the ImportXML script (probably after 4.0c is released).

I do not recommend using the VegasCOM stuff directly. That is only
meant to be an internal API used by the scripting objects to
communicate with Vegas. There are many issues you'd need to deal with
which are currently handled by the scripting objects.

We chose to use .NET (VSA) mainly because it gives scripts full access
to all the .NET Framework classes. Clearly, Microsoft is moving in
that direction. From all indications, the old Windows Scripting (OLE
automation, IDispatchEx, etc.) is no longer being developed.

I'm glad Vegas is working well for you.

Adding markers on the fly in VidCap is more of an app feature (which
has been noted). Also (just FYI) we are considering adding scripting
to VidCap. I think that would be a very valuable addition.

The ability to FTP files is there using .NET Framework... Google for
"ftp client .net framework class" and you should find something that
does the trick. You can probably also fire off a command-line ftp
process... I know the version of ftp that ships with Windows has the
ability to execute commands listed in a text file (which your script
can write).

SonicPJM thanks for reply

Any chance of posting XML documentation files produced by csc.exe for assemblies?
I might try to compile a .chm file for it.
It would be a grate help.


Thanks again

craziedde@hotmail.com

Here you go. This is the latest version of the documentation source XML file (corresponds to version 4.0c).

Where do you want me to upload .chm file?

PS please share it with everybody

... with this whole buyout thing... Is Vegas 4.0 going to go away? You say 'future updates', but aren't those going to stop now?

As far as I know, we are proceeding as planned with 4.0c. Obviously,
the deal greatly improves the chances there will be future releases.