Date: Tue, 11 Apr 2000 08:47:35 -0400 From: Alan Clegg <abc@firehouse.net> To: Konstantinos Konstantinidis <kkonstan@webdaemon.net> Cc: multimedia@freebsd.org Subject: Re: icecast/liveice problems Message-ID: <20000411084734.B31199@laptop.firehouse.net> In-Reply-To: <38F20B27.36D0C68C@webdaemon.net>; from kkonstan@webdaemon.net on Mon, Apr 10, 2000 at 08:11:03PM %2B0300 References: <38F20745.BE1492FD@webdaemon.net> <20000410125437.Z3935@laptop.firehouse.net> <38F20B27.36D0C68C@webdaemon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Out of the ether, Konstantinos spewed forth the following bitstream: > OK, the following is what I use (I use lame for encoding, it's in ports) [..] > All I do is run icecast, which promptly goes to the background > and starts waiting for sources/clients, and then run liveice. This works well for me as well. (now, thanks to you!) > Liveice connects fine with icecast as a source, and so does the > client... everything seems to be perfectly fine. Here is where mine falls over. I get the liveice source running and it appears to be doing things (I can telnet to port 8000 and get a raw stream with this header: HTTP/1.0 200 OK Server: icecast/1.3.0 Content-Type: audio/mpeg x-audiocast-location: Wake County, NC x-audiocast-admin: abc@firehouse.net x-audiocast-server-url: http://www.firehouse.net x-audiocast-mount:/icy_0 x-audiocast-name:Icecast development name: [Wake County Fire Dispatch] x-audiocast-description:Icy protocol in use x-audiocast-url:http://www.firehouse.net x-audiocast-genre:Live x-audiocast-bitrate:32 x-audiocast-public:1 [...] HOWEVER, when a client connects (WinAmp), it "buffers" some data, plays a bit of encoded sound, then, pauses, starts again, pauses, and finally is killed. I'm sure it is not a WinAmp issue, as I can connect to any number of ShoutCast services. Here is a snippet of the log from icecast: [10/Apr/2000:22:23:52] -------add_chunk: Chunk was [4096] bytes [10/Apr/2000:22:23:52] Locking 0x808b00c (Unknown Mutex (probably source)) on li ne 427 in file source.c by thread 5 [10/Apr/2000:22:23:52] DEBUG: wc: Writebytes == 65488. Will write 4096 bytes, wi th meta at 65536, after 48 bytes [10/Apr/2000:22:23:52] DEBUG: sock_write_bytes_or_kick: -1 err [35] [10/Apr/2000:22:23:52] ------write [ 3] [ 23]:[ 24] [ -1] [10/Apr/2000:22:23:52] --------err[ 3] [ 0] [ 30] [10/Apr/2000:22:23:52] Unlocking 0x808b00c (Unknown Mutex (probably source)) on line 465 in file source.c by thread 5 [10/Apr/2000:22:23:52] Locking 0x808b00c (Unknown Mutex (probably source)) on li ne 788 in file source.c by thread 5 [10/Apr/2000:22:23:52] Unlocking 0x808b00c (Unknown Mutex (probably source)) on line 801 in file source.c by thread 5 [10/Apr/2000:22:23:52] -------add_chunk: Chunk was [4096] bytes [10/Apr/2000:22:23:52] Locking 0x808b00c (Unknown Mutex (probably source)) on li ne 427 in file source.c by thread 5 [10/Apr/2000:22:23:52] Kicking client 3 [spook.networkoperations.com] [Too many errors] [listener], connected for 44 seconds, 65488 bytes transfered. 1 clients connected One thing that I have noticed is that the "kicking" happens right around 64k into the data stream EVERY TIME: [10/Apr/2000:22:00:04] Kicking client 2 [spook.networkoperations.com] [Too many errors] [listener], connected for 50 seconds, 65472 bytes transfered. 1 clients connected [10/Apr/2000:22:03:40] Kicking client 3 [spook.networkoperations.com] [Too many errors] [listener], connected for 52 seconds, 65520 bytes transfered. 1 clients connected [10/Apr/2000:22:14:42] Kicking client 1 [spook.networkoperations.com] [Too many errors] [listener], connected for 52 seconds, 65536 bytes transfered. 1 clients connected [10/Apr/2000:22:16:52] Kicking client 4 [spook.networkoperations.com] [Too many errors] [listener], connected for 47 seconds, 65536 bytes transfered. 1 clients connected [10/Apr/2000:22:22:25] Kicking client 2 [spook.networkoperations.com] [Too many errors] [listener], connected for 55 seconds, 65440 bytes transfered. 1 clients connected [10/Apr/2000:22:23:52] Kicking client 3 [spook.networkoperations.com] [Too many errors] [listener], connected for 44 seconds, 65488 bytes transfered. 1 clients connected > Now if only it actually broadcasted something OTHER than silence > I'd be a happy man. BTW, it doesn't work at all with the pcm driver, > so don't even bother with it. I'm actually using the pcm driver and doubt that it is a related problem. The little bit of buffered audio that I do get does have audio content (with a large amount of white noise that I need to filter out). I see the exact same issues with both the version of Icecast in ports and the "beta" 1.3.1 from their web site. This is under FreeBSD 4.0 cvsup'd about a week ago. If anyone would like to listen to the stream to test (it is currently a random shortwave station, but will be fire/rescue dispatch when I get it working), feel free to point to: http://www.firehouse.net:8000 AlanC -- Firehouse Network Consulting We fight fires so you don't have to(tm) http://www.firehouse.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000411084734.B31199>