similar to: about the working scenario

Shouldn't audio-on-demand be served through the staticdir variable in your icecast.conf. ----- Original Message ----- From: "Liu Wen" <ragent@gnuchina.org> To: <icecast@xiph.org> Sent: 14. detsember 2001. A. 14:01 Subject: [icecast] about the working scenario hi,I did not have any prior experience with broadcasting mp3 stream. I am really confused with the working

can anybody explain to me the mountpoint that is mentioned by icecast version 1.3.12? I see that the mountpoint is /default what does this mean and how can I change it in the icecast.conf file. I am running this on a freebsd 4.7 STABLE release. - Noah <p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from

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

David Dennis wrote: > welcome to the list. > > Check the archives. > > There you will find about one newbie a month minimum discovering that the > widely distributed and still available shout package version 0.8.0 > is actually deprecated and highly broken in exactly the manner you > describe. > > Thanks but one point I can make is I get the same results when not

Hi there, that really seems to be the issue here. I've quickly created a new sdist package for python-shout and installed it with the diff applied into my virtual environment and the broadcasting seems to work just fine again. So I can confirm this to solve the issue. Hopefully they accept Bug Fixes fast so everyone could profit from this. Thanks On Mon, Jul 21, 2014 at 2:49 PM,

Hi there, I am trying to use python-shout 0.2.1 to broadcast to a icecast 2.4.0 server, which result in a segmentation fault and I can't understand why. Is anyone else experiencing this problem? Here is the config that I use with icecast 2.4.0. <icecast> <limits> <clients>100</clients> <sources>2</sources>

Hi Running ./configure --prefix=/whatever I got stuck with checking for pkg-config... /usr/bin/pkg-config checking shout/shout.h usability... no checking shout/shout.h presence... no checking for shout/shout.h... no configure: error: must have libshout installed! Having edited configure line 20056 and changed shout/shout.h to /usr/include/shout.h , I run into the next problem:

Hi - got this from both the CVS source and the tarball: (libshout compiled and installed cleanly) [root@hunter stream]# cd Shout-1.0 [root@hunter Shout-1.0]# perl Makefile.PL Checking if your kit is complete... Looks good Writing Makefile for Shout [root@hunter Shout-1.0]# make mkdir blib mkdir blib/lib mkdir blib/arch mkdir blib/arch/auto mkdir blib/arch/auto/Shout mkdir blib/lib/auto mkdir

At 13:44 31-10-2002, Michael Smith declared: >At 01:18 PM 31/10/2002 +0100, you wrote: > >And more importantly (for me) - Can I ask question about Shout.pm? >Yes. And yes, you can ask questions, but you should just do so - not >waste time asking if you can do so. This doesn't (either way) guarantee >anyone will be able to give you useful answers, but you should try

> Karl just pointed out to me that libshout is now installing its header > in $prefix/include/shout.h instead of $prefix/include/shout/shout.h. (Sorry for not replying directly, I'm not on the list and I can't figure out if gmane allows me to reply to a mail.) It's probably best to try and contact the committer first - It's possible few other people understand or care

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

Jeremy Bierbach wrote: Hi Jeremy > It seems likely to me that you still have libshout 1.x installed. No, it's not that. # rpm -q libshout libshout-2.0-1.dag # rpm -q libshout-devel libshout-devel-2.0-1.dag It's the half-hard-coded shout/shout.h path in the source. Since libshout is installed by rpm in /usr/include, the path will never match. Even if

libshout 2.0 install its header file in /usr/include, whereas ices looks for /usr/include/shout/shout.h. Either one or the other should get fixed. [guillomovitch@klama guillomovitch]$ rpm -ql libshout3-devel | grep .h$ /usr/include/shout.h [guillomovitch@klama guillomovitch]$ rpm -ba rpm/SPECS/ices.spec [..] checking shout/shout.h usability... no checking shout/shout.h presence... no checking

Attached is a patch against shout-python-0.2 which does two trivial but very useful things (1) The function "get_connected" is exported so that shout-python becomes usable in nonblocking mode. In the current version of shout-python "open" raises an exception in nonblocking mode. (2) The global interpreter lock is released in the potentially blocking functions

Hi, Another basic question (the list archive search doesn't seem to be working). Is it possible to do scripted playlists with shout? I want to allow the people at my site to upload new mp3 files to the server and have them placed in the playlist automatically. I tried generating the playlist (file) with crontab, but it seems shout only reads the playlist once, at startup. I

thnks for the clarfication. I downloaded libshout2 and ices-0.2 from cvs. I compiled libshout with out a problem but when i try and compile ices I get the following error: <p><p>checking whether to build shared libraries... yes checking whether to build static libraries... yes checking whether -lc should be explicitly linked in... no checking shout/shout.h usability... yes checking

Hi all, I've just released libshout 2.0. This is the official release, not a beta. Thanks to all the testers who provided feedback during the beta period. http://icecast.org/files/libshout/libshout-2.0.tar.gz Libshout 2.0 adds support for icecast 2, Ogg streaming, and IPv6, as well as bug fixes relative to libshout 1. Ogg and Vorbis are now prerequisites. Changes since beta 3: * Minor

Hi all, I've just released libshout 2.0. This is the official release, not a beta. Thanks to all the testers who provided feedback during the beta period. http://icecast.org/files/libshout/libshout-2.0.tar.gz Libshout 2.0 adds support for icecast 2, Ogg streaming, and IPv6, as well as bug fixes relative to libshout 1. Ogg and Vorbis are now prerequisites. Changes since beta 3: * Minor

> Hey there again > > On Wed, Feb 28, 2001 at 12:16:12PM +0100, Thomas Vander Stichele wrote: > > > > The tests I've done in-house were with winamp as a client, and the > > following server/streamer combinations : > > icecast 1.3.0/shout 0.8.0 > > icecast 1.3.7/shout 0.8.0 > > icecast 1.3.8b2/shout 0.8.0 I don't know what it is that causes

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 These patches to libshout and shout.m4 reduce the level of self-hatred significantly. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRX7anAAoJEOs4Jb6SI2Cw2VgH/RDFPJjXdds1Cq3c0QyVyWs4 JWhPw2SI4vNGHF6U2q/DJQeBtsyY5BiUGckdew8skR5q0qc3D7iqBG5kiSC+G3Aq