Quickstream fix using vp.vbs doesn't copy BeyondTV meta data from .tp to .ts files

stevehiner

New member
I recently wrote a batch file to do quickstream fix on BeyondTV recordings. I did it so I can launch it using BeyondTV's Archive feature to launch an arbitrary program, passing the current video file path as an argument. It has the nice side-effect of being a suitable drop target for video files and I'm sure I could easily make it a Send To target as well. I'm running VRD TVSuite 3.20.2.629.

Generally speaking it works well except that when I use it on .tp files and have it save them as .ts files the resulting file does not contain the BeyondTV meta data so BeyondTV doesn't recognize the file. If I use the UI to do a quickstream fix it will copy the meta data correctly.

For example, the script ran this:
cscript //nologo "C:\Program Files (x86)\VideoReDoTVSuite\vp.vbs" "G:\Crouching Tiger, Hidden Dragon.tp" "G:\Crouching Tiger, Hidden Dragon.q.ts" \t4
Output complete to: G:\Crouching Tiger, Hidden Dragon.q.ts

The output file is 402KB smaller than the same file processed using the UI. The script processed file ends with a large block of FF bytes whereas the one processed with the UI has actual data in that same location and it ends with the BTV meta data.

I have a small source file and the two output files if it would be helpful for you to look at them. I just randomly recorded 30 seconds of Crouching Tiger, Hidden Dragon - unfortunately it appears it was during a commercial, not during a cool scene like I had hoped it might be.

I have tried it with both \t1 and \t4 and neither one works right. Neither the \t1 version nor the \t4 version will even play in BeyondTV. If you try to play them BeyondTV says that the file is missing or corrupt. Both versions seem to work fine in VRD.

If the answer is "This is fixed in VRD H264" or "I'll fix it but only in the latest version" then that is a totally acceptable answer to me. I've been looking for a reason to need to upgrade anyway and then I could make my script work with more file types.
 
Last edited:

stevehiner

New member
I figured it out after looking at a comprehensive processing and commercial cutting post on the SnapStream forums (http://forums.snapstream.com/vb/archive/index.php/t-38840.html). First of all I was using "\t4" as the arg and it should have been "/t4" but more importantly I needed to pass /d as well.

The command:
cscript //nologo "C:\Program Files (x86)\VideoReDoTVSuite\vp.vbs" "G:\Crouching Tiger, Hidden Dragon.tp" "G:\Crouching Tiger, Hidden Dragon.q.ts" /t4 /d
generates a file with the BeyondTV metadata.
 

dlflannery

Moderator
I figured it out after looking at a comprehensive processing and commercial cutting post on the SnapStream forums (http://forums.snapstream.com/vb/archive/index.php/t-38840.html). First of all I was using "\t4" as the arg and it should have been "/t4" but more importantly I needed to pass /d as well.

The command:
cscript //nologo "C:\Program Files (x86)\VideoReDoTVSuite\vp.vbs" "G:\Crouching Tiger, Hidden Dragon.tp" "G:\Crouching Tiger, Hidden Dragon.q.ts" /t4 /d
generates a file with the BeyondTV metadata.
Just FYI, and for anyone else with similar requirements, VAP (link in signature) can automate QSF followed by ComSkip, with or without queuing the .vprj files for reviewing/adjusting commercial cuts.
 
Top Bottom