Icecast Streaming Media Server

[jeffnor]

Running on Centos 5.5 64bit
using ices0 for source client.

I have the following mount points

/chiptune (no fallback)
/live falls back to /chiptune shoutcast compatible mount
/customer falls back to live

Issue #1 using /live as the mountpoint it does fallback to chiptune but I get i/o errors, and disconnects ices0 (mp3) for whatever reason i opted to use a 3rd mount point

using /customer it fallsback without the io errors, so i tell everyone to use this mountpoint.

Issue #2 /customer mount point never shows up in status.xml, however the now playing title does update in their media player, winamp, fobar, fserv (ipad app).

for reporting purposes reading the mount point of /chiptune works flawless however if /live starts a source client only the mount point of /live shows the correct titles in status.xml and a media player

/customer never shows up at all in status.xml, but is valid for this setup and does work. I just need to find a way to proxy or relay the titles from live to /customer for reporting purposes.

icecast.conf

<mount>
<mount-name>/live</mount-name>
<stream-name>Radio Network</stream-name>
<fallback-mount>/chiptune</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
<max-listeners>100</max-listeners>
<bitrate>128</bitrate>
<hidden>1</hidden>
<stream-description>LIVE DJ</stream-description>
<Genre>Electronica</Genre>
<Description>A Mix of Random Electronic Music</Description>
<stream-url>http://some.url.here/</stream-url>
<burst-size>65536</burst-size>
<mp3-metadata-interval>4096</mp3-metadata-interval>
</mount>


<mount>
<mount-name>/customer</mount-name>
<fallback-mount>/stream</fallback-mount>
<fallback-override>1</fallback-override>
<stream-name>Customer Stream</stream-name>
<max-listeners>100</max-listeners>
<bitrate>128</bitrate>
<stream-description>Customer stream</stream-description>
<Genre>Electronica</Genre>
<stream-url>http://some.url.here/</stream-url>
<burst-size>65536</burst-size>
<mp3-metadata-interval>4096</mp3-metadata-interval>
</mount>

<shoutcast-mount>/stream</shoutcast-mount>
<listen-socket>
<port>8000</port>
<bind-address>x.x.x.253</bind-address>
</listen-socket>
<listen-socket>
<port>8001</port>
<bind-address>x.x.x.253</bind-address>
<shoutcast-compat>1</shoutcast-compat>
</listen-socket>

<mount>
<mount-name>/chiptune</mount-name>
<stream-name>chiptune music</stream-name>
<max-listeners>100</max-listeners>
<bitrate>128</bitrate>
<burst-size>65536</burst-size>
<mp3-metadata-interval>4096</mp3-metadata-interval>

</mount>

--
ices0.conf the stuff that matter :
<Stream>
<Server>
<Hostname>x.x.x.253</Hostname>
<Port>8000</Port>
<Password>!!!!!!!!</Password>
<Protocol>http</Protocol>
</Server>
<Mountpoint>/chiptune</Mountpoint>
</Stream>


Advice , comments ?

[karlH]

your list of mountpoint does not describe /stream which is what /customer falls back to, I suspect it only appears when you have a shoutcast source client connected.

A useful hint if you want a constant mountpoint as a access point holding place for listeners is to make it a relay eg

/live relays /chiptune (no fallback)
/stream fallback/overrides /chiptune.

I'm unclear what you mean about the I/O errors causing ices to drop.

karl.

[jeffnor]

karlh thanks for the reply

when i had this setup with 1 fallback ice0 would report in the log I/O error could not connect to x.x.x.253 which is itself, but using 2 different mounts with a fallback I don't have this I/O error and ice0 stays connected all the time

I noticed i pasted the wrong XML file into my post too. thats doesnt help troubleshoot this , sorry.

<background>1</background>
<clients>32</clients>
<sources>32</sources>
<threadpool>5</threadpool>
<queue-size>524288</queue-size>
<client-timeout>90</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>30</source-timeout>
<burst-on-connect>1</burst-on-connect>
<hostname>76.73.2.253</hostname>

<mount>
<mount-name>/stream</mount-name>
<stream-name>Indienation.fm Radio Network</stream-name>
<fallback-mount>/8bitbot</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
<max-listeners>100</max-listeners>
<bitrate>128</bitrate>
<hidden>1</hidden>
<stream-description>8bitWonder LIVE DJ</stream-description>
<Genre>Electronica</Genre>
<Description>A Mix of Random Electronic Music</Description>
<stream-url>http://caster.indienation.fm/</stream-url>
<burst-size>65536</burst-size>
<mp3-metadata-interval>4096</mp3-metadata-interval>
</mount>

<mount>
<mount-name>/8bitwonder</mount-name>
<fallback-mount>/stream</fallback-mount>
<fallback-override>1</fallback-override>
<stream-name>IndieNation 8bit Stream</stream-name>
<max-listeners>100</max-listeners>
<bitrate>128</bitrate>
<stream-description>8bit Chiptunage and more @chrispirillo</stream-description>
<Genre>Electronica</Genre>
<stream-url>http://caster.indienation.fm/</stream-url>
<burst-size>65536</burst-size>
<mp3-metadata-interval>4096</mp3-metadata-interval>
</mount>
<shoutcast-mount>/stream</shoutcast-mount>
<listen-socket>
<port>8000</port>
<bind-address>76.73.2.253</bind-address>
</listen-socket>
<listen-socket>
<port>8001</port>
<bind-address>76.73.2.253</bind-address>
<shoutcast-compat>1</shoutcast-compat>
</listen-socket>

<mount>
<mount-name>/8bitbot</mount-name>
<stream-name>IndieNation 8BitsofByte</stream-name>
<max-listeners>100</max-listeners>
<bitrate>128</bitrate>
<burst-size>65536</burst-size>
<mp3-metadata-interval>4096</mp3-metadata-interval>

</mount>
<fileserve>1</fileserve>



Ok so here's the setup
/8bitbot is sourced from ices0 running on the same system. Because I have other mp3 streams on different IP addresss I do not use 127.0.0.1 but the real IP address of the network interface.

/8bitwonder (customer mount point) falls back to /stream
/stream (for live DJs falls back to to /8bitbot

Now listeners can mount to /8bitbot and listen to that stream but we know it wont fall back to /stream when a DJ is sourcing. So we give them the choice to listen at /8bitwonder so they can fall back. I have /stream hidden so people don't try to use that mount point.


You mentioned using /live (stream) to relay to /chiptune (/8bitbot in this case)

/stream to fallback override to /chiptune (/8bitbot) which is does all ready???

how do i relay using a single computer with multiple IP addresses, again I can not use 127.0.0.1 as port 8000 is bound to that port for another shoutcast daemon.

I have read up on master-relay and relay but never can get it to work with this setup.

thank you.

[karlH]

ices like any source client are unaffected by fallback settings. You either connect as a shoutcast source (2 ports) or as an icecast source (1 port) depending on the protocol used (firewall and forwarding rules may apply). Icecast will either accept or reject the source client. The fallback handling only affects listeners.

Check your logs from icecast to see what it thinks is going on. some points of interest in the xml. You have a lot defined that you don't need but the items that stand out as odd are <clients> 32, very low, not much chance of reaching the 100 max listeners you have defined on the mount.

I would start from a single ices feeding a single stream to a mountpoint first (/8bitwonder) and then add the fallback from /stream. If ices is getting an error then there will be a reason for it.

karl.