Marvin,
That is the current version being used and it still has no meta data.
server_id Icecast 2.4.99.1
Testing the metadata from the admin page “Update Metadata” results in the
response:
Message: Mountpoint will not accept URL updates
Return Code: 1
So I would guess it isn’t functioning yet.
> On Jun 12, 2017, at 12:34 PM, Marvin Scholz <epirat07 at gmail.com>
wrote:
>
>
>
> On 12 Jun 2017, at 19:10, Rick Keniuk wrote:
>
>> Thanks Phiipp,
>>
>> I've attempted to download this previously but somehow ended up
with v2.4.99 on Windows. Is there a specific path to your suggested version?
This is on a Windows machine (since that might be an issue here).
>
> Thats correct, that is the 2.5 beta version.
>
>>
>> Rick Keniuk
>>
>> On 6/11/2017 9:36 AM, Philipp Schafft wrote:
>>> Good evening,
>>>
>>> On Sun, 2017-06-11 at 09:24 -0500, Rick Keniuk wrote:
>>>> Anyone know any workarounds for OPUS/FLAC metadata on IceCast?
I’ve
>>>> monitored my inbound stream and this is working correctly (or
at least
>>>> the formatting and data for the OPUS stream is identical to the
>>>> MP3/AAC+ streams). I see people with OPUS streams and metadata
but
>>>> they may not be using IceCast. Is it safe to assume we’ll see
this in
>>>> the next version?
>>> We updated Icecast2 some time ago to handle this. It is in the 2.5
>>> development trunk. 2.4.x is the current stable branch which only
updated
>>> with (security) fixes.
>>>
>>> Hope that helped you.
>>>
>>> Have a nice weekend,
>>>
>>> with best regards,
>>>
>>
>> _______________________________________________
>> Icecast-dev mailing list
>> Icecast-dev at xiph.org <mailto:Icecast-dev at xiph.org>
>> http://lists.xiph.org/mailman/listinfo/icecast-dev
<http://lists.xiph.org/mailman/listinfo/icecast-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.xiph.org/pipermail/icecast-dev/attachments/20170612/5c71a924/attachment.html>
Good afternoon, On Mon, 2017-06-12 at 13:20 -0500, Rick Keniuk wrote:> Marvin, > > That is the current version being used and it still has no meta data. > server_id Icecast 2.4.99.1Icecast2 2.5 beta releases use 2.4.99.x as version number. So that is correct.> Testing the metadata from the admin page “Update Metadata” results in the response: > > Message: Mountpoint will not accept URL updates > Return Code: 1 > > So I would guess it isn’t functioning yet.The metadata update interface is only for MP3 and AAC as they do not have native metadata support. Generally speaking the metadata is in the domain of the source client. So the source client needs to send them. I also had a look at the FLAC code. It currently only extracts the FLAC version number from the header. Full metadata support is still missing. (Note to mostly myself: Is there a ticket for FLAC metadata support already?) Opus metadata support is complete in master. But I'm not sure how old the Windows build is. With best regards,> > On Jun 12, 2017, at 12:34 PM, Marvin ScMarvinholz <epirat07 at gmail.com> wrote: > > On 12 Jun 2017, at 19:10, Rick Keniuk wrote: > > > >> Thanks Phiipp, > >> > >> I've attempted to download this previously but somehow ended up > with v2.4.99 on Windows. Is there a specific path to your suggested > version? This is on a Windows machine (since that might be an issue > here). > > > > Thats correct, that is the 2.5 beta version. > > > >> > >> Rick Keniuk > >> > >> On 6/11/2017 9:36 AM, Philipp Schafft wrote: > >>> On Sun, 2017-06-11 at 09:24 -0500, Rick Keniuk wrote: > >>>> Anyone know any workarounds for OPUS/FLAC metadata on IceCast? I’ve > >>>> monitored my inbound stream and this is working correctly (or at least > >>>> the formatting and data for the OPUS stream is identical to the > >>>> MP3/AAC+ streams). I see people with OPUS streams and metadata but > >>>> they may not be using IceCast. Is it safe to assume we’ll see this in > >>>> the next version? > >>> We updated Icecast2 some time ago to handle this. It is in the 2.5 > >>> development trunk. 2.4.x is the current stable branch which only updated > >>> with (security) fixes.-- 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: 490 bytes Desc: This is a digitally signed message part URL: <http://lists.xiph.org/pipermail/icecast-dev/attachments/20170613/0f465bed/attachment.sig>
Hi Phillipp, I don't think there is a ticket open about FLAC metadata specifically. The original thread from 2015 is as follows: "On Tue, 2015-01-13 at 17:53 -0800, Eduardo Martinez wrote:> Hello, > > > I'm currently using Liquidsoap to stream a group of files to Icecast. > > The stream is sent to Icecast in a few different formats (MP3,HE-AAC > v2,OggFlac,OggOpus). > > > The "Current Song" metadata is correctly displayed for the MP3 and the > AAC stream, but not the OggFLAC or OggOpus stream. > > > I see a few entries in the Icecast forums, but it does look like FLAC > metadata support never made it into a an official feature request. > > > The lack of metadata happens for both Icecast 2.3.3.kh-11 as well as > Icecast 2.4.0Yes. That is correct. Thank you for reporting. We have recently worked on improving the metadata support a bit and also talked about better support on Opus and FLAC on the international Icecast meeting this year. To the other project members: Is there a ticket for this? if not can someone create a meta ticket with child tickets per codec? When there is a ticket please also ping me on IRC. Thank you." On Tue, Jun 13, 2017 at 7:33 AM, Philipp Schafft < phschafft at de.loewenfelsen.net> wrote:> Good afternoon, > > > On Mon, 2017-06-12 at 13:20 -0500, Rick Keniuk wrote: > > Marvin, > > > > That is the current version being used and it still has no meta data. > > server_id Icecast 2.4.99.1 > > Icecast2 2.5 beta releases use 2.4.99.x as version number. So that is > correct. > > > > Testing the metadata from the admin page “Update Metadata” results in > the response: > > > > Message: Mountpoint will not accept URL updates > > Return Code: 1 > > > > So I would guess it isn’t functioning yet. > > The metadata update interface is only for MP3 and AAC as they do not > have native metadata support. Generally speaking the metadata is in the > domain of the source client. So the source client needs to send them. > > > I also had a look at the FLAC code. It currently only extracts the FLAC > version number from the header. Full metadata support is still missing. > (Note to mostly myself: Is there a ticket for FLAC metadata support > already?) > > Opus metadata support is complete in master. But I'm not sure how old > the Windows build is. > > > With best regards, > > > > On Jun 12, 2017, at 12:34 PM, Marvin ScMarvinholz <epirat07 at gmail.com> > wrote: > > > On 12 Jun 2017, at 19:10, Rick Keniuk wrote: > > > > > >> Thanks Phiipp, > > >> > > >> I've attempted to download this previously but somehow ended up > > with v2.4.99 on Windows. Is there a specific path to your suggested > > version? This is on a Windows machine (since that might be an issue > > here). > > > > > > Thats correct, that is the 2.5 beta version. > > > > > >> > > >> Rick Keniuk > > >> > > >> On 6/11/2017 9:36 AM, Philipp Schafft wrote: > > >>> On Sun, 2017-06-11 at 09:24 -0500, Rick Keniuk wrote: > > >>>> Anyone know any workarounds for OPUS/FLAC metadata on IceCast? I’ve > > >>>> monitored my inbound stream and this is working correctly (or at > least > > >>>> the formatting and data for the OPUS stream is identical to the > > >>>> MP3/AAC+ streams). I see people with OPUS streams and metadata but > > >>>> they may not be using IceCast. Is it safe to assume we’ll see this > in > > >>>> the next version? > > >>> We updated Icecast2 some time ago to handle this. It is in the 2.5 > > >>> development trunk. 2.4.x is the current stable branch which only > updated > > >>> with (security) fixes. > > -- > 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 > > _______________________________________________ > Icecast-dev mailing list > Icecast-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast-dev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast-dev/attachments/20170615/50b87425/attachment.html>
Hi all, 2017-06-13 9:33 GMT-05:00 Philipp Schafft <phschafft at de.loewenfelsen.net>:> > Good afternoon, > > > On Mon, 2017-06-12 at 13:20 -0500, Rick Keniuk wrote: > > Marvin, > > > > That is the current version being used and it still has no meta data. > > server_id Icecast 2.4.99.1 > > Icecast2 2.5 beta releases use 2.4.99.x as version number. So that is > correct. > > > > Testing the metadata from the admin page “Update Metadata” results in the response: > > > > Message: Mountpoint will not accept URL updates > > Return Code: 1 > > > > So I would guess it isn’t functioning yet. > > The metadata update interface is only for MP3 and AAC as they do not > have native metadata support. Generally speaking the metadata is in the > domain of the source client. So the source client needs to send them.Not sure if that was an intended feature but I'm pretty sure that metadata update through HTTP calls also works for ogg/vorbis in icecast or at least did at some point. Romain