search for: shouting

Hi all, Has anyone successfully managed to get icecast2 libshout2 and Shout.pm built under freebsd? o far I've been able to build all of them except for Shout.pm. I would like to migrate from icecast1 however I can't do so until I can get everything built. Here is the error I'm having trying to build Shout.pm from the FreeBSD ports tree. # make cc -c -I/usr/local/include -O -pipe

Hello, All! Sorry for my english, I'am from Ukraine. I trying install Shout 2.0.1 module on my server: # perl Makefile.PL Checking if your kit is complete... Looks good Writing Makefile for Shout # make cp example2.pl blib/lib/example2.pl cp example.pl blib/lib/example.pl cp Shout.pm blib/lib/Shout.pm AutoSplitting blib/lib/Shout.pm (blib/lib/auto/Shout) /usr/bin/perl

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:

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

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

And more importantly (for me) - Can I ask question about Shout.pm? <p>Anders Jensen System devel. Cybercity.dk, OSS projektet ---- <erno> hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is. Sig. provided by www.bash.org --- >8 ---- List archives: http://www.xiph.org/archives/

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>

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

Hi Zenon, It seems likely to me that you still have libshout 1.x installed. Try stripping all remnants of libshout out from /usr/(local/)include and /usr/(local/)lib and then (re)install libshout 2.0, downloadable from http://downloads.us.xiph.org/releases/libshout/libshout-2.0.tar.gz (NB: this in turn requires libogg and libvorbis.) -- J. Zenon Panoussis wrote: > > Hi > >

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,

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

> 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

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

-----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

I've spent three days tracking this bug down.. I have yet to find how to fix it in the code, tho I do have a workaround which proves the nature of the bug. Sorry for the somewhat-overkill nature of explaining this bug, but some people have been doubting it so I'm going to give the evidence nessesary to prove the nature of it. If you send page-aligned data to libshout (via shout_send) it

I've spent three days tracking this bug down.. I have yet to find how to fix it in the code, tho I do have a workaround which proves the nature of the bug. Sorry for the somewhat-overkill nature of explaining this bug, but some people have been doubting it so I'm going to give the evidence nessesary to prove the nature of it. If you send page-aligned data to libshout (via shout_send) it

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

> geoff@bumpy:src$ grep -ine shout_strerror stream.c > 151: shout_strerror(sdsc->conn.error)); > 185: shout_strerror(sdsc->conn.error)); > 208: shout_strerror(sdsc->conn.error)); > > all of these generated errors. Those are correct. Now what does your $prefix/include/shout/shout.h have? Also, I bet you that it's

Hello, Sorry but in the mails I have read I did not see any "shout" program comments. I have configured icecast and I am using "shout" to encode MP3s. Is the performance of shout bad or others are better then "shout"? I did not encounter any problems yet. Thank you for any comment. Tamer Demir At 12:10 15.01.2002 +0100, Maarten Stolte wrote: >Hello, >

> Well, I tried that, but it made no difference. I didn't see it show up in > Makefile either. I did note however that --with-shout-prefix is correctly > setting SHOUT-CFLAGS to -I/usr2/friends/geoff/include which I thought would > have been sufficient. THe problem is that hte standard include paths are searched first. I'm not sure if there is a way to get around this.