Skip to main content

# Yamaha MusicCast

Monitor MusicCast device/receivers for music played on Network/USB/CD inputs.

Scrobbling Threshold

Musiccast may not correctly report track length. If this is the case you should reduce the "listened to" duration using Scrobble Thresholds so that multi-scrobbler scrobbles correctly.

##### URL​

If only a domain/IP:PORT is provided to multi-scrobbler it will automatically append the default Musiccast API path. If your Musiccast device is located behind a custom URL (or reverse proxy) you should explicitly provide the base path to use.

EX

`url` | Transformed URL
--- | ---
`http://192.168.0.101` | `http://192.168.0.101/YamahaExtendedControl/v1`
`http://mydomain.com/reverseProxy/cast` | `http://mydomain.com/reverseProxy/cast`

## Configuration​

- ENV
- File
- AIO

Configuration Type

This is configuration for the ENV Config Type.

Environmental Variable | Type | Default | Description
--- | --- | --- | ---
`MCAST_ID` | string |  | A globally unique ID EX `myComponentId`
`MCAST_NAME` | string | Value of `MCAST_ID` | A vanity name EX `My Cool Component`
`MCAST_ENABLE` | boolean | true | Should this component be used?
`MCAST_URL` | string |  | The host or URL of the YamahaExtendedControl endpoint to use

Bold/Italic = Required

Config Structure

This displays the structure of the File Configuration for a musiccast type Source with all possible properties, their shape, and descriptions/types. Use this to understand how to write a valid config.

Loading ...
Config Example

This displays an example config file of a musiccast 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 configuration is correct. Any errors show up as squiggly lines.

important

Only source musiccast configs will validate correctly in the editor but both source and client musiccast configs are allowed in the real `CONFIG/musiccast.json`

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 musiccast 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.

CONFIG/musiccast.json

    [
      {
        "name": "Livingroom Reciever",
        "id": "myYamaha",
        "enable": true,
        "data": {
          "url": "192.168.0.101"
        }
      }
    ]

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 musiccast type from the respective `sources` node below, then expand it.

Loading ...
Config Example

This displays an example config file of a all-in-one (`config.json`) configuration that includes a musiccast 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 musiccast 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.

CONFIG/config.json

    {
      "sources": [
        {
          "name": "Livingroom Reciever",
          "id": "myYamaha",
          "enable": true,
          "data": {
            "url": "192.168.0.101"
          },
          "type": "musiccast"
        }
      ]
    }