[vlc-devel] Push Model Issue

[Steve Lhomme]

On 2019-06-12 23:16, Sean McGovern wrote:
> Hi,
> 
> What is the minimum Windows version we require? D3D11 has been around for quite some time now.
> 
> Could we safely deprecate and/or remove D3D9 in VLC 5.0?

Even on Win7 we don't use D3D11 by default because it's a less capable 
version that's not useful to us (namely it cannot display NV12 textures 
which is what decoders output). So we're probably stuck with D3D9 for a 
while.

A lot of libvlc users also use D3D9 rather than D3D11 in their apps 
(probably for historical reasons but also because it's easier to use).

> -- Sean McGovern
> 
> 
> 
> 	  Original Message
> 
> 
> 
> From: remi at remlab.net
> Sent: June 12, 2019 3:59 PM
> To: vlc-devel at videolan.org
> Reply-to: vlc-devel at videolan.org
> Subject: Re: [vlc-devel] Push Model Issue
> 
> 
> Le keskiviikkona 12. kesäkuuta 2019, 17.58.06 EEST Steve Lhomme a écrit :
>> I will keep investigate on option #2 but I'm running out of ideas on how
>> to solve the performance issue. So I wonder if it makes sense to have
>> the decoder depend on the display module in push to be created an
>> usable. This is a limitation of D3D9 where everything is tied to a HWND.
>> In D3D11 the resources can be shared and are only tied to a GPU.
> 
> If your buffers are tied to the display instance, ultimately, you are screwed
> regardless of the buffering model.
> 
> There is always the scenario where the output format changes mid-stream, such
> that the (new) format of allocated buffers does transitionally not match that
> (old) of decoded pictures. I am not sure how systematically the packetizer
> will destroy and re-create the decoder in this case - but it will not work
> smoothly if the pipeline cannot handle buffers with different formats at the
> same time.
> 
> This is not so much about the buffering model, as about the VLC video output+
> display abstraction not allowing the input format to change.
> 
> 
> I don't know how useful D3D9 is, but if it's needed, I would make the device
> context place-holder storage space for the display to store the necessary
> HWND-dependent object(s). But first, I would create a throw-away HWND and
> device to at least check hardware capabilities ahead of time.
> 
> --
> Реми Дёни-Курмон
> http://www.remlab.net/
> 
> 
> _______________________________________________
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
> https://mailman.videolan.org/listinfo/vlc-devel
> _______________________________________________
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
> https://mailman.videolan.org/listinfo/vlc-devel
>