[vlc-devel] The --vout options has been disabled on Windows
david.robison at psgglobal.net
Tue Dec 12 20:17:52 CET 2017
All I know is that I used to be able to pass a list of video output options I wanted and the order I wanted them in. For example:
This would then use opengl if it was supported and direct3d if not. However, with the latest build, it does not seem to be reading the vout options that I send.
If this is the way it will be going forward, then perhaps I will need to maintain my own compiled version as this feature is critical for us.
David R Robison
Senior Systems Engineer
From: vlc-devel [mailto:vlc-devel-bounces at videolan.org] On Behalf Of Rémi Denis-Courmont
Sent: Tuesday, December 12, 2017 2:14 PM
To: vlc-devel at videolan.org
Subject: Re: [vlc-devel] The --vout options has been disabled on Windows
Le tiistaina 12. joulukuuta 2017, 20.05.11 EET Thomas Guillem a écrit :
> On Tue, Dec 12, 2017, at 19:59, Rémi Denis-Courmont wrote:
> > Le tiistaina 12. joulukuuta 2017, 17.13.39 EET David Robison a écrit :
> > > From what you said, are you saying that it should be possible with
> > > the latest 3.0.0 code?
> > No, he meant that LibVLC 3.0 picks the correct video output
> > automatically for the use cases supported by LibVLC.
> Yes and that's why it's useless to override the vout var again, no ?
I´m not sure what you are trying to say.
LibVLC controls the vout variable to ensure that the candidate video output plugins match the requested render target selected by the application (X11, custom callbacks, etc).
The X11 implementation seems actually correct. The Win32 one is so so.
vlc-devel mailing list
To unsubscribe or modify your subscription options:
More information about the vlc-devel