Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not detected: StudioDisplay/0.5 #7456

Closed
Moonbase59 opened this issue Aug 24, 2023 · 2 comments
Closed

Not detected: StudioDisplay/0.5 #7456

Moonbase59 opened this issue Aug 24, 2023 · 2 comments

Comments

@Moonbase59
Copy link

Moonbase59 commented Aug 24, 2023

AzuraCast uses your library and pointed me here.

I was wondering why my StudioDisplay is reported as Unknown browser 0.00, instead of (at least) StudioDisplay 0.5.

StudioDisplay is a modular MQTT-based signalling & display solution for Web Radio Stations. The software is around since 2017.

It has a stream metadata reader module that reads in-stream metadata from Icecast and Shoutcast audio streams and publishes that to an MQTT server.

Its user agent looks like this (examples):

StudioDisplay/0.5 (Linux; 5.15.0-79-generic; x86_64; 64bit; latin1)
StudioDisplay/0.5 (Windows; 10; AMD64; 64bit; utf-8)
StudioDisplay/0.5 (Darwin; 21.4.0; x86_64; 64bit; utf-8)
StudioDisplay/0.5 (Linux; 5.10.63-v7+; armv7l; 32bit; utf-8)

where

  • StudioDisplay - name (doesn’t change)
  • 0.5 - version*
  • Linux - system**
  • 5.10.63-v7+ - release**
  • armv7l - machine type**
  • 32bit - bitness**
  • utf-8 - encoding expected for in-stream metadata***

* = This is the software version. Known versions so far are 0.4 and 0.5.
** = It uses a Python3 module, so these depend on what the platform module reports.
*** = typically utf-8 or latin1 but can be empty (=guess) or have other values.

It is difficult to categorize, since it’s no browser but concentrates on detecting if an audio stream is live, and reads ICY metadata for displaying purposes ("now playing"). It is also not a bot or a crawler but typically watches this one stream defined in its configuration.

Maybe it could be categorized as a (non-mobile) app, or, better yet, a media player, since it behaves exactly like a media player: Connects to an audio stream and reads it (although throwing away all audio information and just keeping the in-stream metadata).

I’d still be happy if it was at least detected as StudioDisplay 0.5 and not "unknown". It is of interest to station operators (like AzuraCast) to see which listeners are actually listeners and which are just dumb displays hanging at studio walls.

Together with other data, this is typically used by web radio studios for a wall-mounted studio display like this:

grafik

liviuconcioiu added a commit to liviuconcioiu/device-detector that referenced this issue Aug 25, 2023
sgiehl pushed a commit that referenced this issue Aug 25, 2023
* Improves detection for Windows

* Improves detection for macOS

* Adds detection for StudioDisplay

ref #7456
@sgiehl
Copy link
Member

sgiehl commented Aug 25, 2023

Should be fixed with #7457

@sgiehl sgiehl closed this as completed Aug 25, 2023
@Moonbase59
Copy link
Author

Thanks, appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants