Wait a second, ignore my previous post. What happened to this feature? I want to kick listeners who average a datarate over 200. Why would I want to kick my own source? All I'm seeing here is server limit, which seems to be a cap for the whole server, and source avg bitrate limit. I don't have a use...

Oh yeah. That could make a difference if you'd like to sort of screw up some of the stream rippers. I like it lagged.

I'm really curious about the Shoutcast metaint. I never really played with it before. What difference do you think having the higher number in there makes? I just set all 3 of mine to 8192. I hadn't touched it before.

Sorry. Read edit above. The config file on the latest Shoutcast has a strange quirk. My Steamcast runs at http://radio2.j-fan.com:8600. It's relaying localhost:8000. Feel free to check on it anytime. Like I said, with 8192 set as the metaint it's relaying, the Steamcast relay now seems to be working...

Yep, same problem here. It's stuttering and severely lagging behind the local Shoutcast it's relaying. I should mention, I'm not sure if you realize this, but the current release of Shoutcast comes with a different metaint set than 8192, even though it suggests 8192 in the comments. Relaying worked ...

If you run a 128kbps server, don't make the limit 128. With that you're guaranteed everyone will get kicked off. Just set it to keep the people with really bad connections off. From my short experience since this feature was repaired, I recommend setting this to 200 or higher.

Yes it does. Actually, now it has started usually showing the current song title in the directory. Sometimes it doesn't, and I noticed there were other stations showing the same way.

How come my station only displays the station title and genre in bold on the steamcast.com directory? Most stations show the current song playing, but a few don't. It lists what's playing just fine in other directories, and my steamcast server logs the song titles just fine.

Yeah, that was basically my feeling. I don't want to mess up your beta testing. I guess I was just looking for a long-term solution too early, assuming it's a normal problem to have. So do you see this on a lot of people's servers?

Check it out. A peak of 7 listeners on a 5 listener server:

http://radio2.j-fan.com:8600/

If there's a technical reason this is possible, it might be a good idea to change it so that the peak listener number can't exceed the limit under any circumstances. Just an inquiry and a suggestion.

I was checking one of my two Shoutcast servers today, and was horrified to see that the unique listener count was at least 30 below the total count. Does anyone know why this number gets so high? I know that some people might have a shared IP address on a corporate LAN, dormitory, school etc, or eve...

Awesome! If I can get the reporting working with Shoutcast, I will start using Steamcast on all my streams if it's as stable as the current vision. I'm already running a 5-slot relay right now that I'm having no problems with. I love that it lists on all the different directories, and I really appre...

I hope there will be a way to add the support in SAM2. The crossfading in SAM3 is unusable.

SAM2 has a statistics relays feature that allows you to display on your home page how many total listeners (combining all servers) are listening. It's not working with Steamcast. I've tried it in Shoutcast and Icecast mode. Neither works. All it says is "Error parsing XML document. A string lit...

One feature I really use in the Shoutcast config file is the ListenerTimer. I know, I used to think it was stupid, like the rest of you, but now I swear by it. I set mine to an 8 hour limit because that's about as long as I can conceivably imagine a person listening to it in one sitting, barring the...