Displaying 20 results from an estimated 2000 matches similar to: "ideas for on-demand streaming"
2004 Aug 06
0
ideas for on-demand streaming
How do I submit an email to icecast?
-----Original Message-----
From: Gary Major [mailto:gr_major@hotmail.com]
Sent: Wednesday, February 20, 2002 1:34 PM
To: icecast@xiph.org
Subject: Re: [icecast] ideas for on-demand streaming
<p>What you could do, if you were so inclined, is to write a shell script that
would cycle through your directories and create symbolic links in your main
2004 Aug 06
0
ideas for on-demand streaming
What you could do, if you were so inclined, is to write a shell script that
would cycle through your directories and create symbolic links in your main
directory. Not pretty at all, but would solve your issue.
Alternatively, a script could be written to cycle through your directories
to create a custom web page to display ALL songs. A little prettier and
again would solve your issue.
My script
2004 Aug 06
2
ideas for on-demand streaming
On Wed, 20 Feb 2002, Gary Major wrote:
> To define this list you put the full path to your mp3 directory in your
> icecast.conf file. It has been awhile since I set this up, and I forget the
> exact option, although static template comes to mind.
This is great... but it's not showing a full listing of what's in my
directory. My MP3 collection is housed in /music/. There are
2004 Aug 06
3
ideas for on-demand streaming
hey folks,
i'm setting up an archive of mp3s and need to get an on-demand streaming
solution up.
i've got icecast running well and the streaming is great. the thing is that i
need to let folks click a link and start listening from the beginning of an
audio file. seems like i could script something to start up a new stream for
each user and serve them up a unique url, but that seems a
2004 Aug 06
4
Stuttering stream
On Wed, 6 Feb 2002, Jack Moffitt wrote:
> ices is built on libshout. libshout should have perfect timing and it
> also detects and discards corrupt frames and supports VBR streams. It
> is basically the _new_ version of shout.
ices refuses to load. It whines about libmp3lame.so.0 being missing. I
found the message in the archives that supposedly forces ices to compile
with lame
2004 Aug 06
3
"Bind to socket failed"
I'm running RedHat 7.2 (kernel 2.4.17) on a PII 300. I'm using Liveice
with XMMS. I had no problem broadcasting with Shoutcast and Winamp back
before I switched over to Linux. I'd love to get going on broadcasting...
but Icecast refusing to open is a problem.
Running icecast gives me the following.
Starting thread engine...
[04/Feb/2002:13:57:38] Icecast Version 1.3.10 Starting..
2004 Aug 06
3
Stuttering stream
I'm using shout 0.8.0, icecast 1.3.10 on Redhat 7.2.
My stream skips all over the place. I can't even get through one song
without having to restart the stream or having icecast boot me. Most of my
MP3s are 128kbps, and that's the default bitrate in shout. I've turned on
autocorrect and force bitrate, but it still skips. Autocorrect seems to
make the time between skipping a bit
2004 Aug 06
0
Stuttering stream
On Wed, 6 Feb 2002, Jack Moffitt wrote:
> THen I suggest you start to look elsewhere for your problem. libshout
> is quite well tested and every time someone has thought it was skipping,
> it turned out to be NTP chaning their clock or a slow harddrive or
> something similar.
I'm saying "Here's this problem I'm having, how do I fix it?" I don't care
if the
2004 Aug 06
0
Stuttering stream
On Wed, 6 Feb 2002, Jack Moffitt wrote:
> > A good number have id3v2 tags... say 20-30%.
>
> Do you find that it's stuttering on id3v2 files? Since those contain
> data that is counted by the timing code, but not played the the player,
> that seems a likely suspect. Ie, you'll get _playable_ data too slow.
I replaced my normal playlist with a much smaller one of files
2004 Aug 06
1
Artificially high bandwidth?
(By the way, upgrading to .11 seemed to take care of the skipping.
Thanks!)
The stream seems to be working just fine, although Winamp is showing
bandwidth at 130 or higher, occasionally up to 145 or so. Most of my MP3s
are 128 kbps, and ices should be re-encoding everything as 128 anyway.
This is really a minor issue... but I'm wondering what could be taking up
the extra bandwidth? Or
2004 Aug 06
2
"Bind to socket failed"
On Mon, 4 Feb 2002, Jack Moffitt wrote:
> > I'm running RedHat 7.2 (kernel 2.4.17) on a PII 300. I'm using Liveice
> > with XMMS. I had no problem broadcasting with Shoutcast and Winamp back
> > before I switched over to Linux. I'd love to get going on broadcasting...
> > but Icecast refusing to open is a problem.
>
> Did you use the hostname parameter in
2004 Aug 06
0
Newbie question - on demand streaming?
> Well, a number of reasons. Dedicated streamers are better at streaming
> audio/video than webservers,
In theory. In practice this is not true. Apache is far more robust
than any streaming server I've seen yet, and far more stable. Many of
the scaling issues have been addressed, and the drawbacks are minimal.
Streaming servers should be better for two reaosns. 1) they can be more
2004 Aug 06
1
Downsampling mp3 on-demand streams
Hello,
We're streaming radio programs at both 128kbsp and 32kbps, but only
archiving the 128kbps stream to save storage space. I'd like to give users
a similar choice of bitrates when they request an archived stream (served
through icecast's /file/ functionality). Is there a way to change the
bitrate on the fly, or do I really need to save archive both bitrates?
Thanks for the
2004 Aug 06
0
[shout/icecast] problem streaming
hello folks,
i had a problem with streaming on icecast.
Version 1.3.10 / shout 0.8.0
the server startet successful , and shout is eatblish an stream on localhost
port 8001. if an client read the stream via winamp on a windows machine in
the lan , then is there in the first 10 sec anything ok, but after this time
is the permanently drops for one sec
the mp3 files are in diferent bitrates , most of
2004 Aug 06
2
Stuttering stream
> A good number have id3v2 tags... say 20-30%.
Do you find that it's stuttering on id3v2 files? Since those contain
data that is counted by the timing code, but not played the the player,
that seems a likely suspect. Ie, you'll get _playable_ data too slow.
Try a stream with _no_ id3v2 files and see if the problem persists.
> > What version of linux? glibc?
>
> RH 7.2
2005 May 06
2
Static file directory
To All
In icecast-1.3.12 the conf file has Static file directory. I'm upgrading
to icecast-2.2.0, can you set the static file directory in icecast 2.2.0
xml file? If so how is it done?
# less /opt/icecast-1.3.12/etc/icecast.conf
###################### Static file directory
##################################
# This enables the http-server file streaming support in icecast.
# If you
2004 Aug 06
0
ideas for on-demand streaming
You can still do this from icecast as icecast can be a rudimentary http
streamer. If you enter the following: http://your.url.com:8000/list.cgi this
will popup a page that will detail some status info about your icecast
server. About half way down, there should be a link pointing you to a
listing of the current mp3 files that are available via http (need to define
this list). Click on this link
2004 Aug 06
0
stream sounds like poo for no apparent reason
This does sound like a grounding problem. My (limited) understanding is that when you have 2 audio components plugged in to different outlets, there can be a voltage differential between the ground on the 2 devices, which will create an electrical flow between the 2 components, which is the source of the hum. I have had this problem before and solved with a ground loop isolator, (from Radio Shack)
2004 Aug 06
0
stream sounds like poo for no apparent reason
Sorry, here is a link to more information.
http://www.epanorama.net/documents/groundloop/index.html
-----Original Message-----
From: Benninghoff, John
Sent: Wednesday, April 24, 2002 2:28 PM
To: 'icecast@xiph.org'
Subject: RE: [icecast] stream sounds like poo for no apparent reason
<p>This does sound like a grounding problem. My (limited) understanding is that when you have 2
2004 Aug 06
3
Stuttering stream
Expanding on Jack's note.
In a default lame install, the lame library in in /usr/local/lib which is
not in the 'trusted' library directories, hence why the linker/loader can't
find it. What you need to do to fix it (as root), is open up /etc/ld.so.conf
and add /usr/local/lib to the file. This file just contains various paths
that will be searched in addition to /usr/lib & /lib