Icecast - Oct 2021 - Https Meta data

I have a problem with https streaming. In VLC no meta data will be
displayed.

This seems to be an known problem! If you search in the internet, you will
find a comment from VLC, that the problem is created by Icecast.



Is there any possibility to solve this problem?



Thanks,

Hans-Georg





--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren gepr?ft.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20211025/599438e1/attachment.htm>

On 25 Oct 2021, at 19:20, HGAlt wrote:
> I have a problem with https streaming. In VLC no meta data will be
> displayed.
>
> This seems to be an known problem! If you search in the internet, you 
> will
> find a comment from VLC, that the problem is created by Icecast.
Where did you find this comment? This is not true. Lack of ICY metadata 
support
for HTTPS streams in VLC is a known issue in all VLC 3.x versions, due 
to
the way handling of such streams is implemented in VLC. It has nothing 
to do
with Icecast and there is nothing that can be done on Icecasts side to 
fix
this.
>
>
>
> Is there any possibility to solve this problem?
>
>
>
> Thanks,
>
> Hans-Georg
>
>
>
>
>
> --
> Diese E-Mail wurde von Avast Antivirus-Software auf Viren gepr?ft.
> https://www.avast.com/antivirus
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast

Good evening,

On Mon, 2021-10-25 at 19:20 +0200, HGAlt wrote:
> I have a problem with https streaming. In VLC no meta data will be
> displayed.
> This seems to be an known problem! If you search in the internet, you
> will find a comment from VLC, that the problem is created by Icecast.
>  
> Is there any possibility to solve this problem?
let me do a wild guess here: You are using MP3, or AAC.

MP3, as well as AAC do not support metadata (unlike modern streaming
formats) by themself. So they require the use of ICY as a transport.
ICY is a workaround protocol by former Nullsoft that was meant only for
letting Winamp talk with shoutcast. However Icecast has full emulation
of that. TLS or not. To Icecast it is "all the same".

And here is the big but:

As Nullsoft decided that it is a "good" idea to use the
"http" URI
scheme for their protocol now players must check when the user enters a
"http" URL if that is actually HTTP or ICY. So the player does magic
here. And as this is dirty black magic nobody likes it. Therefore
players have never implemented it for "https". As "https"
always meant
"https" not "icys". And for reasons of not confusing things
even more
that is very good.

However there is also no correct scheme as there never was one
registered. So there is no standard way of telling a player to use
"icys". Meaning, metadata will only work if not used with a legacy
codec.

Some players accept URLs with "icys", "icyxs", or
"xicys",... But that
really depends on the player.

Icecast itself (all versions!) are happy to send those metadata if a
player asks for them. So on the Icecast side there is nothing to do.

My suggestion is migration to e.g. Opus for streaming which is
basically "THE" state of the art codec. With Opus metadata just works.

I hope this was helpful, both for you and everyone else reading.

With best regards,

-- 
Philipp Schafft (CEO/Gesch?ftsf?hrer) 
Telephon: +49.3535 490 17 92

L?wenfelsen UG (haftungsbeschr?nkt)     Registration number:
Bickinger Stra?e 21                     HRB 12308 CB
04916 Herzberg (Elster)                 VATIN/USt-ID:
Germany                                 DE305133015
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20211025/61ec840b/attachment.sig>