[vlc-devel] [PATCH 1/2] decoder: let the decoder device know it's force created

Rémi Denis-Courmont remi at remlab.net
Thu Sep 19 08:33:05 CEST 2019


Sure you can change priorities, just have multiple entries with the same capability and different priority. Nothing new here.

Le 19 septembre 2019 09:07:44 GMT+03:00, Steve Lhomme <robux4 at ycbcr.xyz> a écrit :
>On 2019-09-18 18:13, Rémi Denis-Courmont wrote:
>> Le keskiviikkona 18. syyskuuta 2019, 17.09.16 EEST Steve Lhomme a
>écrit :
>>> When selecting between D3D11 and D3D9 on Windows we need to know if
>the
>>> decoder device may be optional or not (with external rendering it's
>not).
>> 
>> The force flag is an old kludge that does not account for how modules
>proving
>> really works. If you need this, your design is broken.
>
>There is nothing new here. It's just using the best pick already in the
>
>D3D/DXVA to the decoder device, since it's going to replace the lavc va
>
>pick.
>
>It's either forced by the user and used in automatic. In automatic we 
>don't want to use D3D11 on Win7 even if it can kind of work (needs
>extra 
>conversion as it can't display NV12). I am not aware of any other way
>to 
>do this fine tuning. We can't dynamically change the priorities of
>modules.
>_______________________________________________
>vlc-devel mailing list
>To unsubscribe or modify your subscription options:
>https://mailman.videolan.org/listinfo/vlc-devel

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/vlc-devel/attachments/20190919/b4dcc378/attachment.html>


More information about the vlc-devel mailing list