Hello all, I'm quit new to icecast, but I have project dealing with streaming (currently only audio) for web radio, and I would love to use the icecast protocol as it already has everything I need. But, In order to be usable for us, we need to be able to 'embed' the icecast server (in a dll or statically) in our program, and control it programatically. We need his to reconfigure the relays using a bandwidth distribution algorithm. We only need the relaying feature, the first server would be a 'normal' icecast, and the final clients would be normal clients (Winamp ...) How easy this coule be done ? I see no dev docs on the site dealing with an Icecast's API, suggesting it hasn't been developped with these kind of usage in mind. Thanks for your time, Regards.
On Wed, 2004-07-28 at 14:11, o.brunet@free.fr wrote: ...> But, In order to be usable for us, we need to be able to 'embed' the icecast > server (in a dll or statically) in our program, and control it programatically. > We need his to reconfigure the relays using a bandwidth distribution algorithm. > > We only need the relaying feature, the first server would be a 'normal' icecast, > and the final clients would be normal clients (Winamp ...)updating of relays is better handled in the trunk code, triggered by the HUP signal. The API is web based, ie /admin/..... and while some functionality may not be available it is improving but if something is missing that you think is important then let us know. karl.
<1091044174.1286.391.camel@bogus.hackers.club> Message-ID: <1091094541.4108c80d8695c@imp5-q.free.fr>> > We only need the relaying feature, the first server would be a 'normal' > icecast, > > and the final clients would be normal clients (Winamp ...) > > updating of relays is better handled in the trunk code, triggered by the > HUP signal. The API is web based, ie /admin/..... and while some > functionality may not be available it is improving but if something is > missing that you think is important then let us know.It's not a matter of completness here, but web interface, even through XML, is not really something very efficient if we want to embed icecast in another product. We need plain C/C++ calls. We are currently looking at source code to see wether easy or not it is. Regards,
<1091044174.1286.391.camel@bogus.hackers.club> <1091094541.4108c80d8695c@imp5-q.free.fr> Message-ID: <1091101478.11394.5.camel@bogus.hackers.club> On Thu, 2004-07-29 at 10:49, o.brunet@free.fr wrote:> > > We only need the relaying feature, the first server would be a 'normal' > > icecast, > > > and the final clients would be normal clients (Winamp ...) > > > > updating of relays is better handled in the trunk code, triggered by the > > HUP signal. The API is web based, ie /admin/..... and while some > > functionality may not be available it is improving but if something is > > missing that you think is important then let us know. > > It's not a matter of completness here, but web interface, even through XML, is > not really something very efficient if we want to embed icecast in another > product. We need plain C/C++ calls.what sort of API call is going to require something more efficient than the current URL based mechanism. The most frequent of the current ones in use is mp3 metadata updates> We are currently looking at source code to see wether easy or not it is.it's certainly possible, assuming licence considerations are handled karl.
<1091044174.1286.391.camel@bogus.hackers.club> <1091094541.4108c80d8695c@imp5-q.free.fr> <1091101478.11394.5.camel@bogus.hackers.club> Message-ID: <20040729151754.GB30565@xiph.org> On Thu, Jul 29, 2004 at 12:44:38PM +0100, Karl Heyes wrote:> > > > It's not a matter of completness here, but web interface, even through XML, is > > not really something very efficient if we want to embed icecast in another > > product. We need plain C/C++ calls.I think it needs to be pointed out that Icecast isn't this uber-complex system. An ultralight embedded stream server could be written in a matter of days which preforms Icecast's most core functions without the web interface, MP3 support, etc. I'll argue that such a server could be designed as part of Icecast, but several things need to change first such as switching to libogg2.