Using start /low /wait

[zehd]

Why does this not work?

(text is wrapped...)

start /low /wait "C:\Program Files\devnz\gbpvr\Third Party\FFmpeg\ffmpeg.exe" -y -i "%~dpn1.mpg" -f avi -ab 224 -ac 2 -acodec mp3 -vcodec mpeg4 -b %Bitrate% -vtag XVID "%~dpn1.avi"

The batch file is passed a valid filespec and the variable is set to 1400...

If I remove 'start /low /wait' from the line it runs fine, but with it, there's an error about not recognizing the -y (the first item outside the first closed quotes) which I'm guessing means the 'start /low /wait ' command doesn't see beyond the first closed quotes...

Is there someway to close the whole phrase in quotes or brackets or something?

Thanks

[David]

I find that the optional "title" of the process is not always optional. An easy way to deal with the quoting problem is to move your ffmpeg command into a separate batch file so that you run:

Code:

start "ffmpeg process" /low /wait "ffmpeg.bat %1"

ffmpeg.bat:

Code:

cd "C:\Program Files\devnz\gbpvr\Third Party\FFmpeg"
ffmpeg.exe -y -i "%~dpn1.mpg" -f avi -ab 224 -ac 2 -acodec mp3 -vcodec mpeg4 -b %Bitrate% -vtag XVID "%~dpn1.avi"

You might need some minor tweaking to the code above. Seems to me that there was something else required to initiate a batch file from the start command. Also, the "CD" command might need to be broken into two parts:

Code:

c:
cd "\Program Files\devnz\gbpvr\Third Party\FFmpeg"

It also looks like you have %Bitrate% set as a variable that might need to be passed into the child ffmpeg.bat.

[pBS]

if the variable is not set properly it will also bomb..if it's set within the same batch file should be ok..if not that may be your problem..
also, you only need quotes if you use the '%~dpn' etc. cuz when windows and other programs feed a name that requires quotes,they will put them automatically...so %1 doesn't need quotes,[it has them already] but "%~dpnx1" does...[because you've 'interpreted' the input, stripping quotes] for the same filename...

it's assuming your first quote is the window title..
you could use: start /low /wait "" "C:\Program Files\devnz\gbpvr\Third Party\FFmpeg\ffmpeg.exe" -y -i "%~dpn1.mpg" -f avi -ab 224 -ac 2 -acodec mp3 -vcodec mpeg4 -b %Bitrate% -vtag XVID "%~dpn1.avi"
as well....the first quotes is the dos-box's window title..[here blank]

mencoder can specify it's priority in it's own command line so start isn't needed but i like ffmpeg better too..

[zehd]

Awesome... Thanks

[zehd]

During FFmpeg encoding I get these errors every once in a while:

[mpeg2video @ 00659964]invalid cbp at 5 26me=211.9 bitrate= 725.9kbits/s
[mpeg2video @ 00659964]Warning MVs not available
[mpeg2video @ 00659964]concealing 45 DC, 45 AC, 45 MV errors

And at the end I get this:

[mp3 @ 00659964]lame: output buffer too small (buffer index: 195, free bytes: 2109)
frame=79903 q=0.0 Lsize= 533142kB time=2665.9 bitrate=1638.3kbits/s
video:455652kB audio:72896kB global headers:0kB muxing overhead 0.869221%

The resulting AVI seems to play OK in its entirety. But there are little freeze frames once in a while. Are there timing glitches that FFmpeg is working through?

Might this be from the slice and dice of Comclean?