similar to: Ices encode stops using Hauppauge pvr usb2

Anyone have the Hauppauge WinTV-PVR-350 card running on CentOS 4.X? What about MythTV? One of my users asked me today to upgrade the kernel on his CentOS 4.4 system today as he claims that this card will only work on recent kernels (2.6.16 or newer). I haven't found any documentation to support this (the Linux page on the Hauppauge web site is hopelessly out of date; it mentions

Hello, I have a problem with icecast icecast-2.0-kh8: - the source disconnect - icecast didn't notice it - the source cannot reconnect until - the source cannot reconnect (it tries every 8 seconds) - after two hours, the source is able to reconnect Here is the interesting parts of the log files: Thanks for your advices and help. Chris (icecast machine has +3sec in its time, that's

hi everyone, congratulations on the release of icecast 2.1.0 I presume this is the right place to post about iceS. please correct if wrong. I have a two instance setup, and have been finding that after a network error occurs, the instance does not reconnect. The source server is behind a linux NAT box. I have simulated the problem by using iptables REJECT with tcp-reset and here is the

Hi: I'm running ices on one box with three streams, one streaming as is and two re-encodes, and another box running icecast2. The straight-through stream is going strong, but the two re-encodes have died. Ices is trying to re-establish them, but it keeps saying it gets a broken pipe, as evidenced below: [2004-03-09 10:47:55] INFO encode/encode_initialise Encoder initialising in VBR mode:

Okay I was poking around the logs, getting ready to test the yp server update, and then I decided to check the configs. I still had localhost set for the hostname, so I changed it to my real hostname. Now I get this in my ices.log when trying to start (although icecast is started fine): [2003-06-05 12:27:00] EROR stream/ices_instance_stream Failed initial connect to myreal.hostname.net:8000

... [2009-02-14 20:54:27] INFO ices-core/main Shutdown complete [2009-02-14 21:01:02] INFO ices-core/main IceS 2.0.1 started... [2009-02-14 21:01:02] INFO signals/signal_usr1_handler Metadata update requested [2009-02-14 21:01:02] INFO playlist-basic/playlist_basic_get_next_filename Loading playlist from file "/etc/ices2/playlist.txt" [2009-02-14 21:01:02] WARN

I tried to stream two different playlists in two different mount points. I created playlist1.m3u for ogg compressed at 96 Kbps and playlist2.m3u for ogg comressed at 32 kbps (wich each playlist contain the right path to ogg files) i created another ices-plylist.xml called ices-playlist32.xml in this one i had changed the path to the playlist file <param

I just built icecast and ices from CVS source. The compile went fine. But I'm having trouble connecting to the server and hearing anything. In one shell, I start icecast with: src/icecast -c conf/icecast.xml That appears to start things off fine. Then in another shell, I start ices: src/ices conf/ices-playlist.xml At this point, icecast prints some text: connection added.... DEBUG: source

[In case anyone is wondering, the missing message is because I emailed Mike directly, not realising I wasn't sending to the list.] On Tue, Aug 16, 2005 at 12:56:57PM +0200, Michael Smith wrote: > On 8/16/05, Paul Martin <pm@nowster.zetnet.co.uk> wrote: > > On Tue, Aug 16, 2005 at 10:31:09AM +0200, Michael Smith wrote: > > > > > This shouldn't cause any

Hi... first post to this list so be gentle with me! I've got Icecast 2.2.0 running well, and using Ices 2.0.1 to feed the OGGs. All was working, then all of a sudden I've started getting these messages in the (ices) log... [2005-05-08 12:10:19] INFO ices-core/main IceS 2.0.1 started... [2005-05-08 12:10:19] EROR stream/ices_instance_stream libshout error: Out of memory [2005-05-08

It was kind of working for a while but I could not hear the stream but it was running. I started messing with alsamixer and now it crashes. I see the error but I don't know how to fix it. ices-oss-xml: (alsa is the same just a different input module) <?xml version="1.0"?> <ices> <!-- run in background --> <background>0</background>

Hmmm, I guess more is incorrect here than I thought. I changed the resample in-rate to be 44100 like it should have have been. But still no joy. Here is the error message as shown in the error.log file. I'm looking things over and am not seeing my error. It looks like the audio resample for this particular stream is good. [root@icecast conf]# ices /usr/local/icecast2/conf/ices.stream.3.xml

Hi, Is it possible to generate an ogg stream at less than 22KBps ? I tried several configuration with ices and darkice, but I always get an configure encoder error: [2003-03-17 16:07:17] INFO input-oss/oss_open_module Opened audio device /dev/dsp at 2 channel(s), 44100 Hz [2003-03-17 16:07:17] INFO audio/resample_initialise Initialised resampler for 2 channels, from 44100 Hz to 22050 Hz

Hi everybody, I'm in charge of an ices2 setup that's broadcasting a local radio station on the Net, and I'm currently under fire because one of our streams has been down twice in two days, forcing me to restart ices2 on each occasion. Our client is understandably unhappy about this. OUR SETUP: I've got ices2 installed on a local machine, broadcasting to an icecast server across

Hey Jack Vakor I dont know if this is a icecast or ices releated probelm. For the past couple of days ive been streaming Ogg Vorbis on our internal network. Today i tried to move the icecast2 server to one of our external servers and it went up find (after i installed the proper libs ;-) Anyway i pointed ices towards the server and got the following error every time it tried to connect to the

mmm... ok. well i got ices2 installed properly now (i hope) after some effort and help (cheers Michael for the prompt response!). the goal is to get ices2 to stream to a peercast client on port 2768. but somehow things are still not going quite as planned. here is the log ----------------------------------------------------- idoru:/var/log# ices /usr/local/etc/ices.conf [2003-03-20 22:55:29]

Hello, I'm testing icecast2(apha2) and ices2(beta2). (sources 2003-08-12) ices2 with ices-playlist works fine! But I have troubles whith ices-live. When ices2 trays to read /dev/dsp a log message appears: INFO input-oss/oss_read Reached EOF, no more data available. and ices2 shutdown. the complete log file (debug=4): ******************* log *******************************************

Hi list!! I have some problems with ices, cant connect to server... The Error Log : [2005-03-07 19:00:08] INFO playlist-builtin/playlist_read Currently playing "/Music/mr bungle - a dub.ogg" [2005-03-07 19:00:08] EROR stream/ices_instance_stream Failed initial connect to 172.16.0.13:8022 (Socket error: Success) [2005-03-07 19:00:08] DBUG reencode/reencode_clear Clearing

Hi, I just installed 2.0.1 but I'm unable to use it. It doesn't want to connect to my server, but instead, it tries to connect to localhost:8000 (default). My configuration file is the same than before. It's working fine with ices 2.0kh60 I wanted to change because since I installed icecast 2.3.1, ices freeze every day at each network interruption (xDSL IP change). My ices runner

Karl, I installed icecast/ices from the latest stable ebuild on gentoo portage. It appears from the log file that ices is only version 2.0.0 even though the ebuild is version 2.1.0. I just reinstalled icecast with the newest (unstable) ebuild and it still doesn't seem to have version 2.0.1 of ices. Do you recommend that I manually compile or that I find a way to use a wrapper for ALSA to