Script menu path, symlinks, and you.

Teetow wrote on 9/13/2007, 3:25 AM
In previous Vegas versions, there was an internal path for the script menu that could be changed. This does not work in Vegas Pro 8 (which is expected, as it was an undocumented feature.)

The problem is, I develop scripts for several users and rely on Perforce to distribute them. If I cannot set the default script path to a path within the Perforce structure, I have to fall back on clunky deployment scripts which require extra user interaction.

My suggestion is that Vegas should follow not only links to individual files (shortcut to myscript.lnk) but also to directories (shortcut to \myscripts.lnk) which would be a one-time addition to each client's workstation, and an acceptable solution.

Comments

jetdv wrote on 9/13/2007, 6:26 AM
Vegas Pro 8 now searches through MANY folders for scripts. Can you not just use one of these?



C:\Documents and Settings\<username>\My Documents\Vegas Script Menu\ 

C:\Documents and Settings\<username>\Local Settings\Application Data\Sony\Vegas Pro\8.0\Script Menu\ 

C:\Documents and Settings\<username>\Application Data\Sony\Vegas Pro\8.0\Script Menu\ 

C:\Documents and Settings\All Users\Application Data\Sony\Vegas Pro\8.0\Script Menu\ 

C:\Documents and Settings\<username>\Local Settings\Application Data\Sony\Vegas Pro\Script Menu\ 

C:\Documents and Settings\<username>\Application Data\Sony\Vegas Pro\Script Menu\ 

C:\Documents and Settings\All Users\Application Data\Sony\Vegas Pro\Script Menu\

ForumAdmin wrote on 9/13/2007, 7:20 AM
Issue noted.

Vegas 8 loads application extensions before it scans for scripts. You may be able to create a "bootstrap" extension which checks for script updates and copies or creates links as needed. You may even be able to use p4.net (perforce bindings for .net).
Teetow wrote on 9/13/2007, 12:27 PM
Admin: Good idea, it's definitely a sufficient workaround for now. Can an extension re-scan the scripting menu aswell?

Right now, I'm using the sysinternals' junction utility to replace the Script Menu directory with a junction that references a directory in the P4 repo. It would be a lot smoother to do it in some "official" way, though.

jetdv: The request was to have Vegas search in a custom directory, in this particular case one that is within the Perforce depot directory structure.
ForumAdmin wrote on 9/13/2007, 1:38 PM
Rescanning the script menu is not directly supported in the managed API. Do you really need to push new scripts mid-run?
Teetow wrote on 9/14/2007, 2:16 AM
Nah, just curious.

Since refreshing the scripting menu can be done by a user, I thought it would be a nice feature to add to the "bootstrap"; something like "Refresh MyScripts(TM)" which would do a P4 sync, the appropriate copying / linking of files, and then refresh the script menu.

But that's just sugar anyway =)