Stopped Working

[Mailman74]

I keep getting this error when trying to load VRDAP. I uninstalled and reinstalled and had no luck. I am using a windows 7 64 bit machine, any suggestions?

[dlflannery]

I keep getting this error when trying to load VRDAP. I uninstalled and reinstalled and had no luck. I am using a windows 7 64 bit machine, any suggestions?
What versions of VAP and VRD are you running? Can you provide a screen capture or the exact wording of the error message you're getting? My development (and primary test) machine is Win7 x64.

Have VAP and VRD been installed on the same user account (logon)? Is it an admin account?

Anything changed that might be connected with this? New version of VRD installed? When you install a new version of VRD you need to run it once "As Administrator" before running VAP. (Right-click shortcut, select Run As Administrator.)

Try renaming your VideoFileManager.xml file and starting VAP. Still get the error? This file is in the VAP data folder. If you don't know where that is, start a command window and enter:
echo %APPDATA%\VAP
If the problem is now gone, please zip the xml file you renamed and attach it to a post here so I can examine it. Otherwise, delete any xml file VAP may have just created and rename the first one back to VideoFileManager.xml.

Is it possible your .NET Framework 2 install has been corrupted or removed?

[Mailman74]

Seems like renaming fixed it.

[dlflannery]

Is there a stalled files subfolder of your Monitored folder? According to your xml file there were three video files parked in that folder waiting to be retried because they stalled in VRD processing. This should not cause the problem you had but it does indicate VRD is stalling on your input files and that problem should be addressed. (Try running the files through QSF in VRD manually, without using VAP.)

I can't see anything wrong with the xml file so that probably means you are going to have this problem again. One thing that may be questionable is using a network folder for your monitored folder. If the problem returns, try using a local folder (you may have to rename the xml file again to get VAP going). You are configured to delete input files when done processing so that should eliminate any concern about disk space used on the local folder, I would think.

If the problem returns, even when using a local monitor folder, please give the version numbers of VAP and VRD that you are using. Also, do any log messages get saved in the log before it crashes? And please furnish either a screen capture or the exact wording of any error message.

[Mailman74]

Ok I thought it was all working. Now I do not get the awaiting cuts option it just goes to complete and never moves the SQF file.

[dlflannery]

Is your configuration exactly the same as the xml file you sent before?
Have you tried making your Monitored folder on a local drive rather than the network share?
Are you sure you are selecting the file in question in the Monitored Files list when you say it is completed rather than awaiting cuts?

[Mailman74]

Is your configuration exactly the same as the xml file you sent before?
Have you tried making your Monitored folder on a local drive rather than the network share?
Are you sure you are selecting the file in question in the Monitored Files list when you say it is completed rather than awaiting cuts?

Yes configuration is the same I had only changed the name.

I have changed the folders to the local drive on my pc.

I select the file that says complete. When I did select the only file saying awaiting cuts I applied cuts but the file never got moved to complete folder.

http://i1245.photobucket.com/albums/gg594/Mailman74/ScreenShot005.jpg

[dlflannery]

I think your problem is because the free version of Comskip distributed with VAP is not intended for WTV (or H.264) file processing. If fails immediately and produces no project (.vprj) file. I guess you didn't notice the message that pops up when you put the mouse pointer over the Use Comskip for AdScans check box in Default Settings. ;) Currently there also are problems with the donor version, see details below.

Just FYI, here are the steps for what you are doing (when Comskip DOES work properly):

When a file goes to AWAITING CUTS status you should:
1. Stop VAP processing (preferably after it is done processing other files).
2. Select the file.
3. Click the Run VideoReDo button.
4. Review and adjust cuts in VRD.
5. Save the file uising File Menu -- Save Project <project name as loaded>
(Not save file as and Not Save Project As)
6. Close VideoReDo
7. Start VAP processing.

VAP should then run VRD to save the final cut file in output folder.
If you don't take at least 30 seconds in step 4, VAP won't do anything after step 7. In which case just repeat the sequence, only you won't need to spend at least 30 seconds in step 4 this time.

Another problem that can cause this behavior is that ComSkip fails to create a .vprj file. What version of ComSkip are you running? Is it the version distributed with VAP or have you subbed in a Donor version? I see you are processing WTV files. The free version of Comskip distributed with VAP will fail on that file type, per design. Actually the donor version will fail too by running but producing invalid .vprj files that give an error when loaded into VRD, until VRD and Comskip both make some changes. See this thread on the Comskip forum for more details:
http://www.kaashoek.com/comskip/viewtopic.php?f=5&t=1147&sid=d0395400fa2daff77c7608e8c4a7d4fe
If you watch the log window while Comskip is running, you can tell if it fails on your file because the time lapsed between starting and finishing Comskip will be very short. Also, if Comskip ran properly there should be a .vprj file for the file being processed located in the output folder (not the tempQSF folder) when the file is in AWAITING CUTS status.

Run your process with Use Comskip Ad Scans unchecked (i.e., using VRD Ad Detective) and see if that makes it work. If it works, that also makes Comskip the suspect.

If you continue to have this problem even using VRD Ad Detective, please cut the section of the log file convering all processing for a failed file and paste or attach here. All processing means from start of QSF to whatever is the last log entry for that file. You might want to uncheck Delete Files and use the reset button so you can make VAP work on just one file of interest and repeat using Comskip then using Ad Detective.

I'm going to think about detecting which version of Comskip is present and not allowing comskip to run on anything but MPEG2 files when the free version is in use. (VAP defaulted to Ad Detective for non-MPEG2 files until recently when users wanted to be able to use the donor version on other file types). I should be able to detect comskip failures by checking for the presence of the .vprj file too.

[Mailman74]

Ok I was using the early donor release comskip before with success. But I did re install the new version of VRDAP and must have forgot to extract the donor version of comskip. I really appreciate your help and explanation about what is going on.

One more thing I am trying to figure out. I used VRD batch program to process a few shows. Now I have a vrpj file and wondering what I should do next.

[Gripweed]

Ok I was using the early donor release comskip before with success. But I did re install the new version of VRDAP and must have forgot to extract the donor version of comskip.

If you are using the donor version of Comskip and you go to load up a new version of VAP, it will ask you if you want to load in the VAP version of Comskip. Just say No and VAP will continue to use the donor version of Comskip.