MetaSpreader configuration settings
MetaSpreader supports configuring your metadata receivers as JSON in the Console.
Your Console > Edit Channel > Metaflow > MetaSpreader
Console
{
"radioplayer": {
"stationid": "--old Station ID",
"email": "-- email of account (required)",
"apikey": "-- apikey (required)",
"typ": "radioplayercloud"
},
"radio.de": {
"broadcast": "",
"apikey": "",
"typ": "radio.de"
},
"jsonpush_1": {
"channelname": "my audiostream name 1",
"url": "https://playerwebsite1/metadata-input",
"typ": "jsonpush"
},
"jsonpush_2": {
"channelname": "my audiostream name 2",
"url": "https://playerwebsite2/metadata-input",
"typ": "jsonpush"
},
}POST request with JSON payload
Radioplayer
Radioplayer Unique ID:
When using the Radioplayer Unique ID, an additional “territoryid” can be entered if required; by default it is 276 (Germany).
Old:
Radio.de (radio.net)
TuneIn
Cover Brands Are Live
The name “brandsarelive” is freely definable.
id
You get the ID for the cover from Brands Are Live.
default_cover
If no cover data is available, the default cover is sent.
typ
The type must be “brandsarelive” to send metadata to this provider.
Icecasts/AIS
FTP-Server
template
template describes the content of filename
Amqp
Last updated