trans2mvp.bat not always running.

[cakes]

Hi,

After my upgrade to 99.12, I discovered that trans2mvp.bat is not always called as expected.

In my config.xml, I have the following lines:
<MVPTranscodeUsingFFmpeg>false</MVPTranscodeUsingFFmpeg>
<MVPTranscodeUseFFDSHOW>false</MVPTranscodeUseFFDSHOW>

So when I play an .avi, my trans2mvp.bat is running as expected (I use ffmpeg for transcoding in my trans2mvp.bat). But when I then stop the playback and try to watch another .avi while the transcoding of the previous .avi is still busy, trans2mvp.bat is not called anymore.

Why? Is that because gbpvr detects another ffmpeg process is still ongoing?

[pBS]

try putting "taskkill.exe /IM ffmpeg.exe" before your ffmpeg line to kill any existing ones if you start another...
[i believe taskkill.exe comes with windows or is freely available,by MS]

also, possibly just putting "start /b /w "" ffmpeg.exe etc etc..." might kill ffmpeg when gbpvr kills the command window..
would be a better fix if it works..

and be sure to check if the cmd.exe window is closed at all..

[cakes]

thanks pBS

kill any existing ones if you start another..

I already did that in my script (although with another utility i found somewhere)...

I also discovered that my trans2mvp.bat does start the second time, but it does so two minutes after I started the 2nd avi in the gbpvr/mvp interface.

when checking the active processes it seems that trans2mvp.bat is launched with low priority. Also it seems that the trans2mvp.bat remains active. Both of these could cause the new instance kicking in late.

Could the way trans2mvp.bat is called have changed in one of the previous versions?

[zehd]

thanks pBS



I already did that in my script (although with another utility i found somewhere)...

I also discovered that my trans2mvp.bat does start the second time, but it does so two minutes after I started the 2nd avi in the gbpvr/mvp interface.

when checking the active processes it seems that trans2mvp.bat is launched with low priority. Also it seems that the trans2mvp.bat remains active. Both of these could cause the new instance kicking in late.

Could the way trans2mvp.bat is called have changed in one of the previous versions?

Hey Cakes. I think you nailed it. Using the batch files, will have trouble because of the priority. That's why ZProcess works a little better in this case. It monitors itself and only launches processes in Below Normal priority, so that other processes will function well two.

Yes, when you cancel a transcode, GB-PVR should close the current transcode window. And it mostly does. It could have something to do with not using the 'call ffmpeg' mechanism, but rather, GB-PVR may leave the trans2mvp.bat to its own devices...

I suspect that because the first window is still transcoding, and using CPU, when the second widow is called, it's unable to run the taskkill in a timely fashion

[sub]

Could the way trans2mvp.bat is called have changed in one of the previous versions?

I'm not aware of anything that has changed on this front. I'm sure its just the CPU usage thats causing this delay.

[cakes]

Hey Zehd, Sub

Thanks for your answers, but I am still puzzled by the reason why. I had the script running smoothly for half year (gbpvr 95.x). Some time ago I did a complete reinstall of my PC, with a fresh install of 99.12 and now it doesn't work anymore...

It is a script that I put a LOT of effort into, so it's hard to let go. But maybe I should start some reading on the wiki to see what zprocess has to offer....