[Icecast-dev] OPUS/FLAC Metadata

[Rick Keniuk]

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?

Rick

[Philipp Schafft]

Good evening,

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,

[Rick Keniuk]

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

Rick Keniuk

Post by Philipp Schafft
Good evening,

Post by Rick Keniuk
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,

[Marvin Scholz]

Post by Rick Keniuk
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.

Post by Rick Keniuk
Rick Keniuk

Post by Philipp Schafft
Good evening,

Post by Rick Keniuk
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
http://lists.xiph.org/mailman/listinfo/icecast-dev

[Rick Keniuk]

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.

Post by Marvin Scholz

Post by Rick Keniuk
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.

Post by Rick Keniuk
Rick Keniuk

Post by Philipp Schafft
Good evening,

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
http://lists.xiph.org/mailman/listinfo/icecast-dev <http://lists.xiph.org/mailman/listinfo/icecast-dev>

[Philipp Schafft]

Good afternoon,

Post by Rick Keniuk
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.

Post by Rick Keniuk
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,

Post by Rick Keniuk

Post by Marvin Scholz

Post by Rick Keniuk
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).

Post by Marvin Scholz
Thats correct, that is the 2.5 beta version.

Post by Rick Keniuk
Rick Keniuk

Post by Philipp Schafft

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.

[Eduardo Martinez]

Hi Phillipp,

I don't think there is a ticket open about FLAC metadata specifically. The

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

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

Good afternoon,

Post by Rick Keniuk
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.

Post by Rick Keniuk
Testing the metadata from the admin page “Update Metadata” results in
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,

Post by Rick Keniuk

Post by Marvin Scholz

Post by Rick Keniuk
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).

Post by Marvin Scholz
Thats correct, that is the 2.5 beta version.

Post by Rick Keniuk
Rick Keniuk

Post by Philipp Schafft

Anyone know any workarounds for OPUS/FLAC metadata on IceCast? I’ve
monitored my inbound stream and this is working correctly (or at

least

Post by Rick Keniuk

Post by Marvin Scholz

Post by Rick Keniuk

Post by Philipp Schafft

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

Post by Rick Keniuk

Post by Marvin Scholz

Post by Rick Keniuk

Post by Philipp Schafft

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

Post by Rick Keniuk

Post by Marvin Scholz

Post by Rick Keniuk

Post by Philipp Schafft
with (security) fixes.

--
Philipp Schafft (CEO/GeschÀftsfÌhrer)
Telephon: +49.3535 490 17 92
Bickinger Straße 21 HRB 12308 CB
Germany DE305133015
_______________________________________________
Icecast-dev mailing list
http://lists.xiph.org/mailman/listinfo/icecast-dev

[Romain Beauxis]

Hi all,

Post by Philipp Schafft
Good afternoon,

Post by Rick Keniuk
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.

Post by Rick Keniuk
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

[Rick Keniuk]

Is this the HTTP call for injecting the “song” metadata?
This is a capture (using RawCap in conjunction with Wireshark) of my AAC+ stream metadata input to IceCast that works fine.

GET /admin/metadata?mode=updinfo&mount=%2FFVHradio_AAC&song=Fox%20Valley%20Hit%20radio%20-%20Hits%20from%20the%20Valley HTTP/1.0
User-Agent: RadioBOSS
Authorization: Basic

The same input to IceCast capture for OPUS that does not work.

GET /admin/metadata?mode=updinfo&mount=%2FFVHradio_OPUS&song=Mike%20%26%20The%20Mechanics%20-%20The%20Living%20Years HTTP/1.0
User-Agent: RadioBOSS
Authorization: Basic

This it the output of my encoder which is DJsoft’s RadioCaster v2.5.0.0

I think Marvin Scholz indicated that OPUS and FLAC do this differently but that makes it confusing for the encoder people.

Sorry
 I’m a noob at this so I may be explaining this incorrectly.

Rick

Post by Romain Beauxis
Hi all,

Post by Philipp Schafft
Good afternoon,

Post by Rick Keniuk
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.

Post by Rick Keniuk
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

[Marvin Scholz]

Is this the HTTP call for injecting the “song” metadata?
This is a capture (using RawCap in conjunction with Wireshark) of my
AAC+ stream metadata input to IceCast that works fine.
GET
/admin/metadata?mode=updinfo&mount=%2FFVHradio_AAC&song=Fox%20Valley%20Hit%20radio%20-%20Hits%20from%20the%20Valley
HTTP/1.0
User-Agent: RadioBOSS
Authorization: Basic
The same input to IceCast capture for OPUS that does not work.
GET
/admin/metadata?mode=updinfo&mount=%2FFVHradio_OPUS&song=Mike%20%26%20The%20Mechanics%20-%20The%20Living%20Years
HTTP/1.0
User-Agent: RadioBOSS
Authorization: Basic
This it the output of my encoder which is DJsoft’s RadioCaster
v2.5.0.0
I think Marvin Scholz indicated that OPUS and FLAC do this differently
but that makes it confusing for the encoder people.

This endpoint is for legacy streams like MP3 and AAC.
While it might work with other formats, it should NOT be used. It does
not matter if the source client or you use it through
the web interface. Both you and the source client should not use this
for anything else than MP3 and AAC or other unsupported
formats.

The source client is supposed to encode the metadata into the stream,
not use any endpoint whatsoever to send them, for Ogg and
other supported formats. There is nothing confusing about this. The
reason this is different for MP3 and AAC is, that it is simply
impossible to do that for these formats, which is why the endpoint you
mentioned exists. Kind of a hack to workaround the limitations
of the formats.

Note that FLAC metadata support is right now not fully working, Icecast
will not display them in the Web interface, afaik, but the
metadata should appear fine on the listener clients if they support it.

Sorry… I’m a noob at this so I may be explaining this
incorrectly.
Rick

Post by Romain Beauxis
Hi all,
2017-06-13 9:33 GMT-05:00 Philipp Schafft

Post by Philipp Schafft
Good afternoon,

Post by Rick Keniuk
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.

Post by Rick Keniuk
Testing the metadata from the admin page “Update Metadata”
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

_______________________________________________
Icecast-dev mailing list
http://lists.xiph.org/mailman/listinfo/icecast-dev

[Rick Keniuk]

Thanks Marvin,

Let me see if I’ve got this sorted in my brain before I discuss this my source encoder's company. My source encoder, RadioCaster v2.5.0.0, is a reliable Windows OS broadcast encoder which streams many formats to several different types of servers as well as act as its own server for small numbers of clients. When the encoder is configured to “push” a data stream to IceCast2, RadioCaster injects the metadata into the stream in what is now considered the legacy formatting:

GET/admin/metadata?mode=updinfo&mount=/mystream&mode=updinfo&song=ACDC+Back+In+Black (from the IceCast 2.3.1 documentation)

I can see this in my stream captures directed to IceCast2 on AAC, MP3, and OPUS (didn’t test FLAC). The problem with RadioCaster is that they need to do this only for AAC and MP3 streams. Correct?

When I configure my source encoder to be a “pull” encoder (RadioCaster can be a direct server for small numbers of clients) it does not show metadata at the listening client for any of the formats. This may be because they are still injecting the metadata as above, incompatible with the listening client, or are not injecting the metadata at all. They may only encode the audio stream in this configuration. I would imagine that when this is injected into the stream correctly, the “pull” encoder configuration will have a valid stream with metadata that will be decoded by the listening client. This will then be the same for the “push” encoder configuration sending that identically formatted stream to the IceCast2 server and in-turn to the rest of the listening clients.

New question
 In IceCast2, can this new method of inserting the metadata directly into the stream be done the same for all the formats OPUS, FLAC as well as AAC and MP3? That might simplify the encoders code. Or, will AAC and MP3 remain as they are injected currently in IceCast2?

So
 I will need to find the specification for injecting the OPUS/FLAC metadata directly into the stream and provide it to them. While coaxing them to revise their application. :-|

Or
 Find another Windows OS encoder with this metadata already properly injected for IceCast2 servers.

Rick

Post by Marvin Scholz

Post by Rick Keniuk
Is this the HTTP call for injecting the “song” metadata?
This is a capture (using RawCap in conjunction with Wireshark) of my AAC+ stream metadata input to IceCast that works fine.
GET /admin/metadata?mode=updinfo&mount=%2FFVHradio_AAC&song=Fox%20Valley%20Hit%20radio%20-%20Hits%20from%20the%20Valley HTTP/1.0
User-Agent: RadioBOSS
Authorization: Basic
The same input to IceCast capture for OPUS that does not work.
GET /admin/metadata?mode=updinfo&mount=%2FFVHradio_OPUS&song=Mike%20%26%20The%20Mechanics%20-%20The%20Living%20Years HTTP/1.0
User-Agent: RadioBOSS
Authorization: Basic
This it the output of my encoder which is DJsoft’s RadioCaster v2.5.0.0
I think Marvin Scholz indicated that OPUS and FLAC do this differently but that makes it confusing for the encoder people.

This endpoint is for legacy streams like MP3 and AAC.
While it might work with other formats, it should NOT be used. It does not matter if the source client or you use it through
the web interface. Both you and the source client should not use this for anything else than MP3 and AAC or other unsupported
formats.
The source client is supposed to encode the metadata into the stream, not use any endpoint whatsoever to send them, for Ogg and
other supported formats. There is nothing confusing about this. The reason this is different for MP3 and AAC is, that it is simply
impossible to do that for these formats, which is why the endpoint you mentioned exists. Kind of a hack to workaround the limitations
of the formats.
Note that FLAC metadata support is right now not fully working, Icecast will not display them in the Web interface, afaik, but the
metadata should appear fine on the listener clients if they support it.

Post by Rick Keniuk
Sorry
 I’m a noob at this so I may be explaining this incorrectly.
Rick

Post by Romain Beauxis
Hi all,

Post by Philipp Schafft
Good afternoon,

Post by Rick Keniuk
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.

Post by Rick Keniuk
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

_______________________________________________
Icecast-dev mailing list
http://lists.xiph.org/mailman/listinfo/icecast-dev <http://lists.xiph.org/mailman/listinfo/icecast-dev>

[Jesus Cea]

Post by Marvin Scholz
The source client is supposed to encode the metadata into the stream,
not use any endpoint whatsoever to send them, for Ogg and
other supported formats. There is nothing confusing about this. The
reason this is different for MP3 and AAC is, that it is simply
impossible to do that for these formats, which is why the endpoint you
mentioned exists. Kind of a hack to workaround the limitations
of the formats.

Reading OPUS OGG fileformat, the metadata is limited to the second
"page". In a live-stream, you could not send a new metadata
information... unless you send a logical "End of Stream" to the icecast
server followed by a new "Start of Stream" followed by new metadata. I
wonder if that is transparent to the client, because the client I use
stops reproducing when finding the EOS mark.

So, how OPUS metadata updates works?

I am deploying a new radio streaming service and I would love to use
OPUS streaming, but I don't understand how to send metadata updates to
icecast, how it send them to the clients and, moreover, current Debian
supported version is 2.4.0 (I could override that, of course).

That is, saying that OPUS metadata is embedded in the stream is
insufficient, because OPUS OGG specification clearly indicates that
metadata is ONLY legal at the very beginning of the file.

Please, provide more details.

* How source EXACTLY communicates metadata updates to the server? "Embed
it in the stream" is not enough information.

* How are those updates send to the clients?. Using legacy ICY?, OGG
embedding?. How it works in that case, because OGG only supports
metadata at the beginning of the stream, and stream concatenation (an
EOS followed with a Start Of Stream) is not supported by many clients...

[Romain Beauxis]

Post by Jesus Cea

Post by Marvin Scholz
The source client is supposed to encode the metadata into the stream,
not use any endpoint whatsoever to send them, for Ogg and
other supported formats. There is nothing confusing about this. The
reason this is different for MP3 and AAC is, that it is simply
impossible to do that for these formats, which is why the endpoint you
mentioned exists. Kind of a hack to workaround the limitations
of the formats.

Reading OPUS OGG fileformat, the metadata is limited to the second
"page". In a live-stream, you could not send a new metadata
information... unless you send a logical "End of Stream" to the icecast
server followed by a new "Start of Stream" followed by new metadata. I
wonder if that is transparent to the client, because the client I use
stops reproducing when finding the EOS mark.
So, how OPUS metadata updates works?
I am deploying a new radio streaming service and I would love to use
OPUS streaming, but I don't understand how to send metadata updates to
icecast, how it send them to the clients and, moreover, current Debian
supported version is 2.4.0 (I could override that, of course).
That is, saying that OPUS metadata is embedded in the stream is
insufficient, because OPUS OGG specification clearly indicates that
metadata is ONLY legal at the very beginning of the file.
Please, provide more details.
* How source EXACTLY communicates metadata updates to the server? "Embed
it in the stream" is not enough information.
* How are those updates send to the clients?. Using legacy ICY?, OGG
embedding?. How it works in that case, because OGG only supports
metadata at the beginning of the stream, and stream concatenation (an
EOS followed with a Start Of Stream) is not supported by many clients...

As far as I know, EOS followed by a new stream is the only way to pass
metadata in ogg-embedded streams. Clients didn't support that very well
back some years ago but I would hope that this is better now.. Only other
alternative to avoid stream concatenation is to remove all subsequent
metadata, I'm afraid.

Romain

[Marvin Scholz]

Post by Romain Beauxis

Post by Jesus Cea

Post by Marvin Scholz
The source client is supposed to encode the metadata into the stream,
not use any endpoint whatsoever to send them, for Ogg and
other supported formats. There is nothing confusing about this. The
reason this is different for MP3 and AAC is, that it is simply
impossible to do that for these formats, which is why the endpoint you
mentioned exists. Kind of a hack to workaround the limitations
of the formats.

Reading OPUS OGG fileformat, the metadata is limited to the second
"page". In a live-stream, you could not send a new metadata
information... unless you send a logical "End of Stream" to the icecast
server followed by a new "Start of Stream" followed by new metadata. I
wonder if that is transparent to the client, because the client I use
stops reproducing when finding the EOS mark.
So, how OPUS metadata updates works?
I am deploying a new radio streaming service and I would love to use
OPUS streaming, but I don't understand how to send metadata updates to
icecast, how it send them to the clients and, moreover, current Debian
supported version is 2.4.0 (I could override that, of course).
That is, saying that OPUS metadata is embedded in the stream is
insufficient, because OPUS OGG specification clearly indicates that
metadata is ONLY legal at the very beginning of the file.
Please, provide more details.
* How source EXACTLY communicates metadata updates to the server? "Embed
it in the stream" is not enough information.
* How are those updates send to the clients?. Using legacy ICY?, OGG
embedding?. How it works in that case, because OGG only supports
metadata at the beginning of the stream, and stream concatenation (an
EOS followed with a Start Of Stream) is not supported by many clients...

As far as I know, EOS followed by a new stream is the only way to pass
metadata in ogg-embedded streams. Clients didn't support that very well
back some years ago but I would hope that this is better now.. Only other
alternative to avoid stream concatenation is to remove all subsequent
metadata, I'm afraid.

This concatenation are valid streams, it's called chaining, afaik. So
players not supporting them are broken and the authors should be
notified about it, I think.

Post by Romain Beauxis
Romain
_______________________________________________
Icecast-dev mailing list
http://lists.xiph.org/mailman/listinfo/icecast-dev

[Jesus Cea]

Post by Marvin Scholz
This concatenation are valid streams, it's called chaining, afaik. So
players not supporting them are broken and the authors should be
notified about it, I think.

And my question is... Is THAT the way an OPUS source communicates new
metadata to the icecast server?. That is the question I would like to
know :-).

[Marvin Scholz]

Post by Jesus Cea

Post by Marvin Scholz
This concatenation are valid streams, it's called chaining, afaik. So
players not supporting them are broken and the authors should be
notified about it, I think.

And my question is... Is THAT the way an OPUS source communicates new
metadata to the icecast server?. That is the question I would like to
know :-).

Exactly

Post by Jesus Cea
--
Jesús Cea Avión _/_/ _/_/_/ _/_/_/
"Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/
"My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
_______________________________________________
Icecast-dev mailing list
http://lists.xiph.org/mailman/listinfo/icecast-dev

[Jesus Cea]

Post by Marvin Scholz
Exactly

Ok, GREAT: Thanks.

I have another question: Could a MP3 source send metadata updates using
ICY metadata (like clients receive new metadata, but in reverse order)
or MUST I update via the HTTP interface?.

[Marvin Scholz]

Post by Jesus Cea

Post by Marvin Scholz
Exactly

Ok, GREAT: Thanks.
I have another question: Could a MP3 source send metadata updates using
ICY metadata (like clients receive new metadata, but in reverse order)
or MUST I update via the HTTP interface?.

A source client can't send ICY metadata to Icecast, it has to use the
HTTP endpoint for this.

Post by Jesus Cea
--
Jesús Cea Avión _/_/ _/_/_/ _/_/_/
"Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/
"My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
_______________________________________________
Icecast-dev mailing list
http://lists.xiph.org/mailman/listinfo/icecast-dev

[Rick Keniuk]

I see that there is source code for Icecast v2.5 beta2. Will there be a release of a compiled version for v2.5 beta2 for Windows? I am excited to test the new OPUS/FLAC metadata support. The OPUS CODEC has superior sound for a given data rate to MP3 or AAC.

Thanks for your help,
Rick

Post by Philipp Schafft
Good evening,

Post by Rick Keniuk
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,
--
Philipp Schafft (CEO/Geschäftsführer)
Telephon: +49.3535 490 17 92
Bickinger Straße 21 HRB 12308 CB
Germany DE305133015