Setting Up Rivendell to Send Metadata to Spinitron

As noted in Eva’s post, Rivendell can send metadata to Spinitron. Yay! This post describes how to set it up.

The technique changed starting with Rivendell version 3, so I’ll cover both the old and the new techniques (tip: the new method is way easier, upgrade Rivendell if you can).

Rivendell Version 2 Now & Next Data

Rivendell v2 users have a few hoops to jump through. Strap yourself in and hang on. This guide assumes a “stock” Rivendell installation.

  • Make a copy of the exemplar. Open a terminal window and type the following command (or simply copy and paste it from here, ensuring the version number matches the Rivendell version you’re actually running):

    cp /usr/share/doc/rivendell-2.19.3/rlm_spinitron_plus.conf /home/rd

  • Using a text file editor, edit that configuration file, setting the station-specific parameters. Settings you need are in Spinitron. Go to Admin: Automation & API: Control Panel, select Rivendell from the “System” menu. The parameters you set look like this

    Leave other settings in the file as they are. Save the file, exit the text editor and close the terminal window

  • Launch RDAdmin and navigate to Manage Hosts → [hostname] → RDAirPlayConfigure Now & Next Parameters

  • Click Add at the bottom of the dialog (under Loadable Modules)

  • Click Select and choose the rlm_spinitron_plus.rlm module (the file selection dialog should open at /usr/lib64/rivendell)

  • In the Argument box, type (or paste) the full path to the configuration file you made in the first step (/home/rd/rlm_spinitron_plus.conf)

  • Click OK to finish up

You should then see the Spinitron module in the list of Loadable Modules. You can monitor the RLM activity in either /var/log/messages, or the Linux system journal.

Important: you will need to restart any running instances of RDAirPlay in order for the changes to take effect.

Rivendell Version 3 (and Later) Now & Next Data

The release of Rivendell version 3 saw a new way of transmitting Now & Next data. It is similar, but way easier to configure compared with version 2.

  • Launch RDAdmin and navigate to Manage Hosts → [hostname] → PyPAD Instances (the name comes from Python modules that transmit program associated data)
  • Click Add, and select
  • Set the station-specific parameters in the edit dialog that opens (APIKey and PlaylistMode may be all that’s necessary to change)
  • Click OK
  • You’ll see the new Spinitron module in the PyPAD Instances list, and it will include a status icon indicating success (green) or failure (red). You can also view the Error Log (it should be empty if there are no errors)

No need to restart RDAirPlay when adding or updaing PyPAD instances with Rivendell 3 or later.

Thank you David for providing these instructions. It’s a great help.


  • Rivendell versions before 2.19.3 don’t work with Spinitron.

  • Values you use for Station and APIKey are in Spinitron. Go to Admin: Automation & API and choose Rivendell from the System drop-down menu.

  • Automation Mode is set in the same page in Spinitron but you can override it from Rivendell. The mode affects how Spinitron handles a spin received from Rivendell when a DJ playlist is available

    • Full Automation: Spinitron ignores the Rivendell spin if a DJ has a playlist open
    • Live Assist: Spinitron puts the Rivendell spin in the DJ playlist, if there is one

    Either way, if there is no available DJ playlist, Spinitron logs spins from Rivendell to playlists that it creates on the fly.

  • For advanced users, it’s possible to set up a user interface in Rivendell that allows DJs to switch automation mode. Don’t ask me how to do it or why you would need this but I know that WMFO did it.