<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
On 06-12-15 15:41, Philipp Schafft wrote:<br>
<span style="white-space: pre;">>> The problem I have is that
the listener statistics are now on the<br>
>> fallback stream, not the 'real' one, so now are listener
graphs are flat<br>
>> at zero :( Of course I could pull the statistics from the
fallback<br>
>> mount, but then we won't have listener stats for when
we're live.<br>
>><br>
>> To me it sounds like a bug; surely the fallback never
needs statistics,<br>
>> only the real steam because this is where listeners
connect to. Or maybe<br>
>> I need a different configuration.<br>
><br>
> Ok, I think there is some confusion here:<br>
> There is *no* difference between a mount used as fallback and
one that<br>
> isn't. The only difference is in the configuration of the
mount falling<br>
> to a specific other mount. That is also why the config looks
like it<br>
> does.<br>
><br>
> When a stream falls back to another one the listeners are
*moved* from<br>
> one to the other mount. So they are no longer on the mount
they entered.<br>
> Therefore they're not on it's statistics.</span><br>
<br>
You know, I have a problem with the term 'moved'. The way it is
worded it seems to indicate that the clients are actively moved to a
different URL (by some special codes in the stream, like a HTTP
redirect or something), which is not the case. It is only an
internal 'move' between mount points. At least that much is clear
now.<br>
<br>
<span style="white-space: pre;">> Beside that you use non-free
codecs this looks fine to me. (And it seems to work fine for you
beside the statistics problem).</span><br>
<br>
This is a bit beside the point, but give a me a free (open source)
codec that works reasonably for music at 28/56 kbit and works on all
platforms, and I'll switch tomorrow :P We had an Ogg stream for
years, nobody used it. Sorry, but that's the way it is.<br>
<br>
<span style="white-space: pre;">>> Is there a different
configuration that will work?<br>
>> The main requirement is that switching over to live
streaming<br>
>> is effortless, i.e. just turn on the encoder on the DJ
machine and start<br>
>> streaming.<br>
><br>
> Ok, I after clarifying (at least I hope so) above here is
what I would<br>
> suggest:<br>
> If you only have a 1:1 mapping between entry and fallback
mounts I would<br>
> just sum up the numbers.</span><br>
<br>
That seems to be the most logical solution for now, though from my
point of view it looks silly. I can have 10 different 'input'
streams, there is only one stream/mount point our listeners connect
to and that's the one I'm interested in; the rest are technical
details. I'm sure there's a technical / architectural reason for
this but clearly designed for a different use case.<br>
<br>
<span style="white-space: pre;">> What the best option is depends
a bit on what you're using and how.<br>
> On the other mail you mentioned MRTG. I think it supports
both a broad<br>
> way of adding data. Both poll and trigger based. If you like
I can asks<br>
> our in-house MRTG staff for his opinion.</span><br>
Thanks, but getting the statistics into MRTG isn't a problem. I'll
just need to extend the script(s) a bit.<br>
<br>
Regards,<br>
<br>
Jeroen van Oosten<br>
<br>
<br>
-- <br>
Bankai Software<br>
Jeroen van Oosten<br>
Telefoon: 010-4134567<br>
E-mail: <a class="moz-txt-link-abbreviated" href="mailto:jvoosten@bankai.nl">jvoosten@bankai.nl</a><br>
KvK inschrijving: 24455492<br>
<br>
"If you think it's expensive to hire a professional to do the job,
wait until you hire an amateur." --Red Adair<br>
<br>
</body>
</html>