Icecast - Sep 2005 - icecast with ices as source

ok, correct me where I'm wrong:

- the <sources> tag defines max ices processes can feed icecast
- several ices sources are sent to the same icecast process, but on
different ports
- the icecast process is configured with 

		<relay>
			<server>127.0.0.1</server>
			.....
		</relay>

for each ices instance ? or with mount ?

thanks,

petre


On 29 Sep 2005 14:34:07 +0100 Anno Domini, the honourable Karl Heyes
wrote using one of his keyboards:
> On Thu, 2005-09-29 at 14:16, Petre Bandac wrote:
> > hello
> > 
> > I have the following problem: is it possible to have several ices
> > "feed" mp3 files to only one icecast process ? or do I have
to make
> > pais
> > - ices/icecast - in order to have several streams on my machine ?
> 
> a single icecast can handle multiple streams, but use a unique
> mountpoint to identify each stream.  eg /low and /high.   Whether
> those come from the same running source client, relays from separate
> machines or multiple source clients is up to you.
> 
> karl.
> 
> 

-- 

Petre Bandac
-
petre@kgb.ro

On 9/29/05, Petre Bandac <petre@kgb.ro> wrote:
> ok, correct me where I'm wrong:
>
> - the <sources> tag defines max ices processes can feed icecast
> - several ices sources are sent to the same icecast process, but on
> different ports
No, usually on the same port. There's no reason to use different ports
(err... well, you have to if you use shoutcast-compatibility, because
shoutcast's protocol is braindead. But for normal usage, just a single
port.
> - the icecast process is configured with
>
>                 <relay>
>                         <server>127.0.0.1</server>
>                         .....
>                 </relay>
>
> for each ices instance ? or with mount ?
You're not configuring a relay, so you don't use the <relay> tag
at
all. You CAN use the <mount> tag to define mount-specific options, but
you don't need to. There's no mandatory per-mount configuration needed
in icecast.

Mike

For ea

problem solved:

icecast.xml

- <sources>20</sources>

- 

<mount>
        <mount-name>/NAME1</mount-name>
</mount>

<mount>
        <mount-name>/NAME2</mount-name> 
</mount>

and each ices.conf has

<Mountpoint>NAME1/</Mountpoint>



thank you for your time,

petre

On Thu, 29 Sep 2005 15:55:57 +0200 Anno Domini, the honourable Michael
Smith wrote using one of his keyboards:
> On 9/29/05, Petre Bandac <petre@kgb.ro> wrote:
> > ok, correct me where I'm wrong:
> >
> > - the <sources> tag defines max ices processes can feed icecast
> > - several ices sources are sent to the same icecast process, but on
> > different ports
> 
> No, usually on the same port. There's no reason to use different ports
> (err... well, you have to if you use shoutcast-compatibility, because
> shoutcast's protocol is braindead. But for normal usage, just a single
> port.
> 
> > - the icecast process is configured with
> >
> >                 <relay>
> >                         <server>127.0.0.1</server>
> >                         .....
> >                 </relay>
> >
> > for each ices instance ? or with mount ?
> 
> You're not configuring a relay, so you don't use the <relay>
tag at
> all. You CAN use the <mount> tag to define mount-specific options,
but
> you don't need to. There's no mandatory per-mount configuration
needed
> in icecast.
> 
> Mike
> 
> For ea

-- 

Petre Bandac
-
petre@kgb.ro