similar to: streaming from the sound card

I get a segmentation fault when starting the IceS encoder on a Linux-based QNAP NAS. I'm trying to set up IceS to stream an ALSA input to Icecast. Icecast works well and confirms when I stream using other things to it. However IceS hits a segmentation fault immediately after starting the encoder. The IceS log is: [~] # sudo ices /etc/ices.xml [2020-05-11 19:24:34] INFO ices-core/main IceS

I am having problems getting Ices to work with ALSA. If I use arecord (arecord -D plughw:0,0 output.wav) I can record the input from my microphone into a file. The playback works perfectly. However, if I use Ices with the same values I hear nothing on the receiving end of my broadcast (although I can connect to it). In order to do a further test, I setup a <savefile> tag in my

On Mon, 2005-05-02 at 17:43, Jack Coates wrote: ... > Ices and Icecast both start okay, and aren't logging any complaints. But > when I try to connect to the ogg stream with Winamp, I get nothing. > Using tethereal, I can see that the the connection handshakes okay, the > metadata is passed back to the client, the client acks, and that's the > end. Nothing is logged by

Hy, I've just installed the latest release of icecast2 and ices from CVS. I have a linux Slackware 9.0 with the default packages. After install of ices and icecast & relative libraries (with no errors), I've started the icecast server. When starts ices, this is the debug: --- INFO ices-core/main ices started... INFO input-oss/oss_open_module Opened audio device /dev/dsp at 2

Hello Everyone, I have a bit of a problem trying to set up Icecast2 + Ice2, on my debian box, I installed icecast2 ver 2.3.2-6 and ices2 2.0.1-8. I'm able to start icecast2 as shown in the logs: [2012-12-24 20:34:27] INFO main/main Icecast 2.3.2 server started [2012-12-24 20:34:27] DBUG yp/yp_recheck_config Updating YP configuration [2012-12-24 20:34:27] INFO

I posted the other day with a question about a player that mysteriously quits playing the icecast stream. I believe the problem is related to the icecast stream for two reasons. 1) Because it quits on more than one different player (Winamp 5 and Foobar2000) and 2) Because I used to use shoutcast with Winamp 2 and never had this problem. Anyway, I tried to get as much information about the problem

Can anybody help me, I have Icecast2 and Ices2 on Mandrake and want to play a static playlist. I am getting the following problem: [2003-06-26 12:56:08] DBUG connection/_handle_get_request Client connected [2003-06-26 12:56:08] DBUG admin/admin_handle_request Got command (streamlist) [2003-06-26 12:56:08] INFO admin/admin_handle_request Bad or missing password on admin command request

Hi there, I just joined the list and have a question on one of the earlier posts: On Oct 28 2003, Ricardo wrote that his server diconnected his clients. I have the exact same problem - and a bit of testing/analysis. <p>I am running an Icecast server and IceS on the same linux box. IceS is encoding a live stream from my sound card. After a while of listening (approx 2 mins) from another

Hello, I had a big trouble with ices (ices-2kh60). It is reading a playlist file containing "-" to tell "read stdin". But I think that when stdin is having problem, then ices become mad. It tries hundreds of time per second to play the playlist file content, generating huge amount of traces, which are rotated, but causing a denial of service on the server which become

Hello all I am sending my icecast configuration. What i am trying to do is 'live stream' so as to be able to broadcast radio live on my website. I am using icecast as the server and ices as the streamer. Below is the configuration for icecast and following it is my configuration for ices. I cannot seem to find out where i went wrong. <icecast> <limits>

Hi, I''m running shorewall-2.0.8-1mdk with iptables-1.2.9-7.1.101mdk on kernel-2.4.22-30mdk, Mandrake 10.1 (kernel-2.6.8.1.10mdk-1-1mdk is installed, but I haven''t rebooted yet). I get a significant number of newnotsyn packet denials from existing, valid connections. Most of these seem to be on port 80 and port 25, and directionality doesn''t seem to matter (I run

> I dont care I just wanted to make sure there is no problem 50 seconds is a bit long. Probably your client buffer is really high and you are streaming at a really low bitrate. But even in that case 50 seconds seems long. If you can post more details on bitrate, client used, buffer size used on the client, etc, that would be helpful for verification. jack. --- >8 ---- List archives:

I have problems with the stdinpcm module in ices2. The player fills its buffer and doen't play anything and fill the buffer again and this repeats (with winamp). when I download the stream with wget I can play it from hard disk... is this a common problem with ices2 or do only I experience this behaviour? the oss module works. --- >8 ---- List archives: http://www.xiph.org/archives/

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

>if you are getting the ogg data from a stream then you can just state a >- in the playlist and it will read it from stdin. > >curl .. http://host:port/mountpoint.ogg | ices ices-playlist.xml > >ideally the playlist should be more flexible and allow starting of >external programs but not just yet. > >karl. Thank you! That got it working. Partly. I managed to get two

Hi: Last week, I upgraded an icecast2 server and enabled the directory code. The primary streams that run on it showed up nicely. As some may recall, I had issues with libshout compiling (seems the sources got hosed somehow, a fresh checkout fixed everything after all else failed), and I just compiled the latest ices2. I noticed, with some surprise, that the config file hadn't changed in

Unfortunately, ices2 isn't writing anything to the logs. I've got them on debug mode, but there still isn't anything being written to indicate it's having a known problem. As far as the interference goes, I've found that reducing the iGain and amping the input source seems to reduce the interfencence a good deal, at least, good enough such that it's only a low murmur in

Hi there - I am currently in the middle of a project where I need to configure an Icecast Server and I am using Ices as the encoder. I want to configure Ices to take in a stream with a sample rate of 128 kHz and output it to the Icecast server. My question is, what are the minimum and maximum sample rates that Ices will continue to work with? Thank you, Heidi Young Software

I'm trying to connect to my icecast2 server with winamp with http:host:8000/test.ogg and I get the following error on the server console: DEBUG: client coming in DEBUG: source not found for client I'm wondering if the playlist.txt file is in the wrong place. It's in /root/ and has absolute pathnames to the ogg files in my home directory /home/user/ogg/ What did

On Sun, 29 Aug 2004 17:53:29 -0700, Ralph Giles wrote: > On Mon, Aug 30, 2004 at 03:03:28AM +0100, Andy Baxter wrote: > >> Is there any way to bring the bitrate in ices2 down below 32 kbps? > > Generally the trick for this is to downsample the audio before encoding. > You can ask ices to do this with a resample stanza in the config file: > > <resample>