similar to: perhaps dump re-encoding question

> > Hello. I am trying to have one stream at 128k, and one at 56k, but > > with the same contents. Is this possible with ices? From a careful > > reading of the options, it looks like reencoding will only generate > > one stream, at the re-encoded rate. > > I have no answer, but I would like to reiterate (posted the same > question Friday, I think) that I would

Hello: I am running the icecast2.3.2 server and ices0.4 with a perl script which provides the filename of the next track to play. I am reencoding in advance using ffmpeg, which has been very reliable. My main stream is mp3, 64kbps / 44.1 kHz (mono) and I have pre-reencoded the tracks to 32kbps / 22.05 kHz (mono), for a lower data rate stream. At this time, I have not figured out how to get a

I did some further investigating into this issue and here's what I found: It appears somewhere between ices0.1.0 and ices 0.2.0 is where the "bug" (for lack of a better term) was introduced that i'm noticing. When I compile ices0.2.0 w/lame 3.89beta, the VBR is *NOT* reencoded, but instead streamed out at full VBR bitrate(s). However, when using ices0.1.0 w/lame 3.89beta, it

OS: FreeBSD4.8 okay I installed ices from /usr/ports/audio/ices copied ices.conf.dist to config.xml can somebody explain to me why the configuration file is not getting loaded root@hurricane# ices [/usr/local/etc/ices] IceS 2.0beta2 (c) Copyright 2001-2002 Michael Smith <msmith@icecast.org> Usage: "ices config.xml" root@hurricane# ices

A couple pf questions regarding reencoding... I've got ogg, mp3, and aac files to stream. a) What are the restrictions in the current version of ices (0.4?), is it that channels and samplerate must be equal in all files? b) will they be reencoded to ogg or to mp3, or is there a choice? Thanks. -- Guy

On Tuesday, 26 June 2001 at 11:15, Denys Sene dos Santos wrote: > > I'm running Ices 0.1.0, but the reencoding don't works > with lame3.88. I prefer 3.88, it's more clean, but with the 3.86 > that the reencoding works. How did you get it to build? ices 0.1.0 explicitly checks version info, and besides that makes library calls that don't exist in 3.86. you are

HI, Every time I try to stream any Ogg files I have this reply from ices : Mounted on http://127.0.0.1:8000/ices Playing /mnt/windows/cosmotron2.mp3 Cannot play /mnt/windows/01_burning_dna.ogg without reencoding Playing à÷1@à÷1@dows/01_burning_dna.ogg Erreur de segmentation (translation : Segmentation faukt ;-) Can you help me please ? This is my first try ... --- >8 ---- List archives:

I currently have 3 mountpoints, 128, 56 and 24. I'm using darkice as the source and I'm relaying to another server running icecast2. I'm assuming that darkice is using lame for transcoding the bit-rates on the fly and sending 128k/s + 56k/s + 24k/s to the relay host... which is using a lot of bandwidth on the source network (which I don't have much to spare). Is there any

I recently upgraded ices from 0.1.0 to 0.2.2. I have found that it is not reencoding my mp3 stream, even though I have it configured to. This is on a RedHat linux 7.0 system, kernel 2.4.11 ices build commands: ./configure --with-perl --with-lame \ --with-lame-includes=/usr/local/src/lame-3.89/include \ --with-lame-libraries=/usr/local/src/lame-3.89/libmp3lame/.libs gmake

Brendan Cully wrote: > > The format of ices.conf changed somewhat in 0.2, to support multiple streams > from the same playlist with different reencoding options. In short, these > settings have been moved into the Stream node. For more info have a look > at the sample ices.conf included with the distribution. I did modify my ices.conf when I made the upgrade. Here's my

I'd like to use the Bitrate and Reencode features of ices and understand I must recompile with lamelib. However, it's Very Unclear where to begin here. This is noted in the ices-0.2.3 INSTALL file: I installed lame as a debian package so lame.h is in /usr/include/lame/lame.h and libmp3lame.a is in /usr/lib. configure finds everything automatically. <p>I assume we

I have an Icecast server and an Asterisk dialplan containing a call to ICES(/my/ices.xml). So Asterisk launches "ices /my/ices.xml" where /my/ices.xml contains: <input> <module>stdinpcm</module> <param name="rate">8000</param> <param name="channels">1</param> </input> and <encode>

Hello everyone, Few weeks ago I tuned icecast with 7 streams from ices. It plays static playlists, sorted by genre. I have 2 problems. First problem: pure quality when reencoding is turned on. Temporary solution was found. I added one string, to reencoding code, that points to liblame use better quality. But is this the one and right solution? Second problem: Ices (or liblame?) does not properly

hello anyone of you who has used the reencoding option of ices to bring the stream at a constant bitrate would be kind to share the experience (the impact on resources and, quoting the README file - "...mpglib part of lame (what does the decoding) is rather unstable and will call exit(0) when errors are encountered." - and stability of the stream). thanks, petre -- Petre Bandac -

On Tuesday, 26 June 2001 at 11:02, Denys Sene dos Santos wrote: > > Lame3.88 has no reencoding. > Because this, I used 3.86... but it needs to copy the libs manualy > to the right places Er, what version of ices are you running? ices 0.1.0 will not work with 3.86. Lame 3.88 also builds much better. > Why is the Lame/Ices/Icecast documentation so poor ??? Because

At 11:17 AM 29/10/2002 -0700, you wrote: >I'm doing a top on my server (ices2 and icecast2 from CVS) and ices is >using 14% of my cpu cycles - bastard! One channel is doing reencoing >and when I just play an ogg without reencoding. The ogg file was >encoded at 64kbs 44khz Is this praise, a bug report, a question, or other? If you're having a problem with the software, it

Hello together, we would like to use IceCast 2.3.1 as a mp3 streamer source for reencoding several sources of ices 0.4. It is working perfectly already by using an mp3 playlist with local stored mp3s. But our plan is to upload an 160 kbps stream and want ices 0.4 to reencode to 96, 56 and 32 kbps. Uploading 1 getting 4 streams. We are streaming with SAM Broadcaster 2. Icecast runs on SuSE 9.3

Hi all: I was just wondering when the multiple streams stuff might be checked in to cvs. I remember the gentleman working on it saying he basically had it running? The reason I'm asking is that I have received a number of requests to stream my mp3 stream at various bitrates. I kind of think running three ices streamers is silly if multiple streams will be available in the near future.

Hi. I'm confused about one of the statements on http://www.vorbis.com/faq.psp#unique I have a server using Ices2 as the source. I provide it with Ogg's encoded at quality 5, and I get it to provide lower bitrate streams like so: ices.xml --snip-- <instance> --snip-- <encode> <samplerate>44100</samplerate>

yep, they simply forward the bitstream to icecast. And in general, bitrate changes are handled by most listening clients, although very few I have found (if any) can handle samplerate changes appropriately. oddsock At 10:03 AM 9/14/2004, you wrote: >You mentioned these programs and their "no-reencoding" mode. Can they >handle collections of MP3s of different bitrate? >