similar to: low bandwidth broadcasting using ices2

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>

On 2006-06-21T15:21+0100 Karl Heyes wrote: > You capture at 48000 but resample from 44100, that will cause problems. > You resample to 22050 so that will affect quality, you haven't said what > bitrate you want to target for, so resampling/downmixing may be required > anyway. I am unsure about these settings. Any particular suggestions? I don't quality with voice, just

Folks: I'm trying to set up a streaming server under Fedora Core 2 using Icecast 2.2.0. Everything compiles; everything runs. There are no indications of a problem in any of the log files. When I look at http://192.168.0.128:8000/status.xsl, everything looks ok. But when I click on "Click to listen", it brings up xmms, but there's no indication of audio, and xmms shows a bit

I'm rebroadcasting a realplayer stream and there are two problems. The icecast2 sounds tinny and its delayed something like 3secs. Any advice to perhaps use speex as it's talk radio? Can I cut the delay? Here is my ices2 config: http://static.natalian.org/2006-06-21/ices-alsa.xml Here is details of the feed, so you can take a listen:

I'm trying to encode audio tracks as ogg vorbis at very low bandwidths for peer to peer broadcasting. I.e. need to have two streams uploading from modem users, which means the bitrate needs to be around 18-22 kbps. It's not easy to get good quality at this bitrate. The recipe I'm using at the moment is: oggenc Mon-Sep-20-04-0\:3\:27.wav -b 20 -M 22 --resample 17000 --downmix -o

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

I'm using ices2's metadata facility to update the name of a track in a vorbis stream: <input> <module>alsa</module> <param name="rate">44100</param> <param name="channels">2</param> <param name="device">hw:1,0</param> <param name="metadata">1</param>

> On Tue, 2003-05-27 at 21:06, adam leigh wrote: > > 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. > > well thats a problem, you should at least see > ices started > if not then try to resolve that first. Email

Hi all, I run a CVS version (i dont remember exactly when did i got it )of Ices2/ Icescast2 on a slackware Linux box . I put this section into the Ices2 conf file : [...] <encode> <samplerate>22000</samplerate> <channels>1</channels> <quality>0</quality> <managed>1</managed> <nominal-bitrate>35000</nominal-bitrate>

Can someone who really knows the Ogg command-line encoder, help recommend the best setting for 33.6k modem stereo music streaming? (56k doesn't count cuz many people's 56k modems don't work at a full 56k, and I want them to be able to surf CD Baby at the same time as listening. 2 minutes / 120 seconds of audio should be about 400k.) I'm at my wit's end: tried everything I

I have been successful in running a playlist through Ices and Icecast... I have run into difficulty running a live stream through the soundcard, however... The following is the log when I attempt to run ices ices-mylive.xml: INFO ices-core/main ices started... EROR input-oss/oss_open_module Couldn't set sample format to AFMT_S16_LE EROR input/input_loop Couldn't initialise input module

First let me say that I was absolutely astounded at the sound quality when using oggenc at q = -1 (around 50 kbps). So much so, that I'm anxious to try some of the lower bit rates that were mentioned in the announcement for 1.0: ... audio and music at fixed and variable bitrates from 16 to 128 kbps/channel. But I am having trouble finding how to use either oggdrop or oggenc to get these

darkice is an execellent bit of software, very well written. and the author of the darkice software, akos, is very active on the darkice ML. http://yp.tilos.hu:9000/tilos_high.ogg <= for a darkice stream. b. On Sat, Nov 22, 2003 at 12:05:55PM -0500, Brendan Cully wrote: > On Saturday, 22 November 2003 at 10:50, Kerry Cox wrote: > > So basically, I download and install ices 0.3,

I've got icecast2 and ices2 working with a playlist of ogg files and it works fine. I've been playing for a few days with getting my audio to work at all. I've now got my audio where I can play an ogg file from ogg123 -d oss filename.ogg. When I run ices ices-live.xml I get the following error in my log file: [2004-09-30 09:38:07] INFO ices-core/main IceS 2.0.0 started...

Hi, <p>apparently, I didn't delete my test samples ... I found them. :) Here's a small table of what nominal bitrate fits to which quality at what sample rate. Quality levels inbetween -1 and 0 are possible, but I didn't test them. Nominal bitrates of those quality settings will be somewhere between those of -1 and 0 and therefore can be guessed. q/channels || -1/mono |

On Sat, 07 Aug 2004 22:34:05 -0400, dave wrote: > Hello, > I've got icecast2 and ices0 going and i've got a stream of mp3 files. I > don't think i've got all the bugs worked out though. Firstly, could someone > either explain or point me to a site that explains bitrate and sample rate? > I want to offer this stream for both broadband and dialup use. I'm

On Mon, Sep 26, 2005 at 05:30:11PM +0200, Michael Smith wrote: > > Assuming this is correct, the next question that arises is "Is Vorbis > > when used this way truly gapless?" > > Yes, it is. ... and I can confirm this. No gaps were perceivable decoding in ogg123. However, an interesting effect can be had if all the parts have the same serial number. You get a bump

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]

This afternoon I've transferred our Ogg Vorbis Icecast2 streams from darkice to the ices2 encoder. Apologies if you were trying to listen; I had to stop and start the streams a few times. They should be stable now as I'm off down the pub now! As a reminder, the URL for the streams is at http://www.virginradio.co.uk/thestation/listen/ogg.html. Ices2 takes slightly different parameters to

>it supposed to, check the log file for details but there is no reason >for it not to work with 2 instances. > >Note as well, that you should have 2 instances each of which has the >icecast connection details and an encode section. > I don't quite understand. You always talk about two instances. Do you really mean two instances of ices2 called seperately? Do I have to make