From jordan at coolmic.net Mon May 1 16:46:16 2017 From: jordan at coolmic.net (Jordan Erickson) Date: Mon, 1 May 2017 09:46:16 -0700 Subject: [Icecast] Need iOS developer for source client project Message-ID: Hi all, I am in need of a developer(s) to come on board with the Cool Mic project (and an upcoming sister project) to develop the iOS version. Cool Mic is an Icecast source client for Android. It streams live audio from the device's microphone, has many useful features and is designed with portability in mind. If you or someone you know is comfortable developing for iOS and is interested in joining our team, please e-mail team at coolmic.net - This is a paid development project. Thank you very much! https://coolmic.net/ Sincerely, Jordan Erickson From thatjackelliott at kpov.org Tue May 2 01:37:50 2017 From: thatjackelliott at kpov.org (Jack Elliott) Date: Mon, 1 May 2017 18:37:50 -0700 Subject: [Icecast] Server not moving clients to fallback (solved) In-Reply-To: References: Message-ID: <6ec92c0a-74ad-1cf7-5711-d8e7ad27de91@kpov.org> Solved. Changing "/stream.mp3" to "/stream" fixed it. The supplied default icecast.xml has "example.ogg" for the mount-name, suggesting that one needs an extension. Icecast will cheerfully stream the mount whether it is called "stream" or "stream.mp3" (my source is mp3 format) but doesn't like to switch to the fallback-mount. I reckon that the supplied config file has "example.ogg" as the mount and "example2.ogg" as the fallback-mount is because, as the documentation states, the mount and the fallback both need to be the same type else players might get confused. I have also found that in the case of mp3, they also need to be the same bitrate for the same reason. -- That Jack Elliott (541) 848 7021 KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point Host, The Sunday Classics On 04/28/2017 09:53 PM, Jack Elliott wrote: > Hi, thanks in advance for any help that can be provided for this > head-scratcher. > > I'm configuring a new server and can't get it to move listen clients > to the fallback file when the source client disconnects. I probably > have a misconfiguration in icecast.xml. > > Here is the section: > > > /stream.mp3 > 65536 > /fallbacks/Generic_Festival_fallback_192kHz.mp3 > 1 > 1 > 1 > > > Seems okay. Here is the section: > > > > /usr/share/icecast2 > > > /var/log/icecast2 > /usr/share/icecast2/web > /usr/share/icecast2/admin > > > > and > > 1 > > is /usr/share/icecast2/web and the fallback file is in > "fallbacks" under it: > > pi at Pi:/usr/share/icecast2/web/fallbacks $ ls > 400Hz_0dBFS_sine_15m.mp3 Generic_Festival_fallback_128kHz.mp3 > fallback_400hz_minus_20dB.mp3 Generic_Festival_fallback_192kHz.mp3 > > Here is icecast's error.log when it starts up: > > [2017-04-28 21:34:07] INFO main/main Icecast 2.4.0 server started > [2017-04-28 21:34:07] INFO connection/get_ssl_certificate No SSL > capability > [2017-04-28 21:34:07] INFO yp/yp_update_thread YP update thread started > [2017-04-28 21:34:07] INFO source/source_fallback_file mountpoint > /fallbacks/Generic_Festival_fallback_192kHz.mp3 is reserved > [2017-04-28 21:34:07] WARN format/format_get_type Unsupported or > legacy stream type: "audio/mpeg". Falling back to generic minimal > handler for best effort. > [2017-04-28 21:34:07] INFO source/source_main listener count on > /fallbacks/Generic_Festival_fallback_192kHz.mp3 now 0 > > So server has found the fallback. No clients connected. > > Okay, start a stream pointed to /stream and the log adds: > > [2017-04-28 21:40:36] INFO connection/_handle_source_request Source > logging in at mountpoint "/stream" > [2017-04-28 21:40:36] WARN format/format_get_type Unsupported or > legacy stream type: "audio/mpeg". Falling back to generic minimal > handler for best effort. > [2017-04-28 21:40:36] INFO admin/admin_handle_request Received admin > command metadata on mount "/stream" > [2017-04-28 21:40:36] INFO admin/command_metadata Metadata on > mountpoint /stream changed to "asdfsdf" > [2017-04-28 21:40:36] INFO source/source_main listener count on > /stream now 0 > > Connect a listen client: > > [2017-04-28 21:41:40] INFO source/source_main listener count on > /stream now 1 > > The listen-client is receiving the stream. > > Now, if I kill the source mount client: > > [2017-04-28 21:42:48] INFO source/get_next_buffer End of Stream /stream > [2017-04-28 21:42:48] INFO source/source_shutdown Source "/stream" > exiting > [2017-04-28 21:42:48] INFO source/source_clear_source 1 active > listeners on /stream released > > and the listen-client exits. There seems to be no attempt here to > move the listen-client to the fallback mount > ("/fallbacks/Generic_Festival_fallback_192kHz.mp3"). > > If I try to connect a listen-client when the /source client is not > running, it doesn't find a mountpoint, server is not connecting it up. > > I get the same behavior with two different types of listen-clients, so > I reckon I've got something not quite right in the config file, but > error.log isn't revealing it to me. > > It baffles science. > From sm at noisynotes.com Fri May 12 11:26:24 2017 From: sm at noisynotes.com (Steve Matzura) Date: Fri, 12 May 2017 07:26:24 -0400 Subject: [Icecast] Strange Metadata Truncation in 2.43 Message-ID: <3o6bhcdlsks7flr2u80ppdl1mu51ru017s@4ax.com> I recently upgraded from 2.41 to 2.43. I feed my Icecast server with either a live stream or from EZStream. I am now finding that track title metadata never exceeds thirty characters. Is this new, or have I got something wrong in the 2.43 configuration? I am actually using the same one I used for 2.41, and I don't ever remember seeing anything in the XML that controls length of metadata fields. But it's 2.43, not 2.41, so something new may have appeared about which I do not yet know. Thanks in advance. From office at michaelfranzl.com Fri May 12 12:37:36 2017 From: office at michaelfranzl.com (Michael Franzl) Date: Fri, 12 May 2017 14:37:36 +0200 Subject: [Icecast] Circumvention of authentication when using fallback mounts Message-ID: Using latest icecast, let's assume the following hosting scenario. We have 2 mountpoints which are configured with authentication callbacks: /mount1 /mount2 Both mountpoints have configured the same fallback stream, mounted at '/fallback'. Both have fallback-override enabled, so they both can move listeners back from the fallback when they come online. Suppose that both mounts are currently not mounted. Now a client is connecting and successfully authenticating with mountpoint /mount1. Because /mount1 is not yet available, he is moved to /fallback. Now suppose /mount2 comes online. The client is now moved from /fallback to /mount2, even though he has never authenticated with /mount2, but only with /mount1. In fact, the client has no permission at all to connect to /mount2. In short, authentication can be circumvented if the same fallback stream is configured for two 'authenticatable' streams. This would not be a problem if we only used two mounts. We could simply configure two separate fallbacks. But suppose now that we use a wildcard to configure not just two, but N private mounts, i.e. /mount*, so that the mount name is fully determined by the source client. In this scenario, we cannot use a common fallback mount any more without possible circumvention of authentication. Latter scenario is useful when the N mounts carry private audio, and fall back to one stream of 'fallback' music. Is there any way to make this scenario work? Thanks, Michael From lion at lion.leolix.org Fri May 12 12:43:46 2017 From: lion at lion.leolix.org (Philipp Schafft) Date: Fri, 12 May 2017 12:43:46 +0000 Subject: [Icecast] Strange Metadata Truncation in 2.43 In-Reply-To: <3o6bhcdlsks7flr2u80ppdl1mu51ru017s@4ax.com> References: <3o6bhcdlsks7flr2u80ppdl1mu51ru017s@4ax.com> Message-ID: <1494593026.3100.23.camel@lion.leolix.org> Good morning, On Fri, 2017-05-12 at 07:26 -0400, Steve Matzura wrote: > I recently upgraded from 2.41 to 2.43. There is no 2.41 nor 2.43. I guess you talk about 2.4.1 and 2.4.3. My statements are for those releases. > I feed my Icecast server with > either a live stream or from EZStream. I am now finding that track > title metadata never exceeds thirty characters. Is this new, or have I > got something wrong in the 2.43 configuration? There is no change between those two versions regarding that. The only changes are a fix for URL Auth as well as a way how brokenness of Microsoft's filesystem is worked around. > I am actually using the > same one I used for 2.41, and I don't ever remember seeing anything > in the XML that controls length of metadata fields. But it's 2.43, not > 2.41, so something new may have appeared about which I do not yet > know. There is no such setting. The maximum length of a single Vorbis Comment Tag is about 2^32-1 Byte (4GiB)[0][1]. I highly suspect that this is something in the source client not sending data correctly. Feel free to provide the URL of your stream so I we can have a look at it. Have a nice day! With best regards, [0] Likely there is a much smaller limit as you may run out of memory first. [1] A maximum of 2^32-1 headers can be stored. The total vorbis comment block would be 16 EiB large. -- Philipp. (Rah of PH2) From sm at noisynotes.com Fri May 12 17:05:21 2017 From: sm at noisynotes.com (Steve Matzura) Date: Fri, 12 May 2017 13:05:21 -0400 Subject: [Icecast] Strange Metadata Truncation in 2.43 In-Reply-To: <1494593026.3100.23.camel@lion.leolix.org> References: <3o6bhcdlsks7flr2u80ppdl1mu51ru017s@4ax.com> <1494593026.3100.23.camel@lion.leolix.org> Message-ID: Phillip: On Fri, 12 May 2017 12:43:46 +0000, you wrote: >On Fri, 2017-05-12 at 07:26 -0400, Steve Matzura wrote: >> I recently upgraded from 2.41 to 2.43. > >There is no 2.41 nor 2.43. I guess you talk about 2.4.1 and 2.4.3. My >statements are for those releases. Yes. OK, I dropped a decimal point. But yes, those are the ones under discussion. >There is no change between those two versions regarding that. The only >changes are a fix for URL Auth as well as a way how brokenness of >Microsoft's filesystem is worked around. >There is no such setting. The maximum length of a single Vorbis Comment >Tag is about 2^32-1 Byte (4GiB)[0][1]. > >I highly suspect that this is something in the source client not sending >data correctly. Feel free to provide the URL of your stream so I we can >have a look at it. H'mm. I thought so. Could be an EZStream issue. The stream URL is http://theglobalvoice.info:8000/broadband - Thanks in advance for having a look. From phschafft at de.loewenfelsen.net Sat May 13 13:12:30 2017 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Sat, 13 May 2017 13:12:30 +0000 Subject: [Icecast] Circumvention of authentication when using fallback mounts In-Reply-To: References: Message-ID: <1494681150.3100.45.camel@de.loewenfelsen.net> Good afternoon, On Fri, 2017-05-12 at 14:37 +0200, Michael Franzl wrote: > Using latest icecast, let's assume the following hosting scenario. (For the records: this applies to 2.4.x as well as current 2.5.x.) > We have 2 mountpoints which are configured with authentication callbacks: > > /mount1 > /mount2 > > Both mountpoints have configured the same fallback stream, mounted at > '/fallback'. Both have fallback-override enabled, so they both can move > listeners back from the fallback when they come online. > > Suppose that both mounts are currently not mounted. Now a client is > connecting and successfully authenticating with mountpoint /mount1. > Because /mount1 is not yet available, he is moved to /fallback. > > Now suppose /mount2 comes online. The client is now moved from /fallback > to /mount2, even though he has never authenticated with /mount2, but > only with /mount1. In fact, the client has no permission at all to > connect to /mount2. > > In short, authentication can be circumvented if the same fallback stream > is configured for two 'authenticatable' streams. > > This would not be a problem if we only used two mounts. We could simply > configure two separate fallbacks. Basically Icecast moves back the listeners without checking which mount they came from. > But suppose now that we use a wildcard to configure not just two, but N > private mounts, i.e. /mount*, so that the mount name is fully determined > by the source client. In this scenario, we cannot use a common fallback > mount any more without possible circumvention of authentication. > > Latter scenario is useful when the N mounts carry private audio, and > fall back to one stream of 'fallback' music. Yes. It also applies in case you have manual configuration for multiple mount sharing the same fallback. > Is there any way to make this scenario work? Not as of now (beside a lot of fallbacks). A bit of a technical sidenote: Basically the client structure would need to keep track of which sources the client was attached to in form of a stack. This is important as there can be fallbacks of fallbacks (and there are valid reasons to build something like that). A pure 'original mount' thing may result in unexpected behavior. That being even more true if there are multiple paths from one mount to another. Speaking of a solution: I think this is a very valid request for 2.5.x. I would open a ticket for it if you don't want to do it yourself. But 2.5.x is still beta. On the other side 2.4.x will only updated with (security or regression) fixes. So I don't see it entering 2.4.x (unless tbr, our Project Manager decides otherwise). Would a update for 2.5.x help you? If you need a backport for 2.4.x you might consider contacting me off-list. I hope that this mail was at least helpful by confirming the problem. Wish you a good weekend, with best regards, -- 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: From office at michaelfranzl.com Sat May 13 14:11:03 2017 From: office at michaelfranzl.com (Michael Franzl) Date: Sat, 13 May 2017 16:11:03 +0200 Subject: [Icecast] Circumvention of authentication when using fallback mounts In-Reply-To: <1494681150.3100.45.camel@de.loewenfelsen.net> References: <1494681150.3100.45.camel@de.loewenfelsen.net> Message-ID: <3a11b7ad-b469-c1a3-5e3f-d8e6c2592386@michaelfranzl.com> On 05/13/2017 03:12 PM, Philipp Schafft wrote: > Basically the client structure would need to keep track of which sources > the client was attached to in form of a stack. This is important as > there can be fallbacks of fallbacks (and there are valid reasons to > build something like that). A pure 'original mount' thing may result in > unexpected behavior. That being even more true if there are multiple > paths from one mount to another. Sounds about right. Here is another unexpected but similar scenario, which is the current behavior of Icecast: If /music is a declared fallback stream of /voice, and a client connects directly to /music, then, when /voice comes online, the client is be moved to /voice, even though the client has never requested to hear voice. I think the simplest solution would be when Icecast, for each client, constructs a chain (a simple 1D array) of mounts he has 'fallen though', and then, when any parent mount of this chain comes online, moves the client up to that parent, but no further than that. If a client is moved back up the chain, all 'lower' parts of that chain can be forgotten. Regarding authentication in this scenario, Icecast should not remember/cache any previous authentications. As soon as a client is moved to *any* mount (caused by falling through or moving back), it should do a fresh authentication request. For example, permission to listen to a stream could have been revoked from the time a client first connects, then falls through to a fallback, to the time when he is moved back to a private stream. > Speaking of a solution: > I think this is a very valid request for 2.5.x. I would open a ticket > for it if you don't want to do it yourself. But 2.5.x is still beta. On > the other side 2.4.x will only updated with (security or regression) > fixes. So I don't see it entering 2.4.x (unless tbr, our Project Manager > decides otherwise). > > Would a update for 2.5.x help you? This would definitely help, yes, and I would appreciate if you could create the ticket in your system. > I hope that this mail was at least helpful by confirming the problem. Yes, it was. Thank you, Michael -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From phschafft at de.loewenfelsen.net Sat May 13 19:46:37 2017 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Sat, 13 May 2017 19:46:37 +0000 Subject: [Icecast] Circumvention of authentication when using fallback mounts In-Reply-To: <3a11b7ad-b469-c1a3-5e3f-d8e6c2592386@michaelfranzl.com> References: <1494681150.3100.45.camel@de.loewenfelsen.net> <3a11b7ad-b469-c1a3-5e3f-d8e6c2592386@michaelfranzl.com> Message-ID: <1494704797.3100.57.camel@de.loewenfelsen.net> Good evening, On Sat, 2017-05-13 at 16:11 +0200, Michael Franzl wrote: > On 05/13/2017 03:12 PM, Philipp Schafft wrote: > > Basically the client structure would need to keep track of which sources > > the client was attached to in form of a stack. This is important as > > there can be fallbacks of fallbacks (and there are valid reasons to > > build something like that). A pure 'original mount' thing may result in > > unexpected behavior. That being even more true if there are multiple > > paths from one mount to another. > > Sounds about right. Here is another unexpected but similar scenario, > which is the current behavior of Icecast: > > If /music is a declared fallback stream of /voice, and a client connects > directly to /music, then, when /voice comes online, the client is be > moved to /voice, even though the client has never requested to hear voice. > > I think the simplest solution would be when Icecast, for each client, > constructs a chain (a simple 1D array) of mounts he has 'fallen though', > and then, when any parent mount of this chain comes online, moves the > client up to that parent, but no further than that. If a client is moved > back up the chain, all 'lower' parts of that chain can be forgotten. That is basically what I thought about. That stack I talked of is basically that 1D array plus a pointer to the current entry ('bottom most' one). > Regarding authentication in this scenario, Icecast should not > remember/cache any previous authentications. As soon as a client is > moved to *any* mount (caused by falling through or moving back), it > should do a fresh authentication request. For example, permission to > listen to a stream could have been revoked from the time a client first > connects, then falls through to a fallback, to the time when he is moved > back to a private stream. I think this is something totally unrelated. Also I think as fallbacks are configured by the admin a client is implicitly considered authenticated ('admin said so in config'). Furthermore re-authing is something that has a lot problematic bad-paths and would likely be unstable on larger setups. (technical note: Icecast does not cache any kind of authentication data. It only keeps track of what is needed to emit a remove event.) Revoking permissions is yet another concept. You can already do that perfectly fine with current Icecast2: part of the POSTed parameters in the URL Auth request is a parameter 'client'. That value can be used to kick the listener using an /admin/killclient*?mount=$MOUNT&id=$CLIENTID (since at least Icecast2 2.3.x) request at any time. This way you can remove a client the moment the permission is revoked with virtually no delay. > > Would a update for 2.5.x help you? > > This would definitely help, yes, and I would appreciate if you could > create the ticket in your system. Will do the next time I look into the system. > > I hope that this mail was at least helpful by confirming the problem. > > Yes, it was. Good. :) Also hope my comment on the revoking and removal helps. Wish you a good weekend. I will be back on Monday. With best regards, -- 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: From office at michaelfranzl.com Mon May 15 18:34:38 2017 From: office at michaelfranzl.com (Michael Franzl) Date: Mon, 15 May 2017 20:34:38 +0200 Subject: [Icecast] Circumvention of authentication when using fallback mounts In-Reply-To: <1494704797.3100.57.camel@de.loewenfelsen.net> References: <1494681150.3100.45.camel@de.loewenfelsen.net> <3a11b7ad-b469-c1a3-5e3f-d8e6c2592386@michaelfranzl.com> <1494704797.3100.57.camel@de.loewenfelsen.net> Message-ID: On 05/13/2017 09:46 PM, Philipp Schafft wrote: > I think this is something totally unrelated. Yes, my thought on the authentication was unrelated, and not relevant to the subject. Thanks for your hints regarding the POST API. Michael -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From thatjackelliott at kpov.org Mon May 15 21:46:07 2017 From: thatjackelliott at kpov.org (Jack Elliott) Date: Mon, 15 May 2017 14:46:07 -0700 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? Message-ID: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> Fraunhofer Institute for Integrated Circuits has stopped providing licenses for MP3 technology, "[...] noting that more superior audio formats have rendered the MP3 obsolete. Speaking to National Public Radio (USA), the Fraunhofer Institute said AAC has since become the 'de facto standard for music download and videos on mobile phones.' " http://www.networkworld.com/article/3196788/consumer-electronics/mp3-player-ipod-licensing-dead.html This raises a point I wanted to ask about. Icecast supports mp3 (it's the current lowest-common denominator for media players, yes?) and ogg. I'd like to send a higher-fidelity stream from our music festival remotes, but ogg isn't an option because the station's media player, iTunes (running on a Mac) doesn't support ogg. Is there any work being done to support AAC in Icecast? Oh, wait. Use of AAC in an encoder requires paying a licensing fee. Drat. So we have mp3 (free, sounds crummy, everything plays it) and ogg (free, sounds better, but does anyone know of any programs for Macs that can play an ogg stream?) -- That Jack Elliott (541) 848 7021 KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point Host, The Sunday Classics From jeffares.robert at gmail.com Mon May 15 22:25:43 2017 From: jeffares.robert at gmail.com (Robert Jeffares) Date: Tue, 16 May 2017 10:25:43 +1200 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> Message-ID: <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> Jack, I am using AAC+ encoded by Darkice and distributed on Icecast2 on a Ubuntu server. I had to install a number of open source libraries and compile darkice from source. No licence. non-free means you build each one stand alone and can't re distribute. Quality is excellent, and it runs on most players. I kept some notes [see below] I am using AAC+ to feed a couple of LPFM sites with almost zero errors over what had been troublesome paths for mp3 HE-AAC audio v2 (with SBR + PS) is the superb audio encoder used to encode high quality audio at really low bitrates (32 kbit/s). Quote from Wikipedia "Data from this testing also indicated that some individuals confused 48 kbit/s encoded material with an uncompressed original." In order to quickly compile your ?libaacplus library, you can type the following commands in your shell: # apt-get install libfftw3-dev pkg-config autoconf automake libtool unzip $ wget http://tipok.org.ua/downloads/media/aacplus/libaacplus/libaacplus-2.0.2.tar.gz $ tar -xzf libaacplus-2.0.2.tar.gz $ cd libaacplus-2.0.2 $ ./autogen.sh --enable-shared --enable-static $ make # make install # ldconfig P.S. If you are using Ubuntu, you'll most probably have to use sudo for the last 2 commands, like: $ sudo make install $ sudo ldconfig In case that website above (hosting libaacplus) goes offline, you can download the copy of that tar.gz file from here: (MD5: 3fc15d5aa91d0e8b8f94acb6555103da) $ wget http://ffmpeg.gusari.org/uploads/libaacplus-2.0.2.tar.gz More info at: ?http://tipok.org.ua/node/17 NOTE: libaacplus is a non-free library, so you won't be able to build GPL alike FFmpeg with this library, i.e. your FFmpeg will not be redistributable. regards Robert Jeffares On 16/05/17 09:46, Jack Elliott wrote: > Fraunhofer Institute for Integrated Circuits has stopped providing > licenses for MP3 technology, "[...] noting that more superior audio > formats have rendered the MP3 obsolete. Speaking to National Public > Radio (USA), the Fraunhofer Institute said AAC has since become the > 'de facto standard for music download and videos on mobile phones.' " > > http://www.networkworld.com/article/3196788/consumer-electronics/mp3-player-ipod-licensing-dead.html > > > This raises a point I wanted to ask about. Icecast supports mp3 (it's > the current lowest-common denominator for media players, yes?) and > ogg. I'd like to send a higher-fidelity stream from our music festival > remotes, but ogg isn't an option because the station's media player, > iTunes (running on a Mac) doesn't support ogg. > > Is there any work being done to support AAC in Icecast? Oh, wait. Use > of AAC in an encoder requires paying a licensing fee. Drat. > > So we have mp3 (free, sounds crummy, everything plays it) and ogg > (free, sounds better, but does anyone know of any programs for Macs > that can play an ogg stream?) > From thatjackelliott at kpov.org Mon May 15 22:34:41 2017 From: thatjackelliott at kpov.org (Jack Elliott) Date: Mon, 15 May 2017 15:34:41 -0700 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> Message-ID: Hi Robert . . . so you're saying that you're feeding Icecast2 an AAC stream and it's not complaining? -- That Jack Elliott (541) 848 7021 KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point Host, The Sunday Classics On 5/15/2017 3:25 PM, Robert Jeffares wrote: > Jack, > > I am using AAC+ encoded by Darkice and distributed on Icecast2 on a > Ubuntu server. I had to install a number of open source libraries and > compile darkice from source. No licence. > > non-free means you build each one stand alone and can't re distribute. > > Quality is excellent, and it runs on most players. > > I kept some notes [see below] > > I am using AAC+ to feed a couple of LPFM sites with almost zero errors > over what had been troublesome paths for mp3 > > HE-AAC audio v2 (with SBR + PS) is the superb audio encoder used to > encode high quality audio at really low bitrates (32 kbit/s). Quote > from Wikipedia "Data from this testing also indicated that some > individuals confused 48 kbit/s encoded material with an uncompressed > original." > > In order to quickly compile your ?libaacplus library, you can type the > following commands in your shell: > > # apt-get install libfftw3-dev pkg-config autoconf automake libtool unzip > $ wget > http://tipok.org.ua/downloads/media/aacplus/libaacplus/libaacplus-2.0.2.tar.gz > $ tar -xzf libaacplus-2.0.2.tar.gz > $ cd libaacplus-2.0.2 > $ ./autogen.sh --enable-shared --enable-static > $ make > # make install > # ldconfig > > P.S. If you are using Ubuntu, you'll most probably have to use sudo > for the last 2 commands, like: > > $ sudo make install > $ sudo ldconfig > > In case that website above (hosting libaacplus) goes offline, you can > download the copy of that tar.gz file from here: (MD5: > 3fc15d5aa91d0e8b8f94acb6555103da) > > $ wget http://ffmpeg.gusari.org/uploads/libaacplus-2.0.2.tar.gz > > More info at: ?http://tipok.org.ua/node/17 > > NOTE: libaacplus is a non-free library, so you won't be able to build > GPL alike FFmpeg with this library, i.e. your FFmpeg will not be > redistributable. > > > > regards > > > Robert Jeffares > > > On 16/05/17 09:46, Jack Elliott wrote: >> Fraunhofer Institute for Integrated Circuits has stopped providing >> licenses for MP3 technology, "[...] noting that more superior audio >> formats have rendered the MP3 obsolete. Speaking to National Public >> Radio (USA), the Fraunhofer Institute said AAC has since become the >> 'de facto standard for music download and videos on mobile phones.' " >> >> http://www.networkworld.com/article/3196788/consumer-electronics/mp3-player-ipod-licensing-dead.html >> >> >> This raises a point I wanted to ask about. Icecast supports mp3 (it's >> the current lowest-common denominator for media players, yes?) and >> ogg. I'd like to send a higher-fidelity stream from our music >> festival remotes, but ogg isn't an option because the station's media >> player, iTunes (running on a Mac) doesn't support ogg. >> >> Is there any work being done to support AAC in Icecast? Oh, wait. Use >> of AAC in an encoder requires paying a licensing fee. Drat. >> >> So we have mp3 (free, sounds crummy, everything plays it) and ogg >> (free, sounds better, but does anyone know of any programs for Macs >> that can play an ogg stream?) >> > From relen at brideswell.com Mon May 15 22:13:23 2017 From: relen at brideswell.com (Richard G Elen) Date: Mon, 15 May 2017 23:13:23 +0100 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> Message-ID: <08810635-c1f8-82fd-6dd6-44053de09388@brideswell.com> You can send AAC-HE from a streaming client (LadioCast on Mac for example) to an Icecast server and it'll broadcast an AAC stream. If you have an AutoDJ system with the appropriate capability (eg Centova) then you can set that up for AAC-HE too in the mount point config.* (*Well, we can - we're running Icecast 2.4.0-kh4 here.) --R On 15-May-17 22:46, Jack Elliott wrote: > Is there any work being done to support AAC in Icecast? Oh, wait. Use > of AAC in an encoder requires paying a licensing fee. Drat. From thatjackelliott at kpov.org Mon May 15 23:31:07 2017 From: thatjackelliott at kpov.org (Jack Elliott) Date: Mon, 15 May 2017 16:31:07 -0700 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: <08810635-c1f8-82fd-6dd6-44053de09388@brideswell.com> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <08810635-c1f8-82fd-6dd6-44053de09388@brideswell.com> Message-ID: <196c1e89-a814-8bbf-05d2-7568483ce8a7@kpov.org> If Icecast2 works fine with AAC, shouldn't that be mentioned in the documentation? -- That Jack Elliott (541) 848 7021 KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point Host, The Sunday Classics On 5/15/2017 3:13 PM, Richard G Elen wrote: > You can send AAC-HE from a streaming client (LadioCast on Mac for > example) to an Icecast server and it'll broadcast an AAC stream. If > you have an AutoDJ system with the appropriate capability (eg Centova) > then you can set that up for AAC-HE too in the mount point config.* > > (*Well, we can - we're running Icecast 2.4.0-kh4 here.) > > --R > > On 15-May-17 22:46, Jack Elliott wrote: >> Is there any work being done to support AAC in Icecast? Oh, wait. Use >> of AAC in an encoder requires paying a licensing fee. Drat. > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From ross at stationplaylist.com Tue May 16 04:26:10 2017 From: ross at stationplaylist.com (Ross Levis) Date: Tue, 16 May 2017 16:26:10 +1200 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> Message-ID: <000001d2cdfc$8d1f7f30$a75e7d90$@com> Rather off topic, but I wonder if this means MP3 encoding is now licence free and encoders can be included in commercial software with no licence. -----Original Message----- From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Jack Elliott Sent: Tuesday, 16 May 2017 9:46 a.m. To: Icecast streaming server user discussions Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? Fraunhofer Institute for Integrated Circuits has stopped providing licenses for MP3 technology, "[...] noting that more superior audio formats have rendered the MP3 obsolete. Speaking to National Public Radio (USA), the Fraunhofer Institute said AAC has since become the 'de facto standard for music download and videos on mobile phones.' " http://www.networkworld.com/article/3196788/consumer-electronics/mp3-player-ipod-licensing-dead.html This raises a point I wanted to ask about. Icecast supports mp3 (it's the current lowest-common denominator for media players, yes?) and ogg. I'd like to send a higher-fidelity stream from our music festival remotes, but ogg isn't an option because the station's media player, iTunes (running on a Mac) doesn't support ogg. Is there any work being done to support AAC in Icecast? Oh, wait. Use of AAC in an encoder requires paying a licensing fee. Drat. So we have mp3 (free, sounds crummy, everything plays it) and ogg (free, sounds better, but does anyone know of any programs for Macs that can play an ogg stream?) -- That Jack Elliott (541) 848 7021 KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point Host, The Sunday Classics _______________________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast From greg at indexcom.com Tue May 16 05:45:23 2017 From: greg at indexcom.com (Greg Ogonowski) Date: Mon, 15 May 2017 22:45:23 -0700 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: <196c1e89-a814-8bbf-05d2-7568483ce8a7@kpov.org> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <08810635-c1f8-82fd-6dd6-44053de09388@brideswell.com> <196c1e89-a814-8bbf-05d2-7568483ce8a7@kpov.org> Message-ID: <254f01d2ce07$9ca66850$d5f338f0$@indexcom.com> It also works with xHE-AAC, which is a new Content Type: audio/usac The StreamS HiFi Radio Player App for iOS/tvOS is the first App to support this. Offers arbitrary URL entry, ICY and HLS support. And best of all, NO hidden agenda. No sign-in or account to use the App. We of course, also offer the encoders. xHE-AAC streams are now starting to appear on the Internet. www.indexcom.com /greg. -----Original Message----- From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Jack Elliott Sent: Monday, 15 May, 2017 16:31 To: Icecast streaming server user discussions; Richard G Elen Subject: Re: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? If Icecast2 works fine with AAC, shouldn't that be mentioned in the documentation? -- That Jack Elliott (541) 848 7021 KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point Host, The Sunday Classics On 5/15/2017 3:13 PM, Richard G Elen wrote: > You can send AAC-HE from a streaming client (LadioCast on Mac for > example) to an Icecast server and it'll broadcast an AAC stream. If > you have an AutoDJ system with the appropriate capability (eg Centova) > then you can set that up for AAC-HE too in the mount point config.* > > (*Well, we can - we're running Icecast 2.4.0-kh4 here.) > > --R > > On 15-May-17 22:46, Jack Elliott wrote: >> Is there any work being done to support AAC in Icecast? Oh, wait. Use >> of AAC in an encoder requires paying a licensing fee. Drat. > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast _______________________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast From epirat07 at gmail.com Tue May 16 08:51:41 2017 From: epirat07 at gmail.com (Marvin Scholz) Date: Tue, 16 May 2017 10:51:41 +0200 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> Message-ID: <0075B862-70A7-41A0-9AFC-F6DF1C2B8190@gmail.com> First: I am not a lawyer, this is no legal advice! On 16 May 2017, at 0:25, Robert Jeffares wrote: > Jack, > > I am using AAC+ encoded by Darkice and distributed on Icecast2 on a > Ubuntu server. I had to install a number of open source libraries and > compile darkice from source. No licence. This sounds like it would violate the license, given that the FAQ on http://www.via-corp.com/us/en/licensing/aac/faq.html states: > An AAC patent license is needed by manufacturers or developers of > end-user encoder and/or decoder products. Additionally on the authors website for libaacplus it clearly says: > These tarballs don't provide any 3GPP source code. It is downloaded > from 3GPP during compilation. To use package compiled by this code, > you may need a license from 3GPP. > > AAC+ codecs incorporate several patents, held by Philips, Dolby, > Ericsson and Nokia. Companies holding patents for HE AAC v1 (SBR) have > formed a patent pool under Via Licensing to provide a single point of > license for product makers. Patents owned by Dolby and Philips > covering the Parametric Stereo used in HE AAC v2 (SBR+PS) are not > included in the Via Licensing pool and are licensed separately by > Dolby. Depending on law in your country, manufacturers and developers > may need to get a license. Because it is a shared library, you may > need special contract for each one application, which links against > this library, directly or indirectly. > > Please also note, that downloaded .doc file has a very restrictive > license: No part may be reproduced except as authorized by written > permission. The copyright and the foregoing restriction extend to > reproduction in all media. This is certainly not something I would like to see recommended to be used, on this mailing list. From thatjackelliott at kpov.org Tue May 16 13:55:06 2017 From: thatjackelliott at kpov.org (Jack Elliott) Date: Tue, 16 May 2017 06:55:06 -0700 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: <0075B862-70A7-41A0-9AFC-F6DF1C2B8190@gmail.com> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> <0075B862-70A7-41A0-9AFC-F6DF1C2B8190@gmail.com> Message-ID: Marvin, fair enough. Via's licensing terms appear to apply to encoders and decoders only, and not to transports, such as Icecast ("An AAC patent license is needed by manufacturers or developers of end-user encoder and/or decoder products"), so using Icecast to transport an AAC-encoded stream is not a violation of the AAC is not mentioned in the Icecast documentation (that I can find) though Icecast apparently is capable of transporting AAC-encoded streams. Are there other types of streams that Icecast can transport besides mp3 and ogg? -- That Jack Elliott (541) 848 7021 KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point Host, The Sunday Classics On 5/16/2017 1:51 AM, Marvin Scholz wrote: > First: I am not a lawyer, this is no legal advice! > > On 16 May 2017, at 0:25, Robert Jeffares wrote: > >> Jack, >> >> I am using AAC+ encoded by Darkice and distributed on Icecast2 on a >> Ubuntu server. I had to install a number of open source libraries and >> compile darkice from source. No licence. > > This sounds like it would violate the license, given that the FAQ on > http://www.via-corp.com/us/en/licensing/aac/faq.html states: > >> An AAC patent license is needed by manufacturers or developers of >> end-user encoder and/or decoder products. > > Additionally on the authors website for libaacplus it clearly says: > >> These tarballs don't provide any 3GPP source code. It is downloaded >> from 3GPP during compilation. To use package compiled by this code, >> you may need a license from 3GPP. >> >> AAC+ codecs incorporate several patents, held by Philips, Dolby, >> Ericsson and Nokia. Companies holding patents for HE AAC v1 (SBR) >> have formed a patent pool under Via Licensing to provide a single >> point of license for product makers. Patents owned by Dolby and >> Philips covering the Parametric Stereo used in HE AAC v2 (SBR+PS) are >> not included in the Via Licensing pool and are licensed separately by >> Dolby. Depending on law in your country, manufacturers and developers >> may need to get a license. Because it is a shared library, you may >> need special contract for each one application, which links against >> this library, directly or indirectly. >> >> Please also note, that downloaded .doc file has a very restrictive >> license: No part may be reproduced except as authorized by written >> permission. The copyright and the foregoing restriction extend to >> reproduction in all media. > > This is certainly not something I would like to see recommended to be > used, on this mailing list. > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From greg at indexcom.com Tue May 16 17:19:25 2017 From: greg at indexcom.com (Greg Ogonowski) Date: Tue, 16 May 2017 10:19:25 -0700 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> <0075B862-70A7-41A0-9AFC-F6DF1C2B8190@gmail.com> Message-ID: <26af01d2ce68$9192bfc0$b4b83f40$@indexcom.com> That is correct. AAC License has nothing to do with transport. Icecast can also transport the new xHE-AAC with a content type of audio/usac. I posted a bit of information about this in an earlier post. /greg. StreamS HiFi Radio -----Original Message----- From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Jack Elliott Sent: Tuesday, 16 May, 2017 06:55 To: Icecast streaming server user discussions; Marvin Scholz Subject: Re: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? Marvin, fair enough. Via's licensing terms appear to apply to encoders and decoders only, and not to transports, such as Icecast ("An AAC patent license is needed by manufacturers or developers of end-user encoder and/or decoder products"), so using Icecast to transport an AAC-encoded stream is not a violation of the AAC is not mentioned in the Icecast documentation (that I can find) though Icecast apparently is capable of transporting AAC-encoded streams. Are there other types of streams that Icecast can transport besides mp3 and ogg? -- That Jack Elliott (541) 848 7021 KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point Host, The Sunday Classics On 5/16/2017 1:51 AM, Marvin Scholz wrote: > First: I am not a lawyer, this is no legal advice! > > On 16 May 2017, at 0:25, Robert Jeffares wrote: > >> Jack, >> >> I am using AAC+ encoded by Darkice and distributed on Icecast2 on a >> Ubuntu server. I had to install a number of open source libraries and >> compile darkice from source. No licence. > > This sounds like it would violate the license, given that the FAQ on > http://www.via-corp.com/us/en/licensing/aac/faq.html states: > >> An AAC patent license is needed by manufacturers or developers of >> end-user encoder and/or decoder products. > > Additionally on the authors website for libaacplus it clearly says: > >> These tarballs don't provide any 3GPP source code. It is downloaded >> from 3GPP during compilation. To use package compiled by this code, >> you may need a license from 3GPP. >> >> AAC+ codecs incorporate several patents, held by Philips, Dolby, >> Ericsson and Nokia. Companies holding patents for HE AAC v1 (SBR) >> have formed a patent pool under Via Licensing to provide a single >> point of license for product makers. Patents owned by Dolby and >> Philips covering the Parametric Stereo used in HE AAC v2 (SBR+PS) are >> not included in the Via Licensing pool and are licensed separately by >> Dolby. Depending on law in your country, manufacturers and developers >> may need to get a license. Because it is a shared library, you may >> need special contract for each one application, which links against >> this library, directly or indirectly. >> >> Please also note, that downloaded .doc file has a very restrictive >> license: No part may be reproduced except as authorized by written >> permission. The copyright and the foregoing restriction extend to >> reproduction in all media. > > This is certainly not something I would like to see recommended to be > used, on this mailing list. > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast _______________________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast From jeffares.robert at gmail.com Wed May 17 00:03:09 2017 From: jeffares.robert at gmail.com (Robert Jeffares) Date: Wed, 17 May 2017 12:03:09 +1200 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: <0075B862-70A7-41A0-9AFC-F6DF1C2B8190@gmail.com> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> <0075B862-70A7-41A0-9AFC-F6DF1C2B8190@gmail.com> Message-ID: <31504d55-051b-2103-0457-18c3d42ab214@gmail.com> I must say this is a very confusing issue. I generate AAC+ on an open source system which downloaded some code during installation from the 3GPP source. It appears the encoding software is being freely distributed, and hardware which decodes the stream pays a licence fee at point of manufacture. We have such hardware. In a number of locations. One brand has AAC+ only, not AAC. I note VLC also plays the encoded stream. Encoding and decoding uses sound cards, which have hard coded processors on board, whose manufacturers presumably have paid various patent holders for the appropriate rights. I am reasonably confident the patent holders would not have allowed me to download the code without fee if they haven't already taken care of their right to reward. Key point for me is that we are not making products for sale, we are employing the technology to provide a stream for licenced products to receive. ------------------------ From http://www.via-corp.com/us/en/licensing/aac/faq.html Are there use fees for AAC? No. License fees are due on the sale of encoders and/or decoders only. There are no patent license fees due on the distribution of bit-stream encoded in AAC, whether such bit-streams are broadcast, streamed over a network, or provided on physical media. --------------------- "In House" use appears not to be of interest to the patent holders. They, correctly, want to collect from products manufactured and sold at a profit. It is in their interest for there to be source material. This is my opinion, based on my reading of the published information from the patent holders. Now answering the original question: Icecast2 will carry a number of streams both audio and video which are not all documented. Icecast>Icecast links over less then optimal WAN are generally robust, provided you keep within the limits of the connecting platform. The software is essentially a delivery system. Setting the buffer to allow for network delays gets over a fair percentage of the problems. Yes you may have quite some delay. Usually it does not matter. In one case I found a faulty server in the path between our originating site and transmission site was causing transmission delays we could not buffer. [Emailing everyone on the whois information produced a result!] I have trialled a number of audio formats in various bitrates. MP3 turned out to be most reliable and we deliver mp3 to various distribution services. I set up an AAC+ system because it could give me a low profile backhaul off air monitor over a limited capacity ADSL circuit. It worked so well I have slowly incorporated AAC+ feeds into other places with good results. AAC+ out performs mp3. I prefer Darkice as an encoder, others use liquidsoap. I also use glasscoder which works well. AAC+ contains it's own header information so you don't have to use a suffix like .mp4 It seems to work in various smartphones, which I assume have paid the royalty. regards Robert Jeffares On 16/05/17 20:51, Marvin Scholz wrote: > First: I am not a lawyer, this is no legal advice! > > On 16 May 2017, at 0:25, Robert Jeffares wrote: > >> Jack, >> >> I am using AAC+ encoded by Darkice and distributed on Icecast2 on a >> Ubuntu server. I had to install a number of open source libraries and >> compile darkice from source. No licence. > > This sounds like it would violate the license, given that the FAQ on > http://www.via-corp.com/us/en/licensing/aac/faq.html states: > >> An AAC patent license is needed by manufacturers or developers of >> end-user encoder and/or decoder products. > > Additionally on the authors website for libaacplus it clearly says: > >> These tarballs don't provide any 3GPP source code. It is downloaded >> from 3GPP during compilation. To use package compiled by this code, >> you may need a license from 3GPP. >> >> AAC+ codecs incorporate several patents, held by Philips, Dolby, >> Ericsson and Nokia. Companies holding patents for HE AAC v1 (SBR) >> have formed a patent pool under Via Licensing to provide a single >> point of license for product makers. Patents owned by Dolby and >> Philips covering the Parametric Stereo used in HE AAC v2 (SBR+PS) are >> not included in the Via Licensing pool and are licensed separately by >> Dolby. Depending on law in your country, manufacturers and developers >> may need to get a license. Because it is a shared library, you may >> need special contract for each one application, which links against >> this library, directly or indirectly. >> >> Please also note, that downloaded .doc file has a very restrictive >> license: No part may be reproduced except as authorized by written >> permission. The copyright and the foregoing restriction extend to >> reproduction in all media. > > This is certainly not something I would like to see recommended to be > used, on this mailing list. > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From greg at indexcom.com Wed May 17 00:09:09 2017 From: greg at indexcom.com (Greg Ogonowski) Date: Tue, 16 May 2017 17:09:09 -0700 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: <31504d55-051b-2103-0457-18c3d42ab214@gmail.com> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> <0075B862-70A7-41A0-9AFC-F6DF1C2B8190@gmail.com> <31504d55-051b-2103-0457-18c3d42ab214@gmail.com> Message-ID: <27a801d2cea1$ce60e9c0$6b22bd40$@indexcom.com> It's really pretty simple. You can download the code and build it all you want... ...for yourself. It cannot be distributed, sold, or used commercially in any way. That's all. /g. -----Original Message----- From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Robert Jeffares Sent: Tuesday, 16 May, 2017 17:03 To: icecast at xiph.org Subject: Re: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? I must say this is a very confusing issue. I generate AAC+ on an open source system which downloaded some code during installation from the 3GPP source. It appears the encoding software is being freely distributed, and hardware which decodes the stream pays a licence fee at point of manufacture. We have such hardware. In a number of locations. One brand has AAC+ only, not AAC. I note VLC also plays the encoded stream. Encoding and decoding uses sound cards, which have hard coded processors on board, whose manufacturers presumably have paid various patent holders for the appropriate rights. I am reasonably confident the patent holders would not have allowed me to download the code without fee if they haven't already taken care of their right to reward. Key point for me is that we are not making products for sale, we are employing the technology to provide a stream for licenced products to receive. ------------------------ From http://www.via-corp.com/us/en/licensing/aac/faq.html Are there use fees for AAC? No. License fees are due on the sale of encoders and/or decoders only. There are no patent license fees due on the distribution of bit-stream encoded in AAC, whether such bit-streams are broadcast, streamed over a network, or provided on physical media. --------------------- "In House" use appears not to be of interest to the patent holders. They, correctly, want to collect from products manufactured and sold at a profit. It is in their interest for there to be source material. This is my opinion, based on my reading of the published information from the patent holders. Now answering the original question: Icecast2 will carry a number of streams both audio and video which are not all documented. Icecast>Icecast links over less then optimal WAN are generally robust, provided you keep within the limits of the connecting platform. The software is essentially a delivery system. Setting the buffer to allow for network delays gets over a fair percentage of the problems. Yes you may have quite some delay. Usually it does not matter. In one case I found a faulty server in the path between our originating site and transmission site was causing transmission delays we could not buffer. [Emailing everyone on the whois information produced a result!] I have trialled a number of audio formats in various bitrates. MP3 turned out to be most reliable and we deliver mp3 to various distribution services. I set up an AAC+ system because it could give me a low profile backhaul off air monitor over a limited capacity ADSL circuit. It worked so well I have slowly incorporated AAC+ feeds into other places with good results. AAC+ out performs mp3. I prefer Darkice as an encoder, others use liquidsoap. I also use glasscoder which works well. AAC+ contains it's own header information so you don't have to use a suffix like .mp4 It seems to work in various smartphones, which I assume have paid the royalty. regards Robert Jeffares On 16/05/17 20:51, Marvin Scholz wrote: > First: I am not a lawyer, this is no legal advice! > > On 16 May 2017, at 0:25, Robert Jeffares wrote: > >> Jack, >> >> I am using AAC+ encoded by Darkice and distributed on Icecast2 on a >> Ubuntu server. I had to install a number of open source libraries and >> compile darkice from source. No licence. > > This sounds like it would violate the license, given that the FAQ on > http://www.via-corp.com/us/en/licensing/aac/faq.html states: > >> An AAC patent license is needed by manufacturers or developers of >> end-user encoder and/or decoder products. > > Additionally on the authors website for libaacplus it clearly says: > >> These tarballs don't provide any 3GPP source code. It is downloaded >> from 3GPP during compilation. To use package compiled by this code, >> you may need a license from 3GPP. >> >> AAC+ codecs incorporate several patents, held by Philips, Dolby, >> Ericsson and Nokia. Companies holding patents for HE AAC v1 (SBR) >> have formed a patent pool under Via Licensing to provide a single >> point of license for product makers. Patents owned by Dolby and >> Philips covering the Parametric Stereo used in HE AAC v2 (SBR+PS) are >> not included in the Via Licensing pool and are licensed separately by >> Dolby. Depending on law in your country, manufacturers and developers >> may need to get a license. Because it is a shared library, you may >> need special contract for each one application, which links against >> this library, directly or indirectly. >> >> Please also note, that downloaded .doc file has a very restrictive >> license: No part may be reproduced except as authorized by written >> permission. The copyright and the foregoing restriction extend to >> reproduction in all media. > > This is certainly not something I would like to see recommended to be > used, on this mailing list. > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast _______________________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast From thatjackelliott at kpov.org Wed May 17 00:33:04 2017 From: thatjackelliott at kpov.org (Jack Elliott) Date: Tue, 16 May 2017 17:33:04 -0700 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: <000001d2cdfc$8d1f7f30$a75e7d90$@com> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <000001d2cdfc$8d1f7f30$a75e7d90$@com> Message-ID: <36f15301-ca9c-7768-3651-376b79cb930d@kpov.org> Encoding not being part of Icecast, I reckon this is indeed off-topic; but to close the thread, it does seem to be the case that mp3 encoding is now license free. "MP3 is supported by everything, everywhere, and is now patent-free. There has never been another audio format as widely supported as MP3, it's good enough for almost anything, and now, over twenty years since it took the world by storm, it's finally free." https://tech.slashdot.org/story/17/05/16/1314221/mp3-is-not-dead-its-finally-free -- That Jack Elliott (541) 848 7021 KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point Host, The Sunday Classics On 5/15/2017 9:26 PM, Ross Levis wrote: > Rather off topic, but I wonder if this means MP3 encoding is now licence free and encoders can be included in commercial software with no licence. > > -----Original Message----- > From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Jack Elliott > Sent: Tuesday, 16 May 2017 9:46 a.m. > To: Icecast streaming server user discussions > Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? > > Fraunhofer Institute for Integrated Circuits has stopped providing licenses for MP3 technology, "[...] noting that more superior audio formats have rendered the MP3 obsolete. Speaking to National Public Radio (USA), the Fraunhofer Institute said AAC has since become the 'de facto standard for music download and videos on mobile phones.' " > > http://www.networkworld.com/article/3196788/consumer-electronics/mp3-player-ipod-licensing-dead.html > > This raises a point I wanted to ask about. Icecast supports mp3 (it's the current lowest-common denominator for media players, yes?) and ogg. > I'd like to send a higher-fidelity stream from our music festival remotes, but ogg isn't an option because the station's media player, iTunes (running on a Mac) doesn't support ogg. > > Is there any work being done to support AAC in Icecast? Oh, wait. Use of AAC in an encoder requires paying a licensing fee. Drat. > > So we have mp3 (free, sounds crummy, everything plays it) and ogg (free, sounds better, but does anyone know of any programs for Macs that can play an ogg stream?) > > -- > That Jack Elliott > (541) 848 7021 > KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point Host, The Sunday Classics > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > From greg at indexcom.com Wed May 17 00:33:20 2017 From: greg at indexcom.com (Greg Ogonowski) Date: Tue, 16 May 2017 17:33:20 -0700 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: <36f15301-ca9c-7768-3651-376b79cb930d@kpov.org> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <000001d2cdfc$8d1f7f30$a75e7d90$@com> <36f15301-ca9c-7768-3651-376b79cb930d@kpov.org> Message-ID: <27b101d2cea5$2f508ee0$8df1aca0$@indexcom.com> That's it. If you don't mind the expense and unreliability of high bit-rate streams. "knock yourselves out!" /g. -----Original Message----- From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Jack Elliott Sent: Tuesday, 16 May, 2017 17:33 To: Ross Levis; 'Icecast streaming server user discussions' Subject: Re: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? Encoding not being part of Icecast, I reckon this is indeed off-topic; but to close the thread, it does seem to be the case that mp3 encoding is now license free. "MP3 is supported by everything, everywhere, and is now patent-free. There has never been another audio format as widely supported as MP3, it's good enough for almost anything, and now, over twenty years since it took the world by storm, it's finally free." https://tech.slashdot.org/story/17/05/16/1314221/mp3-is-not-dead-its-finally-free -- That Jack Elliott (541) 848 7021 KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point Host, The Sunday Classics On 5/15/2017 9:26 PM, Ross Levis wrote: > Rather off topic, but I wonder if this means MP3 encoding is now licence free and encoders can be included in commercial software with no licence. > > -----Original Message----- > From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Jack > Elliott > Sent: Tuesday, 16 May 2017 9:46 a.m. > To: Icecast streaming server user discussions > Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? > > Fraunhofer Institute for Integrated Circuits has stopped providing licenses for MP3 technology, "[...] noting that more superior audio formats have rendered the MP3 obsolete. Speaking to National Public Radio (USA), the Fraunhofer Institute said AAC has since become the 'de facto standard for music download and videos on mobile phones.' " > > http://www.networkworld.com/article/3196788/consumer-electronics/mp3-p > layer-ipod-licensing-dead.html > > This raises a point I wanted to ask about. Icecast supports mp3 (it's the current lowest-common denominator for media players, yes?) and ogg. > I'd like to send a higher-fidelity stream from our music festival remotes, but ogg isn't an option because the station's media player, iTunes (running on a Mac) doesn't support ogg. > > Is there any work being done to support AAC in Icecast? Oh, wait. Use of AAC in an encoder requires paying a licensing fee. Drat. > > So we have mp3 (free, sounds crummy, everything plays it) and ogg > (free, sounds better, but does anyone know of any programs for Macs > that can play an ogg stream?) > > -- > That Jack Elliott > (541) 848 7021 > KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point > Host, The Sunday Classics > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > _______________________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast From epirat07 at gmail.com Wed May 17 06:05:05 2017 From: epirat07 at gmail.com (Marvin Scholz) Date: Wed, 17 May 2017 08:05:05 +0200 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: <27a801d2cea1$ce60e9c0$6b22bd40$@indexcom.com> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> <0075B862-70A7-41A0-9AFC-F6DF1C2B8190@gmail.com> <31504d55-051b-2103-0457-18c3d42ab214@gmail.com> <27a801d2cea1$ce60e9c0$6b22bd40$@indexcom.com> Message-ID: <3DE534A2-16B5-43E1-9C88-475F670AB949@gmail.com> I am not a lawyer, information in this email is no legal advice! On 17 May 2017, at 2:09, Greg Ogonowski wrote: > It's really pretty simple. > You can download the code and build it all you want... ...for > yourself. > It cannot be distributed, sold, or used commercially in any way. > That's all. > /g. That only applies to the source code. You still need to license the encoder afaik, as it is not licensed. In theory you would buy a software encoder from someone who has already licensed it and everything would be fine. But all (?) open source decoders of course can't do that. So the burden to take care of licensing is on you, just how it was with mp3 and the LAME encoder. > > > -----Original Message----- > From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Robert > Jeffares > Sent: Tuesday, 16 May, 2017 17:03 > To: icecast at xiph.org > Subject: Re: [Icecast] Frauenhofer signing off on mp3, ogg stream > player for Macs? > > I must say this is a very confusing issue. > > I generate AAC+ on an open source system which downloaded some code > during installation from the 3GPP source. > > It appears the encoding software is being freely distributed, and > hardware which decodes the stream pays a licence fee at point of > manufacture. > > We have such hardware. In a number of locations. One brand has AAC+ > only, not AAC. > > I note VLC also plays the encoded stream. > > Encoding and decoding uses sound cards, which have hard coded > processors on board, whose manufacturers presumably have paid various > patent holders for the appropriate rights. > > I am reasonably confident the patent holders would not have allowed me > to download the code without fee if they haven't already taken care of > their right to reward. > > Key point for me is that we are not making products for sale, we are > employing the technology to provide a stream for licenced products to > receive. > > ------------------------ > > From http://www.via-corp.com/us/en/licensing/aac/faq.html > > Are there use fees for AAC? > > No. License fees are due on the sale of encoders and/or decoders only. > There are no patent license fees due on the distribution of bit-stream > encoded in AAC, whether such bit-streams are broadcast, streamed over > a network, or provided on physical media. > > --------------------- > > "In House" use appears not to be of interest to the patent holders. > They, correctly, want to collect from products manufactured and sold > at a profit. It is in their interest for there to be source material. > > This is my opinion, based on my reading of the published information > from the patent holders. > > > Now answering the original question: Icecast2 will carry a number of > streams both audio and video which are not all documented. > Icecast>Icecast links over less then optimal WAN are generally robust, > provided you keep within the limits of the connecting platform. The > software is essentially a delivery system. Setting the buffer to allow > for network delays gets over a fair percentage of the problems. Yes > you > may have quite some delay. Usually it does not matter. In one case I > found a faulty server in the path between our originating site and > transmission site was causing transmission delays we could not buffer. > [Emailing everyone on the whois information produced a result!] I > have > trialled a number of audio formats in various bitrates. MP3 turned out > to be most reliable and we deliver mp3 to various distribution > services. > I set up an AAC+ system because it could give me a low profile > backhaul > off air monitor over a limited capacity ADSL circuit. It worked so > well > I have slowly incorporated AAC+ feeds into other places with good > results. AAC+ out performs mp3. I prefer Darkice as an encoder, others > use liquidsoap. I also use glasscoder which works well. > > AAC+ contains it's own header information so you don't have to use a > suffix like .mp4 It seems to work in various smartphones, which I > assume have paid the royalty. > > > regards > > > Robert Jeffares > > > > On 16/05/17 20:51, Marvin Scholz wrote: >> First: I am not a lawyer, this is no legal advice! >> >> On 16 May 2017, at 0:25, Robert Jeffares wrote: >> >>> Jack, >>> >>> I am using AAC+ encoded by Darkice and distributed on Icecast2 on a >>> Ubuntu server. I had to install a number of open source libraries >>> and >>> compile darkice from source. No licence. >> >> This sounds like it would violate the license, given that the FAQ on >> http://www.via-corp.com/us/en/licensing/aac/faq.html states: >> >>> An AAC patent license is needed by manufacturers or developers of >>> end-user encoder and/or decoder products. >> >> Additionally on the authors website for libaacplus it clearly says: >> >>> These tarballs don't provide any 3GPP source code. It is downloaded >>> from 3GPP during compilation. To use package compiled by this code, >>> you may need a license from 3GPP. >>> >>> AAC+ codecs incorporate several patents, held by Philips, Dolby, >>> Ericsson and Nokia. Companies holding patents for HE AAC v1 (SBR) >>> have formed a patent pool under Via Licensing to provide a single >>> point of license for product makers. Patents owned by Dolby and >>> Philips covering the Parametric Stereo used in HE AAC v2 (SBR+PS) >>> are >>> not included in the Via Licensing pool and are licensed separately >>> by >>> Dolby. Depending on law in your country, manufacturers and >>> developers >>> may need to get a license. Because it is a shared library, you may >>> need special contract for each one application, which links against >>> this library, directly or indirectly. >>> >>> Please also note, that downloaded .doc file has a very restrictive >>> license: No part may be reproduced except as authorized by written >>> permission. The copyright and the foregoing restriction extend to >>> reproduction in all media. >> >> This is certainly not something I would like to see recommended to be >> used, on this mailing list. >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From greg at indexcom.com Wed May 17 07:01:12 2017 From: greg at indexcom.com (Greg Ogonowski) Date: Wed, 17 May 2017 00:01:12 -0700 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: <3DE534A2-16B5-43E1-9C88-475F670AB949@gmail.com> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> <0075B862-70A7-41A0-9AFC-F6DF1C2B8190@gmail.com> <31504d55-051b-2103-0457-18c3d42ab214@gmail.com> <27a801d2cea1$ce60e9c0$6b22bd40$@indexcom.com> <3DE534A2-16B5-43E1-9C88-475F670AB949@gmail.com> Message-ID: <003f01d2cedb$5e5f9dd0$1b1ed970$@indexcom.com> The comment here about the source code and encoder/decoder licensing is completely correct. /greg. StreamS HiFi Radio -----Original Message----- From: Marvin Scholz [mailto:epirat07 at gmail.com] Sent: Tuesday, 16 May, 2017 23:05 To: Greg Ogonowski; Icecast streaming server user discussions Subject: Re: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? I am not a lawyer, information in this email is no legal advice! On 17 May 2017, at 2:09, Greg Ogonowski wrote: > It's really pretty simple. > You can download the code and build it all you want... ...for > yourself. > It cannot be distributed, sold, or used commercially in any way. > That's all. > /g. That only applies to the source code. You still need to license the encoder afaik, as it is not licensed. In theory you would buy a software encoder from someone who has already licensed it and everything would be fine. But all (?) open source decoders of course can't do that. So the burden to take care of licensing is on you, just how it was with mp3 and the LAME encoder. > > > -----Original Message----- > From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Robert > Jeffares > Sent: Tuesday, 16 May, 2017 17:03 > To: icecast at xiph.org > Subject: Re: [Icecast] Frauenhofer signing off on mp3, ogg stream > player for Macs? > > I must say this is a very confusing issue. > > I generate AAC+ on an open source system which downloaded some code > during installation from the 3GPP source. > > It appears the encoding software is being freely distributed, and > hardware which decodes the stream pays a licence fee at point of > manufacture. > > We have such hardware. In a number of locations. One brand has AAC+ > only, not AAC. > > I note VLC also plays the encoded stream. > > Encoding and decoding uses sound cards, which have hard coded > processors on board, whose manufacturers presumably have paid various > patent holders for the appropriate rights. > > I am reasonably confident the patent holders would not have allowed me > to download the code without fee if they haven't already taken care of > their right to reward. > > Key point for me is that we are not making products for sale, we are > employing the technology to provide a stream for licenced products to > receive. > > ------------------------ > > From http://www.via-corp.com/us/en/licensing/aac/faq.html > > Are there use fees for AAC? > > No. License fees are due on the sale of encoders and/or decoders only. > There are no patent license fees due on the distribution of bit-stream > encoded in AAC, whether such bit-streams are broadcast, streamed over > a network, or provided on physical media. > > --------------------- > > "In House" use appears not to be of interest to the patent holders. > They, correctly, want to collect from products manufactured and sold > at a profit. It is in their interest for there to be source material. > > This is my opinion, based on my reading of the published information > from the patent holders. > > > Now answering the original question: Icecast2 will carry a number of > streams both audio and video which are not all documented. > Icecast>Icecast links over less then optimal WAN are generally robust, > provided you keep within the limits of the connecting platform. The > software is essentially a delivery system. Setting the buffer to allow > for network delays gets over a fair percentage of the problems. Yes > you may have quite some delay. Usually it does not matter. In one > case I found a faulty server in the path between our originating site > and transmission site was causing transmission delays we could not > buffer. > [Emailing everyone on the whois information produced a result!] I > have trialled a number of audio formats in various bitrates. MP3 > turned out to be most reliable and we deliver mp3 to various > distribution services. > I set up an AAC+ system because it could give me a low profile > backhaul off air monitor over a limited capacity ADSL circuit. It > worked so well I have slowly incorporated AAC+ feeds into other places > with good results. AAC+ out performs mp3. I prefer Darkice as an > encoder, others use liquidsoap. I also use glasscoder which works > well. > > AAC+ contains it's own header information so you don't have to use a > suffix like .mp4 It seems to work in various smartphones, which I > assume have paid the royalty. > > > regards > > > Robert Jeffares > > > > On 16/05/17 20:51, Marvin Scholz wrote: >> First: I am not a lawyer, this is no legal advice! >> >> On 16 May 2017, at 0:25, Robert Jeffares wrote: >> >>> Jack, >>> >>> I am using AAC+ encoded by Darkice and distributed on Icecast2 on a >>> Ubuntu server. I had to install a number of open source libraries >>> and compile darkice from source. No licence. >> >> This sounds like it would violate the license, given that the FAQ on >> http://www.via-corp.com/us/en/licensing/aac/faq.html states: >> >>> An AAC patent license is needed by manufacturers or developers of >>> end-user encoder and/or decoder products. >> >> Additionally on the authors website for libaacplus it clearly says: >> >>> These tarballs don't provide any 3GPP source code. It is downloaded >>> from 3GPP during compilation. To use package compiled by this code, >>> you may need a license from 3GPP. >>> >>> AAC+ codecs incorporate several patents, held by Philips, Dolby, >>> Ericsson and Nokia. Companies holding patents for HE AAC v1 (SBR) >>> have formed a patent pool under Via Licensing to provide a single >>> point of license for product makers. Patents owned by Dolby and >>> Philips covering the Parametric Stereo used in HE AAC v2 (SBR+PS) >>> are not included in the Via Licensing pool and are licensed >>> separately by Dolby. Depending on law in your country, manufacturers >>> and developers may need to get a license. Because it is a shared >>> library, you may need special contract for each one application, >>> which links against this library, directly or indirectly. >>> >>> Please also note, that downloaded .doc file has a very restrictive >>> license: No part may be reproduced except as authorized by written >>> permission. The copyright and the foregoing restriction extend to >>> reproduction in all media. >> >> This is certainly not something I would like to see recommended to be >> used, on this mailing list. >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From toots at rastageeks.org Wed May 17 08:36:57 2017 From: toots at rastageeks.org (Romain Beauxis) Date: Wed, 17 May 2017 10:36:57 +0200 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: <31504d55-051b-2103-0457-18c3d42ab214@gmail.com> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> <0075B862-70A7-41A0-9AFC-F6DF1C2B8190@gmail.com> <31504d55-051b-2103-0457-18c3d42ab214@gmail.com> Message-ID: 2017-05-17 2:03 GMT+02:00 Robert Jeffares : > I must say this is a very confusing issue. > > I generate AAC+ on an open source system which downloaded some code during > installation from the 3GPP source. > > It appears the encoding software is being freely distributed, and hardware > which decodes the stream pays a licence fee at point of manufacture. > > We have such hardware. In a number of locations. One brand has AAC+ only, > not AAC. > > I note VLC also plays the encoded stream. > > Encoding and decoding uses sound cards, which have hard coded processors on > board, whose manufacturers presumably have paid various patent holders for > the appropriate rights. > > I am reasonably confident the patent holders would not have allowed me to > download the code without fee if they haven't already taken care of their > right to reward. This is not the case. You should rather think of it as the drug dealer model. The more the codec is disseminated, the more licensing fees you can charge to big players in the field. This is also why most of the time, only encoding is required to have a proper license, not decoding. Besides, some of these patented/licensed codecs have become open source as a collateral of being integrated into Android which is itself open-source. Romain -------------- next part -------------- An HTML attachment was scrubbed... URL: From sm at noisynotes.com Wed May 17 14:29:32 2017 From: sm at noisynotes.com (Steve Matzura) Date: Wed, 17 May 2017 10:29:32 -0400 Subject: [Icecast] Frauenhofer signing off on mp3, ogg stream player for Macs? In-Reply-To: <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> Message-ID: Is there a way to run Darkice without an audio interface? On Tue, 16 May 2017 10:25:43 +1200, you wrote: >Jack, > >I am using AAC+ encoded by Darkice and distributed on Icecast2 on a >Ubuntu server. I had to install a number of open source libraries and >compile darkice from source. No licence. > >non-free means you build each one stand alone and can't re distribute. > >Quality is excellent, and it runs on most players. > >I kept some notes [see below] > >I am using AAC+ to feed a couple of LPFM sites with almost zero errors >over what had been troublesome paths for mp3 > >HE-AAC audio v2 (with SBR + PS) is the superb audio encoder used to >encode high quality audio at really low bitrates (32 kbit/s). Quote from >Wikipedia "Data from this testing also indicated that some individuals >confused 48 kbit/s encoded material with an uncompressed original." > >In order to quickly compile your ?libaacplus library, you can type the >following commands in your shell: > ># apt-get install libfftw3-dev pkg-config autoconf automake libtool unzip >$ wget >http://tipok.org.ua/downloads/media/aacplus/libaacplus/libaacplus-2.0.2.tar.gz >$ tar -xzf libaacplus-2.0.2.tar.gz >$ cd libaacplus-2.0.2 >$ ./autogen.sh --enable-shared --enable-static >$ make ># make install ># ldconfig > >P.S. If you are using Ubuntu, you'll most probably have to use sudo for >the last 2 commands, like: > >$ sudo make install >$ sudo ldconfig > >In case that website above (hosting libaacplus) goes offline, you can >download the copy of that tar.gz file from here: (MD5: >3fc15d5aa91d0e8b8f94acb6555103da) > >$ wget http://ffmpeg.gusari.org/uploads/libaacplus-2.0.2.tar.gz > >More info at: ?http://tipok.org.ua/node/17 > >NOTE: libaacplus is a non-free library, so you won't be able to build >GPL alike FFmpeg with this library, i.e. your FFmpeg will not be >redistributable. > > > >regards > > >Robert Jeffares > > >On 16/05/17 09:46, Jack Elliott wrote: >> Fraunhofer Institute for Integrated Circuits has stopped providing >> licenses for MP3 technology, "[...] noting that more superior audio >> formats have rendered the MP3 obsolete. Speaking to National Public >> Radio (USA), the Fraunhofer Institute said AAC has since become the >> 'de facto standard for music download and videos on mobile phones.' " >> >> http://www.networkworld.com/article/3196788/consumer-electronics/mp3-player-ipod-licensing-dead.html >> >> >> This raises a point I wanted to ask about. Icecast supports mp3 (it's >> the current lowest-common denominator for media players, yes?) and >> ogg. I'd like to send a higher-fidelity stream from our music festival >> remotes, but ogg isn't an option because the station's media player, >> iTunes (running on a Mac) doesn't support ogg. >> >> Is there any work being done to support AAC in Icecast? Oh, wait. Use >> of AAC in an encoder requires paying a licensing fee. Drat. >> >> So we have mp3 (free, sounds crummy, everything plays it) and ogg >> (free, sounds better, but does anyone know of any programs for Macs >> that can play an ogg stream?) >> > >_______________________________________________ >Icecast mailing list >Icecast at xiph.org >http://lists.xiph.org/mailman/listinfo/icecast From thatjackelliott at kpov.org Thu May 18 00:14:41 2017 From: thatjackelliott at kpov.org (Jack Elliott) Date: Wed, 17 May 2017 17:14:41 -0700 Subject: [Icecast] Is discussing of using Icecast for AAC on- or off-topic? Message-ID: <0b4a0370-1ef8-4a44-3654-1f6c7b8fd69c@kpov.org> I'm newer here than most of you, don't know the conventions. I've been tinkering with using Icecast2 as a transport and have run into some issues and have some observations. Would it be cool to do that here? -- That Jack Elliott (541) 848 7021 KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point Host, The Sunday Classics From jeffares.robert at gmail.com Wed May 24 06:28:54 2017 From: jeffares.robert at gmail.com (Robert Jeffares) Date: Wed, 24 May 2017 18:28:54 +1200 Subject: [Icecast] Fall back from 2 different sources. In-Reply-To: References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> Message-ID: <02261571-9cd6-bfc8-454d-21591f6c8c72@gmail.com> Hi all, we have an industrial strength server acting as a relay for several services using Icecast2. Some of the stations have installed two seperate broadband connections to guard against network outages, which do occur and can last several hours. Exploring the fallback option we find it is limited to different mounts on the same server. What we want to do is have two different Icecast2 servers, on two different IP addresses with the relay server picking which ever is 'up'. There is a chance someone has already figured this out. [hope hope] regards Robert Jeffares From epirat07 at gmail.com Wed May 24 06:56:47 2017 From: epirat07 at gmail.com (Marvin Scholz) Date: Wed, 24 May 2017 08:56:47 +0200 Subject: [Icecast] Fall back from 2 different sources. In-Reply-To: <02261571-9cd6-bfc8-454d-21591f6c8c72@gmail.com> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> <02261571-9cd6-bfc8-454d-21591f6c8c72@gmail.com> Message-ID: <49EE2394-6B97-4120-87CE-46F8B4C225DE@gmail.com> Please do not highjack another thread, this is a very annoying thing to do. You might have done it by accident, clicking reply on an email and manually changing the subject to a completely different one. Do not do that for mailing lists, your mail will still have a header saying it is a reply to the email you are replying to. What you do instead is create a new email and write it to the address of the list, not a reply. Thanks. No need to resend of course, but please remember it for future threads. > Am 24.05.2017 um 08:28 schrieb Robert Jeffares : > > Hi all, > we have an industrial strength server acting as a relay for several services using Icecast2. > > Some of the stations have installed two seperate broadband connections to guard against network outages, which do occur and can last several hours. > > Exploring the fallback option we find it is limited to different mounts on the same server. > > What we want to do is have two different Icecast2 servers, on two different IP addresses with the relay server picking which ever is 'up'. > > There is a chance someone has already figured this out. [hope hope] > > regards > Robert Jeffares > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From sm at noisynotes.com Wed May 24 13:25:06 2017 From: sm at noisynotes.com (Steve Matzura) Date: Wed, 24 May 2017 09:25:06 -0400 Subject: [Icecast] Question About Difference between SVRINFONAME and SRVINFODESCRIPTION Message-ID: <532bicdf8aiq1i3ienjd23srrv552qv7dg@4ax.com> SRVINFONAME shows up in the title bar of a media player but does not change automatically when it changes on the stream. If the stream is restarted on the media player, the contents of SVRINFONAME is refreshed. What about SRVINFODESCRIPTION? Where is it displayed in a media player screen, and when is it refreshed in a media player if it changes on the stream? I'm trying to solve a years-old problem on my Icecast (2.4.3) server where the show title is sent in SRVINFONAME. I'm wondering if I change that to SRVINFODESCRIPTION might things get better? From epirat07 at gmail.com Wed May 24 13:44:09 2017 From: epirat07 at gmail.com (Marvin Scholz) Date: Wed, 24 May 2017 15:44:09 +0200 Subject: [Icecast] Question About Difference between SVRINFONAME and SRVINFODESCRIPTION In-Reply-To: <532bicdf8aiq1i3ienjd23srrv552qv7dg@4ax.com> References: <532bicdf8aiq1i3ienjd23srrv552qv7dg@4ax.com> Message-ID: <935BAD6E-1191-4660-933B-3C001807EC38@gmail.com> If you are referring to the stream title and description, changes to them will usually not be picked up by media players as these values are sent as HTTP headers, which can't be resent. On 24 May 2017, at 15:25, Steve Matzura wrote: > SRVINFONAME shows up in the title bar of a media player but does not > change automatically when it changes on the stream. If the stream is > restarted on the media player, the contents of SVRINFONAME is > refreshed. What about SRVINFODESCRIPTION? Where is it displayed in a > media player screen, and when is it refreshed in a media player if it > changes on the stream? I'm trying to solve a years-old problem on my > Icecast (2.4.3) server where the show title is sent in SRVINFONAME. > I'm wondering if I change that to SRVINFODESCRIPTION might things get > better? > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From sm at noisynotes.com Wed May 24 15:25:39 2017 From: sm at noisynotes.com (Steve Matzura) Date: Wed, 24 May 2017 11:25:39 -0400 Subject: [Icecast] Question About Difference between SVRINFONAME and SRVINFODESCRIPTION In-Reply-To: <935BAD6E-1191-4660-933B-3C001807EC38@gmail.com> References: <532bicdf8aiq1i3ienjd23srrv552qv7dg@4ax.com> <935BAD6E-1191-4660-933B-3C001807EC38@gmail.com> Message-ID: <1d9bicdhd55go5c5hjtvplgtjljcgr4hml@4ax.com> Don't know why I didn't think of that myself. I *KNEW* they were http headers, but you know the old saying about not seeing the forest for the trees. :-) On Wed, 24 May 2017 15:44:09 +0200, you wrote: >If you are referring to the stream title and description, changes to them >will usually not be picked up by media players as these values are sent as >HTTP headers, which can't be resent. > >On 24 May 2017, at 15:25, Steve Matzura wrote: > >> SRVINFONAME shows up in the title bar of a media player but does not >> change automatically when it changes on the stream. If the stream is >> restarted on the media player, the contents of SVRINFONAME is >> refreshed. What about SRVINFODESCRIPTION? Where is it displayed in a >> media player screen, and when is it refreshed in a media player if it >> changes on the stream? I'm trying to solve a years-old problem on my >> Icecast (2.4.3) server where the show title is sent in SRVINFONAME. >> I'm wondering if I change that to SRVINFODESCRIPTION might things get >> better? >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >_______________________________________________ >Icecast mailing list >Icecast at xiph.org >http://lists.xiph.org/mailman/listinfo/icecast From jake at jakebriggs.com Wed May 24 19:01:50 2017 From: jake at jakebriggs.com (Jake) Date: Thu, 25 May 2017 07:01:50 +1200 Subject: [Icecast] Fall back from 2 different sources. In-Reply-To: <02261571-9cd6-bfc8-454d-21591f6c8c72@gmail.com> References: <63248264-a0f3-cce1-d7bf-4c2b1f9c3a46@kpov.org> <3a3995ac-b502-3e12-47d7-5ee1d5900410@gmail.com> <02261571-9cd6-bfc8-454d-21591f6c8c72@gmail.com> Message-ID: This sounds like you need load balancing in front of your icecast servers, mod_proxy_balancer and mod_proxy_http modules if you use Apache. Unfortunately, I've never done this personally :P On 24 May 2017 6:28:54 PM NZST, Robert Jeffares wrote: >Hi all, >we have an industrial strength server acting as a relay for several >services using Icecast2. > >Some of the stations have installed two seperate broadband connections >to guard against network outages, which do occur and can last several >hours. > >Exploring the fallback option we find it is limited to different mounts > >on the same server. > >What we want to do is have two different Icecast2 servers, on two >different IP addresses with the relay server picking which ever is >'up'. > >There is a chance someone has already figured this out. [hope hope] > >regards >Robert Jeffares >_______________________________________________ >Icecast mailing list >Icecast at xiph.org >http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From theelder.ksof at gmail.com Mon May 29 03:09:56 2017 From: theelder.ksof at gmail.com (BRIAN NICHOLS) Date: Sun, 28 May 2017 22:09:56 -0500 Subject: [Icecast] =?utf-8?q?=28no_subject=29?= Message-ID: What is a *Icecast v2 compatible encoding device*? *Blessings? to you?,* *?"?The Elder?"?* *Brian L. Nichols* *[901] 591-0208* -------------- next part -------------- An HTML attachment was scrubbed... URL: From walteryork at hotmail.com Mon May 29 14:21:39 2017 From: walteryork at hotmail.com (Walter York) Date: Mon, 29 May 2017 14:21:39 +0000 Subject: [Icecast] Proper way to start multiple icecast services through bash script? Message-ID: I have 4 instances of icecast running on my server. #Command to start icecast /usr/bin/icecast -c /etc/icecast.xml -b & /usr/bin/icecast -c /etc/icecast1.xml -b & /usr/bin/icecast -c /etc/icecast2.xml -b & /usr/bin/icecast -c /etc/icecast3.xml -b & I am trying to integrate an automated Let's Encrypt Certificate renewal. My testing found that I need to restart the icecast processes for the certificate to update. I created a bash script that would open the firewall port, renew the cert, combine the certificates, overwrite the old cert, close the firewall port, kill the icecast services and then start them. Everything works except for the restarting of the services. Killing them works fine but starting them hangs. Please help me create the steps to start the 4 icecast instances via bash. I have tried no & and && as well. Feeling really stupid right now. Thank you in advance for your time and please spell out the answer without assuming my knowledge or lacktherof! ? #Kill all processes with the name icecast ps -ef | grep icecast | grep -v grep | awk '{print $2}' | xargs -r kill -9 #Start my icecast instances /usr/bin/icecast -c /etc/icecast.xml -b & /usr/bin/icecast -c /etc/icecast1.xml -b & /usr/bin/icecast -c /etc/icecast2.xml -b & /usr/bin/icecast -c /etc/icecast3.xml -b & PS: If I can get this working I can post it to github for everyone who would like to secure their icecast traffic and renew it automatically. -------------- next part -------------- An HTML attachment was scrubbed... URL: From epirat07 at gmail.com Mon May 29 14:23:00 2017 From: epirat07 at gmail.com (Marvin Scholz) Date: Mon, 29 May 2017 16:23:00 +0200 Subject: [Icecast] Proper way to start multiple icecast services through bash script? In-Reply-To: References: Message-ID: Any specific reason to run 4 Icecasts? On 29 May 2017, at 16:21, Walter York wrote: > I have 4 instances of icecast running on my server. > > > #Command to start icecast > /usr/bin/icecast -c /etc/icecast.xml -b & > /usr/bin/icecast -c /etc/icecast1.xml -b & > /usr/bin/icecast -c /etc/icecast2.xml -b & > /usr/bin/icecast -c /etc/icecast3.xml -b & > > > I am trying to integrate an automated Let's Encrypt Certificate > renewal. My testing found that I need to restart the icecast > processes for the certificate to update. I created a bash script that > would open the firewall port, renew the cert, combine the > certificates, overwrite the old cert, close the firewall port, kill > the icecast services and then start them. > > > Everything works except for the restarting of the services. Killing > them works fine but starting them hangs. Please help me create the > steps to start the 4 icecast instances via bash. I have tried no & > and && as well. Feeling really stupid right now. Thank you in > advance for your time and please spell out the answer without assuming > my knowledge or lacktherof! ? > > > #Kill all processes with the name icecast > ps -ef | grep icecast | grep -v grep | awk '{print $2}' | xargs -r > kill -9 > #Start my icecast instances > > /usr/bin/icecast -c /etc/icecast.xml -b & > /usr/bin/icecast -c /etc/icecast1.xml -b & > /usr/bin/icecast -c /etc/icecast2.xml -b & > /usr/bin/icecast -c /etc/icecast3.xml -b & > > > PS: If I can get this working I can post it to github for everyone who > would like to secure their icecast traffic and renew it automatically. > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From walteryork at hotmail.com Mon May 29 14:27:45 2017 From: walteryork at hotmail.com (Walter York) Date: Mon, 29 May 2017 14:27:45 +0000 Subject: [Icecast] Proper way to start multiple icecast services through bash script? In-Reply-To: References: Message-ID: Yes, the web players I've tested have a hard time parsing meta properly using only one instance with separate streams. Tested at least 6 of them looking for reliable meta and cross browser/OS compatibility. On May 29, 2017, at 10:23 AM, Marvin Scholz > wrote: Any specific reason to run 4 Icecasts? On 29 May 2017, at 16:21, Walter York wrote: I have 4 instances of icecast running on my server. #Command to start icecast /usr/bin/icecast -c /etc/icecast.xml -b & /usr/bin/icecast -c /etc/icecast1.xml -b & /usr/bin/icecast -c /etc/icecast2.xml -b & /usr/bin/icecast -c /etc/icecast3.xml -b & I am trying to integrate an automated Let's Encrypt Certificate renewal. My testing found that I need to restart the icecast processes for the certificate to update. I created a bash script that would open the firewall port, renew the cert, combine the certificates, overwrite the old cert, close the firewall port, kill the icecast services and then start them. Everything works except for the restarting of the services. Killing them works fine but starting them hangs. Please help me create the steps to start the 4 icecast instances via bash. I have tried no & and && as well. Feeling really stupid right now. Thank you in advance for your time and please spell out the answer without assuming my knowledge or lacktherof! ? #Kill all processes with the name icecast ps -ef | grep icecast | grep -v grep | awk '{print $2}' | xargs -r kill -9 #Start my icecast instances /usr/bin/icecast -c /etc/icecast.xml -b & /usr/bin/icecast -c /etc/icecast1.xml -b & /usr/bin/icecast -c /etc/icecast2.xml -b & /usr/bin/icecast -c /etc/icecast3.xml -b & PS: If I can get this working I can post it to github for everyone who would like to secure their icecast traffic and renew it automatically. ________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast ________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From epirat07 at gmail.com Mon May 29 14:34:08 2017 From: epirat07 at gmail.com (Marvin Scholz) Date: Mon, 29 May 2017 16:34:08 +0200 Subject: [Icecast] Proper way to start multiple icecast services through bash script? In-Reply-To: References: Message-ID: <32EE7196-EFC4-4405-AA67-B68C453B3E52@gmail.com> On 29 May 2017, at 16:27, Walter York wrote: > Yes, the web players I've tested have a hard time parsing meta > properly using only one instance with separate streams. Tested at > least 6 of them looking for reliable meta and cross browser/OS > compatibility. There is no difference using one or multiple separate instances that I am aware of. Thats really weird. > On May 29, 2017, at 10:23 AM, Marvin Scholz > > wrote: > > Any specific reason to run 4 Icecasts? > > On 29 May 2017, at 16:21, Walter York wrote: > > I have 4 instances of icecast running on my server. > > > #Command to start icecast > /usr/bin/icecast -c /etc/icecast.xml -b & > /usr/bin/icecast -c /etc/icecast1.xml -b & > /usr/bin/icecast -c /etc/icecast2.xml -b & > /usr/bin/icecast -c /etc/icecast3.xml -b & > > > I am trying to integrate an automated Let's Encrypt Certificate > renewal. My testing found that I need to restart the icecast > processes for the certificate to update. I created a bash script > that > would open the firewall port, renew the cert, combine the > certificates, overwrite the old cert, close the firewall port, kill > the icecast services and then start them. > > > Everything works except for the restarting of the services. Killing > them works fine but starting them hangs. Please help me create the > steps to start the 4 icecast instances via bash. I have tried no & > and && as well. Feeling really stupid right now. Thank you in > advance for your time and please spell out the answer without > assuming > my knowledge or lacktherof! ? > > > #Kill all processes with the name icecast > ps -ef | grep icecast | grep -v grep | awk '{print $2}' | xargs -r > kill -9 > #Start my icecast instances > > /usr/bin/icecast -c /etc/icecast.xml -b & > /usr/bin/icecast -c /etc/icecast1.xml -b & > /usr/bin/icecast -c /etc/icecast2.xml -b & > /usr/bin/icecast -c /etc/icecast3.xml -b & > > > PS: If I can get this working I can post it to github for everyone > who > would like to secure their icecast traffic and renew it > automatically. > > ________________________________ > > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > ________________________________ > > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From yahav.shasha at gmail.com Mon May 29 14:35:13 2017 From: yahav.shasha at gmail.com (Yahav Shasha) Date: Mon, 29 May 2017 17:35:13 +0300 Subject: [Icecast] Proper way to start multiple icecast services through bash script? In-Reply-To: References: Message-ID: try this: /usr/bin/icecast -c /etc/icecast.xml -b > /dev/null 2>&1 & as for killing them, don't overcomplicate things, killall icecast -KILL also, perhaps you don't even need to kill and start them again, try to HUP them and see if the certificate updates. On Mon, May 29, 2017 at 5:27 PM, Walter York wrote: > Yes, the web players I've tested have a hard time parsing meta properly > using only one instance with separate streams. Tested at least 6 of them > looking for reliable meta and cross browser/OS compatibility. > On May 29, 2017, at 10:23 AM, Marvin Scholz wrote: > >> Any specific reason to run 4 Icecasts? >> >> On 29 May 2017, at 16:21, Walter York wrote: >> >> I have 4 instances of icecast running on my server. >>> >>> >>> #Command to start icecast >>> /usr/bin/icecast -c /etc/icecast.xml -b & >>> /usr/bin/icecast -c /etc/icecast1.xml -b & >>> /usr/bin/icecast -c /etc/icecast2.xml -b & >>> /usr/bin/icecast -c /etc/icecast3.xml -b & >>> >>> >>> I am trying to integrate an automated Let's Encrypt Certificate >>> renewal. My testing found that I need to restart the icecast >>> processes for the certificate to update. I created a bash script that >>> would open the firewall port, renew the cert, combine the >>> certificates, overwrite the old cert, close the firewall port, kill >>> the icecast services and then start them. >>> >>> >>> Everything works except for the restarting of the services. Killing >>> them works fine but starting them hangs. Please help me create the >>> steps to start the 4 icecast instances via bash. I have tried no & >>> and && as well. Feeling really stupid right now. Thank you in >>> advance for your time and please spell out the answer without assuming >>> my knowledge or lacktherof! ? >>> >>> >>> #Kill all processes with the name icecast >>> ps -ef | grep icecast | grep -v grep | awk '{print $2}' | xargs -r >>> kill -9 >>> #Start my icecast instances >>> >>> /usr/bin/icecast -c /etc/icecast.xml -b & >>> /usr/bin/icecast -c /etc/icecast1.xml -b & >>> /usr/bin/icecast -c /etc/icecast2.xml -b & >>> /usr/bin/icecast -c /etc/icecast3.xml -b & >>> >>> >>> PS: If I can get this working I can post it to github for everyone who >>> would like to secure their icecast traffic and renew it automatically. >>> >>> ------------------------------ >>> >>> Icecast mailing list >>> Icecast at xiph.org >>> http://lists.xiph.org/mailman/listinfo/icecast >>> >> ------------------------------ >> >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> >> > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > -- Yahav Shasha, Web Developer +972-(0)549214421 http://www.linkedin.com/in/yahavs -------------- next part -------------- An HTML attachment was scrubbed... URL: From yahav.shasha at gmail.com Mon May 29 14:36:56 2017 From: yahav.shasha at gmail.com (Yahav Shasha) Date: Mon, 29 May 2017 17:36:56 +0300 Subject: [Icecast] Proper way to start multiple icecast services through bash script? In-Reply-To: <32EE7196-EFC4-4405-AA67-B68C453B3E52@gmail.com> References: <32EE7196-EFC4-4405-AA67-B68C453B3E52@gmail.com> Message-ID: also, this isn't a good enough reason to run 4 separate instances, would suggest writing a parsing script that does work with your setup, or even writing your own xslt file. On Mon, May 29, 2017 at 5:34 PM, Marvin Scholz wrote: > > > On 29 May 2017, at 16:27, Walter York wrote: > > Yes, the web players I've tested have a hard time parsing meta properly >> using only one instance with separate streams. Tested at least 6 of them >> looking for reliable meta and cross browser/OS compatibility. >> > > There is no difference using one or multiple separate instances that I am > aware of. Thats really weird. > > On May 29, 2017, at 10:23 AM, Marvin Scholz > rat07 at gmail.com>> wrote: >> >> Any specific reason to run 4 Icecasts? >> >> On 29 May 2017, at 16:21, Walter York wrote: >> >> I have 4 instances of icecast running on my server. >> >> >> #Command to start icecast >> /usr/bin/icecast -c /etc/icecast.xml -b & >> /usr/bin/icecast -c /etc/icecast1.xml -b & >> /usr/bin/icecast -c /etc/icecast2.xml -b & >> /usr/bin/icecast -c /etc/icecast3.xml -b & >> >> >> I am trying to integrate an automated Let's Encrypt Certificate >> renewal. My testing found that I need to restart the icecast >> processes for the certificate to update. I created a bash script that >> would open the firewall port, renew the cert, combine the >> certificates, overwrite the old cert, close the firewall port, kill >> the icecast services and then start them. >> >> >> Everything works except for the restarting of the services. Killing >> them works fine but starting them hangs. Please help me create the >> steps to start the 4 icecast instances via bash. I have tried no & >> and && as well. Feeling really stupid right now. Thank you in >> advance for your time and please spell out the answer without assuming >> my knowledge or lacktherof! ? >> >> >> #Kill all processes with the name icecast >> ps -ef | grep icecast | grep -v grep | awk '{print $2}' | xargs -r >> kill -9 >> #Start my icecast instances >> >> /usr/bin/icecast -c /etc/icecast.xml -b & >> /usr/bin/icecast -c /etc/icecast1.xml -b & >> /usr/bin/icecast -c /etc/icecast2.xml -b & >> /usr/bin/icecast -c /etc/icecast3.xml -b & >> >> >> PS: If I can get this working I can post it to github for everyone who >> would like to secure their icecast traffic and renew it automatically. >> >> ________________________________ >> >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> ________________________________ >> >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> > _______________________________________________ > > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -- Yahav Shasha, Web Developer +972-(0)549214421 http://www.linkedin.com/in/yahavs -------------- next part -------------- An HTML attachment was scrubbed... URL: From lion at lion.leolix.org Mon May 29 15:27:22 2017 From: lion at lion.leolix.org (Philipp Schafft) Date: Mon, 29 May 2017 15:27:22 +0000 Subject: [Icecast] Proper way to start multiple icecast services through bash script? In-Reply-To: References: Message-ID: <1496071642.1823.72.camel@lion.leolix.org> Good afternoon, On Mon, 2017-05-29 at 17:35 +0300, Yahav Shasha wrote: > try this: > /usr/bin/icecast -c /etc/icecast.xml -b > /dev/null 2>&1 & > as for killing them, don't overcomplicate things, killall icecast -KILL You should never kill process with SIGKILL if not really, really needed. Using SIGKILL will not give them a chance to clean up. E.g. no flushing of logs, no telling clients (just connection resets), no cleanup of open sockets (may result in stalled connections), no closing of databases (for applications that use databases) or other backend services and child processes. Icecast2 perfectly handles SIGTERM. > On Mon, May 29, 2017 at 5:27 PM, Walter York wrote: > >>> #Kill all processes with the name icecast > >>> ps -ef | grep icecast | grep -v grep | awk '{print $2}' | xargs -r > >>> kill -9 use pkill here. That is portable. It has a lot options to select the correct process. Also avoid using signal numbers. they're not portable and bad style. SIGTERM is the default for pkill. with best regards, -- Philipp. (Rah of PH2) From walteryork at hotmail.com Mon May 29 15:44:06 2017 From: walteryork at hotmail.com (Walter York) Date: Mon, 29 May 2017 15:44:06 +0000 Subject: [Icecast] Proper way to start multiple icecast services through bash script? In-Reply-To: References: , Message-ID: Shasha, Thank you! Tested and it worked!!! Here is my code should anyone desire... It is in three parts. Could have parameterized the code... find yourdomain.tld and replace with your domain.tld. Be aware of any line that has yourdomain.tld to replace what matches for your needs. #Copy and paste or run manually outside of script ############## Begin Initial Certbot Install #################### #Install certbot, epel must be installed yum install certbot #Enable port 443 in Firewall for Certbot #firewall-cmd --list-all firewall-cmd --permanent --add-port=443/tcp firewall-cmd --reload #Run Command for Certbot to create certificate certbot certonly \ --standalone \ --agree-tos \ --non-interactive \ --text \ --rsa-key-size 4096 \ --email admin at yourdomain.tld \ --domains "stream.yourdomain.tld" #Disable port 443 in Firewall for Certbot firewall-cmd --permanent --remove-port=443/tcp firewall-cmd --reload #Letsencrypt certificates will now be located in /etc/letsencrypt/live/yourdomain.tld/ ############## End Initial Certbot Install #################### #!/bin/bash ############## Begin Certbot Renewal #################### #Enable port 443 in Firewall for Certbot firewall-cmd --permanent --add-port=443/tcp firewall-cmd --reload #Run Certbot Renew all certs certbot renew --force-renewal #Disable port 443 in Firewall for Certbot firewall-cmd --permanent --remove-port=443/tcp firewall-cmd --reload #Backup expiring Icecast certificate mv -f /usr/share/icecast/ssl/stream_yourdomain.tld_combined.pem /usr/share/icecast/ssl/stream_yourdomain.tld_combined_$(date +%Y%m%d_%T).bak && touch /usr/share/icecast/ssl/stream_yourdomain.tld_combined.pem #Append FullChain to icecast certificate cat /etc/letsencrypt/live/stream.yourdomain.tld/fullchain.pem > /usr/share/icecast/ssl/stream_yourdomain.tld_combined.pem #Append privkey to icecast certificate cat /etc/letsencrypt/live/stream.yourdomain.tld/privkey.pem >> /usr/share/icecast/ssl/stream_yourdomain.tld_combined.pem #The following is for my implementation. If you have a single service consider removing the following to just service icecast restart #Kill all processes with the name icecast ps -ef | grep icecast | grep -v grep | awk '{print $2}' | xargs -r kill -9 #Start my icecast instances /usr/bin/icecast -c /etc/icecast.xml -b > /dev/null 2>&1 & /usr/bin/icecast -c /etc/icecast1.xml -b > /dev/null 2>&1 & /usr/bin/icecast -c /etc/icecast2.xml -b > /dev/null 2>&1 & /usr/bin/icecast -c /etc/icecast3.xml -b > /dev/null 2>&1 & ############## End Certbot Renewal #################### #Run at command line # Command to create CRON job to run once a week on Sunday at midnight crontab -e #Insert the following line 0 0 * * 0 /usr/share/icecast/ssl/certrenew.sh #Check that CRON job was added crontab -l ________________________________ From: Icecast on behalf of Yahav Shasha Sent: Monday, May 29, 2017 10:35 AM To: Icecast streaming server user discussions Subject: Re: [Icecast] Proper way to start multiple icecast services through bash script? try this: /usr/bin/icecast -c /etc/icecast.xml -b > /dev/null 2>&1 & as for killing them, don't overcomplicate things, killall icecast -KILL also, perhaps you don't even need to kill and start them again, try to HUP them and see if the certificate updates. On Mon, May 29, 2017 at 5:27 PM, Walter York > wrote: Yes, the web players I've tested have a hard time parsing meta properly using only one instance with separate streams. Tested at least 6 of them looking for reliable meta and cross browser/OS compatibility. On May 29, 2017, at 10:23 AM, Marvin Scholz > wrote: Any specific reason to run 4 Icecasts? On 29 May 2017, at 16:21, Walter York wrote: I have 4 instances of icecast running on my server. #Command to start icecast /usr/bin/icecast -c /etc/icecast.xml -b & /usr/bin/icecast -c /etc/icecast1.xml -b & /usr/bin/icecast -c /etc/icecast2.xml -b & /usr/bin/icecast -c /etc/icecast3.xml -b & I am trying to integrate an automated Let's Encrypt Certificate renewal. My testing found that I need to restart the icecast processes for the certificate to update. I created a bash script that would open the firewall port, renew the cert, combine the certificates, overwrite the old cert, close the firewall port, kill the icecast services and then start them. Everything works except for the restarting of the services. Killing them works fine but starting them hangs. Please help me create the steps to start the 4 icecast instances via bash. I have tried no & and && as well. Feeling really stupid right now. Thank you in advance for your time and please spell out the answer without assuming my knowledge or lacktherof! ? #Kill all processes with the name icecast ps -ef | grep icecast | grep -v grep | awk '{print $2}' | xargs -r kill -9 #Start my icecast instances /usr/bin/icecast -c /etc/icecast.xml -b & /usr/bin/icecast -c /etc/icecast1.xml -b & /usr/bin/icecast -c /etc/icecast2.xml -b & /usr/bin/icecast -c /etc/icecast3.xml -b & PS: If I can get this working I can post it to github for everyone who would like to secure their icecast traffic and renew it automatically. ________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast ________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast _______________________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast -- Yahav Shasha, Web Developer +972-(0)549214421 http://www.linkedin.com/in/yahavs -------------- next part -------------- An HTML attachment was scrubbed... URL: From walteryork at hotmail.com Mon May 29 16:09:01 2017 From: walteryork at hotmail.com (Walter York) Date: Mon, 29 May 2017 16:09:01 +0000 Subject: [Icecast] Proper way to start multiple icecast services through bash script? In-Reply-To: <1496071642.1823.72.camel@lion.leolix.org> References: , <1496071642.1823.72.camel@lion.leolix.org> Message-ID: Philipp, I replaced: ps -ef | grep icecast | grep -v grep | awk '{print $2}' | xargs -r kill -9 with: pkill icecast This works. I did try "pkill -HUP icecast" but it didn't seem to have intended effect of refreshing certificate. ________________________________ From: Icecast on behalf of Philipp Schafft Sent: Monday, May 29, 2017 11:27 AM To: Icecast streaming server user discussions Subject: Re: [Icecast] Proper way to start multiple icecast services through bash script? Good afternoon, On Mon, 2017-05-29 at 17:35 +0300, Yahav Shasha wrote: > try this: > /usr/bin/icecast -c /etc/icecast.xml -b > /dev/null 2>&1 & > as for killing them, don't overcomplicate things, killall icecast -KILL You should never kill process with SIGKILL if not really, really needed. Using SIGKILL will not give them a chance to clean up. E.g. no flushing of logs, no telling clients (just connection resets), no cleanup of open sockets (may result in stalled connections), no closing of databases (for applications that use databases) or other backend services and child processes. Icecast2 perfectly handles SIGTERM. > On Mon, May 29, 2017 at 5:27 PM, Walter York wrote: > >>> #Kill all processes with the name icecast > >>> ps -ef | grep icecast | grep -v grep | awk '{print $2}' | xargs -r > >>> kill -9 use pkill here. That is portable. It has a lot options to select the correct process. Also avoid using signal numbers. they're not portable and bad style. SIGTERM is the default for pkill. with best regards, -- Philipp. (Rah of PH2) _______________________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast Icecast Info Page - Xiph.Org Foundation lists.xiph.org While this list and IRC are preferred for user support. There is also a web forum for user support. See icecast.org for links. To see the collection of prior postings ... -------------- next part -------------- An HTML attachment was scrubbed... URL: From lion at lion.leolix.org Mon May 29 21:20:49 2017 From: lion at lion.leolix.org (Philipp Schafft) Date: Mon, 29 May 2017 21:20:49 +0000 Subject: [Icecast] Proper way to start multiple icecast services through bash script? In-Reply-To: References: , <1496071642.1823.72.camel@lion.leolix.org> Message-ID: <1496092849.1823.91.camel@lion.leolix.org> Good evening, On Mon, 2017-05-29 at 16:09 +0000, Walter York wrote: > Philipp, > > > I replaced: ps -ef | grep icecast | grep -v grep | awk '{print $2}' | xargs -r kill -9 > > with: pkill icecast > This works. :) > I did try "pkill -HUP icecast" but it didn't seem to have intended effect of refreshing certificate. This is not supported in Icecast2 2.4.x (stable). But there is a branch (ph3-update-TLS) for Icecast2 2.5.x that added support for that. We're currently in the process of merging it into 2.5.x (development). Have a nice evening, with best regards, -- Philipp. (Rah of PH2)