similar to: access.log via Icecast web server?

Good afternoon, I have two playlists going, on separate mount points, and they both exhibit this behavior. It appears that ices is shutting down when it reaches the end of the playlist. I'm getting these same four lines at the end of the logs of both playlists: [2019-12-08  00:00:53] INFO playlist-builtin/write_ogg_data module shutdown requested [2019-12-08  00:00:53] INFO input/input_loop

Good afternoon, On Thu, 2019-03-28 at 21:15 +0800, Prince Naryk wrote: > can u please check my config file and see if there is something wrong with > it, You define the same listen port 3 times. Also your hostname is not set to a hostname but an IP. You also set max clients to 5000. Which is fine for Icecast. However your OS may add additional restrictions. Why do you define a

I'm using the KH edition of Icecast 2.4.0 but it may also related to the standard release. I added the following to my config xml file but the file cannot be parsed is the error... <mount type="default"> <max-listener-duration>28800</max-listener-duration> </mount> Any ideas of the problem? Thanks. -------------- next part --------------

Hi guys, Can anyone share some (deep technical) light on how «Server Side Spot Replacement" on live radio streaming with Icecast can be done? Thanks, BR Rune -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast-dev/attachments/20170411/e322cb01/attachment.html>

Hi all, I have been struggling to setup icecast with ssl on port 443. I am running Debian Wheezy and installed icecast by downloading the source and compiling. This went all ok, including ssl support. When running ssl on a port >1024 and not chrooting ssl works fine, so the certificate is ok. But when enabling chroot everything works but ssl. Any ideas ? TIA! Paul This is (part of) my

Thank you, ogginfo returned: ----- Note: Stream 1 has serial number 0, which is legal but may cause problems with some tools. New logical stream (#1, serial: 00000000): type vorbis Vorbis headers parsed for stream 1, information follows... Version: 0 Vendor: ffmpeg Channels: 1 Rate: 22050 Nominal bitrate: 35.333000 kb/s Upper bitrate not set Lower bitrate not set Vorbis stream 1: Total data

Good morning, On Sun, 2020-10-11 at 10:24 +1000, Damian wrote: > Can I also ask, which is the recommended course of action? Sure, just keep in mind that we had weekend, so people were off. ;) > Should I rebuild icecast with OpenSSL or is there now a fixed version > via backports that I can use? Based on... On Sat, 2020-10-10 at 23:06 +1000, Damian wrote: > Edit (apologies for the

Couldn't you also just have a client stream locally from icecast that can do things on metadata change? I mean it's a bit icky but it'd work. ---- Philipp Schafft wrote ---- >Good morning, > >On Thu, 2018-11-08 at 12:45 -0500, Alex Hackney wrote: >> I actually got this to work this morning finally. The problem was on my >> auth server. > >Perfect. :) >

Anyone know any workarounds for OPUS/FLAC metadata on IceCast? I’ve monitored my inbound stream and this is working correctly (or at least the formatting and data for the OPUS stream is identical to the MP3/AAC+ streams). I see people with OPUS streams and metadata but they may not be using IceCast. Is it safe to assume we’ll see this in the next version? Rick

Hi I have a potential project for which my client requests that we load balance the streaming service. Of course, the Icecast server scales very well. - http://icecast.org/loadtest/ However, the client requests high-availability and, due to the scale of the potential project, we would like to load balance the service over two or more servers. I think the load balancing aspect is not my

I would like for icecase status json xls to be able to provide the currently song title playing encoded in utf8. I have a problem getting the song titles / artist names for greek or japanese characters. Check below status-json.xsl part, for an example :

Hi all: Recently Stream Licensing LLC has changed their requirements so that streaming internet stations in the US must title stream the album along with the song title and artist. I use ices for the backup automation when no live programming is taking place. Ices shows the song title and artist on the player with no problem. My question is how I configure ices to show the album as

Hello, I'd like to have my icecast client (libshout based) that would use the HTTP header: "Authorization: bearer <token>" as its authentication method. I didn't find documentation on how to do it, also couldn't find anything like that in libshout source code. Is this possible in the current code? Additionally, if not possible, is this feature something interesting

I have a problem with adding my icecast-stream till the YP-directory. I don't get any error messages regarding WHY my station isn't added to the YP either. Stream URL: bananradion.bananklubben.se:8086 Hostname: bananradion.bananklubben.se <listen-socket> <port>8086</port> <!-- <bind-address>127.0.0.1</bind-address> -->

Good day, no answers in Google about that. I asked https://stackoverflow.com/questions/53290693/how-to-alter-duration-of-ogg-with-js - in short I have Ogg Vorbis files on the client side (webapp) and I need to concatenate them in one file for downloading. I did concatenation with this line of code: const blob = new Blob(listOfChunksBlobs, {'type': 'audio/ogg'}); And I play the

I actually got this to work this morning finally. The problem was on my auth server. I see the source auth hook being sent a lot, is there anyway to get the current metadata in that hook? Ideally, every time the source is updated, I'd like to get a hook so I can track the songs that are being played. Alternatively, the only way I can see doing it, is to make a get request every X seconds

something im still confused, im sorry a newbie here :) what should be placed on my hostname ? bind address ? listen socket ? On Thu, Mar 28, 2019 at 10:46 PM Prince Naryk <princekyran.pabate at gmail.com> wrote: > I only have one listen port. So is that mean i'll be disabling the other > two? If So which should i disable? > > Also the "foo" header, is it ok to

Hi All, I'm facing a problem in icecast relay machines. I'm seeing frequently that some of the relay machines are crashing and generates core dump but the reason for the crash is not clear from the trace of the core. Here is how the gdb trace looks like: (gdb) bt #0 0xffffe435 in __kernel_vsyscall () #1 0xf742c607 in raise () from /lib/i386-linux-gnu/libc.so.6 #2 0xf742fa33 in

Hi All, I'm facing a problem in icecast relay machines. I'm seeing frequently that some of the relay machines are crashing and generates core dump but the reason for the crash is not clear from the trace of the core. Here is how the gdb trace looks like: (gdb) bt #0 0xffffe435 in __kernel_vsyscall () #1 0xf742c607 in raise () from /lib/i386-linux-gnu/libc.so.6 #2 0xf742fa33 in

It seems, that with FLAC and OPUS streams (not individual files) the song title (meta data) updates do not work. Also the ICEcast admin web interface isn’t working for FLAC and OPUS; while it is working for MP3, AAC as well as OGG streams. I.e. when sending a continuous FLAC or OPUS stream to an ICEcast server, it seems impossible to update the meta data mid-stream (like it works for MP3, AAC