vp.vbs spelling mistakes

SnoopyDog

New member
There's some minor spelling mistakes in vp.vbs. The wscript.echo one has been there for years, so maybe when you are going over the documentation it could be fixed. Just to avoid scripters wondering why their script's not working if following these usage instructions :)

In new comments at the top:
' Usage: ccript //nolog ScanAdndSplit.vbs <source file> <output folder> [/q]
Probably should be cscript.

In
wscript.echo( " cscript vb.vps <source file/project> <destination file/project> [/qsf] [/p <profile>] [/q] [/na] [/e]" )
b and p has swapped places. Should probably be vp.vbs
 

SnoopyDog

New member
I found an another one in usage instructions.
In
wscript.echo( " cscript vb.vps <source file/project> <destination file/project> [/qsf] [/p <profile>] [/q] [/na] [/e]" )
If using a space between /p and the profile parameter didnt work when invoking batch-mode through comspec command-line. When deleting the space everything went well.
Should read [/p<profile>]
 
Last edited:

Danr

Administrator
Staff member
if using a space between /p and the profile parameter didnt work when invoking batch-mode through comspec command-line. When deleting the space everything went well.
Should read [/p<profile>]
That doesn't seem correct. What is comspec? What is your exact profile name? If it has spaces in it, it should be surrounded in quotes.
 

SnoopyDog

New member
comspec = http://en.wikipedia.org/wiki/COMSPEC
Yes, the profile name is enclosed in quotes.
The profile switch and name I was testing with:
/p "MPEG-2 Transport Stream" ......which equals [/p <profile>]
V.4 had a colon instead of a space between switch and profile name. In V.5 I removed the space and then batch processing worked ok, like this:
/p"MPEG-2 Transport Stream" ......which equals [/p<profile>]

I guess if space follows the /p switch gets interpreted as no profile name.
 
Last edited:

SnoopyDog

New member
Hi DanR!

Had a chance to test your profile syntax you're using for invoking batch mode through command-line more extensively. I now realize why you didn't change it according to my suggestion. However you didn't test it far enough to encounter the bug, which I now think this is all about.

cscript vp.vbs <source file/project> <destination file/project> [/qsf] [/p <profile>] [/q] [</na>] [/e]
It turns out the key seems to be if using the quite mode or not.
Running these lines from the cmd.exe without the quite mode switch, batch processing goes well:
- C:\Program Files\VideoReDoTVSuite5>cscript vp.vbs "D:\TV\test\20140930_17-49-02_Kanal 9_Top Gear - S14E01.VPrj" "D:\TV\test\min.ts" /p "MPEG-2 Transport Stream"
- C:\Program Files\VideoReDoTVSuite5>cscript vp.vbs "D:\TV\test\20140930_17-49-02_Kanal 9_Top Gear - S14E01.VPrj" "D:\TV\test\min.ts" /p"MPEG-2 Transport Stream"
Doesn't matter if there is a space between the /p switch and profile name.

However if running the line with a space between the /p switch and profile name in combination with the /q switch:

C:\Program Files\VideoReDoTVSuite5>cscript vp.vbs "D:\TV\test\20140930_17-49-02_Kanal 9_Top Gear - S14E01.VPrj" "D:\TV\test\min.ts" /p "MPEG-2 Transport Stream" /q
cmd.exe throws the following error and fails to initialize processing:
? Invalid number of arguments - usage is:
cscript vp.vbs <source file/project> <destination file/project> [/qsf] [/p <profile>] [/q] [</na>] [/e]
/qsf = Open file in QSF mode.
/p <profile> = Profile name or path to profile XML file.
/q = Run in Quite mode.
/na = Disable audio alert, overrides default set via Tools>Options>Audio Alerts.
/e = Path strings are escaped.
If removing the space between the /p switch and profile name in combination with the /q switch batch processing is successful.

C:\Program Files\VideoReDoTVSuite5>cscript vp.vbs "D:\TV\test\20140930_17-49-02_Kanal 9_Top Gear - S14E01.VPrj" "D:\TV\test\min.ts" /p"MPEG-2 Transport Stream" /q
So instead of a spelling error it seems you have a bug to work out.
 
Top Bottom