AzuraCast / AzuraCast

A self-hosted web radio management suite, including turnkey installer tools for the full radio software stack and a modern, easy-to-use web app to manage your stations.
https://www.azuracast.com/
GNU Affero General Public License v3.0
3.01k stars 556 forks source link

Listener numbers double #7181

Closed HitMaxi closed 2 weeks ago

HitMaxi commented 3 months ago

Installation Method

Docker Installation

AzuraCast Release Channel

Stable Channel

Current AzuraCast Version

No response

What happened?

Hello, I have a question and I hope you can answer it for me.

Why in my Azuracast, the listeners are counted twice at 2 mounting points in every program....

With a hanging point, I have the local server at a mounting point, I have stored a streaming URL under advanced settings....

So e.g. Stream 1. 2 listener. Stream 2 2 listener

= 4 listener but only 1 program 2 attachment points

Relevant log output

No response

HitMaxi commented 3 months ago

??

BusterNeece commented 3 months ago

Hey, so what you're doing here isn't really okay, just so you know.

I got four e-mails from you about this issue in quick succession, and now you're posting for updates even though the issue's only been open for two days.

Do you think that because we make a piece of software that we give away for free, that we owe you a 24-hour turnaround on every issue reported?

It seems like a lot of people do. Please don't.

HitMaxi commented 2 months ago

Sorry, I didn't mean anything bad, I'm just desperate why it doesn't work..

bombelman commented 2 months ago

I see this happening as well. What I do know is that the Dashboard shows the the total connections to your mountpoint, not from the perspective of a unique ip. For example, I know some players pull 1 stream for the audio and another for the metadata. This then shows up as 2 connections in Shoutcast DNAS, but 1 unique connection. (not just in AzuraCast) This could differ with player or website script source. Try different players and see if this is the case.

A possible solution would be to have AzuraCast list only the unique connections instead of the total connections.

Screenshot 2024-06-12 at 9 42 58 AM

HitMaxi commented 2 months ago

Thank you for your help, but the problem still persists.

I have the system running with an Icecast... All channels are affected, only 1 channel works correctly even though it has the same settings!

The same problem is also on the Azurcast demo system... I made the same settings there and it's the same there. I assume that this is a BUG in the Azuracast system...

Von: bombelman @.> Gesendet: Mittwoch, 12. Juni 2024 14:45 An: AzuraCast/AzuraCast @.> Cc: HitMaxi @.>; Author @.> Betreff: Re: [AzuraCast/AzuraCast] Listener numbers double (Issue #7181)

I see this happening as well. What I do know is that the Dashboard shows the the total connections to your mountpoint, not from the perspective of a unique ip. For example, I know some players pull 1 stream for the audio and another for the metadata. This then shows up as 2 connections in Shoutcast DNAS, but 1 unique connection. (not just in AzuraCast) This could differ with player or website script source. Try different players and see if this is the case.

A possible solution would be to have AzuraCast list only the unique connections instead of the total connections.

Screenshot.2024-06-12.at.9.42.58.AM.jpg (view on web) https://github.com/AzuraCast/AzuraCast/assets/107536852/964dfa38-05b9-43ad-8cea-ed701f50cf6d

— Reply to this email directly, view it on GitHub https://github.com/AzuraCast/AzuraCast/issues/7181#issuecomment-2162915512 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BJAC72UOSSUTKYKSG326VNDZHA7DJAVCNFSM6AAAAABI5L44HCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRSHEYTKNJRGI . You are receiving this because you authored the thread.Message ID: @.***>

-- Diese E-Mail wurde von AVG-Antivirussoftware auf Viren geprüft. www.avg.com

github-actions[bot] commented 1 month ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 2 weeks ago

Thank you for your bug report, this issue has been closed due to inactivity. Should this issue persist, please re-open the bug report.