similar to: newbie questions

> I just want to stream a set of mp3 files so that folks on modems can hear them using winamp or (in a perfect world) RealPlayer. > > i've set up an old 486 running debian 2.2r2 using the debian icecast packages (shout doing the streaming). > > so far so good, with a bit of fiddling i had a stream that worked fine over the local network > > remote users are unable to

On Wed, 4 Apr 2001, John Griffiths wrote: > i've set up an old 486 running debian 2.2r2 using the debian icecast packages (shout doing the streaming). As my sig points out, yes, it is possible. RiR is linux and icecast stripped to the bare necessities. > so far so good, with a bit of fiddling i had a stream that worked fine over the local network As I too have seen in practice :/

> hey ya all, > > I need some direction , as i have seem to hit stupid row. > I have IceCast running, and streaming, all works excellent. > > What i would like to do is : add the link to my website and when it is > clicked on, it opens the stream in winamp > Does anyone have information on how i go about doing this ? > > Thank you in advance. > Rick -

> > Hmm. I tried a windows laptop box (kinda slow) and indeed after about > > 30-40 minutes playback starts stuttering and eventually disconnects > > from the icecast server. > > > > Nothing else is running on this box. What gives? Why am I losing about > > 25% of the connections to this error? > > Are you using shout? Let me clarify here with the

ok... topology. 486 with 10BaseT card hooking into 10/100 hub hooking into 10/100 switch hooking into cisco router combining two 128KbpsISDN lines into a consolidated 256kbps line. listening on my desktop machine is fine, also 10baseT into the same hub as the server. the bitrate on the mp3's is 128 (great for listening off the HD) whats a good bitrate to encode for streaming audio? At

I'm having a couple problems trying to get Icecast and LiveIce set up on a Linux 7.0 system. I'm running Icecast 1.3.10 without a config file (using all defaults). I can use shout to stream to it and connect to it from a windows machine running WinAmp. It works OK except winamp stops every few seconds and tells me that it's buffering. It buffers for a few seconds and then plays a

Well, this may not be unique to RC2. I believe this is the first time I have noticed it. It is definitely the first time I have vorbis encoded this song. Try encoding They Might Be Giants - Istanbul. Go to offset around 50 seconds. It should say "Maybe people just like it better that way." However, the maybe is pretty bassy (low pitch) and is just gone. Anyway, RC2 is so much

Hello all: I am very much enjoying reading this list. It's great to see discussion (mostly readable by non-vorbis-developer types) on the potential of vorbis and OGG in general. But I'd like to ask about the immediate future. I am very keen to adopt OGG vorbis for a number of uses, but I am awaiting a few things. And I do not wish to pester and hassle those hard at work to make this

hello, I try to listen to the stream at http://ogg.radiostudio.org:8007/ostream.ogg with ogg123, it's a 44100/mono stream. It sounds to me like a mono file played as a stereo file. there are very often silent drop outs and the music is pitched. is this a bug in ogg123? I changed to stereo encoding and know it's better (normal pitch without silence), but I have klicks/scratches in

At 4:37 PM -0400 7/6/01, Brendan Cully wrote: >On Friday, 06 July 2001 at 13:21, tom erbe wrote: >> At 1:48 PM -0400 7/6/01, Brendan Cully wrote: >> > > 0.2 doesn't segfault, but it seems to overrun the server (if that >> >> makes any sense), it plays a 3 minute file in seconds. >> > >> >I'd like to know more about this. Are you

I have got libao up to oggenc and ogg123 working on Mac OS X Public Beta now. I'd like to submit patches, but last time I did, they never got committed by anyone. Who is in charge of committing stuff? Does someone want to nominate themselves to review and commit my patches? The patches are briefly: - On Mac OS X dlopen() is not very well supported, so libao has been cleaned up a bit to

I know you're tired of hearing me complain about ogg123, but this time I noticed that some of the error messages are a bit inconsistant. Also, I noticed that some things (like "Error connecting to server") are fatal errors that kill ogg123, while I think they should simply go on to the next file in the list like "input not an Ogg Vorbis audio stream" does. Another problem

Using the PPC frsqrte and fres instructions, I got the percentage time take in the smoothing code in _vp_compute_mask() down from 13.64% to 1.88% of the running time. In my local copy of Vorbis I have a fast_math.[hc] in vorbis/lib and have a _fast_sqrt() inline in fast_math.h. If anyone else wants to try it out, it follows. I can currently encode my test file (the first 15 seconds of

Depending on what you are broadcasting, for 28.8 I would go 16kbps and be really safe... Lithium ----- Original Message ----- From: "John Griffiths" <john@capmon.com> To: <icecast@xiph.org> Cc: <icecast@xiph.org> Sent: Thursday, April 05, 2001 3:12 PM Subject: [icecast] bitrate for slow modems > ok so 24kbps for 56k modems... > > can i go any lower and get

I have a small feature request for oggenc: Can a command line option be added to allow the user to set the first serial number to be used for the output ogg stream? This only takes a few lines of code, actually. Rationale: it is quite helpful for debugging other encoders. If oggenc is the "reference" encoder, ensuring that your new whiz-bang encoder has diffable output to oggenc is a

Hey. Last night I hacked grip so that it'd allow me to use vorbize and comments with grip. It's very ugly because grip'd need a bit of rearrangement in order to facilitate the way the vorbis comments work (that is, the comments are not added in after the encoded file has been written). Any one who wants to use it should patch grip-2.94 (http://www.nostatic.org/grip), and make sure you

Hi people! I think it would be cool if ogg123 had a mode in which you could conrol it with stdin. pausing, quitting/stopping and seeking would be enough imho. mpg123 already has something like this (I think -e). I'd do it myself but I'm busy. Shouldn't take much time. Bye, Peter Surda (Shurdeek) <surda@bigfoot.com>, ICQ 10236103, +4369910964300 -- The dark ages

Looking at it, I think this patch is actually better than the one I sent before, mainly because it keeps from adding a bunch of weird parameters to functions at the expense of a single global variable (globals... ick). Aaron Plattner <HR NOSHADE> <UL> <LI>text/plain attachment: ogg123.diff.2 </UL> -------------- next part -------------- A non-text attachment was

Here's my latest hack of the current httpstream.c as well as updated resources. Yes, I know it was time that would have been better spent on writing new streaming code from scratch :P <HR NOSHADE> <UL> <LI>application/octet-stream attachment: resource.h </UL> -------------- next part -------------- A non-text attachment was scrubbed... Name: resource.h Type:

I tried to use ogg123 -b to play from a slow HTTP server, and I realized that ogg123 starts to play immediately even if the buffer isn't full, so if it can't read the ogg fast enough it skips, even with a huge buffer. Is this the way it's supposed to work? It seems to me like the buffer shouldn't start playing until it's full. Am I misunderstanding the purpose of having a