postprocessing.bat queues up ffmpeg instead of multiple instances?!

[pvruser]

i just reloaded my XP on a new SATA drive this weekend and after being hit by the DST bug and fixing that i realize now that postprocessing.bat does not execute for multiple recordings at the same time anymore, but instead waits for the current one to finish.
i have 2 tuners and used to do pillar removing with ffmpeg for both finished recordings at the same time on my old setup. since the reload it's just doing one at a time. i have a dual core that's used less than 50% when doing a single ffmpeg and it can handle 2 transcodings, 2 recordings and me watching a HD mpeg at the same time without issues.
no changes in gbpvr other than i had to re-install over the old one obviously but all settings have been kept.

any ideas? could not find anything relevant in the forums...
thanks!

[sub]

i realize now that postprocessing.bat does not execute for multiple recordings at the same time anymore, but instead waits for the current one to finish.

It never did. It has always run these one at a time, based on the assumption that you'd most likely be doing CPU or Disk intensive activity like transcoding or comskipping (where multiple could adversely affect machine performance).

ParallelProcessing.bat on the other hand does run multiple at the same time.

[pvruser]

It never did. It has always run these one at a time, based on the assumption that you'd most likely be doing CPU or Disk intensive activity like transcoding or comskipping (where multiple could adversely affect machine performance).

ParallelProcessing.bat on the other hand does run multiple at the same time.

hmm i know for sure i had 2 ffmpegs going at the same time from postprocessing in the task manager. i'll look into what i may have in the old backup folder from the previous installation that may have been deleted by the new installation (same 0.99.12 though).
i also set the comskip section to ASAP (but that setting was there before) although i'm not using comskip but i understand that its needed to start parallel processing.
are you absolutely sure there's no setting in the DB or the config xml to start postprocessing ASAP when you have multiple recordings done?
i'm confused

[sub]

Ever since the day this feature was introduced it has always run multiple PostProcessing.bat files synchronously. There is no setting that changes this.

You can of course just spawn some other batch file (or ffmpeg process) from your PostProcessing.bat so that the main batch file completes immediate, and starts the next one, which again spawns some other batch file.... in effect running them in parallel.

[pvruser]

Ever since the day this feature was introduced it has always run multiple PostProcessing.bat files synchronously. There is no setting that changes this.

You can of course just spawn some other batch file (or ffmpeg process) from your PostProcessing.bat so that the main batch file completes immediate, and starts the next one, which again spawns some other batch file.... in effect running them in parallel.

i looked through the logs from before the OS reload. the odd thing is that indeed you're right, postprocessing never started for 2 files at the same time - it always waited for the first file to complete before it started the second. what i dont understand is how it was possible to have 2 ffmpeg processes in the task manager. this just feels like the twilight zone :o

i guess i'll just accept this as a fact and maybe do as you said - spawn another process from the batch file. then again it might not be worth the trouble of rewriting and redoing all the logic (shutdown is also included in the conversion)

thanks anyway!

[sub]

what i dont understand is how it was possible to have 2 ffmpeg processes in the task manager

I dont know what you had in your PostProcessing.bat, but if you'd done a "start ffmpeg.exe" in their, then the PostProcessing.bat would have exited pretty quickly while the ffmpeg.exe continued to run to completion.

[pvruser]

I dont know what you had in your PostProcessing.bat, but if you'd done a "start ffmpeg.exe" in their, then the PostProcessing.bat would have exited pretty quickly while the ffmpeg.exe continued to run to completion.

no i avoided that because i needed it to wait until conversion was finished and then check if it needs to suspend the computer (unless there's a recording in progress or to begin shortly or another conversion in progress). obviously i could call the suspend check from a new "encode-only" batch file which in turn would be called by postprocessing but that's probably smth i'll look into when i get the time. for now it works and i guess thats all that matters