Error!Unable to find VASST.scripts.Add Timecode

jtpvidman wrote on 11/17/2010, 1:08 PM
Looking for some assistance. Downloaded and successfully installed trial version of PA 2.0 on Vegas Pro 9.0 64 bit (Windows 7). Docked the application and ran a few test batches. Created a new project to add timecodes to about 10 files. I also created a new preset call "timecode". Process started and completed successfully.

Today I closed the VP 9.0 window that PA used to process the batch. When I launched VP again I received the following message.

Scriptfactory:Internal error! unable to find VASST.scripts.add timecode" .

After acknowledging the error I noticed that the docked PA 2.0 window was completely blank. PA 1.0 still functioned correctly. I uninstalled, rebooted and reinstalled PA 2.0 without success. I noticed that the other programs (i.e. lower 3rd, montage, motion, etc.) all launched successfully within VP. PA 2.0 would not. PA 2.0 would however launch successfully outside of VP. As long as PA 2.0 was docked I received this message.

Haven't tried a reinstall of VP yet because everything else appears to be functioning. Any help would be greatly appreciated.

Comments

JohnnyRoy wrote on 11/19/2010, 9:01 AM
We are aware of this problem and have it fixed in an upcoming update. Send me an email via this forum and I'll get you a link to try out.

~jr
jtpvidman wrote on 12/1/2010, 1:23 PM
JR,

Thanks for the reply but I ended up resolving the issue. I alway suspected it had something to do with the Production Assistant settings file but it appears there were two of them out there. One located in the C:\programs files(x86)\sony\production assistant 2.0 directory and the other one I found I found burried in the C:\users\owner\appdata\roaming\sony\production assistant\2.0 directory. (I'm pretty sure this directory was hidden)

I replaced the Production Assistant settings file in the C:\users\owner\appdata\roaming\sony\production assistant\2.0 with one I found in the \1.0 directory and it fixed the problem.

I haven't been able to replicate the problem since. If there is something you would still like for me to test please let me know. I'll send you my email address.

JohnnyRoy wrote on 12/1/2010, 4:07 PM
That's only going to work until you use the Timecode preset again and then it will break. Trust me... you want the update. Email me for an interim fix. We are still working on the final update code.

~jr