AVISYNTH ERROR WHILE WATCHING MOVIE??????

[defense]

This has to be the craziest thing i've seen as of yet. I made a BACKUP of "GHOST" & like always, I go through chapter by chapter to see if I notice anything unusual or any freezing or skipping. Anyway, i'm watching Ghost and everything is fine..until I get to the second to last chapter..which is like Chapter 14..and I see an ALL BLACK SCREEN with red letters that say this:

Avisynth: caugh and access violation at 0x105e3765 attemptin to read from 0x106bd973 and during this entire time you can hear the voices and music in the background...but you don't get the picture..and this error stays up the entire time.

Can anyone tell me what the hell has happened..what caused this and what I can do about it?

Very, Very strange, to say the least.

[SLK001]

I believe that you had a problem with your original .D2V file, and it pointed to something that had an error in it (or wasn't where it was supposed to be). This probably occurred at the layer break point.

Just a guess, mind you.

[defense]

@SLK, thanks for your answer. Being that it was an avisynth error I was sure my complied vobs would show this error on my HD and sure enough they did. Isn't the layerbreak usually around the middle of the movie though? This error occurred with about 9 minutes left in the entire 2 hour movie. Something happened with avisynth though I guess..lol.....anyway, if there was a problem with the .D2V file, what type of problems could cause this?

Have you ever seen this before. It was definintely a first for me. I'll try to reencode one more time and see if it happens...that really sucks though.....my first wasted SONY ACCU came because of something like that.....oh well....only 84 cents down the drain. lol....

You think i'll have any luck trying again? And have you ever seen anything like this before?

[SLK001]

It may be caused by how you generate your .D2V. If you used DVDDECRYPTOR of SMARTRIPPER to generate this file (I've had problems doing it this way), then it may have "burped" some where along the line (as I said, I suspect the "layer break"). I always rip directy to HD, then use DVD2AVI to generate mine.

Depending on the construction of the DVD, the layer break can occur almost anywhere in the movie. I would just suspect that the whole movie alone is greater than 4,700,000,000 bytes.

[defense]

@SLK, I actually use DVD2DVDR and allow it's internal ripper to handle the ripping. I've never seen this before as I said, but I've ripped the movie again with DVD DECRYPTER, because I had a hunch it may of been caused by a ripping issue. Hopefully that is the case, that way the chances of it happening with two seperate rippers would probably be slim.

Anyway, i'll report whether it worked or not when I reencode the movie again. Damn, 4 hours of computer time wasted...lol