>
> well that's the very first APU generation and unfortunately nobody is
> working on that old hardware any more.
>
Agreed, definitely old hardware. Unfortunately we have 10,000 of these
things in production and they have been playing hardware accelerated mpeg2
fine until we upgraded to Ubuntu
>
> Are you sure that the Gentoo based setup isn't software decoding based?
>
Yes 100% confident. We configured VLC to use VA-API decoding with software
based deinterlacing. The VA-API implementation is using the VDPAU backend
shim as shown in the vainfo output: *vainfo: Driver version:
>
> What regression was that? The difference between VDPAU and VA-API is only
> marginal for codec support.
>
The regression revolved around deinterlacing the content. If we had to
deinterlace 1080i for instance, the playback was very choppy and dropped
frames.
Well how was the stack configured
Well how was the stack configured then? Pure software playback?
In 19.10, yes the whole stack was told to use software playback and
decoding.
I would investigate this way. 1920x1080 is not a high resolution and
should decode with the CPU just fine.
Our older Gentoo based setup with
On Mon, 2019-12-02 at 15:16 +0100, Christian König wrote:
> > The reason we had to switch to VDPAU with Ubuntu 16.04 is that we
> > saw a major regression with mpeg2 playback using va-api.
> What regression was that? The difference between VDPAU and VA-API is
> only marginal for codec support.
The reason we had to switch to VDPAU with Ubuntu 16.04 is that we saw
a major regression with mpeg2 playback using va-api.
What regression was that? The difference between VDPAU and VA-API is
only marginal for codec support.
During our testing we put Ubuntu 19.10 on one of these boxes and
Hi Will,
well that's the very first APU generation and unfortunately nobody is
working on that old hardware any more.
MPEG2 is known to not be fully supported by that chipset in general. So
the best approach is probably to not use hardware acceleration for MPEG2
clips in general.
Regards,
