From per.gunnarsson at yandex.com Wed Nov 6 19:47:53 2019 From: per.gunnarsson at yandex.com (Per Gunnarsson) Date: Wed, 6 Nov 2019 20:47:53 +0100 Subject: [Icecast] How to stream directly with curl to icecast mount point? Message-ID: <3ac18ce8-22e6-3149-e101-689dbe009db8@yandex.com> Hello! I have tried streaming with curl directly to an input.harbor on liquidsoap, and now I am curious if it's possible to stream to an icecast mountpoint in a similar way. If this is the case, which curl options should I use? Whe I stream to input.harbor, I do like this: parec --raw --rate=48000 --channels=1 | \ oggenc -Q -r -R 48000 -C 1 -q 10 --utf8 --title 'My apartment' --artist mustafejen? --genre 'curl test' - | \ curl -s -ssl --user source:james_bond -H "Content-Type: audio/ogg" -T - https://mustafejen.se:8000/tset.ogg Cheers, Per Gunnarsson From subscription at nextdial.com.br Thu Nov 7 21:00:59 2019 From: subscription at nextdial.com.br (subscription at nextdial.com.br) Date: Thu, 7 Nov 2019 18:00:59 -0300 Subject: [Icecast] Return ClientId in responses In-Reply-To: References: <2c0ed96b-caab-b671-2a1c-b1fc8b256258@brideswell.com> Message-ID: <714b0f00f3114e459ba907f03326e164@nextdial.com.br> Hello guys, Is possible to configure Icecast to return the ClientId in the response headers? Best, Thiago -------------- next part -------------- An HTML attachment was scrubbed... URL: From d at digitaldarragh.com Thu Nov 21 12:59:35 2019 From: d at digitaldarragh.com (=?iso-8859-1?Q?Darragh_=D3_H=E9iligh?=) Date: Thu, 21 Nov 2019 12:59:35 +0000 Subject: [Icecast] Making the playlist history publically accessible. Message-ID: I have written the playlist history to a file. It's a CSV file that I store within /var/log/icecast2/ But I've decided that I want to consume this file by an application on a different server. The different server is on the same network. I'm thinking. I could just add this text file into the Icecast2 web directory and get it via HTTP to use by the other application. But before I start working on this, are there any other methods any of you have used to provide the playlist history to the world? Thanks Darragh -------------- next part -------------- An HTML attachment was scrubbed... URL: From d at digitaldarragh.com Mon Nov 25 09:53:20 2019 From: d at digitaldarragh.com (=?iso-8859-1?Q?Darragh_=D3_H=E9iligh?=) Date: Mon, 25 Nov 2019 09:53:20 +0000 Subject: [Icecast] Making the playlist history publicly accessible. Message-ID: Good morning, Further to my request last week, I am providing an update as I have completed the implementation of this functionality. Steps: 1. Write a cut down file for each stream to the web directory in Icecast. 2. The file is not CSV. Each record is separated with a semi colon. This is because the track names can have commas. 3. I'm only saving the last 10 lines. 4. Using the system.web and system.net.io namespaces in .net core, I'm reading the CSV file over HTTPS. Icecast on this server is listening over HTTPS. It's a requirement as mixing HTTP with HTTPS isn't supported in my configuration. 5. I then separate out the path and the file name to give me the artist, album and track name. I pass this as a list from the controller using a strongly typed view. Thinking back, it probably would have been easier to do this with Javascript. But I am more comfortable with C# over Javascript. Some day, I should really document this solution. There are so many scripts handling the automation of this, if I ever tried to get someone else to maintain the streams, it would be hard for them to work out the various flows. An example is at www.ceol.fm/NowPlaying From: Icecast On Behalf Of Darragh ? H?iligh Sent: Thursday 21 November 2019 13:00 To: Icecast streaming server user discussions Subject: [Icecast] Making the playlist history publically accessible. I have written the playlist history to a file. It's a CSV file that I store within /var/log/icecast2/ But I've decided that I want to consume this file by an application on a different server. The different server is on the same network. I'm thinking. I could just add this text file into the Icecast2 web directory and get it via HTTP to use by the other application. But before I start working on this, are there any other methods any of you have used to provide the playlist history to the world? Thanks Darragh -------------- next part -------------- An HTML attachment was scrubbed... URL: From yerry at walla.co.il Mon Nov 25 13:07:53 2019 From: yerry at walla.co.il (=?UTF-8?B?15nXqNeZINeh15XXpNeo?=) Date: Mon, 25 Nov 2019 15:07:53 +0200 Subject: [Icecast] =?utf-8?q?Reducing_delay_time?= Message-ID: <^63B1D477626312E7EE84EB4941C2AF4B990BB1B0@walla.co.il> An HTML attachment was scrubbed... URL: From jordan at coolmic.net Mon Nov 25 16:39:25 2019 From: jordan at coolmic.net (Jordan Erickson) Date: Mon, 25 Nov 2019 08:39:25 -0800 Subject: [Icecast] Reducing delay time In-Reply-To: <^63B1D477626312E7EE84EB4941C2AF4B990BB1B0@walla.co.il> References: <^63B1D477626312E7EE84EB4941C2AF4B990BB1B0@walla.co.il> Message-ID: <16f13071-85f8-1c21-71a7-390c8d723518@coolmic.net> Hello, Here is a write-up on this subject that you will likely benefit from: http://lists.xiph.org/pipermail/icecast/2015-September/013488.html Cheers, Jordan Erickson On 11/25/19 5:07 AM, ??? ???? wrote: > Hi all, > I tried to install latest windows version of icecast on my laptop? > butt which is also installed on my laptop as online client (streaming > source) > When I tried to connect client listener? on local network I found out > that the delay is more? 10 secs? > ? > Is there a way to reduce delay by configuration (I tried to configure > buffering to 0 but it didn't help) > ? > Thanks in advance > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > From rondejavu at gmail.com Wed Nov 27 20:57:13 2019 From: rondejavu at gmail.com (Rondejavu) Date: Wed, 27 Nov 2019 15:57:13 -0500 Subject: [Icecast] IceCast and ICES Message-ID: <69B3A3FB-C6FF-452B-8AB3-10DB1C957F4F@gmail.com> I?ve successfully implemented IceCast on a Raspberry Pi and can access the stream ONLY if I use an ffmpeg statement to start the stream. Unfortunately, the stream is choppy and the sound quality is poor. I?ve tried using ICES, but I don?t get any sound. Terminal command that works: ffmpeg -ac 2 -f alsa -i hw:0,0 -acodec mp3 -ab 48k -ac 2 -content_type audio/mpeg -f mp3 icecast://source:password at ipaddress:port/stream ICES terminal command that doesn?t work: ices2 /home/pi/ices-2.0.2/conf/ices-alsa.xml What am I missing? Thanks for any help/suggestions. From artuch at speedy.com.ar Thu Nov 28 00:07:56 2019 From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch) Date: Wed, 27 Nov 2019 21:07:56 -0300 Subject: [Icecast] IceCast and ICES In-Reply-To: <69B3A3FB-C6FF-452B-8AB3-10DB1C957F4F@gmail.com> References: <69B3A3FB-C6FF-452B-8AB3-10DB1C957F4F@gmail.com> Message-ID: <901c6a7006a3cb04005236992d09fd184b06e3c4.camel@speedy.com.ar> Hi Rondejavu, El mi?, 27-11-2019 a las 15:57 -0500, Rondejavu escribi?: > I?ve successfully implemented IceCast on a Raspberry Pi and can > access the stream ONLY if I use an ffmpeg statement to start the > stream. Unfortunately, the stream is choppy and the sound quality is > poor. I?ve tried using ICES, but I don?t get any sound. > > Terminal command that works: > ffmpeg -ac 2 -f alsa -i hw:0,0 -acodec mp3 -ab 48k -ac 2 > -content_type audio/mpeg -f mp3 > icecast://source:password at ipaddress:port/stream > > ICES terminal command that doesn?t work: > ices2 /home/pi/ices-2.0.2/conf/ices-alsa.xml > > What am I missing? Thanks for any help/suggestions. Take a look at the logs, at ices-alsa.xml and also start Icecast2 firstly. Regards. Jos? Luis > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From mjbrenegan at yahoo.com Thu Nov 28 11:39:56 2019 From: mjbrenegan at yahoo.com (Michael Brenegan) Date: Thu, 28 Nov 2019 11:39:56 +0000 (UTC) Subject: [Icecast] IceCast and ICES In-Reply-To: <69B3A3FB-C6FF-452B-8AB3-10DB1C957F4F@gmail.com> References: <69B3A3FB-C6FF-452B-8AB3-10DB1C957F4F@gmail.com> Message-ID: <412239976.4213824.1574941196012@mail.yahoo.com> I may be wrong, but looking at your ffmpeg command, it looks as though you are trying to stream mp3 files.? Ices2 is no longer compatible with mp3 files, and instead has moved to ogg.? For an ices version that handles mp3 files, you will need to compile ices0.4. Good luck, Michael J. Brenegan USAR, Retired Clinical Engineering Yale/New Haven Hospital On Wednesday, November 27, 2019, 3:57:26 PM EST, Rondejavu wrote: I?ve successfully implemented IceCast on a Raspberry Pi and can access the stream ONLY if I use an ffmpeg statement to start the stream. Unfortunately, the stream is choppy and the sound quality is poor.? I?ve tried using ICES, but I don?t get any sound. Terminal command that works: ffmpeg -ac 2 -f alsa -i hw:0,0 -acodec mp3 -ab 48k -ac 2 -content_type audio/mpeg -f mp3 icecast://source:password at ipaddress:port/stream ICES terminal command that doesn?t work: ices2 /home/pi/ices-2.0.2/conf/ices-alsa.xml What am I missing?? Thanks for any help/suggestions. _______________________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From pm at nowster.me.uk Thu Nov 28 13:22:28 2019 From: pm at nowster.me.uk (Paul Martin) Date: Thu, 28 Nov 2019 13:22:28 +0000 Subject: [Icecast] IceCast and ICES In-Reply-To: <412239976.4213824.1574941196012@mail.yahoo.com> References: <69B3A3FB-C6FF-452B-8AB3-10DB1C957F4F@gmail.com> <412239976.4213824.1574941196012@mail.yahoo.com> Message-ID: <20191128132228.GA94019@thinkpad.nowster.org.uk> On Thu, Nov 28, 2019 at 11:39:56AM +0000, Michael Brenegan wrote: > I may be wrong, but looking at your ffmpeg command, it looks as > though you are trying to stream mp3 files.? Ices2 is no longer > compatible with mp3 files, and instead has moved to ogg.? For an > ices version that handles mp3 files, you will need to compile > ices0.4. One alternative is to use liquidsoap, but its configuration is not for the faint-hearted. With appropriate libraries, you can get liquidsoap to do simultaneous encoding to pretty much any current format (Vorbis, MP3, FLAC, Opus, AAC), and clever things like failover to a standby feed or file on silence detection. An example configuration, very close to the one I'm using: #!/usr/bin/liquidsoap # Enable telnet server for on-the fly metadata changes set("server.telnet", true) # Logging. Very useful for debugging problems. set("log.file.path", "/tmp/liquid.log") # ALSA audio source, at 48kHz sampling # Many consumer sound cards work at 48kHz natively and resample # for any other rate. set("frame.audio.samplerate", 48000) source = mksafe(input.alsa()) # Allow telnet server to override metadata source = server.insert_metadata(id="ID", source) # Metadata used when silence detected def fault_meta(m) = [ ("title", "There is a fault"), ("artist", "My Radio") ] end # Add metadata to emergency stream. # The file can be any supported type. emergency= map_metadata( fault_meta, mksafe(single("/srv/audio/birdsong.opus")) ) # Detect 30 seconds of silence on ALSA source source = strip_blank( max_blank=30.0, threshold=-60.0, source ) # Switch over to emergency stream on silence, and switch back automatically source = fallback(track_sensitive=false, [source, emergency]) # Icecast server common parameters ice_host = "127.0.0.1" ice_port = 8000 ice_pass = "hunter2" station = "My Radio" # A FLAC feed output.icecast( %ogg(%flac(samplerate=48000, compression=5)), host = ice_host, port = ice_port, password = ice_pass, mount = "radio.flac", name = "My Radio FLAC", description = station, url="", encoding="UTF-8", source ) # An Ogg Vorbis feed output.icecast( %ogg(%vorbis(quality=0.0, samplerate=48000)), host = ice_host, port = ice_port, password = ice_pass, mount = "radio.ogg", name = "My Radio Vorbis", description = station, url="", encoding="UTF-8", source ) # An Opus feed # Be aware that Opus always uses 48kHz sampling internally. output.icecast( %ogg(%opus(bitrate=128, samplerate=48000, application="audio", complexity=5)), host = ice_host, port = ice_port, password = ice_pass, mount = "radio.opus", name = "My Radio Opus", description = station, url="", encoding="UTF-8", source ) # An MP3 feed output.icecast( %mp3(bitrate=128, samplerate=48000), host = ice_host, port = ice_port, password = ice_pass, mount = "radio.mp3", name = "My Radio MP3", icy_metadata = "true", description = station, url="", encoding="UTF-8", source ) -- Paul Martin From artuch at speedy.com.ar Thu Nov 28 19:51:42 2019 From: artuch at speedy.com.ar (=?ISO-8859-1?Q?Jos=E9?= Luis Artuch) Date: Thu, 28 Nov 2019 16:51:42 -0300 Subject: [Icecast] IceCast and ICES In-Reply-To: References: <901c6a7006a3cb04005236992d09fd184b06e3c4.camel@speedy.com.ar> Message-ID: Hi Pete, El jue, 28-11-2019 a las 09:51 -0500, Rondejavu escribi?: > I am starting IceCast first. The log indicates that everything is > working. Maybe I need to change something in my HTML code? > > audio controls > Source src=?ipaddress:port/stream? > /audio > > -Pete > Not change your HTML code, in fact, it is already working ok. You must solve the problem on the source side. As Paul said, try some audio format supported by Ices2, such as ogg, opus ... The log of *Ices2* should be similar to: [2019-11-24 23:04:10] INFO ices-core/main IceS 2.0.2 started... [2019-11-24 23:04:10] INFO input-alsa/alsa_open_module Opened audio device default [2019-11-24 23:04:10] INFO input-alsa/alsa_open_module using 2 channel(s), 44100 Hz, buffer 341 ms [2019-11-24 23:04:10] INFO input-alsa/alsa_open_module Starting metadata update thread [2019-11-24 23:04:10] INFO signals/signal_usr1_handler Metadata update requested [2019-11-24 23:04:10] DBUG metadata/metadata_thread_signal reading metadata from "/etc/ices2/metadata" [2019-11-24 23:04:10] INFO encode/encode_initialise Encoder initialising in VBR mode: 2 channel(s), 44100 Hz, quality [2019-11-24 23:04:11] INFO metadata/metadata_thread_signal tag 1 is TITLE= [2019-11-24 23:04:11] INFO metadata/metadata_thread_signal tag 2 is ARTIST= [2019-11-24 23:04:11] INFO metadata/metadata_thread_signal tag 3 is ALBUM= [2019-11-24 23:04:11] INFO metadata/metadata_thread_signal tag 4 is CONTACT= [2019-11-24 23:04:11] INFO metadata/metadata_thread_signal Updating metadata [2019-11-24 23:04:11] INFO stream/ices_instance_stream Connected to server: localhost:6666/entzun.opus [2019-11-24 23:04:11] DBUG encode/encode_clear Clearing encoder engine [2019-11-24 23:04:11] INFO encode/encode_initialise Encoder initialising in VBR mode: 2 channel(s), 44100 Hz, quality Best regards. Jos? Luis > > On Nov 27, 2019, at 7:08 PM, Jos? Luis Artuch > > wrote: > > > > ?Hi Rondejavu, > > > El mi?, 27-11-2019 a las 15:57 -0500, Rondejavu escribi?: > > > I?ve successfully implemented IceCast on a Raspberry Pi and can > > > access the stream ONLY if I use an ffmpeg statement to start the > > > stream. Unfortunately, the stream is choppy and the sound quality > > > is > > > poor. I?ve tried using ICES, but I don?t get any sound. > > > > > > Terminal command that works: > > > ffmpeg -ac 2 -f alsa -i hw:0,0 -acodec mp3 -ab 48k -ac 2 > > > -content_type audio/mpeg -f mp3 > > > icecast://source:password at ipaddress:port/stream > > > > > > ICES terminal command that doesn?t work: > > > ices2 /home/pi/ices-2.0.2/conf/ices-alsa.xml > > > > > > What am I missing? Thanks for any help/suggestions. > > Take a look at the logs, at ices-alsa.xml and also start Icecast2 > > firstly. > > Regards. > > Jos? Luis > > > _______________________________________________ > > > Icecast mailing list > > > Icecast at xiph.org > > > http://lists.xiph.org/mailman/listinfo/icecast