playbin3 picking wrong h265 decoder
bill.hofmann at gmail.com
Wed Dec 28 23:07:16 UTC 2022
Works like a charm, thanks. Decode is now smooth as butter. Is there a
place where this (and other env variables) are documented?
On Wed, Dec 28, 2022 at 1:07 PM Nicolas Dufresne via gstreamer-devel <
gstreamer-devel at lists.freedesktop.org> wrote:
> Le mer. 28 déc. 2022, 15 h 15, Bill Hofmann via gstreamer-devel <
> gstreamer-devel at lists.freedesktop.org> a écrit :
>> On 1.21.3, with a build that I have verified includes vah265dec, with a
>> graph that looks like:
>> playbin3 uri="http://127.0.0.1/foo.m3u8"
>> video-sink="kmssink name=kmssink0 connector-id=308 plane-id=31
>> audio-sink="volume name=volume0 volume=0.01 ! alsasink name=alsa
>> I note that it looks like avdec_h265 is getting picked for the decoder,
>> and it is having problems keeping up with the stream. I know (from a
>> hand-built graph) that the VA versions keep up reasonably well (4k h265
>> Main10 L5.1 stream).
>> I recall that there was some way of changing priorities of different
>> plugins, but for the life of me, can't find out where that is documented.
>> Any hints? Perhaps this belongs somewhere in the decodebin/playbin docs?
>> Gonna be moving to uridecodebin3, for other reasons, but I expect I'd
>> have the same problem there.
> This is the new VA plugin, we are just an air from being able to deprecate
> the old one, meanwhile, you have to rank it. From command line (hopefully I
> got the env name right):
> export GST_PLUGIN_FEATURE_RANK=vah265dec:9999
+1 510 387-0952
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the gstreamer-devel