<div dir="ltr"><div>Hi Phillipp,<br><br></div>I don't think there is a ticket open about FLAC metadata specifically. The original thread from 2015 is as follows:<br><br>"<span class="gmail-im">On Tue, 2015-01-13 at 17:53 -0800, Eduardo Martinez wrote:<br>
> Hello,<br>
><br>
><br>
> I'm currently using Liquidsoap to stream a group of files to Icecast.<br>
><br>
> The stream is sent to Icecast in a few different formats (MP3,HE-AAC<br>
> v2,OggFlac,OggOpus).<br>
><br>
><br>
> The "Current Song" <span class="gmail-il">metadata</span> is correctly displayed for the MP3 and the<br>
> AAC stream, but not the OggFLAC or OggOpus stream.<br>
><br>
><br>
> I see a few entries in the Icecast forums, but it does look like <span class="gmail-il">FLAC</span><br>
> <span class="gmail-il">metadata</span> support never made it into a an official feature request.<br>
><br>
><br>
> The lack of <span class="gmail-il">metadata</span> happens for both Icecast 2.3.3.kh-11 as well as<br>
> Icecast 2.4.0<br>
<br>
</span>Yes. That is correct. Thank you for reporting.<br>
We have recently worked on improving the <span class="gmail-il">metadata</span> support a bit and also<br>
talked about better support on Opus and <span class="gmail-il">FLAC</span> on the international<br>
Icecast meeting this year.<br>
<br>
To the other project members:<br>
Is there a ticket for this? if not can someone create a meta ticket with<br>
child tickets per codec? When there is a ticket please also ping me on<br>
IRC. Thank you."<br><br><br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 13, 2017 at 7:33 AM, Philipp Schafft <span dir="ltr"><<a href="mailto:phschafft@de.loewenfelsen.net" target="_blank">phschafft@de.loewenfelsen.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Good afternoon,<br>
<span class=""><br>
<br>
On Mon, 2017-06-12 at 13:20 -0500, Rick Keniuk wrote:<br>
> Marvin,<br>
><br>
> That is the current version being used and it still has no meta data.<br>
> server_id Icecast 2.4.99.1<br>
<br>
</span>Icecast2 2.5 beta releases use 2.4.99.x as version number. So that is<br>
correct.<br>
<span class=""><br>
<br>
> Testing the metadata from the admin page “Update Metadata” results in the response:<br>
><br>
> Message: Mountpoint will not accept URL updates<br>
> Return Code: 1<br>
><br>
> So I would guess it isn’t functioning yet.<br>
<br>
</span>The metadata update interface is only for MP3 and AAC as they do not<br>
have native metadata support. Generally speaking the metadata is in the<br>
domain of the source client. So the source client needs to send them.<br>
<br>
<br>
I also had a look at the FLAC code. It currently only extracts the FLAC<br>
version number from the header. Full metadata support is still missing.<br>
(Note to mostly myself: Is there a ticket for FLAC metadata support<br>
already?)<br>
<br>
Opus metadata support is complete in master. But I'm not sure how old<br>
the Windows build is.<br>
<br>
<br>
With best regards,<br>
<span class="im HOEnZb"><br>
> > On Jun 12, 2017, at 12:34 PM, Marvin ScMarvinholz <<a href="mailto:epirat07@gmail.com">epirat07@gmail.com</a>> wrote:<br>
> > On 12 Jun 2017, at 19:10, Rick Keniuk wrote:<br>
> ><br>
> >> Thanks Phiipp,<br>
> >><br>
> >> I've attempted to download this previously but somehow ended up<br>
> with v2.4.99 on Windows. Is there a specific path to your suggested<br>
> version? This is on a Windows machine (since that might be an issue<br>
> here).<br>
> ><br>
> > Thats correct, that is the 2.5 beta version.<br>
> ><br>
> >><br>
> >> Rick Keniuk<br>
> >><br>
> >> On 6/11/2017 9:36 AM, Philipp Schafft wrote:<br>
</span><span class="im HOEnZb">> >>> On Sun, 2017-06-11 at 09:24 -0500, Rick Keniuk wrote:<br>
> >>>> Anyone know any workarounds for OPUS/FLAC metadata on IceCast? I’ve<br>
> >>>> monitored my inbound stream and this is working correctly (or at least<br>
> >>>> the formatting and data for the OPUS stream is identical to the<br>
> >>>> MP3/AAC+ streams). I see people with OPUS streams and metadata but<br>
> >>>> they may not be using IceCast. Is it safe to assume we’ll see this in<br>
> >>>> the next version?<br>
> >>> We updated Icecast2 some time ago to handle this. It is in the 2.5<br>
> >>> development trunk. 2.4.x is the current stable branch which only updated<br>
> >>> with (security) fixes.<br>
<br>
</span><div class="HOEnZb"><div class="h5">--<br>
Philipp Schafft (CEO/Geschäftsführer)<br>
Telephon: <a href="tel:%2B49.3535%20490%2017%2092" value="+4935354901792">+49.3535 490 17 92</a><br>
<br>
Löwenfelsen UG (haftungsbeschränkt) Registration number:<br>
Bickinger Straße 21 HRB 12308 CB<br>
04916 Herzberg (Elster) VATIN/USt-ID:<br>
Germany DE305133015<br>
</div></div><br>______________________________<wbr>_________________<br>
Icecast-dev mailing list<br>
<a href="mailto:Icecast-dev@xiph.org">Icecast-dev@xiph.org</a><br>
<a href="http://lists.xiph.org/mailman/listinfo/icecast-dev" rel="noreferrer" target="_blank">http://lists.xiph.org/mailman/<wbr>listinfo/icecast-dev</a><br>
<br></blockquote></div><br></div>