[Icecast] Current Listeners count wrong for HTML Audio on Android?

Brad Isbell brad at audiopump.co
Mon May 4 18:45:17 PDT 2015


Klaas,
Using Wireshark, I see that two TCP connections are initially made to your
streaming server, but one is closed after 10 seconds.  The other is used
for the actual stream.  I suspect that Icecast reports both connections two
you, but for the purposes of bandwidth consumption you are probably safe.

Do double check with your own devices though, with a packet sniffer.  I
only tested one device.  Browsers vary quite a bit in how they handle media.

Thanks,
 *Brad Isbell // AudioPump, Inc.*
brad at audiopump.co
Skype: bradisbell
Phone: +1 312-488-4680

On Mon, May 4, 2015 at 8:10 PM, Klaas van der Linden <
vanderlinden at culturalservices.nl> wrote:

> Thanks for this information, but the two connections do not die out when
> using my player in the Android browser. In fact they even stay when the
> Audio.src is set to some invalid string.
>
>
>
> You can observe this here:
> http://concertzender.nl/wp-content/themes/cz-theme/App/test/ , by
> clicking one of the large icons - and then monitor the corresponding stream
> here: http://streams.greenhost.nl:8080/
>
>
>
> (The player doesn’t work on safari (windows/mac) or firefox, probably
> because mp3 is not supported they fail to register the ‘canplay’ event or
> something like that – I’m not sure. I got it to work on IE, Opera, Chrome
> and iPhone Safari and on Android.)
>
>
>
> Any suggestions as to how to debug this?
>
>
>
>
>
> *From:* icecast-bounces at xiph.org [mailto:icecast-bounces at xiph.org] *On
> Behalf Of *Brad Isbell
> *Sent:* zondag 3 mei 2015 2:46
> *To:* Icecast streaming server user discussions
> *Subject:* Re: [Icecast] Current Listeners count wrong for HTML Audio on
> Android?
>
>
>
> Klaas,
>
> You will find that there often are multiple connections, particularly for
> HTML5 audio elements in WebKit browsers as they probe to see if the media
> is seekable or not.  The multiple connections die out soon after starting
> though, leaving you one connection for actually streaming the audio.
>
>
>
> You can verify this yourself with a packet sniffer such as Wireshark.  It
> wouldn't hurt to double check to make sure your application isn't really
> using all that data.
>
>
> *Brad Isbell // AudioPump, Inc.*
> brad at audiopump.co
> Skype: bradisbell
> Phone: +1 312-488-4680
>
>
>
> On Sat, May 2, 2015 at 6:59 PM, Klaas van der Linden <
> vanderlinden at culturalservices.nl> wrote:
>
> Dear all,
>
> The problem I am facing, is that one of my clients is concerned about data
> usage.
>
> My client monitors the current number of listeners in  the Mount Point
> list streams.greenhost.nl:8080.
>
>
>
> The case is, when I start a stream from an HTML app on an Android device,
> I can see two listeners being added to “Current Listeners”. This peculiar
> behaviour only occurs on Android, not on laptops or iPhones.
>
>
>
> The code I use concerns a simple HTML Audio object:
>
> var audioObj = new Audio();
>
> audioObj.src = aValidMountpoint;
>
> audioObj.play();
>
>
>
> I tested these lines and it appears that for Android a “Current Listener”
> is added on both the second and the third line.
>
>
>
> I can’t imagine there really are two streams streaming at the same time,
> as it is only one object that arranges this.
>
>
>
> Is this a known issue? Any workaround or any way to prove my client that
> there is only one stream playing?
>
>
>
> Regards,
>
>
>
> Klaas van der Linden
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.xiph.org/pipermail/icecast/attachments/20150504/e986ab42/attachment.htm 


More information about the Icecast mailing list