x264 r1123 (32bits): problem with color space

[daimroc]

Well, until now, I use a simple avs script to open the video with de DirectShowSource function.

I use ffdshow to decode the video. The output options I always have configurated checking the YV12, RGB32 and high quality YV12 convert to RGB.

I never have problems with the color space, but know with this revision (1123 32 bits) I get the following error: unsupported input format (YUY2).

In the avs I use the nnedi to deinterlaced the video, and it need the YV12 color space. In fact, if I uncheck the YV12 in ffdshow, I get the error that nnedi needs this input format.

If I use ConvertToYV12() in the avs then I don't get any error, but in this case I see that ffdshow isn't used, because I don't see the icon of ffdshow in the icontry. If I open ths avs with virtualdubmod then I can see the ffdshow icon in the icontry, so the configuration of ffdshow looks correct.

What is the problem? why don't I use ffdshow? I alwys use avisynth, ffdshow and x264 at this way and I never have problems.




Thanks.
Daimroc.

[daimroc]

Well, I have tried to use and older version of x264 that I am sure that I had no problems with it and I have the same problem.

So perhaps the problem is that I modify the configuration of ffdshow perhaps, because if I use virtualdubmod or media player classic home cinema to open the avs file, I can see the ffdshow icontry, but if I use avs from cmd (command line) to encode the video with x264 I have the problem.

I am sure that I don't modify any in the system, but if I have the problem it's because something it's different.

Someone know which could the problem be?

I am trying to install avisynth again and ffshow but the problem persists.



Thanks.
Daimroc.

[bob0r]

Open the avs in virtualdub.

[daimroc]

Well if I open the avs with virtualdubmod I don't use x264, because the recent builds are only CLI, for command line.

I would like to use x264 in command line.




Thanks.
Daimroc.

[kemuri-_9]

post your script...

from what you're trying to explain, it should be ideally something like

DirectShowSource("some file.ext", pixel_type="YV12")

which is not optimal as DirectShowSource has frame determinism problems...

[daimroc]

The avs is that:

DirectShowSource("VTS_01_1.VOB", audio = false)

Only this. I don't resize or do anything else.

When you say that directShowSource has frame determinism, what do you mean? what kind of problem it is?



Thanks.
Daimroc.

[kemuri-_9]

When you say that directShowSource has frame determinism, what do you mean? what kind of problem it is?


"frame determinism" is the fact the frames will be guaranteed to be exactly the same every time the video is opened.
DirectShowSource can't guarantee this as it often/usually has different frames with each load.

and since you're opening a .VOB,
you should be using neuron2's DGMPGDec (or DGMPGDecNV if you have a compatible Nvidia gfx card).