get some weird message while play video stream

[i-rinat]

get some weird message while play video stream

[i-rinat]

not implemented conversion VA FOURCC �

I saw similar messages on machine with AMD videoadapter. The following occurs: libva returns some weird fourcc. I don't have every conversion implemented, so I just print an error message. There should be four character code after 'VA FOURCC', if it was actual format. Maybe there are memory corruption somewhere. I can't reproduce issue at this time (don't have access to that machine anymore).

just be curious if this is harmless?

libvdpau-va-gl returns VDP_STATUS_NO_IMPLEMENTATION in such case and does nothing. If application you're using survives this, it's ok.

[grancier]

Hello i-rinat,

I am also receiving this error in VLC 2.1.2 when I play x.264 mpeg4 files either .mkv or .mp4. It just shows a green video screen. The audio does play. I have an AMD Radeon 6000HD video card.

What would be needed to implement the conversion. I was looking through VLC code specifically http://git.videolan.org/gitweb.cgi/vlc.git/?a=commit;h=d6817151944c7697f30106124474f92deb19f246 and it is supposed to convert between VLC YUV format to VDPAU chroma type and YCbCr format. Is it possible for you to outline what would be required to do this conversion in the driver?
I might be able to implement it.

Thanks.

[i-rinat]

Ok, @grancier , this is where conversion takes place:

libvdpau-va-gl/vdpau-soft.c

Line 973 in e09defe

softVdpVideoSurfaceGetBitsYCbCr(VdpVideoSurface surface, VdpYCbCrFormat destination_ycbcr_format,

As you can see, there are chained if () {} else if () {} else... and so on. Every conversion have "from" part and "to" part. You pick the pair you want and then try to figure out how to convert image between those formats. NV12 to NV12 conversion is easy -- you just copy lines one by one or all of them at once if pitches are the same. YV12 have different planes for U and V, so you must unzip (you know, like zip in python) packed UV pairs.
That was the easy part. Here comes the hard one. You may only implement conversion if you know at least source format. The bad news is -- AMD driver (or xvba-va-driver wrapper, can't say for sure) returns garbage. There must be human readable source format name, that's the whole purpose of FOURCC. If there was something like VA FOURCC NV21 -> VDP_YCBCR_FORMAT_NV12, there would be chance to fix that by implementing NV21 to NV12 conversion. But there is no any. How do you know what format is if even its name is garbled? I have no answer.

Recent versions of opensource radeon drivers got VDPAU capabilites. You should definitely try them. People over Internet say they work nice. (Unfortunately I don't have capable hardware to test.)

[i-rinat]

It's external bug. Closing.

[genodeftest]

Where can this issue be fixed? If it is an external bug, where is the bug? I am seeing the same issue in VLC on Intel iGPUs and video doesn't play at all either.

[i-rinat]

Where can this issue be fixed? If it is an external bug, where is the bug?

In either VA driver (i965-va-driver, recent fglrx versions have native VA-API driver too) or in VA-API compatibility layer (xvba-va-driver).
In either case, there is still possibility that error is hidden somewhere else, or even in libvdpau-va-gl. No one can be sure.