because I don't know jetcast. Radio Toolbox only supports shoutcast, icecast2 and steamcast at this time.

you have to remember that client connection are subject to high rates of transfer on connect. No I have no timeframe for new releases, I do this in my spare time.

well unfortunately my attention has been towards work as of late. Hopefully soon I can sit down and hammer out a new release.

I may be able to make that optional. I'll look into it.

what is the meta interval for the problematic server?

Steamcast can only relay servers with meta intervals of 8192 or 16384

Any other setting and you get blips, something which I am hammering a solution out to as we speak.

well I certainly don't want you to have to be stuck in such a situation so I would remove it until a new release that has some CPU handling.

well I am certainly not tossing it out, I am just saying that as of right now I do not know where the problem is, I have used FC 4 and all appears well with the latest version of steamcast.

wish I could give you something, if you want you can try to (re)build rh7.3 compatibility libs. That is appearently where the problem lies.

well I have had reports of issues with fedora core 1 machines as well

so it is likely related.

is your fedora core machine a dual processor or Hyper threading machine?

you use SIGUSR1 with the kill command not steamcast.

it's still very untested but to rehash signal SIGUSR1 should do the trick

if you are referring to www.radiotoolbox.com/dir

the problem is windows media doesn't supply us with enough data to make a listing. If you have a shoutcast/icecast/steamcast server you can list that way and it will be just as good.

does winamp load the pls or m3u files?

if so, then delete your session.rtb file and load m3u or pls file again.

it's typically created when you start banning people from the interface.