If I convert an mp4 video downloaded from YouTube using the VLC GUI I get a usuable file. VLC displays the parameters used as:
sout=#transcode{vcodec=WMV2,vb=2000,scale=1,acodec=wma2,ab=128,channels=2,samplerate=44100}:file{dst='E:\Delete\TestTarget\blue light gui wmv2 wma2.asf'}
I can display the resulting file using VLC and edit it using Windows Movie Maker.
But if I use Visual Basic Script to do a batch conversion and use the VLC parameters:
sVLCparams = """C:\Program Files\VideoLAN\VLC\vlc.exe"" -I dummy -v " & """" & cFOL & sFileName & """" & " --sout=#transcode{vcodec=WMV2,vb=2000,scale=1,acodec=wma2,ab=128,channels=2,samplerate=44100}:standard{access=file,mux=asf,dst=" & """" & cFOLREN & sFileNameRoot & ".wmv" & """}" & " vlc://quit"
then I get the same size output file but the VBS script generates hundreds of 'vbv buffer overflow' errors. VLC can play the converted file but Windows Movie Maker cannot display the file.
The main difference between the parameters is that the VBS method uses the 'standard' parameter - without this the conversion does not run or causes VLC to crash.
Since I have a lot of files to convert I would liketo get the VBS batch program working. Anybody any thoughts what the difference might be? And whilst I'm asking, how do I know what to set the vb parameter to? Most files are 480 pixels wide.
thanks, Davy