Re: HLS, DASH, MPD and LMS future version
bpa <bpa.a11gdz-NUepA2SMhDQqspMVqqL2D+4xXEVPTSb/[email protected]>
| Newsgroups | gmane.music.equipment.slimdevices.devel |
|---|---|
| Organization | Logitech Squeezebox Forums |
| Message-ID | <[email protected]> |
philippe_44 wrote: > I was not suggesting at all no support in 8.1/8.2 and only do something > beyond. I agree with plugin approach for these, I was more thinking > along the lines of integrated support beyond that. I agree that if a > plugin offers support for hls:// then other plugins will benefit from it > if they spit out a hls:// link. I was thinking of cases where a plugins > would need to subclass the PH for hls:// and that might be less > "convenient" if hls:// is not a core protocol handler. I haven't come across a need for a hls:// accessible to third party plugin. HLS URLs are http/https with appropriate HLS mime type. Plugins such as iHeart or Tune-in just return a http URL. The plugin takes it when users tries to play the http URL and LMS determines type from MIME. To avoid LMS recursing on http m3u8 URL (which occur many times within m3u8 playlist) - the plugin replaces all http URLs during initial processing by its own URL hlsplay:// to avoid default LMS http processing. > That's an issue I had with "Reliable/Buffered" where until I integrated > directly inside Slim::Protocol::Player::HTTP, then no plugin could > benefit from it. But I agree, the problem is likely different here and > subclassing might not be needed most of the time. This is where I have no knowledge of your use cases and the need for other plugin to access hls:// or to subclass. It seems unnecessary but as HLS plugin has to handle content as well - multiple audio formats - subclassing may be appropriate but I'd need to study Reliable/ cache to understand. I think having a plugin in 8.1/8.2 will show up show HLS will be used and whether subclasses or access to hls:// is required. Perhaps this Spotify issue might be the test case. > Agreed in general, although I would do a bit different with a "built-in > plugin" in a 8.3 then, a 3rd party plugin in 8.1/8.2 and then a core > integration in 8.4 OK - this is more gradual but I'm OK with it. ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=114498