('A beets plugin for creating and exporting songs that match your running session.',)
Going Running (Beets Plugin)
The beets-goingrunning is a beets plugin for obsessive-compulsive music geek runners. It lets you configure different training activities by filtering songs based on their tag attributes (bpm, length, mood, loudness, etc), generates a list of songs for that specific training and copies those songs to your player device.
Have you ever tried to beat your PR and have good old Bob singing about ganja in the background? It doesn’t really work. Or don't you know how those recovery session end up with the Crüe kickstarting your heart? You'll be up in your Zone 4 in no time.
The fact is that it is very difficult and time consuming to compile an appropriate playlist for a specific training session. This plugin tries to help runners with this by allowing them to use their own library.
To use this plugin at its best and to benefit the most from your library, you will want to make sure that your songs have the most possible information on rhythm, moods, loudness, etc.
Without going into much detail the most fundamental information you will want to harvest is
bpm. Normally, when you run a fast pace training you will keep your pace (the number of times your feet hit the ground in a minute) around 170-180. If you are listening to songs with the same rhythm it helps a lot. If your library has many songs without the bpm information (check with
beet ls bpm:0) you will not be able to use those songs. So, you should consider updating them. There are many tools you can use:
Use the built-in acousticbrainz plugin to fetch the bpm plus many other information about your songs. This is your starting point. It is as easy as
beet cousticbrainzand it will do the rest. This tool is based on an on-line database so it will be able to fetch only what has been submitted by someone else. If you have many "uncommon" songs you will need to integrate it with other tools. (My library was still 30% uncovered after a full scan.)
Use the bpmanalyser plugin. This will scan your songs and calculate the tempo (bpm) value for them. If you have a big collection it might take a while, but since this tool does not use an on-line database, you can potentially end up with 100% coverage. This plugin will only give you bpm info.
Essentia extractors. The Acoustic Brainz (AB) project is based partly on these low and high level extractors. There is currently a highly under-development project xtractor plugin which aims to bring your library to 100% coverage. However, for the time being there are no distributable static extractors, so wou will have to compile your own extractors.
There are many other ways and tools we could list here but I think you got the point...
The plugin can be installed via:
$ pip install beets-goingrunning
Activate the plugin in your configuration file by adding
goingrunning to the plugins section:
plugins: - goingrunning
Check if plugin is loaded with
beet version. It should list 'goingrunning' amongst the loaded plugins.
Invoke the plugin as:
$ beet goingrunning training [options] [QUERY...]
or with the shorthand alias
$ beet run training [options] [QUERY...]
The following command line options are available:
--list [-l]: List all the configured trainings. With
beet goingrunning --list you will be presented the list of the trainings you have configured in your configuration file.
--count [-c]: Count the number of songs available for a specific training. With
beet goingrunning longrun --count you can see how many of your songs will fit the specifications for the
--dry-run [-r]: Only display what would be done without actually making changes to the file system. The plugin will run without clearing the destination and without copying any files.
--quiet [-q]: Do not display any output from the command.
--version [-v]: Display the version number of the plugin. Useful when you need to report some issue and you have to state the version of the plugin you are using.
All your configuration will need to be created under the key
goingrunning. There are three concepts you need to know to configure the plugin:
flavours. They are explained in detail below.
Targets are named destinations on your file system to which you will be copying your songs. The
targets key allows you to define multiple targets so that under a specific training session you will only need to refer to it with the
The configuration of the target names
MPD1 will look like this:
goingrunning: targets: MPD1: device_root: /media/MPD1/ device_path: MUSIC/AUTO/ clean_target: yes delete_from_device: - LIBRARY.DAT generate_playlist: yes copy_files: yes
device_root indicates where your operating system mounts the device. The key
device_path indicates the folder inside the device to which your audio files will be copied. In the above example the final destination is
/media/MPD1/MUSIC/AUTO/. It is assumed that the folder indicated in the
device_path key exists. If it doesn't the plugin will exit with a warning. The device path can also be an empty string if you want to store the files in the root folder of the device.
clean_target, when set to yes, instructs the plugin to clean the
device_path folder before copying the new songs to the device. This will remove all audio songs and playlists found in that folder.
Some devices might have library files or other data files which need to be deleted in order for the device to re-discover the new songs. These files can be added to the
delete_from_device key. The files listed here are relative to the
You can also generate a playlist by setting the
generate_playlist option to
yes. It will create an .m3u playlist file and store it to your
There might be some special conditions in which you do not want to copy files to the device. In fact, the destination folder (
device_path) might refer to an ordinary folder on your computer and you might want to create only a playlist there. In this case, you want to disable the copying of the music files by setting
copy_files: no. By default,
copy_files is always enabled so in the above
MPD1 target it could also be omitted and files would be copied all the same.
Trainings are the central concept behind the plugin. When you are "going running" you will already have in mind the type of training you will be doing. This configuration section allows you to preconfigure filters that will allow you to launch a
beet run 10K command whilst you are tying your shoelaces and be out of the house as quick as possible. In fact, the
trainings section is there for you to be able to preconfigure these trainings.
The configuration of a hypothetical 10K training might look like this:
goingrunning: trainings: 10K: query: bpm: 160..180 mood_aggressive: 0.6.. ^genre: Reggae ordering: bpm: 100 average_loudness: 50 use_flavours:  duration: 60 target: MPD1
The keys under the
query section are exactly the same ones that you use when you are using beets for any other operation. Whatever is described in the beets query documentation applies here with two restriction: you must query specific fields in the form of
field: value and (for now) regular expressions are not supported.
At the time being there is only one ordering algorithm (
ScoreBasedLinearPermutation) which orders your songs based on a scoring system. What you indicate under the
ordering section is the fields by which the songs will be ordered. Each field will have a weight from -100 to 100 indicating how important that field is with respect to the others. Negative numbers indicate a reverse ordering. (@todo: this probably needs an example.)
You will find that many of the query specification that you come up with will be repeated across different trainings. To reduce repetition and at the same time to be able to combine many different recipes you can use flavours. Similarly to targets, instead of defining the queries directly on your training you can define queries in a separate section called
flavours (see below) and then use the
use_flavours key to indicate which flavours to use. The order in which flavours are indicated is important: the first one has the highest priority meaning that it will overwrite any keys that might be found in subsequent flavours.
The duration is expressed in minutes and serves the purpose of defining the total length of the training so that the plugin can select the exact number of songs.
This key indicates to which target (defined in the
targets section) your songs will be copied to.
You might also define a special
goingrunning: trainings: fallback: target: my_other_player
Any key not defined in a specific training will be looked up from the
fallback training. So, if in the
10K example you were to remove the
target key, it would be looked up from the
fallback training and your songs would be copied to the
Play count and favouring unplayed songs
In the default configuration of the plugin, on the
fallback training there are two disabled options that you might want to consider enabling:
favour_unplayed. They are meant to be used together. The
increment_play_count option, on copying your songs to your device, will increment the
play_count attribute by one and store it in your library and on your media file. The
favour_unplayed option will instruct the algorithm that picks the songs from your selection to favour the songs that have lower
play_count. This feature will make you discover songs in your library that you might have never heard. At the same time it ensures that the proposed songs are always changed even if you keep your selection query and your ordering unchanged.
The flavours section serves the purpose of defining named queries. If you have 5 different high intensity trainings different in length but sharing queries about bpm, mood and loudness, you can create a single definition here, called flavour, and reuse that flavour in your different trainings with the
Note: Because flavours are only used to group query elements, the
query key should not be used here (like it is in trainings).
goingrunning: flavours: overthetop: bpm: 170.. mood_aggressive: 0.8.. average_loudness: 50.. rocker: genre: Rock metallic: genre: Metal sunshine: genre: Reggae 60s: year: 1960..1969 chillout: bpm: 1..120 mood_happy: 0.5..1
This way, from the above flavours you might add
use_flavours: [overthetop, rock, 60s] to one training and
use_flavours: [overthetop, metallic] to another so they will share the same
overthetop intensity definition whilst having different genre preferences. Similarly, your recovery session might use
use_flavours: [chillout, sunshine].
When it comes to handling queries, this plugin introduces some major differences with respect to the beets core you need to be aware of.
Recurring fields extend the selections
You might define different flavours in which some of the same fields are defined, like the
genre field in the
rocker and the
metallic flavours above. You can define a training that makes use of those flavours and optionally adding the same field through a direct query section, like this:
goingrunning: trainings: HM: query: genre: Folk use_flavours: [rocker, metallic]
The resulting query will include songs corresponding to any of the three indicated genres:
genre='Folk' OR genre='Rock' OR genre='Metal'. This, of course, is applicable to all fields.
Fields can be used as lists
Sometimes it is cumbersome to define a separate flavour for each additional value of a specific field. For example, it would be nice to have the above
chillout flavour to include a list of genres instead of having to combine it with multiple flavours. Well, you can just do that by using the list notation like this:
goingrunning: flavours: chillout: bpm: 1..120 mood_happy: 0.5..1 genre: [Soul, Oldies, Ballad]
or like this:
goingrunning: flavours: chillout: bpm: 1..120 mood_happy: 0.5..1 genre: - Soul - Oldies - Ballad
The resulting query will have the same effect including all indicated genres:
genre='Soul' OR genre='Oldies' OR genre='Ballad'. This technique can be applied to all fields.
Negated fields can also be used as lists
What is described above also applies to negated fields. That is to say, you can also negate a field and use it as a list to query your library by excluding all those values:
goingrunning: flavours: not_good_for_running: ^genre: [Jazz, Psychedelic Rock, Gospel]
When the above flavour is compiled it will result in a query excluding all indicated genres:
genre!='Jazz' AND genre!='Psychedelic Rock' AND genre!='Gospel'. This technique can be applied to all fields.
Using a separate configuration file
In my experience the configuration section can grow quite long depending on your needs, so I find it useful to keep my
goingrunning specific configuration in a separate file and from the main configuration file include it like this:
include: - plg_goingrunning.yaml
Show all the configured trainings:
$ beet goingrunning --list
Check what would be done for the
$ beet goingrunning 10K --dry-run
Let's go! Copy your songs to your device based on the
10K training and using the plugin shorthand:
$ beet run 10K
Do the same as above but today you feel Ska:
$ beet run 10K genre:ska
- If something is not working as expected please use the Issue tracker.
- If the documentation is not clear please use the Issue tracker.
- If you have a feature request please use the Issue tracker.
- In any other situation please use the Issue tracker.
Please check the ROADMAP file. If there is a feature you would like to see but which is not planned, create a feature request in the Issue tracker.
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size beets_goingrunning-1.2.2-py3-none-any.whl (24.2 kB)||File type Wheel||Python version py3||Upload date||Hashes View|
|Filename, size beets-goingrunning-1.2.2.tar.gz (22.4 kB)||File type Source||Python version None||Upload date||Hashes View|
Hashes for beets_goingrunning-1.2.2-py3-none-any.whl