Problem with QSF not using QSF output for Ad Scan

#1
Using VAP 1.3.5, VideoRedo on 3.10.3.629, both running on Windows 10 Professional. Files processed by VAP are generated from Plex DVR and stored on NAS. When watching processing last night, I noticed in the logs that when I run QSF, VAP shows the proper .TS file for QSF. I see it create the proper MPG file in the Temp folder I have created. But when Ad detection starts, I want it to use Comskip. (testing to see if Comskip works better than Ad Detective)

It tells me the file type is not compatible with Comskip and reverts to Ad Detective. I started looking into this and found that instead of VAP feeding Comskip the MPG that QSF created, it is feeding it the original .TS file instead according to the VAP logs.

Is anyone else seeing this? Or am I missing something or doing something wrong?

Thanks,

David
 
#3
I don't run VRD versions other than TVS Suite 5 and I don't fully understand your issue. However I believe I found something in the code that could cause a problem similar to what you describe. I've made a fix (which I can't test because it doesn't impact the VRD version I run). I've supplied the test executable in VAPexe136T2.zip, which you can download here:
vap.videoredo.net/VAPexe136T2.zip
This is not an installer, just substitute for your VideoReDoAutoProcessor.exe file.
 
#4
I don't run VRD versions other than TVS Suite 5 and I don't fully understand your issue. However I believe I found something in the code that could cause a problem similar to what you describe. I've made a fix (which I can't test because it doesn't impact the VRD version I run). I've supplied the test executable in VAPexe136T2.zip, which you can download here:
vap.videoredo.net/VAPexe136T2.zip
This is not an installer, just substitute for your VideoReDoAutoProcessor.exe file.
Giving it a try now- have a larger file to process so it'll take a while.

Thanks,

David
 
#5
Giving it a try now- have a larger file to process so it'll take a while.

Thanks,

David
Gave it a try, and Comskip ran this time- however I think the .TS file is being used still rather than the .mpg that QSF is generating based on the logs. I've attached logs here so you can see what I'm seeing.

Note where it says in the log "Started ComSkip detection followed by autocuts, input: KUSI News at Ten (1999) - 2017-12-22 00 00 00 - Episode 12-22.ts", followed by
"VideoReDo completed Comskip ad detection on input: \\N5550\_NAS_Media\PlexDVR\Temp Processing\KUSI News at Ten (1999) - 2017-12-22 00 00 00 - Episode 12-22.mpg"

I can't tell if I'm ending up with the correct .mpg file as my finished output, or with the original .ts file.

Hope that helps make things clearer?

David
 

Attachments

#6
It's doing the right thing. In the one log line it's referring to the original input (.ts) file name. In the other one it's referring to the QSF'ed temp file name (.mpg) that was input to Comskip. I verified this by examining the code and the files produced when I ran a similar test case.
 
Last edited:
#7
And a Merry Christmas and a Very Happy New Year to you. It amazes me here how quick and helpful here on these forums are and have been for many years. Your add-on is incredible and is much appreciated.

HO HO HO

John
 
Top