Azuracast
Azuracast may not correctly report track length or position. If this is the case you should reduce the "listened to" duration using Scrobble Thresholds so that multi-scrobbler scrobbles correctly.
The Azuracast server should have Use High-Performance Now Playing Updates enabled in Administration -> System Settings
URL
The URL used by MS to connect to Azuracast has the syntax:
[ws|wss]://HOST:[PORT]
MS will automatically add the path required for websockets, /api/live/nowplaying/websocket, to your URL if none is provided. If you use a reverse proxy with a path-based URL or otherwise need a custom path to access the websockets path correctly then explicitly provide it. Examples:
URL From Config => MS Uses
'ws://192.168.0.101' => ws://192.168.0.101/api/live/nowplaying/websocket
'ws://azura.mydomain.com' => ws://azura.mydomain.com.com/api/live/nowplaying/websocket
'wss://mydomain.com/custom/azura/ws' => wss://mydomain.com/custom/azura/ws
Should Scrobble Behavior
This Source supports toggling scrobbling on or off manually. This action can be taken on the Web Dashboard by clicking the link next to Should Scrobble found in each Source's status card.
Additionally, the default behavior for scrobbling can be explicitly set by adding the following value to a Source's options in file or aio config:
{
"data": {
// ...
},
"options": {
// set to true to always scrobble automatically
// set to false to never scrobble automatically
"systemScrobble": true
}
}}
Multi-scrobbler will set the default scrobbling behavior based on if either of these settings is configured:
- live status (
AZURA_LIVEormonitorWhenLive) or - listener count (
AZURA_LISTENERS_NUMormonitorWhenListeners)
If either is configured then MS will automatically scrobble based on when these conditions are met.
If neither is configured automatic scrobble defaults to off and you should either manually initiate it or explicitly set the default behavior.
Configuration
- ENV
- File
- AIO
This is configuration for the ENV Config Type.
| Environmental Variable | Required? | Default | Description |
|---|---|---|---|
AZ_URL | Yes | Azuracast URL without station name | |
AZ_STATION | Yes | The station name shown on the public page | |
AZURA_LIVE | No | Yes | Only scrobble when station status is ONLINE |
AZURA_LISTENERS_NUM | No | true | Only scrobble if station has any listeners (true) or listeners are equal-to/greater-than X |
Config Structure
This displays the structure of the File Configuration for a azuracast type Source with all possible properties, their shape, and descriptions/types. Use this to understand how to write a valid config.
Config Example
This displays an example config file of a azuracast Source File Configuration that adheres to the shown Config Structure.
- text mode lets you edit the JSON directly.
- tree mode gives you a guided point-and-click editing experience that always keeps the JSON syntax valid.
Both modes validate that the configuraion is correct. Any errors show up as squiggly lines.
After you finish editing, switch to text and then copy all text to get a completed config.
Config Example Mobile Experience
This displays an example config file of a azuracast Source File Configuration that adheres to the shown Config Structure.
The example config file editor is meant for a larger screen experience so only the read-only example is shown. Please use this site on a tablet/laptop/desktop to enable file editor features.
[
{
"type": "azuracast",
"enable": true,
"name": "azura",
"data": {
"url": "ws://192.168.0.101",
"station": "my-station-name",
"monitorWhenLive": true,
"monitorWhenListeners": 1
}
}
]
Config Structure
This displays the structure of the all-in-one (config.json) configuration with all possible properties, their shape, and descriptions/types. Use this to understand how to write a valid config.
Select the azuracast type from the respective sources node below, then expand it.
Config Example
This displays an example config file of a all-in-one (config.json) configuration that includes a azuracast Source that adheres to the shown Config Structure.
- text mode lets you edit the JSON directly.
- tree mode gives you a guided point-and-click editing experience that always keeps the JSON syntax valid.
Both modes validate that the configuraion is correct. Any errors show up as squiggly lines.
After you finish editing, switch to text and then copy all text to get a completed config.
Config Example Mobile Experience
This displays an example config file of a all-in-one (config.json) configuration that includes a azuracast Source that adheres to the shown Config Structure.
The example config file editor is meant for a larger screen experience so only the read-only example is shown. Please use this site on a tablet/laptop/desktop to enable file editor features.
{
"sources": [
{
"type": "azuracast",
"enable": true,
"name": "azura",
"data": {
"url": "ws://192.168.0.101",
"station": "my-station-name",
"monitorWhenLive": true,
"monitorWhenListeners": 1
}
}
]
}