| Summary: | ICECast / Shoutcast title streaming | ||
|---|---|---|---|
| Product: | [Unmaintained] noatun | Reporter: | Ingo Heeskens <ingo> |
| Component: | general | Assignee: | Charles Samuels <charles> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | landrews |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Ingo Heeskens
2003-01-26 13:51:20 UTC
I've got a semi working approach here, it won't make it into KDE 3.2 though. First: It is great that someone is working on the problem. But what i can really not understand is that there are working implementions since long e.g. xmms. Is it that hard to addapt such code? Subject: Re: ICECast / Shoutcast title streaming Its like writing a love-story: There are a lot of stories allready written but adapting one for your own is a lot of work! Afaik xmms for example is written in C while KDE is completly C++. Thats two different languages. xmms has a totally different internal structure than KDE and aRts... Arnold look at amarok! (kdenonbeta/amarok). we solved this by a arts-proxy, which extracts the data out of the stream for our mediaplayer. works and is a seperate module anyone can use. regards, muesli muesli: didn't Markey tell you that the semi-working approach is your proxy? ;) It just didn't fit into the Noatun API at all and has bugs when the other side dies (i.e. listening port being kept open, very annoying), not to say that I'd never ever commit this for 3.2 because of both a feature freeze and the high probability of introducing buggy code (just because it works here doesn't mean it works perfectly for others too). Subject: Re: ICECast / Shoutcast title streaming
On Friday 02 January 2004 7:32 am, Stefan Gehn wrote:
> muesli: didn't Markey tell you that the semi-working approach is your
> proxy? ;) It just didn't fit into the Noatun API at all and has bugs when
> the other side dies (i.e. listening port being kept open, very annoying),
> not to say that I'd never ever commit this for 3.2 because of both a
> feature freeze and the high probability of introducing buggy code (just
> because it works here doesn't mean it works perfectly for others too).
Ryan 'Phalynx' Cumming created a similar device, which I've never [tried]
using.
It did work.
rikkus said his implementation of the icecast hinting wasn't too good.
This should definitely be added to noatun, but I can't see how we could
reasonably get it in for 3.2, aside from a plugin at noatun.k.o when we're
more certain of it.
Maybe a distribution that puts broken stuff will include it like how Red Hat
included a broken fork(2).
- -Charles
I'll try to move my code in for KDE 3.3 and provide a patch for KDE 3.2.x installs (will put it up on noatun.kde.org). CVS commit by metz: Yes, this is the one most people probably waited for :) Now you can see shoutcast titles and servernames in Noatun. FEATURE: 53439 A titleproxy.cpp 1.1 [GPL (v2+)] A titleproxy.h 1.1 [GPL (v2+)] M +1 -1 Makefile.am 1.84 M +31 -18 engine.cpp 1.98 M +45 -9 player.cpp 1.88 M +12 -3 noatun/engine.h 1.4 M +5 -0 noatun/player.h 1.9 |