View Full Version : VAP not responding
July 21st, 2011, 12:12 AM
All the sudden today my vap started freezing once a file starts to process (still says transferring when it locks). I have to force close to get out of vap. It was working fine just yesterday. I tried a reinstall / update to V .77, restarted pc, etc, i am using .wtv files. Any suggestions on what the problem could be? Thanks.
Edit: Looks like this is happening to only .wtv files. dvr-ms files seem to go through no problem. This is weird as .wtv files have been working for me for the past few weeks. I have tried multiple .wtv files all with the same results.
July 21st, 2011, 12:53 AM
What version/build of VRD are you using? Did you just install a newer version? If so that is a likely culprit. Try doing the same processes manually outside VAP.
Is there anything different about the files having problems from the ones that used to run OK?
VAP will detect stalls of VRD processes and kill the process and put messages in the log. However it takes at least 2 minutes before VAP will decide a process has stalled -- have you waited that long before killing VAP ?
Wait a minute! I just noticed you said it still said transferring. That means it hasn't even started processing the file in VRD so it can't be a stall. A likely culprit now is theTVDB metadata search is failing to connect to the server. Look on the "Other" tab of Advanced Settings. If you have "Stop Monitoring if the TVDB.com is down" checked, that is probably the explanation. Files will stay in the transferring status as long as VAP can't connect to theTVDB.com, and it only retries every 5 minutes once it detects a failed connection. Try checking "Do not do theTVDB.com searches".
If this is the problem there should be some related messages in the log.
July 21st, 2011, 07:37 AM
I have tried using the stop monitoring if thetvdb.com is down option after seeing on the forum that it had helped other out with a similar problem but it gives me the same thing.
The odd thing is that is seems just .wtv files are having this issue.
I am using videoredo h.264 v 4-20-6-619a (been using this version for a few weeks now) .wtv files open fine manually.
Thing is I don't think it is even kicking the files over to videoredo so I don't think stalling is the issue.
Files are identical to those I have been using with vap since I first started using it. Thanks for the help.
July 21st, 2011, 09:41 AM
Just to be clear:
You do NOT want the "stop monitoring if theTVDB.com is down" checked. Having that checked and having theTVDB.com down is what leads to files lingering in the transferring status.
Did you try checking the "do not use theTVDB.com" box?
From your description it doesn't sound like theTVDB.com is the issue. Could you possibly get a copy of one of these files to me? If they are GB size, see if you can edit out a smaller file that exhibits the same problem. I'm willing to download a GB if you're willing to upload it somewhere, however.
One possibility is that the mediaInfo DLL, which is called just before a transferred file is bumped out of transferring status (to new status) is hanging on these files. I've seen this behavior before on a few TiVo files (in Australia IIRC) so the code already bypasses the mediaInfo call for .tivo files. If I have one of your problem files I can run in the debugger and determine exactly where the problem occurs.
If this is the problem I may need to call mediaInfo.dll in a thread so I can kill it if it hangs.
July 21st, 2011, 11:22 AM
I think I may have just been being impatient it is now working but still weird how it is taking so long and at the same time completely locking the program. It never did that before.
On another note I am having a separate issue where vap sometimes does not run the ad scan. It says it does but finishes in only a few seconds. Then when I open it to confirm cuts it shows no marks from the scan. If I rerun the file it works. Again this is only sometimes, id say about 20% of the time. Has anyone else had this issue?
July 21st, 2011, 12:57 PM
You're not seeing any suspicious messages in the log window (or file) about theTVDB failures or VRD process stalls or aborts?
How long are the delays? Could you time a few of them please?
If you have mediaInfo installed, do you get long delays when you run it on the files that have long delays in VAP? In VAP, is the status still stuck at transferring during the long delays? How are the files being deposited into the monitor folder? If the file is slowly being built up there by some other process, it will show as transferring during that time until it's all there. To eliminate theTVDB time outs as a possible cause of your delays, check "Do not use theTVDB.com". The only other possilble cause then is the mediaInfo call.
Apparently AdScan is actually running or you wouldn't have a project file (.vprj) to load, so I have to suspect this is a VRD problem. What happens if you ad scan the same files manually? What size are the files, or better yet load one into VRD, hit Ctrl-L to get file info, copy to clipboard and then paste in a post here.
Attached is test version 0.78.T3 which uses threads to call mediaInfo.dll. The call times out after 30 secs if mediaInfo fails to respond and an appropriate message is logged. To use it, rename or copy off the current VideoReDoAutoprocessor.exe file in your installation folder (just to save it) and substitute the one extracted from the zip. If the message appears we know mediaInfo is the problem.
July 21st, 2011, 01:53 PM
For reference a 1 hour program that worked had a .vprj file size of 6.24kb and one that didn't work was 2 hours long and had a .vprj file size of 2.34kb. I'll get back to you once I run into this issue again.
Powered by vBulletin® Version 4.2.0 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.