fix syntax

This commit is contained in:
boyska 2022-02-23 13:41:06 +01:00
parent 8576b212d1
commit e23590ddd2

View file

@ -257,14 +257,15 @@ wanted RadioManifest to be deployable as _"just a bunch of static files"_, as a
=== The `<streaming>` section overlaps too much with /streaminfo.json === === The `<streaming>` section overlaps too much with /streaminfo.json ===
Almost. While `/streaminfo.json` is clearly valuable data, we wanted to account for more usecases: Almost. While `/streaminfo.json` is clearly valuable data, we wanted to account for more usecases:
- A radio should be able to list more than one URL for streaming. This can be for load balancing reasons, for
example. M3U are a simple way to achieve this. * A radio should be able to list more than one URL for streaming. This can be for load balancing reasons, for
- A radio can (and probably should) have not only more URLs for streaming, but actually stream different example. M3U are a simple way to achieve this.
versions: different qualities, different codecs, etc. It is reasonable that, as a user, you don't really * A radio can (and probably should) have not only more URLs for streaming, but actually stream different
care about all those details: «Just gimme the audio!». However, your client could select the best codec for versions: different qualities, different codecs, etc. It is reasonable that, as a user, you don't really
your usecase. Or, it may let the user explicitly select "low quality, low bandwidth" for users that want to care about all those details: «Just gimme the audio!». However, your client could select the best codec for
save bandwidth. This is possible with radiomanifest adding multiple `<source>` elements, and is your usecase. Or, it may let the user explicitly select "low quality, low bandwidth" for users that want to
unfortunately not with `/streaminfo.json` save bandwidth. This is possible with radiomanifest adding multiple `<source>` elements, and is
unfortunately not with `/streaminfo.json`
== Meta == Meta