search for: shout_set_host

Displaying 5 results from an estimated 5 matches for "shout_set_host".

2004 Aug 06
1
can't compile ices 2 on ppc
...shout_set_format' stream.o(.text+0x9c): relocation truncated to fit: R_PPC_REL24 shout_set_format stream.o(.text+0xac): undefined reference to `shout_set_protocol' stream.o(.text+0xac): relocation truncated to fit: R_PPC_REL24 shout_set_protocol stream.o(.text+0xc8): undefined reference to `shout_set_host' stream.o(.text+0xc8): relocation truncated to fit: R_PPC_REL24 shout_set_host stream.o(.text+0xe4): undefined reference to `shout_get_error' stream.o(.text+0xe4): relocation truncated to fit: R_PPC_REL24 shout_get_error stream.o(.text+0x120): undefined reference to `shout_set_port' str...
2006 Jan 12
0
libshout and mp3 streaming?
Hi List, i have a problem streaming mp3's to the icecast server via libshout-2.1. Everything works fine as long as i send ogg's to the icecast server. libshout as well as icecast do not report any errors. what might be the problem? my code looks like this: shout_init() shout_set_host(...) shout_set_password(...) shout_set_mount(...) shout_open() shout_set_format(...) while( !feof(infile) ) { shout_delay(...) shout_send(...) } i noticed that when sending ogg's shout_delay() does delay the sending .. but with mp3 files it doesnt - the whole file gets streamed to t...
2014 Nov 17
2
hostname resolution in libshout
...ug/1391654 They say their hostname resolves to both ipv4 and ipv6 and they bound icecast to the ipv4 interfaces. (I'm not sure why they don't bind to both). Mixxx cannot connect to icecast presumably because libshout is resolving and connecting to the ipv6 address. We do nothing but call shout_set_host with the user-provided host string. They are requesting that libshout "fall back" on the ipv4 resolution of the hostname if the ipv6 version fails to connect. Two questions: 1) Is this intended behavior that isn't working? 2) Is this desired behavior to have within libshout? (i.e. a...
2008 Sep 10
2
Updated version of patch
...priate locking around accesses to s->conn. It is a little hard to figure out precisely at what places locking would be needed. The safest method I could think off is simply to include thread safe versions of the shout api functions which have a shout_t as its first argument. For example int shout_set_host_safe_ts(shout_t *self, char* host, pthread_mutex_t *mutex){ int ret; pthread_mutex_lock (mutex)); ret=shout_set_host(s->conn,host); pthread_mutex_unlock (mutex)); return ret; } One should then use the thread safe version instead of the original api functions. To avoid mistakes I wo...
2008 Aug 30
3
Updated version of patch
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