VAP6 - TVSuite 6 Auto-Processor Program

dlflannery

Moderator
@turas
Thanks for the detailed info that allowed me to track down this bug quickly!

Beta version 1.0B5 has been released with the fix. See first post for download.
 

turas

New member
@dlflannery thanks, seems to work better now!

one more thing i notice is, that when the video is in status "waiting for cuts", and i open / save the project in vrd6, and then close vrd6 again, the video stays in status "waiting for cuts".
when i open / save / close once again, all is fine.
 

dlflannery

Moderator
@dlflannery thanks, seems to work better now!

one more thing i notice is, that when the video is in status "waiting for cuts", and i open / save the project in vrd6, and then close vrd6 again, the video stays in status "waiting for cuts".
when i open / save / close once again, all is fine.
Slow down! For VAP to detect the project file had been edited, I had to use a time-stamp interval. Just keep VRD6 open a little longer before saving the project, something like 30 seconds should be OK. If you spend any time reviewing/adjusting the cuts that should suffice too.
 

turas

New member
Slow down! For VAP to detect the project file had been edited, I had to use a time-stamp interval. Just keep VRD6 open a little longer before saving the project, something like 30 seconds should be OK. If you spend any time reviewing/adjusting the cuts that should suffice too.
ok, should be ok then. normally it will take a while that's true :)
and if the implementation didn't change from vap5 it has never posed a problem to me.
thx
 

turas

New member
hi again.
with avc-file recordings all seems to be fine for me now.
i got a next problem with recordings of type ts/mpeg2.

first, it seems that vap6 is always selecting "program stream" instead of "transport stream".
qsf runs and creates a mpg file (which i don't want - i would like everything to stay in ts) in the designated temp qsf folder.
then ad scan tries to start, but fails because it can't find the input file in exactly the same temp qsf folder...?

see files attached and log below, hope they will help identify the problem...

Code:
20.11.2019 07:36:49 No command line arguments found
20.11.2019 07:36:49 Started program -- VideoReDo-AutoProcessor for TVSuite6 Ver. 1.0B5
20.11.2019 07:36:49 Using configuration/data file: C:\Users\Werner\AppData\Roaming\VAP6\VideoFileManager.xml
20.11.2019 07:36:49 Comskip files present, so Comskip commercial detection is enabled
20.11.2019 07:36:49 Comskip is Early Access (donator) version
20.11.2019 07:36:49 VRD install folder: C:\Program Files (x86)\VideoReDoTVSuite6\
20.11.2019 07:36:49 Read 0 input filename metadata parsing template(s)
20.11.2019 07:36:49 Read 0 title translation data lines
20.11.2019 07:36:51 Running VRD version: 6.60.5.809 - Nov 16 2019
20.11.2019 07:36:51 Smart QSF is enabled
20.11.2019 07:36:55 Read 0 profile match list items
20.11.2019 07:38:03 New output profile selected: HEVC-2-TS (TS)
20.11.2019 07:38:37 0 file ignore keys were read
20.11.2019 07:38:37 0 file wildcard match keys were read
20.11.2019 07:38:37 Read 0 input filename metadata parsing template(s)
20.11.2019 07:38:37 Read 0 title translation data lines
20.11.2019 07:38:37 Read 0 profile match list items
20.11.2019 07:38:37 Metadata-based templates:
20.11.2019 07:38:37   Series Output Folder = ""
20.11.2019 07:38:37   Series Output file = ""
20.11.2019 07:38:37   Movie Output Folder = ""
20.11.2019 07:38:37   Movie Output File Name = ""
20.11.2019 07:38:37   Title = ""
20.11.2019 07:38:37 720 is video width for: hawaii five-0 - test.ts
20.11.2019 07:38:37 MPEG2 is encoding for: hawaii five-0 - test.ts
20.11.2019 07:38:37 Started QSF, input: hawaii five-0 - test.ts
20.11.2019 07:38:38 Using filter dimensions from MediaInfo: 720 X 576

20.11.2019 07:38:38 Using profile: Program Stream

20.11.2019 07:38:38 VideoReDo said: INFO: starting QSF6.vbs
20.11.2019 07:38:40 VideoReDo said: INFO: VideoReDo version 6.60.5.809 - Nov 16 2019
20.11.2019 07:38:41 VideoReDo said: INFO: VideoReDo opened file/project: Y:\00_Recording-In\hawaii five-0 - test.ts
20.11.2019 07:38:41 VideoReDo said: INFO: Applying QSF filter: 720X576
20.11.2019 07:39:07 VideoReDo completed QSF on input: Y:\00_Recording-In\hawaii five-0 - test.ts
20.11.2019 07:39:07 720 is video width for: hawaii five-0 - test.ts
20.11.2019 07:39:07 MPEG2 is encoding for: hawaii five-0 - test.ts
20.11.2019 07:39:07 Started Ad Scan, .vprj only, input: hawaii five-0 - test.ts

20.11.2019 07:41:08 File: E:\VideoOut\01_fixed\hawaii five-0 - test.mpg unavailable for 2 minutes
20.11.2019 07:41:08 Ad Scan canceled: Input file not found: E:\VideoOut\01_fixed\hawaii five-0 - test.mpg
 

Attachments

dlflannery

Moderator
@turas
I can't duplicate your problem. I created a .ts mpeg2 input file with the exact same name as yours.
Process flow was QSF then AdScan (not Comskip) to .vprj only.
You are apparently using an HEVC output profile that you created, which I of course don't have. So I created a profile by starting with the built-in Transport Stream profile and just changing the output codec from match source to HEVC.
Everything ran OK for me.

It looks like you are using a network location for your folders. This might be the problem. Try assigning a drive letter to each network folder you use. Sometimes that helps. To completely rule out this potential issue, try making all your VAP6 folders local (temporily).

What concerns you about using an mpeg2 PS temporary file rather than an mpeg2 TS file? AFAIK that should pose no issues.

Your attachment appeared to be empty(?).
 

turas

New member
sorry for the empty attachment - added it now.
only network-folders are "monitor folder" and "processed inputs to" folders - and they are assigned a drive-letter (y: )
qsf and output folders are local (on e:, n: )

my first question is why "Program Stream" and not "Transport Stream" is selected? the source is a "ts - transport stream" and not a "mpg - program stream".
it's not about liking or not - it's about understanding why this happens. how is the selection of profile made?
(and btw... with avc files the ts uses the correct profile and it stays a ts)

and the main-question of course is that the temp file (in unexpected mpg-format) is correctly created by qsf (on e: ) ... but then the ad-scan step doesn't pick it up from there...

do you have vrd5 and vrd6 and vap5 / vap6 on your test-system?
i still have both installed to be able to switch back to my "old workflow" in case of problems...
 

Attachments

dlflannery

Moderator
The use of .mpg instead of .ts container for a mpeg2 video in a temporary QSF'ed file is a non-issue IMHO, unless you can identify a specific encoding issue that would apply. It's done that way because doing it another way would needlessly complicate the code logic, which is complicated enough already. The final output file container and codec will be determined by the Output Profile you have selected, which is HEVC-2-TS according to your log excerpt.

The failure to find the temp file is something I can't debug since it doesn't happen when I duplicate your setup (AFAIK) on my system.

I also have both 5 and 6 versions of VAP/VRD installed.

When your VAP6 failed to find the temp .mpg file, did you notice whether that file was actually present on the TempQSF folder?
 
Last edited:

turas

New member
Yes, the temp file is already created and available in the tempQSF folder when AdDetect step is starting.

Any additional logging, etc I could do?
 

dlflannery

Moderator
Yes, the temp file is already created and available in the tempQSF folder when AdDetect step is starting.

Any additional logging, etc I could do?
No the log files you have provided are good.

Maybe it would help if I had your actual input video file and the output profile you're using.

Export the Output Profile and zip/attach here.
Hopefully you can provide the input file, or another that has the same issue, some way or another.
 

dlflannery

Moderator
@turas
To explain why an mpeg2 encoding is used in the temp file, see this post:
In particular note this:
If you want to use QSF and recode at the same time it's best to just set the profile to Force Recode and set the bitrates manually. Alternatively you can QSF to a file of like type first, which will be fast, then recode the fixed file using the regular mode without the QSF
This is the case you have -- going from an mpeg2 input to an HEVC output. The .mpg temp file (containing an mpeg2 video) is the "file of like type". AFAIK whether it's in an .mpg or .ts container doesn't matter. After you review/adjust cuts the final file will be output with HEVC video in a .ts container, per your selected Output Profile.

If you had chosen to only QSF, with no AdScan, VAP6 would perform a "smart" two-step QSF. It would first QSF to a temporary file containing mpeg2 video, then recode that file to gen the output file per your HEVC profile.
 
Last edited:

turas

New member
If you had chosen to only QSF, with no AdScan, VAP6 would perform a "smart" two-step QSF. It would first QSF to a temporary file containing mpeg2 video, then recode that file to gen the output file per your HEVC profile.
ok. but i want vap6 to do an adscan. without it it's of no use for me.

...AFAIK whether it's in an .mpg or .ts container doesn't matter...
yes, i always got that.

matter of fact i have never cared about which type the temp-file is.
i'm just thinking that the type of temp-file - which is chosen by vap6 automatically - could be the source of the problem.

i did another test with one avc-testfile and one mpeg-testfile (see linked attachment).

i set all directories to the same local drive (e: )
to rule out problems with my transcoding output profile, i selected "Program Stream" as output profile.

the avc-testfile is successfully qsfed and adscanned.
the mpeg-file is failing the adscan.

i've also included the source-files and output-profiles this time.
let's see if this allows to reproduce the problem.

since the zip is too big to be attached directly i uploaded it here: HVCvsMPEG.zip
 

dlflannery

Moderator
@turasI'm trying to get zip stuff now but a couple of initial comments:

i wasn't implying that you should only QSF rather than AdScan -- just explaining the use of temp files in either case.

The "Program Stream" output profile built into TVS6 chooses an output codec of "match source". Thus you can't use it to recode an input containing mpeg2 to an output containing HEVC or H.264. Maybe you know that, just sayin'.

The gofile page you linked is just sitting there with a spinning circle for about 10 minutes now. There is a small amount of spikey internet activity but averaging only roughly 10 - 30 Kbps. I suspect way to low for a reasonable download time. (My internet tests 100 Mbps).

EDIT: About an hour now and still just the spinning circle -- giving up.
 
Last edited:

turas

New member
EDIT: About an hour now and still just the spinning circle -- giving up.
strange, just tried again and it downloads in about 1 second :(
will try to find another upload-service

The "Program Stream" output profile built into TVS6 chooses an output codec of "match source". Thus you can't use it to recode an input containing mpeg2 to an output containing HEVC or H.264. Maybe you know that, just sayin'.
thx for the hint. i do not really plan to use the "program stream" output profile. just used it to have a different one than my personally created selected.
 

dlflannery

Moderator
hope this one is working: HVSCvsMPEG.zip
It looks like the problem is with your HEVC-2-TS output profile. The error is TVS6 failing to save the file with that profile, not with failure to find the temp file. (Actually the log error complains the OUTPUT file is missing.) I am attaching the exported HEVC profile I created just starting with the built-in Transport Stream profile and changing the Output codec from "Match Source" to "HEVC". With this profile both the very short "hawaii 50 - mpeg test.ts" file you sent, and another larger mpeg2 TS file I created, process OK. With your profile, either file leads to failure.

You can verify this by taking the .vprj file created and reviewed in VAP6 (i.e., file status = "CUTS REVIEWED"), and load it manually into TVS6, then try to save the video using your profile. I haven't made a detailed comparison of the two profiles and don't know what the critical difference is.

It may be there is something about your profile that needs more than a minute of input to work on. My test file is only a minute long. (And yours is only 2 seconds.). Might be worth trying it with a longer video, although you probably have done that already.
 

Attachments

Last edited:
Top Bottom