[vlc-devel] The --vout options has been disabled on Windows

[Thomas Guillem]

On Wed, Dec 13, 2017, at 08:38, Steve Lhomme wrote:
> On Tue, Dec 12, 2017 at 8:17 PM, David Robison
> <david.robison at psgglobal.net> wrote:
> > 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:
> >
> > --vout=opengl,direct3d
> >
> > 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.
> 
> You may also edit the plugins.dat that should retain the priority of
> modules. It's ugly but you don't have to change any binary.
> 
> Jokes aside, what's the reason for forcing "vout" and "avcodec-hw" in
> libvlc_media_player_set_hwnd() ? Why does libvlc decides that it can
> only be used by the default vout ? (same question for
> libvlc_media_player_set_xwindow() or
> libvlc_media_player_set_nsobject()). If it doesn't work then it's the
> libvlc user's problem.

I totally agree. Only the vmem function set should force the vout.
Almost all OS vout windows can now work with every vout. And if a bad
vout is forced, it will just fail, not crash.

> 
> Nothing in the doc says it forces the default system output to be used:
> * Set a Win32/Win64 API window handle (HWND) where the media player
> should
> * render its video output. If LibVLC was built without Win32/Win64 API
> output
> * support, then this has no effects.
> 
> 
> 
> > Best Regards,
> >
> > David R Robison
> > Senior Systems Engineer
> >
> >
> > -----Original Message-----
> > 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.
> >
> > --
> > 雷米‧德尼-库尔蒙
> > https://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
> _______________________________________________
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
> https://mailman.videolan.org/listinfo/vlc-devel