Icecast - Aug 2004 - different play lists on different ports?

> I'm running icecast 3.1.10 (from the ports collection) on a freebsd 4.3
jack> First of all, I hope you meant 1.3.10. If there's an icecast 3.1.10
jack> floating around, there are bigger problems.

Yes, pardon, finger dyslexia.

jack> 1.3.10 definately works with multiple mounts (what you called
instances)
jack> without problems. 

No, what I meant by instances was multiple non-forked instances of the
executable in the process table, ie icecast run multiple times with different
port options.  I see from your answer below that this is no longer possible.

jack> You likely are using the wrong option to iceplay (god knows why you are
jack> using that really outdated and inadequate tool).

Because the version I'm using is neither outdated nor inadequate.  It's
been
improved by other people and it works great.  The version I'm using has
mysql
as a back end for keeping album and playlist information (and everything is
handled via a web interface for creating, editing, and choosing playlists,
requesting songs, etc, but that's not part of iceplay, that's just the
stuff
that wraps around it.  Very similar to dj lizard).

jack> We do everything on one port, but you can specify multiple ports. Each
jack> port is the saem as the others.  However, requestings different
jack> mountpoints on the any port should get you the different streams.

I'll see what I can do with that mount points instead of using different
ports.  Thanks for the info.

--- >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 at
xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

I'm running icecast 3.1.10 (from the ports collection) on a freebsd 4.3
machine with a hacked version of iceplay doing the encoding.  With older
version of icecast you could start multiple instances and tell iceplay to
broadcast to each one of those instances with a different playlist.  This
version of icecast seems to only run one instance, even if I try to start more
than one.

So, I've tried using multiple ports in the icecast.conf file, but every port
plays the same playlist.  Is this a "feature" or should I actually be
able to
point different encoding processes with different play lists at each port I
define in icecast.conf?

Thanks...

--- >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.

> I'm running icecast 3.1.10 (from the ports collection) on a freebsd 4.3
First of all, I hope you meant 1.3.10.  If there's an icecast 3.1.10
floating around, there are bigger problems.
> machine with a hacked version of iceplay doing the encoding.  With older
> version of icecast you could start multiple instances and tell iceplay to
> broadcast to each one of those instances with a different playlist.  This
> version of icecast seems to only run one instance, even if I try to start
more
> than one.
1.3.10 definately works with multiple mounts (what you called
instances) without problems.  You likely are using the wrong option to
iceplay (god knows why you are using that really outdated and inadequate
tool).

At the console in icecast, you can see what mountpoints the sources try
to grab. Type sources will also show you this.
> So, I've tried using multiple ports in the icecast.conf file, but every
port
> plays the same playlist.  Is this a "feature" or should I
actually be able to
> point different encoding processes with different play lists at each port I
> define in icecast.conf?
The ports all do the exact same thing.  Each port is just a copy, their
only real use is Shoutcast compatibility since they do everything on
different ports.  We do everything on one port, but you can specify
multiple ports.  Each port is the saem as the others.

However, requestings different mountpoints on the any port should get
you the different streams.  

Here are a few other random idea:
you playlist files are either the same, or are getting mixed together? 
you aren't requesting mountpoints, but always the default mount?

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.

> No, what I meant by instances was multiple non-forked instances of the
> executable in the process table, ie icecast run multiple times with
different
> port options.  I see from your answer below that this is no longer
possible.
If you run multiple copies of icecast, they will be completely separate,
and work as two separate entities.  I have run many instances of icecast
on the same box all on different ports, with little problems.  For each
single instance, you can ask it to listen on multiple ports, which all
act the same.  But two instances ports are separate. And the icecast
instances won't even know about each other.
> jack> You likely are using the wrong option to iceplay (god knows why
you are
> jack> using that really outdated and inadequate tool).
> 
> Because the version I'm using is neither outdated nor inadequate. 
It's been
> improved by other people and it works great.  The version I'm using has
mysql
> as a back end for keeping album and playlist information (and everything is
> handled via a web interface for creating, editing, and choosing playlists,
> requesting songs, etc, but that's not part of iceplay, that's just
the stuff
> that wraps around it.  Very similar to dj lizard).
I would suggest replacing the send loop in iceplay with the Shout perl
module, which uses C code for timing. Perl is just not good enough to do
accurate timing, and you'll get artifacts and skips and disconnects more
often than with something that's using the reliable code.  In any case,
if it works for you great :)  At a certain point, I could no longer get
reliable streams out of it.  My testing showed perl to be just a bit to
course grained to do what it needed to do.
> I'll see what I can do with that mount points instead of using
different
> ports.  Thanks for the info.
The different ports will work across multiple instances.  But they are
equivalent on a single instance.

For example:

icecast isntance one, running on ports 8000, 8001, 8002

icecast instance two, running on ports 9000, 9001, 9002

8000,8001,8002 will all act identically with no difference.

9000,9001,9002 will all act identically with no difference

8000,1,2 and 9000,1,2 will not be anything alike.  They will not share
sources or anything else, unless you've explicitly done this.  (eg,
sending the same stream to both servers).

Running two icecast's on one box is functionally the same as two
icecasts on two different boxes.

Hopefully this clears things up a bit.

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.