similar to: ices & reencoding

>But wasn't there some plan already in the standard-docs to use >Servername + "cluster password" for listing a cluster of servers? >Well okay, but maybe this requires an addition to icecast2 :-) > that was the original plan, and may still be implemented to enable relay servers from multiple locations to cluster together, but as you mention, this requires updates to

Why does my stream not show up in the Icecast directory but it does show up in the Shoutcast directory? I have the following lines listed in my icecast.conf file. icydir yp.shoutcast.com directory yp.icecast.org If I check the icecast.log file I see the following is occurring every couple minutes. [28/Dec/2001:11:12:04] [1:Calendar Thread] directory_touch_xa([yp.icecast.org:80 ])

I want to link to a method of a different controller. I thought I new how to do this but the code that I have is not working: <%= link_to ''Welcome Page'', { :action => ''index'', :controller => ''music_controller'' } %> Any ideas, thanks ~S -- Posted via http://www.ruby-forum.com/.

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

Hi Everyone -- First and foremost, I'd like to thank the creators of Icecast and all the ancillary tools. Most excellent work! I'm running a somewhat unique radio station called LamRim Radio which hosts Tibetan Buddhist teachings and recently hosted a semi-real-time teaching by His Holiness the Dalai Lama of Tibet... http://www.lamrim.com/ Icecast has been the enabling

i have installed ices with lame suport (thanks to all who helped!), and it happily reencodes bitrates. i have installed otto, and that too is brillient however i can't get otto to call ices in such a way that it will reencode stuff streamed thru otto... when i have had ices working with reencoding, i've configured it via the xml config file rather than with command line switches

hi, if i reencode a stream that is in mp3pro (streamed with sam) to a lower bitrate by using ices/lame, is the reencoded stream mp3 or mp3pro ? thank you -- Mit freundlichen Gr?ssen Carsten Henkel mailto:carsten@chatlabel.de Eine gl?ckliche Frau braucht 4 Tiere: einen Jaguar in der Garage, einen Nerz im Schrank, einen Hengst im Bett und einen Esel, der alles

Carsten Henkel wrote: > hi, > if i reencode a stream that is in mp3pro (streamed with sam) to a > lower bitrate by using ices/lame, is the reencoded stream mp3 or mp3pro > ? MP3. LAME does not do MP3Pro. And in fact, the stream that is reencoded will also only be a reencode of the MP3-compatible layer of the MP3Pro stream, as Ices does not know how to decode MP3Pro streams

Guten Tag Geoff Shang, Am Freitag, 14. Januar 2005 um 13:22 schrieben Sie: GS> Carsten Henkel wrote: >> if i reencode a stream that is in mp3pro (streamed with sam) to a >> lower bitrate by using ices/lame, is the reencoded stream mp3 or mp3pro GS> MP3. LAME does not do MP3Pro. And in fact, the stream that is reencoded GS> will also only be a reencode of the

Hi, I'm having trouble getting ices 0.2.3 to reencode MPEG-2 LSF mp3s, the files are playing back around twice as fast as they are supposed to, ie the "chipmunk effect". I'm not encoding the originals but I've tried encoding them with lame to the same effect which causes me to believe the problem is with ices' decoding. The source files are of varying bitrates and

Carsten Henkel wrote: > thank you for the information. is there a way to encode mp3pro with > linux ? There's no free implementation that I'm aware of. Thompson may be able to sell you something, but I've no idea how much it will cost. Frankly, I'd move to Ogg Vorbis, it's supported by more players anyway. Geoff. -- Geoff Shang <geoff@hitsandpieces.net>

> There's no free implementation that I'm aware of. Thompson may be > able to sell you something, but I've no idea how much it will cost. > Frankly, I'd move to Ogg Vorbis, it's supported by more players > anyway. From a quality standpoint, I'd love to, but from a 'supporting paid users of a stream with minimal effort' standpoint, the amount of

On Tuesday, 27 November 2001 at 18:14, Bolt Thrower wrote: > 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 \ >

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

Moritz Grimm wrote: > > Bolt Thrower wrote: > > > >From my ices.conf: > > <Bitrate>64</Bitrate> > > > My mp3s are encoded with the following command: > > /usr/local/src/lame3.86/lame -S -V 1 -b 128 -h -m j \ > > --tt "title" --ta "artist" --tl "album" \ > > --ty "year"

Is it possible to cancel the DOM write to the element passed to Ajax.Updater? I didn''t see anything in the documentation, and I''d like to use this instead of Ajax.Request. There are situations where the results that are returned will not be what is expected, and I have no control over this. For this reason, I''d like to be able to cancel writing to the DOM. Thanks in

I always kind of liked this title (the title of Davids super Rails presentation), but then I saw this quote today: "The pursuit of happiness is a most ridiculous phrase; if you pursue happiness you''ll never find it." by C.P Snow I''d have to agree with this quote. It''s the same as love... go looking for it, and you''ll never find it. Soooo... David,

Since the mailing list archives are a bit difficult to go through at the moment, I'll go ahead and simply ask. If I fire up ices-0.4 with reencode enabled, at pretty much the end of every song I get an error: bitstream problem: resyncing... Occasionally it will also throw in a: mpg123: Can't rewind stream by NNN bits! And eventually after a dozen songs or so I'll get a rash

On Wednesday, 28 November 2001 at 12:43, Bolt Thrower 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

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