| View previous topic :: View next topic |
| Author |
Message |
Anonymous
Guest
|
 Posted: Mon May 29, 2006 9:57 pm Post subject: status.xsl |
 |
|
I use 2 mountpoints: 1 for a 24/7 program (/Radio24.mp3) and one for spontaneous live streams (/Radio.mp3).
I display the (ripped) status.xsl on my website for the 24/7 mountpoint and whenever the /Radio.mp3 goes on air this stat is on top.
Now I'd like to have only one link for tuning in: /Radio.mp3 which has a fallback to /Radio24.mp3. This works fine so far but:
The /Radio.mp3 stats pops up on top while not beeing on air just cos it has a fallback to /Radio24.mp3 which is on air. But only the a href="{@mount}.m3u" and the "Current Listeners"
This is pretty annoying as it took ages to rip the status.xsl down to my needs.
Is there a way to avoid it?
or much better: is there a way to seperate the status xsl for each mountpoint?
cheers
Last edited by Anonymous on Tue May 30, 2006 6:23 am; edited 1 time in total |
|
| Back to top |
|
 |
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Mon May 29, 2006 11:05 pm Post subject: |
|
|
stats don't transfer between mountpoints. If you really want a single point of entry between multiple mountpoints and to keep the stats across switchovers then define a local relay. A relay that reads from the same icecast and initially relays the fallback stream, configured to override if a live connection comes in. You can mark the fallback and live mountpoints as hidden so the webroot pages won't see those stats, only the relay will be visible.
karl. |
|
| Back to top |
|
|
Anonymous
Guest
|
| Posted: Tue May 30, 2006 6:57 am Post subject: |
|
|
ok thanks. will try to figure it out although it won't display what is playing on the /Radio24.mpe mount
so i'll relay /Radio.mp3 which falls back to /Radio24.mp3 |
|
| Back to top |
|
|
Anonymous
Guest
|
| Posted: Tue May 30, 2006 5:31 pm Post subject: |
|
|
now it reads "/Radio.mp3 - Not Connected" on top.
and how to mark the fallback and live mountpoints as hidden? |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Wed May 31, 2006 7:09 pm Post subject: |
|
|
use the <hidden> setting in <mount>
karl. |
|
| Back to top |
|
|
Anonymous
Guest
|
| Posted: Thu Jun 01, 2006 10:31 am Post subject: |
|
|
ok it seems to be more complicated than thought.
| Code: |
<master-server>localhost</master-server>
<master-server-port>8000</master-server-port>
<master-update-interval>120</master-update-interval>
<master-username>admin</master-username>
<master-password>****</master-password>
<relays-on-demand>0</relays-on-demand>
<relay>
<server>85.25.46.101</server>
<port>8000</port>
<mount>/Radio.mp3</mount>
<local-mount>/Radio.mp3</local-mount>
<on-demand>0</on-demand>
</relay>
<mount>
<mount-name>/Radio.mp3</mount-name>
<password>XX1</password>
<fallback-mount>/Radio24.mp3</fallback-mount>
<hidden>1</hidden>
</mount>
<mount>
<mount-name>/Radio24.mp3</mount-name>
<password>XX2</password>
<hidden>1</hidden>
</mount> |
it works somehow but I'm not sure if it really relays it and /Radio24.mp3 pops up in the stats anyway instead of /Radio.mp3 when no live stream is connected + the fallback doesn't work (can't connect to /Radio24.mp3 via /Radio.mp3)
so all i want is that /Radio.mp3 as main link for both mountpoints and only the relay /Radio.mp3 should pop up in the stats reading the server descriptions of both mountpoints. keeping the peak stats would be fine too. |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Thu Jun 01, 2006 1:28 pm Post subject: |
|
|
You don't relay the relay itself, that won't work right. Have 3 mountpoints, The relay should have the external mountpoint name eg /stream.mp3 which relays /radio24.mp3, then /radio.mp3 fallback overrides /radio24.mp3.
/stream.mp3 becomes the external point of access for your listeners and /radio.mp3 becomes your point of access for your live source client.
karl. |
|
| Back to top |
|
|
Anonymous
Guest
|
| Posted: Thu Jun 01, 2006 6:04 pm Post subject: |
|
|
ok everything works as planned but the clients can't connect via /Radio.mp3 while /Radio24.mp3 is on air.
/Radio24.mp3 is a ezstream stream. when i stop ezstream, /Radio.mp3 can connect.
i tried all possible variations of passwords and mountpoint fallback overrides. this below is the only one working as described by you but a) it doesn't override /Radio24.mp3 or b) it's a password conflict.
here my config:
| Code: |
<master-server>localhost</master-server>
<master-server-port>8000</master-server-port>
<master-update-interval>5</master-update-interval>
<relay>
<server>localhost</server>
<port>8000</port>
<mount>/Radio.mp3</mount>
<local-mount>/Stream.mp3</local-mount>
</relay>
<mount>
<mount-name>/Stream.mp3</mount-name>
<password>PW1</password>
<hidden>0</hidden>
</mount>
<mount>
<mount-name>/Radio.mp3</mount-name>
<password>PW1</password>
<fallback-override>1</fallback-override>
<fallback-mount>/Radio24.mp3</fallback-mount>
<hidden>1</hidden>
</mount>
<mount>
<mount-name>/Radio24.mp3</mount-name>
<password>PW2</password> (same as in ezstream)
<hidden>1</hidden>
</mount> |
i already tried to use PW1 for all but it won't work.
cheers. |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Thu Jun 01, 2006 9:22 pm Post subject: |
|
|
You make a couple of confusing statements that need some clarifying.
Firstly for some reason your relay is trying to relay your live stream which as you have said is not on all the time, whereas I said you should relay the /Radio24.mp3 stream which will be connected all the time (note that relays are restarted every <master-update-interval> seconds).
"but the clients can't connect via /Radio.mp3 while /Radio24.mp3 is on air."
The only client that should connect on /Radio.mp3 is the source client that is going to provide the live stream. Listener clients use /Stream.mp3.
karl. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
