files stuck in transferring status

stimpy99

New member
when I move my tivo files into the monitor folder they now remain in a transferring status and do not process.

This began a few weeks ago with a few files and if moved out and copied back into the monitor folder they would process. now no files will process at all.

I also get no starting log file found on every startup and have to re-enter all folder data every time.
Dont know if this is affecting the above or a separate issue.

Was running older ver of VAP, just loaded V1.2 with no difference, still hung.

HP Pavilion AMD athlon 64 x2 5000+ 2.6ghz
4gb ram,
Win 7 home premiun 64bit

Any help apppreciated.
Bob
 

dlflannery

Moderator
OK sub the attached test executable for the ver. 1.20 VideoReDoAutoProcessor.exe in the install folder.
Suggest you first rename the 1.20 executable, e.g., to VAP120.exe, then copy the new .exe in. Obviously VAP should be shut down when you do this.

Before doing the above, delete the VideoFileManager.xml file from your VAP data folder, which will force a cold start where you set the folders. To find the data folder open a command window and type:
echo %APPDATA%\VAP
On win 7 it should be: C:\Users\<username>\AppData\Roaming\VAP where you substitute your login name for <username>

There may be a sizeable delay before all the input files show in the monitored file list on initial startup but they should all show up OK.
 

stimpy99

New member
Hi DL

Thank you.
I repl the exe and del the xml and re-start and put moved files into the monitor folder.
It Help alot. I can now process HALF the files. the other half still in xfer status. Also most of the ok files were in block proc status.
I had to manually un-block.
The half stuck has been about 1 hour so far in that state, will watch.

Also.... is there a way to turn off the file proc notice in the control bar. I cant even type this reply as it keeps blocking all inputs till it goes away.\???

Thanks
Bob
 

dlflannery

Moderator
Please upgrade VAP to Ver. 1.21, just released.
What version of VRD are you running?
What is your process flow? QSF? AdScan? Using Comskip?
Are you using any command-line options?

Can you load one of the "stuck" files directly into VRD? If so hit Ctrl-L and copy the file information into the clipboard using the button provided for that purpose. Then paste it into a post here.

What is the log file saying? Please copy the lines in the log file from the last time you launched VAP til the end and attach or paste into a post here, inside
Code:
 tags.

In Advanced Configuration on the "Other" tab, check "Do not do theTVDB searches" (may not be exact wording).  Then move one or more of the stuck files out of the monitored folder for 30 seconds and then move it (them) back in.  Does that help?
 
Last edited:

stimpy99

New member
V 1.21T1 that you sent me above.. is that the same as 1.21?
I just use VAP to do QSF - Adscan - then move processed. on my .TIVO files.
All that works fine once the files come out of Xfer.
Running in vanilla, no custom setting.
I restarted VAP and moved files back into the monitor folder. worked so far.
I Did not start VAP processing at this point.
Started processing and transferred more files.
All but 2 of 30 files processing now.
Both are files stuck before also.
Tried to load into VReDo and got "End of stream" unable to open file.
Both files had size of 0 bytes so a failed Tivo downlosd. no problem there.

Thanks
I will keep monitoring and update.
Thank you DL
Bob
 

jtcreate

Member
V 1.21T1 that you sent me above.. is that the same as 1.21?
I just use VAP to do QSF - Adscan - then move processed. on my .TIVO files.
All that works fine once the files come out of Xfer.
Running in vanilla, no custom setting.
I restarted VAP and moved files back into the monitor folder. worked so far.
I Did not start VAP processing at this point.
Started processing and transferred more files.
All but 2 of 30 files processing now.
Both are files stuck before also.
Tried to load into VReDo and got "End of stream" unable to open file.
Both files had size of 0 bytes so a failed Tivo downlosd. no problem there.

Thanks
I will keep monitoring and update.
Thank you DL
Bob

Curious. Was there ever a resolution to this? I just came across this problem. I was testing some new .TS files and I have a few stuck in "Transferring status". I'll wrap up and send a couple to you. They're kind of large as they are "Raw" size. These came off of the NextPVR software.
 

dlflannery

Moderator
I didn't see anything left for me to resolve. I have no more information than what you see in the earlier posts of this thread.

Don't send me .tivo files for test unless you want to provide your MAK also. Actually I'm not too keen on having to switch to your MAK anyway. I'm afraid I may screw up tivo decoding with my MAK. I will do it only if it turns out to be the only way to attack an issue.

I assume you are aware of the issues with errors in TS files downloaded from TiVo's. Try loading the files directly into VRD. If it sees problems, then VAP probably will too.
 
Last edited:

dlflannery

Moderator
Additional comment: When VAP detects a new file in the input it immediately runs a VRD COM process to get information (video encoding and width) of that file. If a corrupt file (e.g., a .TiVo TS file) causes that COM process to stall, it might prevent the file from ever leaving the TRANSFERRING status. When you load TS file into VRD, hit Ctrl-L to get the video info, which is an approximation of the COM process that VAP runs.

If this is the problem I could probably program around it by imposing a timeout on the COM process. However, if the file is that corrupt I don't see why you would ever want VAP to try to run VRD processes on it anyway.
 

jtcreate

Member
Additional comment: When VAP detects a new file in the input it immediately runs a VRD COM process to get information (video encoding and width) of that file. If a corrupt file (e.g., a .TiVo TS file) causes that COM process to stall, it might prevent the file from ever leaving the TRANSFERRING status. When you load TS file into VRD, hit Ctrl-L to get the video info, which is an approximation of the COM process that VAP runs.

If this is the problem I could probably program around it by imposing a timeout on the COM process. However, if the file is that corrupt I don't see why you would ever want VAP to try to run VRD processes on it anyway.

I wouldn't in that case. Although its not common, a corrupt .TS file can find its way into the auto process every once in a while. So a safety timeout and method of file ejection is actually a good idea. :)
 
Top Bottom