d2v fails at times. [Archive]

fasttoon

27th January 2008, 00:44

I wasn't sure how to make the title.

I'm using dgindex, avisynth and virtualdubmpeg2.

The d2v files break at various times. either after I generate it, during setting up avisynth or during encoding. Most times it works fine and everything completes nice and easy, other times when the computer is doing other stuff it breaks the d2v file, sometimes it just breaks.

I don't know where to look as to why this is happening, btw this is something ongoing on 3 of my computers, all set up differently, all running winxp, all have the current versions of the programs.

Sometimes a simple reboot and resetting the status in job control is all it takes, other times I have to rerun dgindex all over. Sometimes I have to run it up to 5-6 times to finish my encoding most times just initially and the encodes are done.

btw when it breaks all the d2v files break, I might queue up 10 jobs and run it overnight and in the morning I'll see for example from job 5 on it's status is errors. Thats when I either reboot and hope it fixes itself or I run dgindex for all of the unfinished jobs and reset job control and it completes but other times I have to keep doing over and over and over.....

I'm frustrated, any help will be appreciated.

Any information needed to diagnose this can be provided.

Thanks for any help.

mitsubishi

27th January 2008, 01:36

Sounds really odd. On 3 different machines... Do these have something in common (like antivirus or dubious "memory cleaners").

i would say what makes you sure it is dgindex/dgdecode, but you say it actually sometimes damages the d2v file? Surely DGdecode opens the file in read-only mode. Post a broken one.

You have just one pair of index/decode in the plugins folder?

Guest

27th January 2008, 02:27

@fasttoon

Your trouble report is too vague to answer. What exactly do you mean by "the d2v files break"?

What job control are you talking about? DGIndex has no job control.

fasttoon

27th January 2008, 07:41

ok, understand, what do you need from me?

and job control is in virtualdubmpeg2 so I can queue up d2v projects for encoding.

as for the different machines, yes they do have a lot of similar and/or same programs running, like winxp sp2 updated usually every 3-6 months (different times so each one usually doesn't have the same updates), sygate firewall, avira antivir, no-ip client, winvnc, a few more stuff but after that it's different, like the media players are varied like vls, mpc, fusion on different machines. I guess I can post a list if thats important. And no memory cleaners, only cleaner is eraser and I only use it to erase recycle bin.

One machine I installed amvapp pack and upgraded all the various programs, the other machines I did standalone stuff like avisynth then dgmpgdec then virtualdubmpeg2 then virtualdubmod etc.

as for breaks it does, I open the files in a player like mpc and it gives the red error message, usually the same like -can't find file , don't remember exactly what the message is but I'll write it down next time, when that happens none of my projects that I loaded up into virtualdub will work and also will not open with mpc. When does it break, either right after using dgindex or during the time I check the project with avisynth scripts and mpc, or in the middle of encoding using virtualdub. When it doesn't work then I can reboot and sometimes the d2v files will work otherwise I can rerun the job with dgindex and use the same avs script already loaded in virtualdub to run the encoding.

sorry about not being more precise.

maybe you can give some pointers on how to put this error report in a way you can understand.

maybe a list of something that I can fill out or follow or something?

anyway I've been living with this problem since I started encoding this way about 5-6 months ago. Sometimes I have no problems for weeks then it just gets crazy for a day or two or a week, not all the way just one day I'll have to do it all over then it's fine for a day or two then it's all messed up again.

Guest

27th January 2008, 07:52

When a job fails, find out what script it is. Then try to open that script in another invocation of VirtualDub. If it fails, post links both to the script and the D2V file, and tell me exactly what the failure mode/message is. If it does not fail, it is not a DGMPGDec problem. I cannot help you with VirtualDubMod or PC debugging.

fasttoon

28th January 2008, 20:14

Thanks.

Download link: http://rapidshare.com/files/87356827/New_Folder.rar.html

Also ran this project 3 times before it failed so I could get the error msg, the message is always the same so I have been ignoring it and just go straight to running dgindex to fix it. There is no original backup for these as I forgot but I can rerun dgindex, make a backup and run it again until it fails. Let me know.

Also I've listed the steps and programs used to for projects so I might as well post it.

==================================================

The main computer used is a multiboot windows/linux
Winxp1 is for everyone, and is almost always in use.
Winxp2 is for me only and not fully completed
Ubuntu is for me only

I noticed Winxp1 produces more errors.
Winxp2 also gets errors but not as frequently
Winxp2 is a fully working os but doesn't have all the programs I need.

1. rip dvd

rip dvd using one of the following to a folder either in vob or iso format.

anydvd 6.0.1.1
dvd decrypter 3.5.4.0
dvdshrink 3.2
imgburn 2.3.2.0
smartripper 2.41

mount using daemon tools if iso

2. dgindex

Run dgindex and save project to a folder.

dgindex 1.49

3. avisynth

test dgindex produced avs script, if works then copy mpeg2source path to my own template

avisynth 2.58 build:May 17 2007
media player classic 6.4.9.1

4. virtualdubmpeg2

open avs in virtualdub, set encoder and settings, and save to job control for processing.

virtualdubmpeg2 1.6.1.9

The problem starts after running dgindex.

A. Open up avs produced by dgindex. Fails 1 out of 25 times

B. Open up avs in my template. Fails 1 out of 20 times

C. Open up avs in virtualdub. Fails 1 out of 20 times

D. Processing in virtualdub. Fails 1 out 15 times. (fails in middle of processing)

Error is "MPEG2Source: Could not open one of the input files.(moviepath, line 3)"

(or line 15 in my script template) btw I always use the dgindex avs script to test.

the fail rate is an approximation as I have not kept statistics.

When the project fails at "A" I just process again using dgindex and let it overwrite all files produced.

When the project fails at "B" I just repeat above.

When the project fails at "C" and "D" all d2v projects need reprocessing by dgindex.

I can't be sure of solution to "A" and "B" because it's usually my first project and I've never checked other projects if there are any.

Other solution is to reboot and usually 1 out 5 times it will all work again.

Run dgindex on all failed projects then reset failure status in virtualdub job control to waiting by clicking on postpone button twice and running project. All avs and/or virtualdub settings are left alone.

Other attempts at fixing it.

redo path and/or move project folder
copy original d2v and avs produced by dgindex to another folder for backup purposes
use programs installed on winxp2 while using winxp1 (less incidents of errors)

other observations.
increased incidents of errors when other users are gaming or using other programs with high cpu usage. (virtualdub)
Winxp1 has the highest incidence of errors.
Winxp2 has the 3rd highest incidence of errors.
Other computer is currently out but had 2nd highest incidence of errors.
Work computer has the lowest incidence of errors (but hardly use it for processing video so maybe that's why)
original copy of d2v/avs and broken d2v/avs is the same, new d2v/avs also seems the same.

Thanks for your time in helping me out.

Guest

29th January 2008, 03:10

You didn't answer my question. When a script fails in VirtualDubMod batching, if you then open it directly in another instance of VirtualDubMod (not batched), does it fail then too?

Try it without Daemon tools. Physically rip the files to your hard drive.

I am behind my corporate firewall until Feb 3 and can't access file sharing sites. So you'll have to wait until then or give me an FTP that I can access.

Carpo

29th January 2008, 12:26

avisynth 2.58 -- i would suggest dropping back to 2.57 or even .56 and try again, im not sure that all scripts work with 2.58, most should work with 2.56/7

fasttoon

29th January 2008, 21:57

@Carpo - did use older versions, I upgraded to see if it would resolve the problem. Used older version of dgindex as well, that's why this post, I finally got tired of redoing everything and nothing I've done nor searching the web (probably because I don't know how to word this problem) gave me any help or ideas. I really want to find out how to fix this.

@neuron2 - not sure what you mean, if it fails I go directly to the avs created by dgindex and it fails there too with the error MPEG2Source: Could not open one of the input files.(moviepath, line 3). Initially I worked backwards by checking virtualdub but the avs template will give the errors, so I go back to the avs created by dgindex. I use media player classic to open up the avs files.

In other words based on this error, once it fails in virtualdub it's start from the beginning and reprocess with dgindex, no need to even try because of past experience it won't work no matter what I do short of a miracle of reboot and this is if I'm lucky.

And as far as ripping I do like to rip the vob files directly to harddrive so my first ripper is almost always smartripper, then dvdshrink, then anydvd, only if I can't get it that way do I use dvddecrypter/imgburn as iso. Loading it I almost always use deamon tools, sometimes I use nero, lastly I use microsoft vcd. Once in a great while I'll have a problem and just make a copy using nero and then use the nrg file to process.

If I'm not getting what you're saying maybe you could give me a step by step to understand what you want me to do.

Thanks for the replies.

Guest

29th January 2008, 23:56

Well, you're over complicating things for a trouble report by bringing in the batching and all that stuff.

If I understand you, you say you get into a situation where simply loading a script gives you the "Could not open one of the input files" error. OK, so put in your next post the script that fails, the top of the D2V file, and tell us exactly what the paths are for your script, your D2V file, and your source file.

fasttoon

30th January 2008, 02:02

Guest

30th January 2008, 10:59

Yes, of course I mean the VOBs, as they are the files referenced in the D2V file.

Please get an application called Unlocker off the web.

Then, when you are in the failing script state, run Unlocker on each of the source VOB files and see if any application has them open. If so, unlock all the handles and try the script again.

fasttoon

3rd February 2008, 04:16

They are never in the same place, most times they are in the same folder as the project, sometimes I put them on removable racks as I would run out of room on the processing drive, either case it has failed whether the vobs are in the same project folder, on another drive still on the machine or on removable racks available or pulled, there has also been a few times I just did it straight of the dvd and removed the dvd while processing.

I don't think the source files (vobs) placement are the problem, as the first time this happened I started putting the vobs (VIDEO_TS) folder in the project folder but then I started poking around and found out the m2v are what the d2v files point to.

If the vobs should be in the project folder could you explain why? As I don't understand the reasoning nor has this been a hinder in successful conversion.

Funny thing about your mentioning unlocker, found it a few weeks ago because I couldn't delete a file, and just before logging on here I had another failure, ran unlocker on all the files, nothing locked. (avs, m2v, d2v, ac3, vob)

Any other ideas?

Guest

3rd February 2008, 04:51

I just did it straight of the dvd and removed the dvd while processing. You can't do that!

The files listed in the D2V file have to be present and accessible during the processing.

When you get the error message, make sure that the referenced file *is still present* and is not locked by some other process.

The error message is correctly telling you a file cannot be opened. Find out why the file cannot be opened and you will have your solution.

fasttoon

3rd February 2008, 22:19

ok, according to you I can't do that but I have in the past, it's only when I had to reprocess with dgindex that I started putting the vob files in the project folder so I don't have to find the dvd or mount an iso or get the vobs loaded from a removable rack.

It still fails with the vob files in the project folder as I mentioned in the last reply.

So kindly forget about what I did in the past because while I mentioned it as to how I was doing it and what steps I have been doing to resolve this problem.

So the last failure (today? yesterday?) was when the vob files, avs, d2v, m2v files were all located the same project folder, error message was the same, tried to open avs, d2v in mpc and it gave error message, made new avs file with path (not copy and paste) and same error message. Unlocker did not show anything locking the files.

Please, understand my problem.

Whenever I say something to reply or to show how I have been doing in the past is not the problem, I am telling you how I used to do it or what I have done to resolve this error.

I know you are the one that wrote this program, I don't know it as much as you or as much as most people.

Please, the d2v file fails. Help me fix it.

Give me specific steps to go thru and solve this problem rather than asking me for more details and criticsizing my prior procedures which may not be currently how I do things now or is to your liking. Suggestions are fine, criticsizing me is not helpful, makes me feel as I should forget this and be done, won't stop me from trying to figure it out, will make me stop posting here and find someplace else to get help, it does show you're just as fustrated as I am but putting the blame on me at this point is more on you defending your program and ego than to acknowledge I have a problem that is eluding solution.

The d2v files fail no matter what I do and as pointed out, I can run the project multiple times successfully without any changes and it will fail at some point, when it fails no matter what I do I can't run the d2v files except with a reboot which only works sometimes or to rerun the dgindex program again which works most times. Why am I running it multiple times? 1. to produce the failure and see what has changed. 2. to produce failed files so you could analyze (which I uploaded). Do I do this now? NO! I don't have time to try and analyze something which has surpassed my knowledge of what I'm doing. I just rerun the project with dgindex, THAT I know how to do and it resolves the problem most times. I am posting because I have reached the end on my patience on this irritating problem and don't know where else to turn.

So please help me fix this problem. Your suggestion of locking and using unlocker was great, unfortunately it was not the solution, idea's like this is what I'm looking for.

Thanks for your time and help in resolving this issue.

ps. I am not you nor do I understand how the program works, while I have been using many programs and doing conversions for years now it really takes me about that long to understand what I'm doing. For me it's more of an experimentation of changing settings, changing procedures to see how it turns out for me. I read all the posts, reports, try out new programs, etc., etc. and see the results. Do I know what I'm doing? NO! or at least it takes me a long time maybe years to really understand what a part of the process is really doing. Like avisynth and avs files, do I know what a frameserver is? Do I know how the other filters and such work? Keep reading about it but I'm not really sure, I do know the basic that it does conversion on the fly but how? Don't know and if someone asks me - well.... Been using avisynth for about 18 months and I still don't understand almost all of it.

So treat me like a noob or an idiot or whatever by giving me step by step instructions that I can follow to narrow down and/or pinpoint the problem.

Thanks again.

jeffy

3rd February 2008, 22:49

@fasttoon:
How much physical and virtual memory do you have? It might be failing at some point in time when you run out of *some* resources. When it fails, how much free memory is shown in the task manager? [It would explain why reset helps.]

Guest

4th February 2008, 05:34

everything is one folder in this case

K:\Knife

mpeg2source("K:\Knife\VTS_01_1.d2v")

source you mean vobs? usually in same folder but in this case it's not or do you mean the other one created by dgindex, m2v? It's in the K:\Knife folder. The m2v file works in mpc so I don't think thats the problem.

and as for too much info, well in the beginning you said it wasn't enough. I don't know enough about this to know how to word the problem so you understand, so I just made a list of what steps I took, sorry if it was too much.

I'm posting the beginning of the d2v file, hope thats what you meant.
=================================================

DGIndexProjectFile16
4
J:\VIDEO_TS\VTS_01_1.VOB
J:\VIDEO_TS\VTS_01_2.VOB
J:\VIDEO_TS\VTS_01_3.VOB
J:\VIDEO_TS\VTS_01_4.VOB

================================================

Your error here is that you say the source files are on K: while the D2V file refers to drive J:. You cannot move the source files after making the project if you have full paths enabled in the options menu.

Since you admit that you don't know what you are doing, please follow this rule:

Do not move or remove the source files, the D2V file, or the AVS script until the processing is complete.

Please note that I can only debug the scenario you present me with. If you keep changing it, you have to start our debugging process all over again, i.e, by giving me all paths, filenames, D2V, script, etc.

Finally, forgive me for not being more attentive to you but I was in Beijing on business with spotty internet access and have only just now returned. I will be checking this thread often.