[vlc-devel] [PATCH] [RFC] input: set "input-current" early so control interfaces can control earlier

Steve Lhomme robux4 at gmail.com
Tue Oct 27 12:47:38 CET 2015

On Tue, Oct 27, 2015 at 12:31 PM, Rémi Denis-Courmont <remi at remlab.net> wrote:
> Le 2015-10-27 12:24, Steve Lhomme a écrit :
>>> 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 ?
> I just mean that input-current is not a good place to *modify* the
> (playlist's) input.
> If you want to change the default stream output for playlist items, you can
> (create and) set the "sout" variable on the playlist object. This won't
> confuse other interfaces, won't break streaming wizards. If instead you just
> want to play one single item with sout, then you can create a new input item
> with a sout option like the wizards already do.
> Neither of those, nor your approach solve the problem of doing VoD. The
> playlist is not suited for VoD; it is suited for live playback (no sout),
> live streaming (paced sout), and passable for offline conversion (unpaced
> sout).

No sure what you mean by VoD, but if you mean playing one file over
many Chromecast, that's not going to work, nor is the intended goal.
At least that's not what I'm trying to do. I suppose with an external
app you could have VLC "broadcast" the video and tell many Chromecast
to read that. But the goal here is to select one Chromecast to play
what would otherwise play on the user's PC or device.

> --
> Rémi Denis-Courmont
> http://www.remlab.net/
> _______________________________________________
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
> https://mailman.videolan.org/listinfo/vlc-devel

More information about the vlc-devel mailing list