<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Thanks Marvin,<div class=""><br class=""></div><div class="">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: </div><div class=""><br class=""></div><div class="">GET/admin/metadata?mode=updinfo&mount=/mystream&mode=updinfo&song=ACDC+Back+In+Black (from the IceCast 2.3.1 documentation)</div><div class=""><br class=""></div><div class="">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?</div><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">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?</div><div class=""><br class=""></div><div class="">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. :-|</div><div class=""><br class=""></div><div class="">Or… Find another Windows OS encoder with this metadata already properly injected for IceCast2 servers.</div><div class=""><br class=""></div><div class="">Rick</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 16, 2017, at 6:18 AM, Marvin Scholz <<a href="mailto:epirat07@gmail.com" class="">epirat07@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">On 16 Jun 2017, at 5:41, Rick Keniuk wrote:</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">Is this the HTTP call for injecting the “song” metadata?<br class="">This is a capture (using RawCap in conjunction with Wireshark) of my AAC+ stream metadata input to IceCast that works fine.<br class=""><br class="">GET /admin/metadata?mode=updinfo&mount=%2FFVHradio_AAC&song=Fox%20Valley%20Hit%20radio%20-%20Hits%20from%20the%20Valley HTTP/1.0<br class="">User-Agent: RadioBOSS<br class="">Authorization: Basic<br class=""><br class="">The same input to IceCast capture for OPUS that does not work.<br class=""><br class="">GET /admin/metadata?mode=updinfo&mount=%2FFVHradio_OPUS&song=Mike%20%26%20The%20Mechanics%20-%20The%20Living%20Years HTTP/1.0<br class="">User-Agent: RadioBOSS<br class="">Authorization: Basic<br class=""><br class="">This it the output of my encoder which is DJsoft’s RadioCaster v2.5.0.0<br class=""><br class="">I think Marvin Scholz indicated that OPUS and FLAC do this differently but that makes it confusing for the encoder people.<br class=""></blockquote><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">This endpoint is for legacy streams like MP3 and AAC.</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">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</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">the web interface. Both you and the source client should not use this for anything else than MP3 and AAC or other unsupported</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">formats.</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">The source client is supposed to encode the metadata into the stream, not use any endpoint whatsoever to send them, for Ogg and</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">other supported formats. There is nothing confusing about this. The reason this is different for MP3 and AAC is, that it is simply</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">impossible to do that for these formats, which is why the endpoint you mentioned exists. Kind of a hack to workaround the limitations</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">of the formats.</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Note that FLAC metadata support is right now not fully working, Icecast will not display them in the Web interface, afaik, but the</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">metadata should appear fine on the listener clients if they support it.</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class=""><br class="">Sorry… I’m a noob at this so I may be explaining this incorrectly.<br class=""><br class="">Rick<br class=""><br class=""><blockquote type="cite" class="">On Jun 15, 2017, at 10:51 AM, Romain Beauxis <<a href="mailto:toots@rastageeks.org" class="">toots@rastageeks.org</a>> wrote:<br class=""><br class="">Hi all,<br class=""><br class="">2017-06-13 9:33 GMT-05:00 Philipp Schafft <<a href="mailto:phschafft@de.loewenfelsen.net" class="">phschafft@de.loewenfelsen.net</a><span class="Apple-converted-space"> </span><<a href="mailto:phschafft@de.loewenfelsen.net" class="">mailto:phschafft@de.loewenfelsen.net</a>>>:<br class=""><blockquote type="cite" class=""><br class="">Good afternoon,<br class=""><br class=""><br class="">On Mon, 2017-06-12 at 13:20 -0500, Rick Keniuk wrote:<br class=""><blockquote type="cite" class="">Marvin,<br class=""><br class="">That is the current version being used and it still has no meta data.<br class="">server_id Icecast 2.4.99.1<br class=""></blockquote><br class="">Icecast2 2.5 beta releases use 2.4.99.x as version number. So that is<br class="">correct.<br class=""><br class=""><br class=""><blockquote type="cite" class="">Testing the metadata from the admin page “Update Metadata” results in the response:<br class=""><br class="">Message: Mountpoint will not accept URL updates<br class="">Return Code: 1<br class=""><br class="">So I would guess it isn’t functioning yet.<br class=""></blockquote><br class="">The metadata update interface is only for MP3 and AAC as they do not<br class="">have native metadata support. Generally speaking the metadata is in the<br class="">domain of the source client. So the source client needs to send them.<br class=""></blockquote><br class="">Not sure if that was an intended feature but I'm pretty sure that<br class="">metadata update through HTTP calls also works for ogg/vorbis in<br class="">icecast or at least did at some point.<br class=""><br class="">Romain<br class=""></blockquote><br class="">_______________________________________________<br class="">Icecast-dev mailing list<br class=""><a href="mailto:Icecast-dev@xiph.org" class="">Icecast-dev@xiph.org</a><br class=""><a href="http://lists.xiph.org/mailman/listinfo/icecast-dev" class="">http://lists.xiph.org/mailman/listinfo/icecast-dev</a></blockquote></div></blockquote></div><br class=""></div></body></html>