<html><head></head><body>Hi,<br><br>Again, it would be nice if the underlying assumption, that NVDEC (and any other future extra hw decoder) was permanently a superset or subset of DX and VA.<br><br>I doubt that will work in reality. They are developed by different companies with different agendas and schedules.<br><br><div class="gmail_quote">Le 24 septembre 2019 09:55:59 GMT+03:00, Thomas Guillem <thomas@gllm.fr> a écrit :<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail"><br>On Mon, Sep 23, 2019, at 18:50, Rémi Denis-Courmont wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Le maanantaina 23. syyskuuta 2019, 11.29.23 EEST Steve Lhomme a écrit :<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">It's like the display module, it's treated as a resource that is created<br>on demand by the decoder. In the past we need a display module to create<br>the decoder/VA (depending on the display pictures). Now the VA needs a<br>"decoder device" (the hint) before it's created.<br><br>It's true that most decoders (ie not lavc or nvdec) will not need a<br>decoder device at all. And I agree we should not create it for those.<br></blockquote>On-demand creation avoids the delay and resource usage for software decoder. <br>My problem is, now that NVDEC is added, we no longer have a "static" choice of <br>decoder device on a given system - NVDEC competes with DirectX and VA/VDPAU.<br><br>This potentially breaks the whole idea of creating the decoder device <br>(exclusively) from the window. Or NVDEC needs to permanently remain a <br>functional superset of DirectX and VA/VDPAU...<br></blockquote><br>We can still disable NVDEC on Windows by default since DX11 should cover most of the need.<br><br>For Linux, I don't see the problem. There will be one VAAPI and one NVDEC decoder device that will be loaded just after the window. Only one will be able to load depending on your main GPU/Display/Driver. Therefore, the avcodec VAAPI va or NVDEC decoder will be automatically loaded according to that decoder device.<br><br>> <br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">-- <br>レミ・デニ-クールモン<br><a href="http://www.remlab.net/">http://www.remlab.net/</a><hr>vlc-devel mailing list<br>To unsubscribe or modify your subscription options:<br><a href="https://mailman.videolan.org/listinfo/vlc-devel">https://mailman.videolan.org/listinfo/vlc-devel</a><br></blockquote><hr>vlc-devel mailing list<br>To unsubscribe or modify your subscription options:<br><a href="https://mailman.videolan.org/listinfo/vlc-devel">https://mailman.videolan.org/listinfo/vlc-devel</a></pre></blockquote></div><br>-- <br>Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.</body></html>