M2v file with dvd2avi and GK

[maormini]

Hi!

I got a large (49GB) m2v file that was rendered using pinnacle edition.

When I open it up in DVD2AVI (1.76) I see the picture perfectly, once it's already a d2v file and I try to open it in any encoding program (VirtualDub, DVX, GordionKnot...) all I get are either green frames of mixed up colors!

Am I missing a filter, or did I maybe do something else wrong?

[stax76]

is the source width and height a multible of 4?

[maormini]

The resolution is 720x608.
By the way when I encode it to DVD structure (VOB's) in Pinnacle edition, I can open it in all the encoding programs without any problem, but I loose a lot of detail when I transcode it to VOB (Of course the original 49.7GB file has superb quality much superior to VOB)

In case I forgot to mention the m2v file was created in pinnacle edition (silver).

[ultimatebilly]

When I open it up in DVD2AVI (1.76) I see the picture perfectly, once it's already a d2v file and I try to open it in any encoding program (VirtualDub, DVX, GordionKnot...) all I get are either green frames of mixed up colors!
Virtualdub doesn't support d2v-files...
You have to frameserve with avisynth...
You can create an avisynth-script with Gordianknot...
Opening the d2v-files in GordianKnot doesn't work?
Make sure you have the latest version of GordianKnot and the latest version of avisynth installed...
The m2v-file must have a really huge bitrate...
Does anybody know if there is a constraint in maximal bitrate in the mpeg2dec-plugins?

[stax76]

you can try to install different grafic drivers, different DirectShow versions, in DVX you can try different things in the AviSynth script and then look how the preview looks, try colorspace conversations, different resolutions (at least mod 4 because of a DirectShow bug), try different mpeg2dec.dll's, different DVD2AVI versions, if you use the DVX or GK packs you should have the right versions, I got almost daily bug reports about this, I have no clue what's the problem, there seem to be different variations and reasons and solutions for this problem, in DVX you could also try Settings -> Build own DirectShow graph, I think it's DirectShow related because before I used DirectShow this not reported, I wonder why this problem also occurs in GK, I thought GK don't use DirectShow