Keeping the console window open after execution has finished

[leke]

I have an app that rips .ts files, but I'm having a problem seeing the the error message ffmpeg is displaying because the console window closes right after the message is rendered. 

If I manually type the equivalent command from the command line, the .ts file rips ok, so I'm guessing it's not the command itself that is the issue. 

How do I get the console window to remain open when running it through my autoIt app? 

Code in question...

Func RipIt($WhereIsFfmpeg, $TsPath)
    ; Creates rip in same folder as original.
    $ffmpeg_command = $WhereIsFfmpeg & " -i " & $TsPath & " -b:v 1200k -vcodec libx264 " & $TsPath & ".mp4" ; The ffmpeg rip settings.
    Run($ffmpeg_command, "", @SW_MAXIMIZE) ; the ffmpeg command.
EndFunc

 Thanks

Source code.exe

[MyEarth]

Check on the help for StderrRead / StdoutRead so you can get the output from ffmpeg command line

P.S. In $ffmpeg_command don't forget the quotes " " if there are space in the path/variable like:

'"' & $TsPath & '"'

 

Edited October 11, 2015 by MyEarth

[leke]

Check on the help for StderrRead / StdoutRead so you can get the output from ffmpeg command line

P.S. In $ffmpeg_command don't forget the quotes " " if there are space in the path/variable like:

'"' & $TsPath & '"'

 

Thanks, I tried the adding quotes first and it ended up being the problem. I did read about the StderrRead / StdoutRead args in the docs, but couldn't figure out what they were supposed to do. I guess I should just add them in to the Run function with the old code and see what happens. 

[water]

Use RunWait. This waits until the called program has finished processing.

[TheSaint]

For Ffmpeg I tend to use the following

Run(@ComSpec & " /c " & 'ffmpeg.exe ' & $parameters, $ffmpegdir, @SW_SHOW)

And while troubleshooting, I use /k instead of /c which then keeps your console window open.

 

Edited October 12, 2015 by TheSaint