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.@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.
ok, should be ok then. normally it will take a while that's trueSlow 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.
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: 184.108.40.2069 - 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 220.127.116.119 - 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
No the log files you have provided are good.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?
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 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
ok. but i want vap6 to do an adscan. without it it's of no use for me.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.
yes, i always got that....AFAIK whether it's in an .mpg or .ts container doesn't matter...
strange, just tried again and it downloads in about 1 secondEDIT: About an hour now and still just the spinning circle -- giving up.
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.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'.
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.