[Icecast-dev] OPUS/FLAC Metadata

Philipp Schafft phschafft at de.loewenfelsen.net
Tue Jun 13 14:33:52 UTC 2017


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


More information about the Icecast-dev mailing list