How can we open a separate VEGAS with script and run a script on that.

iEmby wrote on 7/16/2024, 11:10 PM

suppose u are working in VEGAS on a project.
you have a nested project on current project.
now u want run a script on you nested project without closing active project and without manually open nested project.

this will clear you

i want when i press once 'Collect Project Media' it should collect all media first then it should open those nested timeline automatically and run 'Collect Project Media' again on them them come back on active VEGAS after collecting all media from all nested timelines.

It should be done in one script RUN.

for checking my MiniTools scripts

https://www.vegascreativesoftware.info/us/forum/vegas-pro-scripts-collections-share-your-script-here--145667/#ca916979

Comments

jetdv wrote on 7/17/2024, 9:20 AM

You can certainly automatically run a standalone script when starting VEGAS. You can't run an embedded script in a custom command, though. To run a script automatically when starting VEGAS, add a "-SCRIPT:" command followed by the path to the script you want to run - for example:

"C:\Program Files\VEGAS\VEGAS Pro 21.0\vegas210.exe" -SCRIPT:"C:\Program Files\VEGAS\VEGAS Pro 21.0\Script Menu\ImportScript.cs"

iEmby wrote on 7/17/2024, 9:56 AM

You can certainly automatically run a standalone script when starting VEGAS. You can't run an embedded script in a custom command, though. To run a script automatically when starting VEGAS, add a "-SCRIPT:" command followed by the path to the script you want to run - for example:
"C:\Program Files\VEGAS\VEGAS Pro 21.0\vegas210.exe" -SCRIPT:"C:\Program Files\VEGAS\VEGAS Pro 21.0\Script Menu\ImportScript.cs"

its looks like so complex..sir for me atleast.. i am droping this idea.. then..

bvideo wrote on 7/17/2024, 11:31 AM

Is the Project ReadProject(path) API a useful starting point for opening an existing project while processing an already opened project? Note that we are probably operating on 'vegas.Project' when we are navigating all the elements of the initial script or command. So we might need to refactor some existing code to refer to an arbitrary Project rather than the singular vegas.Project.

Note that nesting is a potentially recursive process, i.e. that a nested project might have a nested project, and so on.

zzzzzz9125 wrote on 7/17/2024, 12:32 PM

Is the Project ReadProject(path) API a useful starting point for opening an existing project while processing an already opened project?

@iEmby I would like to ask the meaning of "collect" first. If the script only needs to read the media paths in the nested project and copy them to somewhere you want, and doesn't need to replace the media files in the project, then ReadProject(path) is a good idea. Otherwise it might not be. I've wondered a similar question about whether I can edit other projects without actually opening them, but from my personal understanding, no. You can read the contents of the projects, but when it comes to editing, Vegas Pro will throw errors.

For a single project, if you put all the files it refers to in the same directory as the project file (not subdirectories), the project can read them, but then you're not actually "collecting" them. ArchiveProject(String fileName) does the same thing.

In this case, it's recommended to use OpenFile(String fileName), which will close the current active project, but you can open it later.