[vlc-devel] [PATCH] [RFC] input: set "input-current" early so control interfaces can control earlier
robux4 at gmail.com
Tue Oct 27 10:24:34 CET 2015
On Tue, Oct 27, 2015 at 10:03 AM, Rémi Denis-Courmont <remi at remlab.net> wrote:
> Le 2015-10-27 10:07, Steve Lhomme a écrit :
>> On Mon, Oct 26, 2015 at 4:43 PM, Rémi Denis-Courmont <remi at remlab.net>
>>> On Monday 26 October 2015 08:59:29 Steve Lhomme wrote:
>>>> For Chromecast we want to be able to set a custom sout for the selected
>>>> input to play but the control interface get the event too late and the
>>>> input thread has already created its sout/vout.
>>> That callback is for interfaces to update their views and register
>>> with the input. Modifying the input there won´t work as you can (and
>>> do) have more than one interface running.
>> I assume none of them do that at the moment. So it shouldn't be an
>> issue if only one does.
> It is an issue even with only one. Besides, the feature would eventually be
> replicated to the HTTP interface, and possibly the skin engine.
So you'd vote for another kind of object to be able to talk to the
Chromecast and control playback ? In the end the player is the
Chromecast and not VLC. VLC acts more like a remote control and a
provider of data.
For example with the Chromecast Android app it's possible to pause
playback of the Chromecast. VLC will receive that event and will have
to deal with it. For now I use a blocking (pace control) HTTP server
so it doesn't have to do anything. But if the Chromecast loads another
app, VLC has to know and force its internal playback to stop.
For now the only things you need to provide (command line for the
moment) is that you want to use the Chromecast module (whatever form
it will take) and the name/IP address you want to use for playback.
> Rémi Denis-Courmont
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
More information about the vlc-devel