search for: liblam

...installed libxml-1.8.11 but when I start up IceS, it says something about the namespace. So I tried compiling libxml2 but that, for some reason, doesn't compile on my machine. 2. I cannot get the reencoding to work. I have compiled lame3.70 and installed but IceS still says it can't find liblame. Is it not included in lame3.70 tar file? If not, where can I get it? Thanks in advance. == spark21c@yahoo.com ===== ¹Ú»óÁØ - Sangjune Park spark21c@yahoo.com --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from th...

...I have completed some from-git install documentation, available here: http://revis.co.uk/site/?q=node/157 I'll generalise it, transfer it to the wiki and tidy up the installation page shortly. Installation issues: The configure script seems to have a small glitch in that for the packages liblame-dev libxvidcore4-dev libx264-dev libfaac-dev libfaad2-dev it detects only that the library is installed and *not* the headers required to build. Eg if liblame is installed configure will complete, however make will bug out until liblame-dev is installed. Not sure if this is working as intended...

...ault install variables. The last one I compiled was lame3.87. I then have the ices-0.0.1.beta5 and config'd the sources with ./configure --with-perl --with-lame and installed. Yet, when I run ices -R, it complains with the following line when I run the -R option: Support for reencoding with liblame was not found. You can't reencode this. Yikes! It's right there and I didn't note any documentation regarding this error...so I assume this is new? What am I doing wrong? Thanks for your thoughts. Ryan Sayre -- ryan@tron-thorpe.com ** Ryan Sayre ** Systems Engineer -- Oregon Tro...

Hello everyone, Few weeks ago I tuned icecast with 7 streams from ices. It plays static playlists, sorted by genre. I have 2 problems. First problem: pure quality when reencoding is turned on. Temporary solution was found. I added one string, to reencoding code, that points to liblame use better quality. But is this the one and right solution? Second problem: Ices (or liblame?) does not properly closes played mp3's... Few days and the limit of kern.maxfiles is exhausted. How to fix this problem? PS: System is FreeBSD 5.3 -- Yours, Victor mailto:...

...I am trying to install Rmpi on 64-bit HP-Proliant server. I am facing the following error: * Installing *source* package 'Rmpi' ... Try to find mpi.h ... Found in /usr/local/mpich-1.2.7p1/include Try to find libmpi or libmpich ... Found libmpich in /usr/local/mpich-1.2.7p1/lib Try to find liblam ... checking for main in -llam... no liblam not found. Probably not LAM-MPI checking for openpty in -lutil... no checking for main in -lpthread... no configure: creating ./config.status config.status: creating src/Makevars ** libs gcc -I/usr/local/lib64/R/include -I/usr/local/lib64/R/include -DPACK...

...#39;on the fly'? I'm thinking of having a live stream (through darkice), with the title, author, etc. metadata changed every once in a while to reflect the actual program. How would I do that? Should I insert such data into the mp3 / ogg voribs data somehow by calling some functions of liblame / libvorbis? Or is there some possibility to do this through the protocol with which the data is sent to icecast? At the moment, the only place I put meta data into is when the source logs in to the icecast server. There, in the header, there is a possibility to put metadata. But this persist...

To all users: The recently exploits announced at bugtraq can be fixed by the following patch. This patch should fix a few other potential holes as well, and I will post a followup patch soon that is even more thorough. Note: this exploit would give the attacker priviledges of the user running icecast. If you are running icecast as a normal user account or as root, this would be a good time to

To all users: The recently exploits announced at bugtraq can be fixed by the following patch. This patch should fix a few other potential holes as well, and I will post a followup patch soon that is even more thorough. Note: this exploit would give the attacker priviledges of the user running icecast. If you are running icecast as a normal user account or as root, this would be a good time to

...sfully , except for using lame.h , i for the life of me , can not get it to include it , no matter what version ( i have tried from 3.66 to 3.70 ) and can not get it to include it. ( heh i started using 2.* series and have not figured out it is not included :P. The other issue i find i hear about liblame , hense i can not find it anywhere. when ./configure --with-lame-includes=/usr/include/lame , the lame.h is there as with most of the versions above 3.66 hense it will not include it if it life depends on it ( or mine ) I tried streaming with out lame and it is choppy as all hell, so i am guess...

...much luck with LiveIce staying > alive either... I had a silly cron script running to check if it was alive > and bring it back up again! > > I switched to Darkice about 2 months ago and the stream has been rock solid. > This on a linux box running 2.4.14 kernel. Darkice uses liblame without > spawning lame externally and, in my opinion, is much more straight forward in > it's configuration. Check it out: http://darkice.sourceforge.net It's the same for me: 2 months with liveice + cron and now DarkICE ... alive and kicking from fLORENCE/italy :) -- GHERd...

...icecast server? We are using Darkice on FreeBSD. Works GREAT (still stuck running old version because the new one bombed on compilation, but NO COMPLAINTS!) I'm assuming this would fall in Darkice's hands because from what I gather it reads the pcm audio device and just passes the data to liblame. So if it read the PCM data in stereo and then split left and right and called two instances of liblame... ???? Is it a possibility? It would make my life SO much easier. We are trying to put 12 sound cards each into two systems to support 24 audio streams... it would cut the number down to 6, o...

I am trying to build Rmpi on Suse 10.2 linux. While I would like to use the RPM version of liblam-7.1.2, I have not been able to do so. It seems that Rmpi makes some pretty strong assumptions when trying to guess the MPI version. Has anyone successfully built Rmpi against lam-7.1.2 recently using R-2.6.0? If so, can you give some pointers about where the libraries and header files need to be...

...ce on > FreeBSD. Works GREAT (still stuck running old version because the new one > bombed on compilation, but NO COMPLAINTS!) thanks > > I'm assuming this would fall in Darkice's hands because from what I > gather it reads the pcm audio device and just passes the data to liblame. > So if it read the PCM data in stereo and then split left and right and > called two instances of liblame... ???? > > Is it a possibility? It would make my life SO much easier. We are trying > to put 12 sound cards each into two systems to support 24 audio streams... > it wou...

Greeting all -- I'm having some problems setting up multiple streams with iceS, for example, a hi-bandwidth and lo-bandwidth stream of the same audio. Could someone post a config that works in this case? thanks .oOo.oOo.o..o.oOo.oOo. Ben Wilson admin -- thelocust.org ben@thelocust.org 'OoO'OoO'O''O'OoO'OoO' --- >8 ---- List archives:

Dear R Gurus: Is there a problem with Rmpi on x86 with SUSE 10.1, please? I've tried everything and it still won't load. Has anyone else dealt with this please? Thanks, Edna Bell

...s checking whether gcc -std=gnu99 accepts -g... yes checking for gcc -std=gnu99 option to accept ISO C89... none needed I am here /usr/lib/lam and it is LAM Trying to find mpi.h ... Found in /usr/lib/lam/include Trying to find libmpi.so or libmpich.a ... Found libmpi in /usr/lib/lam/lib Try to find liblam.so ... Found liblam in /usr/lib/lam/lib checking for openpty in -lutil... yes checking for main in -lpthread... yes configure: creating ./config.status config.status: creating src/Makevars ** libs gcc -std=gnu99 -I/home/bs/R_home/R-2.11.1/include -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\&qu...

...:~/Rmpi # R CMD INSTALL /home/hfuss/build/Rmpi_0.5-3.tar.gz --configure-args=--with-mpi=/usr/local/lam-mpi * Installing *source* package 'Rmpi' ... Try to find mpi.h ... Found in /usr/local/lam-mpi/include Try to find libmpi or libmpich ... Found libmpi in /usr/local/lam-mpi/lib Try to find liblam ... Found liblam in /usr/local/lam-mpi/lib checking for openpty in -lutil... no checking for main in -lpthread... no configure: creating ./config.status config.status: creating src/Makevars ** libs gcc -I/usr/local/lib/R/include -I/usr/local/lib/R/include -DPACKAGE_NAME=\"\" -DPACKAGE_TAR...

...ing whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed Try to find mpi.h ... Found in /import/home/u1/uaf/ogorman/lam/include Try to find libmpi.so or libmpich.a checking for main in -lmpi... yes Try to find liblam.so ... checking for main in -llam... yes checking for openpty in -lutil... yes checking for main in -lpthread... yes configure: creating ./config.status config.status: creating src/Makevars ** libs gcc -std=gnu99 -I/usr/local/pkg/r/r-2.6.1/lib64/R/include -I/usr/local/pkg/r/r-2.6.1/lib64/R/include...

...--> <Public>1</Public> <!-- Stream bitrate, used to specify bitrate if reencoding, otherwise just used for display on yp and on the server. Try to keep it accurate --> <Bitrate>96</Bitrate> <!-- If this is set to 1, and ices is compiled with liblame support, ices will reencode the stream on the fly to the stream bitrate. --> <Reencode>0</Reencode> <!-- Number of channels to reencode to, 1 for mono or 2 for stereo --> <Channels>2</Channels> </Stream> <Stream> <Server>...

Hello. We have been using LiveIce to serve mp3 streams for 10 months or so. So far, IceCast has been pretty reliable. Well, until LiveIce is introduced into the picture. We originally tried LiveIce running on FreeBSD. It ran for a while, but we suffered wierd problems: disconnects, skips and such. We are streaming from a radio receiver -- at 28800 compatible bitrates. So we switched to the