Icecast - Aug 2004 - winamp shout

i am using icecast v1.3.11

my friend streams music to my server with the shout plugin for winamp.  
there are a couple of problems.

1. icecast doesn't seem to recognize when a client disconnects.  i enabled
the shoutcast and icecast directory servers, and they were both saying that i
had around 400 listeners last night, when in fact i only had 8.  the only lines
in the icecast configuration file that seem to have anything to do with managing
client connections are set like this:

########################### Client Timeout ####################################
# (How to deal with clients when no encoder is connected)
# A negative value means keep them forever
# 0 (zero) means kick them out instantly
# X > 0 means keep them X seconds
###########################

client_timeout 0

######################### Kicking clients #####################################
# If set to 1, then clients whose source has disconnected will
# be kicked. If set to 0, they will simply be moved to another
# stream. This only has an effect if client_timeout is <= 0.
#########################

kick_clients 1

has anybody else had this problem, or know how to fix it?

2. this shoutcast streamer seems to send the meta data and actual audio stream
to random mountpoints.  usually it's icy_0/icy_1, but sometimes icecast will
refuse the encoder saying "invalid mountpoint".  there don't seem
to be any obvious configuration options on this streamer.  my meta data options
are set like this:

########################## Stream Meta Data
##################################### This is a experimental feature, at best.
# When it does not work, it will put the whole stream out of synk on the client
# side, and you will get a big mess.
# use_meta_data controls whether this icecast server will use title streaming
at#               all. It's turned off by default, cause it creates chirps
in the
#               stream if you're not careful.
# streamtitletemplate is a the template for creating the title that gets sent
to#                     the client and the directory server. %s will be
#                     substituted for the actual filename.
# streamurl is the default url for each stream.
# nametemplate is a template for the name of each stream.
# desctemplate is a template for the description of each stream.
##########################
use_meta_data 1
streamurllock 0
streamtitletemplate %s
streamurl http://radio.celloboy.net
nametemplate %s
desctemplate %s

i used to have use_meta_data set to 0, but i set it to 1 hoping it would clean
this up a bit.  does anybody know what's going on?

thanks for your help,
ryan

--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
'icecast-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

> 
> 1. icecast doesn't seem to recognize when a client disconnects.  i
enabled the shoutcast and icecast directory servers, and they were both saying
that i had around 400 listeners last night, when in fact i only had 8.  the only
lines in the icecast configuration file that seem to have anything to do with
managing client connections are set like this:
Could be a bug in icecast, though I wouldn't think so.  I would keep
kick_clients at it's default value, in case there is a bug with
non-standard values.
> 2. this shoutcast streamer seems to send the meta data and actual audio
stream to random mountpoints.  usually it's icy_0/icy_1, but sometimes
icecast will refuse the encoder saying "invalid mountpoint".  there
don't seem to be any obvious configuration options on this streamer.  my
meta data options are set like this:
Dont' use that lame dsp plugin :)  Use oddsocks at www.oddsock.org.  It
supports mountpoints properly.
> i used to have use_meta_data set to 0, but i set it to 1 hoping it would
clean this up a bit.  does anybody know what's going on?
Not sure what you mean.

jack.

--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
'icecast-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

> > 1. icecast doesn't seem to recognize when a client disconnects.  i
enabled the shoutcast and icecast directory servers, and they were both saying
that i had around 400 listeners last night, when in fact i only had 8.  the only
lines in the icecast configuration file that seem to have anything to do with
managing client connections are set like this:
> 
> Could be a bug in icecast, though I wouldn't think so.  I would keep
> kick_clients at it's default value, in case there is a bug with
> non-standard values.
> 
i restored the defaults so we'll see how that turns out.  i read the BUGS
file in the source package for 1.3.11, and it says something about a client
count bug in 1.3.7..   "* Sometimes the client count is not correct."
does this ring any bells for anybody?

--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
'icecast-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.