Re: HLS, DASH, MPD and LMS future version

> 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.

I'd hesitate to include it in 8.1. That should be bug fixes only. But we 
should probably stabilize/release 8.2 and include it there? Make that 
"the release", then start a new branch with more experimental work, core 
integration or whatever.

> Currently, this plugin approach already works.  Tune-in (Internetradio

Laggers who'd want to stick with 8.1 can still use the plugin, but would 
have to install it themselves, right?

> 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.

But isnt't that the case with the plugin as a 3rd party addition 
already? Users can enable it if they want to?

> 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.

That's news to me, too. From discussions within the librespot community 
I must assume that might have been a podcast. Podcast integration seems 
to be much more driven by the podcast provider than with regular music. 
Eg. streams would/could come from those services, not Spotify.

>> That also led me to think about versions now. I was asking @mherger if
>> we should not
>>
>> - Release 8.1.2 and say it's done, no further fixes
>> - Release 8.2 and call it stable, which means 8.2.x will only provide
>> bug fixes (if we do that I'll have one or two last proposals :))
>> - Open a 8.3 (or beyond!) to work on that topic, and maybe others

I'd second that plan. Although I'd suggest we could include HLS as a 
plugin in 8.2. It then could easily be disabled if somebody wanted to 
for whatever reason (as bpa outlined).

> 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

Why not in v8.2.0?

I'd vote against 8.1. Once 8.2.0 released, any work on 8.1. should stop. 
I don't want to maintain three branches...

> 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.

Sounds like a plan!