I can't take credit for this, I found it as a comment on the associated Youtube video from the tutorial:
"Just wanted to let you know why people have had problem with the script.
When i installed Pismo File Mount Audit Package the default mount path was "C:\Volumes" and in the start .bat file it's pointing to "C:\frameserver\vegas.avs\vegas.avi". If you change those 2 lines in the bat script to "C:\Volumes\vegas.avs\vegas.avi" it should work."
I made the change in the .bat file, and the first time I ran the script, it failed, but then I ran it again and it worked. So then I exited Vegas, came back in, ran it again and it worked again without a glitch. Don't understand why or how, perhaps someone here can shed more light on this?
I'm running it with V12 and HB10.2, but I'm going to try to go back to V13 with this new knowledge and see if it solves the problem once and for all.
Edit: I just came across this on the Pismo support forum:
http://pismotechnic.proboards.com/thread/23/make-v177-mount-same-directory
so it appears the c:\volumes is something new that happened after the original script was written. So I think we can either use the older version of PFMA, or edit the .bat file as instructed by the Youtube video comment.
As indicated in the PFMA changelog:
-- build 174 - 2015.03.25
Removed virtual-mount-point functionality on Windows. Now mounts get a real mount point in the c:\Volumes folder. Mounts now show in the Windows Explorer drive list even if they do not have a drive letter assigned.
Latest:
Newest version of Vegas, Handbrake and Pismo - worked perfectly! Just follow the instructions above and you'll be good to go! If anyone is curious, just see Hetsig's comment on this video:
Happy Handbraking!
"Just wanted to let you know why people have had problem with the script.
When i installed Pismo File Mount Audit Package the default mount path was "C:\Volumes" and in the start .bat file it's pointing to "C:\frameserver\vegas.avs\vegas.avi". If you change those 2 lines in the bat script to "C:\Volumes\vegas.avs\vegas.avi" it should work."
I made the change in the .bat file, and the first time I ran the script, it failed, but then I ran it again and it worked. So then I exited Vegas, came back in, ran it again and it worked again without a glitch. Don't understand why or how, perhaps someone here can shed more light on this?
I'm running it with V12 and HB10.2, but I'm going to try to go back to V13 with this new knowledge and see if it solves the problem once and for all.
Edit: I just came across this on the Pismo support forum:
http://pismotechnic.proboards.com/thread/23/make-v177-mount-same-directory
so it appears the c:\volumes is something new that happened after the original script was written. So I think we can either use the older version of PFMA, or edit the .bat file as instructed by the Youtube video comment.
As indicated in the PFMA changelog:
-- build 174 - 2015.03.25
Removed virtual-mount-point functionality on Windows. Now mounts get a real mount point in the c:\Volumes folder. Mounts now show in the Windows Explorer drive list even if they do not have a drive letter assigned.
Latest:
Newest version of Vegas, Handbrake and Pismo - worked perfectly! Just follow the instructions above and you'll be good to go! If anyone is curious, just see Hetsig's comment on this video:
Happy Handbraking!