Re: HLS, DASH, MPD and LMS future version

bpa wrote: 
> I don't see why it would prevent them. I think it is similar to saying
> faad is bundled with LMS  - I suggest the HLS plugin are bundled with a
> normal LMS.  If I finish the PlayHLSv3 - then it can be included in a
> 8.1.* and 8.2.* release without any changes to core LMS.
> 
> Currently, this plugin approach already works.  Tune-in (Internetradio
> fixURL routine in Tunein.pm) detects "presence" of HLS support (ignorent
> of plugin or core implementation) by checking if there is a "type"
> called "hls".
> 
> Making HLS support available to all user of 8.* is desirable.  The need
> for https support made upgrades to 8.* essential however I think upgrade
> hesistancy will re-emerge as there will seem no great need to go from
> 8.1 to 8.2.  A plugin approach will enable PlayHLS to be included in a
> minor rev of 8.1 and 8.2. If it causes a user a problem the plugin can
> be disabled so minimise support issues. 
> 
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.

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. 

> 
> The more users use HLS services, the more issues will be found that need
> to be addressed in a "proper" integration into core LMS.  The recent
> comment about Spotify and HLS is a case in point. I was unaware that
> Spotify can offer HLS streams and IIRC it has not been reported before. 
> A mixcloud plugin update could be the test of practicality of plugins
> and the "dependency" issue. Mixcloud live streams use HLS fMPEG4 and
> some other non-live streams are in DASH.
> 
> With this version roll-out, I see the development as follows
> 
> 1. Finish a PlayHLS v3. Don't tackle the "rogue" streams and assess how
> popular they are. Include as plugin in 8.2.x (not .0)  and possibly do a
> minor rev of 8.1
> 2. Do a PlayDASH and similar to point 1. 
> 3. As part of 8.3 effort look at integrating HLS & DASH into core LMS as
> per Slim::Player::Protocols::HLS.pm  and
> Slim::Player::Protocols::DASH.pm suggestions. Solution should also
> address issues found by experiences gained from plugins support of HLS
> and DASH.
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



LMS 8.2 on Odroid-C4 - *SqueezeAMP!*, 5xRadio, 5xBoom, 2xDuet, 1xTouch,
1xSB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000, ShairPortW,
2xChromecast Audio, Chromecast v1 and v2, Squeezelite on Pi,  Yamaha
WX-010, AppleTV 4, Airport Express, GGMM E5, RivaArena 1 & 3
------------------------------------------------------------------------
philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261
View this thread: http://forums.slimdevices.com/showthread.php?t=114498