mpeg2dec3 / mpegdecoder problems

[litz]

Need a solution, if anyone has any ideas ...

This is all using yv12 processing :

mpeg2dec3.dll crashes avisynth when processing some of my .ts files. It gets to a certain point, and I get an avisynth "access violation" error. This crashes avisynth, no further frame fetches are possible.

mpegdecoder.dll has no problem with the exact same .d2v file, on the exact same .ts.

The problem is this : the .ts is 1080i.

mpegdecoder totally fails on 1080i yielding really weird color problems. mpeg2dec3 spits out perfectly process frames, except for the crashing problem.

Is there a solution? A sample of the .ts in question can be provided upon request.

I really hope someone has an idea as this has totally stopped me in my tracks dealing with these .ts files.

thanks

- litz

[trbarry]

The following is something I posted elsewhere recently about this same problem. It assumes you are using VirtualdubMod ...

It is usually garbage in the stream that causes this. I successfully fixed one a couple days ago by:

0) Before encoding be sure to "save processing settings". This will keep track of any deleted sections. Without this you will never be able to match up a bad frame number.

1) Write down the record number where the error occurred. You have to do this before you close any boxes.

2) Starti Vdub again with the file (hopefully you previously did a "save processing settings" you can reload). Reload it. Check to make sure audio is also loaded like before.

3) Select edit/goto and choose a frame number about 10-20 past the bad frame. Then click on the "select end of range" icon.

4) Select edit/goto and choose a frame number about 10-20 before the bad frame. Do not try to get there by passing over the bad section using the mouse or arrow keys. Click on the "select beginning of range" icon. There should now be a small highlighted section.

5) Hit the delete key to delete the bad section, including matching audio.

6) Use the left and right arrow keys to scroll a few dozen frames in each direction to see if it still blows up. If it does, repeat and delete a wider range.

7) Save processing settings to remember the deleted section. Try again.

It worked for me.

- Tom

[Nic]

If you could PM me a link to the .ts file ill look at it :)

Cheers,
-Nic