disco

the DiscoDOS CLI.

usage: disco [-h] [-v] [-o] {search,mix,suggest,import,setup} ...

optional arguments

-h, --help

show this help message and exit

-v, --verbose

increases output verbosity / shows what DiscoDOS is doing under the hood (-v is INFO level, -vv is DEBUG level).

-o, --offline

DiscoDOS checks for connectivity to online services (Discogs, MusicBrainz, AcousticBrainz) itself. This option forces offline mode. A lot of options work in on- and offline mode. Some behave differently, depending on connection state.

disco import

usage: disco import [-h] [--add-to-collection | --tracks | --brainz]
                    [--resume OFFSET]
                    [RELEASE_ID]
release_id

the Discogs release ID you want to import to DiscoBASE. If left empty, the whole collection will be imported. If the additional option -a is used, the release will be added to your Discogs collection _and_ imported to DiscoBASE. Note that a regular import of a given release ID is quite time consuming: We have to check wether or not this release ID is already in the Discogs collection (we don’t want duplicates), thus we have to run through all of your releases via the Discogs API. Unfortunately Discogs does not allow us to search for release IDs in ones collection, we only can “iterate” through them. Therefore the recommended way of adding newly gained releases is by using the -a option.

-h, --help

show this help message and exit

--add-to-collection, -a

This is the recommended (and fastest) way of adding newly gained releases to your collection. The given release ID is added to your Discogs collection (same as when you click an “Add to collection” in the Discogs Webinterface. Additionally the release is added to the DiscoBASE. Note that for performance’s sake, we don’t do a time-consuming check if the release is already in your Discogs collection by asking the Discogs API, but only do a quick check if the ID is in the local DiscoBASE already.

--tracks, -u

extends the Discogs import (releases and also tracks will be downloaded) - takes siginficantly longer than the regular import. Note: This is the same as “disco search all -u”.

--brainz, -z

imports additional information from MusicBrainz/AcousticBrainz. This action takes a long time. -z quick match, -zz detailed match (takes even longer, but more results). Notes: This is the same as “disco search all -z”. Prior to using this option, an extended Discogs import is recommended (disco import –tracks). Otherwise only tracks that were already downloaded to the DiscoBASE (eg used in mixes and updated using “disco mix -u”) will be updated.

--resume <offset>

resumes long-running processes at the given offset position (expects a number). You can combine this option currently with the *Brainz matching import operation only (-z, -zz)

disco mix

usage: disco mix [-h] [-v]
                 [-c | -D | -e POSITION | -E | -b FIELDS | -a SEARCH_TERMS | -r POSITION | -d POSITION | --copy | -u | -z]
                 [-p POSITION] [--resume OFFSET] [-s COLUMN]
                 [mix_name]
mix_name

mix name or mix ID being displayed, edited, created, copied, deleted, etc. If mix_name is left out, a list of available mixes is shown and all other arguments are ignored.

-h, --help

show this help message and exit

-v, --verbose

increases mix tracklist view detail. -v adds tracknames, artists, transition rating/notes and general track notes. -vv shows when and how MusicBrainz matching was done and also direct weblinks to Discogs releases, MusicBrainz releases/recordings and AccousticBrainz recordings.

-c, --create-mix

creates new mix (named as given in mix_name argument).

-D, --delete-mix

deletes the mix (given in mix_name) and all its contained tracks!

-e <position>, --edit <position>

edits/adds details of a track in a mix (editable fields: key, BPM, track number, position in mix, key notes, transition rating, transition notes, general track notes, custom MusicBrainz recording ID).

-E, --edit-mix

edits/adds general info about a mix (name, played date, venue).

-b <fields>, --bulk-edit <fields>

bulk-edits specific fields of each track in mix. Syntax of FIELDS argument: <field1>,<field2>,… available fields: key,bpm,track_no,track_pos,key_notes,trans_rating, trans_notes,notes,m_rec_id_override.

-a <search_terms>, --add-to-mix <search_terms>

searches for release/track in collection and adds it to the mix, This option is actually a shortcut to “disco search -m mix_name search_term” and behaves identically. If SEARCH_TERMS is a number, it is assumed being a Discogs release ID. A quick database check is done and if non-existent yet, the release is 1) added to the Discogs collection and 2) imported to DiscoBASE. This is a convenience function eg when trying to quickly add a release to the mix that’s not in the DiscoBASE yet (possibly an only recently gained record?).

-r <position>, --reorder-tracks <position>

reorders tracks in current mix, starting at POSITION. Note that this is a troubleshooting function and usually shouldn’t be necessary to use.

-d <position>, --delete-track <position>

removes the track at the given position from the mix.

--copy

copies the mix given in mix_name argument. Asks for new name!

-u, --discogs-update

updates tracks in current mix with additional info from Discogs. Can be combined with -p when mix ID provided or with –resume when mix ID not provided (all tracks in mixes update).

-z, --brainz-update

updates tracks in current mix with additional info from MusicBrainz and AcousticBrainz. Leave out mix ID to update every track contained in any mix. -z quick match, -zz detailed match (takes longer, but more results). Can be combined with -p when mix ID provided or with –resume when mix ID not provided (all tracks in mixes *Brainz matching).

-p <position>, --pos <position>

in combination with -a this option adds the found release/track at the given position in the mix (rather than at the end). In combination with -u, -z or -zz the update process is started at the given position in the mix.

--resume <offset>

resumes long-running processes at the given offset position (expects a number). You can combine this option currently with “all tracks in mixes Discogs update” (disco mix -u) or with “all tracks in mixes *Brainz matching” (disco mix -z, disco mix -zz).

-s <column>, --sort <column>

sort tracklist by specified column. add “asc” or “desc” to specify ascending or descending sort order. “track_pos asc” is the default. Experimental feature: currently expects sql column names.

disco setup

usage: disco setup [-h] [--force]
-h, --help

show this help message and exit

--force

force upgrade database schema - only use if you know what you are doing.

disco suggest

usage: disco suggest [-h] [-b BPM] [-k KEY] [search_terms]
search_terms

track or release name you want to show a “track-combination report” for.

-h, --help

show this help message and exit

-b <bpm>, --bpm <bpm>

suggests tracks based on BPM value, within a pitch-range of +/-6 percent.

-k <key>, --key <key>

suggests tracks based on musical key.