similar to: ices: Metadata for im_stdinpcm

Hello, I have been unable to install Ices2 on the latest version of Tiger. I have tried two methods: one using DarwinPorts to install, and the other grabbing the source and building it myself. Both seem to exit compilation with the same or similar errors that I don't understand. I am not a C hacker, so I won't be able to solve this myself. All the supporting libs installed just fine

/bin/sh ../libtool --mode=link gcc -I/usr/include/libxml2 -pthread -g -O2 -o ices input.o cfgparse.o stream.o ices.o signals.o im_playlist.o reencode.o encode.o playlist_basic.o im_stdinpcm.o stream_shared.o metadata.o playlist_script.o audio.o resample.o im_oss.o log/libicelog.la timing/libicetiming.la thread/libicethread.la avl/libiceavl.la -lvorbisenc -L/usr/local/lib -lshout -lvorbis

I'm trying to complie ices2.0.1 on a more-or-less stock Fedora 3 installation, and I'm getting the following compiler error (during linking, I think). /bin/sh ../libtool --mode=link gcc -I/usr/include/libxml2 -pthread -g -O2 -o ices input.o cfgparse.o stream.o ices.o signals.o im_playlist.o reencode.o encode.o playlist_basic.o im_stdinpcm.o stream_shared.o metadata.o playlist_script.o

Justin, I'm not a linux guy, or a that well versed on ICES, but, I went thru the code (stream.c) and just kinda nosed around the broadcast part. When we look at distros that this uses, it may be the correct version of the package, but it might actually be a supporting package, like curl or something like that. If you look at the code attached below, it shows there might be some kind of

After reading this posting in the icecast archives (http://www.xiph.org/archives/icecast/3483.html) about setting the stream url in the metadata with ices2, I couldn't see that it actually was possible to set the ice-url anywhere. Please let me know if the attached patch is any use, and if I'm sending it to the right place! (Unix linefeeds). I use it with Peercast. It means you can add

Does this happen at the beginning, or always after 30 seconds, or what? Are you using shout? Are these VBR files? Do you have use_metadata turned on in the icecast config? jack. > I use liveice/icecast on a linux box redhat 6 (2.2.18) and my problem is that the streamed audio gets chopped -on the LAN!!! The audio is encoded in 32kbps and I have a 512kbps/512kbps connection, so it should be

I've tried everything I know how (and a lot I don't) to get ices to compile on this beige G3 ppc box. I've got the latest cvs of libshout and ices. Gentoo linux ppc 1.2-r1, from stage3 tarball. gcc 2.95.3 I've made sure that libshout points to libshout.so.2.0.2. Don't know what else to try. I've got the box here, and I've port-forwarded through my firewall to

On 4/18/05, Jason M. Sullivan <jsullivan@nc.rr.com> wrote: > > I'm trying to complie ices2.0.1 on a more-or-less stock Fedora 3 > installation, and I'm getting the following compiler error (during linking, > I think). > > /bin/sh ../libtool --mode=link gcc -I/usr/include/libxml2 -pthread -g -O2 -o ices input.o cfgparse.o stream.o ices.o signals.o im_playlist.o

I do use metadate since i need people to see the titles. I use livecast in mixer mode. The chopping starts right away I don't use VBR (I commented it out at least). The mp3's are made with XING audiocatalyst (for windows) so I don't really know. Sorry. Arvid ----- Original Message ----- From: Jack Moffitt <jack@icecast.org> To: <icecast@xiph.org> Sent: Tuesday, March 27,

On 2002.12.02 16:08 SwiftBiscuit wrote: > I've just finished a little encoding set and the > following happened: > > 22Khz resampled, q-0.4 encode = ~38kbs = one error at > the beginning only. > > 22Khz resampled, q-0.5 encode = ~37kbs = 6 to 7 sleep > errors in the first second or so, nothing after that. > > 22Khz resampled, q-0.6 encode = ~35kbs = 14 to 15

Hi, I use liveice/icecast on a linux box redhat 6 (2.2.18) and my problem is that the streamed audio gets chopped -on the LAN!!! The audio is encoded in 32kbps and I have a 512kbps/512kbps connection, so it should be enough to stream several connections at once. It sounds just like when a cd gets dirty or scracthed on the back. Anyway, it seems to go away if you can endure the terrible sound for

hiho, i'm quite new to this list , and maybe this is a little out of topic, but i want to announce something related to vorbis. i'm the maintainer of the music_site http://www.killerfish.de and we hardly discuss to use vorbis for our releases. i attached a mail i sended to monty earlier, and he asked me to post it here. here we go. > we use ra / mp3 on our site, BUT we're about to

hiho, i'm quite new to this list , and maybe this is a little out of topic, but i want to announce something related to vorbis. i'm the maintainer of the music_site http://www.killerfish.de and we hardly discuss to use vorbis for our releases. i attached a mail i sended to monty earlier, and he asked me to post it here. here we go. > we use ra / mp3 on our site, BUT we're about to

In format_mp3.c tatic int format_mp3_write_buf_to_client(format_plugin_t *self, client_t *client, unsigned char *buf, int len) { int ret; if(((mp3_state *)self->_state)->metadata) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is always true because previously it did state->metadata = strdup("") in format_mp3_get_plugin(). It causes annoying artifacts in xmms

From reading through the code, I can understand that the parameters are read from the XML config file and stored in the void pointer "data", but if I am writing a new playlist module that needs additional parameters, how would I go about handling adding this to the code? I have a MySQL playlist module written, but I cannot seem to integrate the parameters such that the admin would

I'm trying to wedge an input filter in front of ices (latest nightly from 5/5), and if I'm using the 'stdinpcm' input module, ices segfaults on me after a few seconds. I'm running on FreeBSD-4.8. Here's the relevant section of my config file: <input> <module>stdinpcm</module> <param

Hi Jens, this series removes the revalidate_disk() function, which has been a really odd duck in the last years. The prime reason why most people use it is because it propagates a size change from the gendisk to the block_device structure. But it also calls into the rather ill defined ->revalidate_disk method which is rather useless for the callers. So this adds a new helper to just