Automatic QuickStream Fix Processing for VideoRedo Plus 2

Posted by JD 04/02/2010 at 09:08

Here’s a little program that automates Video Redo Plus Quick Stream Fix, QSF, processing.

Here’s the comment header:

;#########################################################
;
; Purpose:
;     This AHK script accepts an input file (usually .dvr-ms)
;     and passes it to VideoRedoPlus to manually perform 
;     a process known as QSF - QuickStreamFix using the default
;     settings.
;     The Input file location can be anywhere.
;
;     The Output file location is set by your last manual use
;     of the QSF process (it may not be what you want).
;     
; Usage:
;     Drag and Drop a media file onto the QSF.ahk script.
;     Don't touch your PC until the processing begins.
;     
; Comments:
;     I wish the command line version of QSF worked as advertised.
;     It never did for me.  Only this manual method worked to 
;     remove the resized frames from .dvr-ms files.  .wtv files 
;     may or may not work; sometimes they do, sometimes they don't.
;     This script works ony Windows7 x32 Ultimate.
;
;     Here's the method that didn't work to create the desired output as reference.
;     cscript //nologo "C:\Program Files\VideoReDoPlus\vp.vbs"  %1 %1-qsf.mpg /t1 /q

; Known Issues:
;     1) The default settings for QSF are used. This may not be what you want.
;     2) Sometimes the output filename defaults to an 8.3 format for some unknown reason.
;     3) After running the process, the state of a few keyboard keys appear
;     to be left in bad states. Currently, I manually press the <cntl>, <alt>
;     and <caps lock> keys to for a reset of the states.
;
; Author:
;     JDPFU.com - 3/2010
;
; Tested With
;     Windows7 x32 
;     VideoReDo Plus 2.5.7.604
;     AutoHotKey v1.0.48.05
;
;#########################################################

At this point, I’m not releasing the source, just the compiled AHK binary. The link to the file is in my RSS feed (publishing system limitation), so you’ll need to subscribe to get it.

There are assumptions like the path to your installed copy of VideoRedo Plus. Now, it must be here:
“C:\Program Files\VideoReDoPlus\VRDPlus.exe”

Why bother with this?

In my Windows7 Media Center setup, most of the created files change resolutions in the middle. That prevents other post-recording processing from working like commercial cutting. I’ve written about the detailed process to convert files already. Here’s a quick overview as a reminder

  1. Move all the .wtv files from the Recorded TV location to a faster drive with LOTS of free storage
  2. Convert all the .wtv files into .dvr-ms files
  3. Run this QSF process on each as described above to output .mpg files; verify the output is reasonable
  4. Run each .mpg file through comskip to mark commercial locations and create a .vprj file.
  5. Manually open the .vprj file with VRD, validate/correct commercial locations, save to .mpg
  6. Perform any other post-processing desired like transcoding to x.264 with cropping and scaling.

Note that you may still need to manually run the QSF process for some files when the default settings determine the wrong resolution. The best way that I know to see if I’m happy with the result is to check the output file size. It should be close to the size of the input file or within, say, 10% smaller or larger.

Feedback?

Let me know if you have any issues beyond those in the comments above. You shouldn’t need to have AutoHotKey installed for this to work. It should be self contained, but you must have VideoReDo Plus installed. I’ve never used VideoRedo Suite, so it won’t work with that version. Also, there’s no reason to believe it won’t work in WinXP and later platforms. I don’t know about x64 platform compatibility.

Future Plans

At some point, I plan to release the source script under GPL v2 license. I’ll probably merge a few other scripts used in the process together into a single 100% automatic move, convert, qsf, comskip process. I have automated each part and just need to build a script to put them all together. Scripting on Windows really sucks when compared to the power on *nix systems.

Trackbacks

Use the following link to trackback from your own site:
https://blog.jdpfu.com/trackbacks?article_id=578

  1. JD 04/02/2010 at 16:34

    I fixed the need to manually toggle keys after the program ran. All better now.
    Also, here’s a link to the file

  2. JD 04/09/2010 at 08:03

    Over the last week or so, I’ve created a perl script to automate steps 1-4 above. It has been stable enough to setup as an automatic scheduled task every few hours. It hasn’t been 100% perfect, but there have only been a few failures usually when a prior run locked up in VRDP and didn’t complete. All later runs seem to have issues when that happens. I’ll probably just reduce the scheduled runs to happen twice daily.

    Why did I use Perl? That’s my hammer. It was a fairly trivial install of Strawberry Perl on Windows7, then almost everything sorta … worked. Finally found a use for Notepad+ too. If there is any desire to have the scripts, let me know. It is coded so that beginning from any step is possible. If the WTV conversion completed, it will skip that and continue from there. Same for running comskip.