Difference between revisions of "MusicBrainz Picard/Documentation/Options"

From MusicBrainz Wiki
m (Conversion script moved page MusicBrainz Picard/Documentation/Options to musicBrainz Picard/Documentation/Options: Converting page titles to lowercase)
(No difference)

Revision as of 03:33, 19 September 2012

Products > MusicBrainz Picard > Picard documentation > Options

General

  • Server address: The domain name for the server. Default value: musicbrainz.org (for the main MusicBrainz server).
  • Port: The port number for the server. Default value: 80 (for the main MusicBrainz server).
  • Username: Your MusicBrainz website username, used to submit PUIDs and retrieve personal user folksonomy tags.
  • Password: Your MusicBrainz website password.
  • Automatically scan all new files: Check this box if you want Picard to scan each music file you add and look for a fingerprint (AcoustID or PUID, depending on your preferences). This takes time, but may be helpful for you and MusicBrainz. Leave it unchecked if you don't want Picard to do this scan automatically. In any case, you can direct Picard to scan a particular music file at any time using the Scan button in the toolbar.

Metadata

  • Translate artist names to this locale where possible: When checked, Picard will see whether an artist has an alias for the selected locale. If it does, Picard will use that alias instead of the artist name when tagging. When "English" is the selected locale, the artist sort name (which is, by Style Guideline, stored in Latin script) is used as a fallback if there is no English alias.
  • Use standardized artist names: Check to only use standard Artist names, rather than Artist Credits which may differ slightly across tracks and releases. Note: If the "translate artist names" option above is also checked, it will override this option if a suitable alias is found.
  • Use release relationships: Check to retrieve and write release-level relationships to your files, e.g. URLs, composer, lyricist, performer, conductor, DJ mixer, etc. (You must have this enabled to use Picard to retrieve cover art)
  • Use track relationships: Check to write track-level relationships to your files, e.g. composer, lyricist, performer, remixer, etc.
  • Use folksonomy tags as genres: Check to write MusicBrainz folksonomy tags as genres. (See options under "Folksonomy Tags")
  • Preferred release country: Select a country if you want Picard to automatically try and select the release event with that country when tagging.
  • Various artists: Choose how you want the 'Various Artists' artist spelled.
  • Non-album tracks: Choose how you want 'non-album tracks' (Recordings that do not belong to any Release) to be grouped.

Preferred Releases

  • Preferred release types: Adjust the sliders for various release types to tweak how likely Picard is to match a file or cluster to releases of various types. You can use this to decrease the likelihood of Picard matching a file or album to a Compilation or Live version, for example.
  • Preferred release countries: Add one or more countries into the list to make Picard prefer matching clusters/files to releases from the chosen countries.
  • Preferred release formats: Add one or more formats into the list to make Picard prefer matching clusters/files to releases of the specified format.

Folksonomy tags

The following settings are only applicable if you enable the use folksonomy tags as genres option.
  • Ignore tags: Comma-separated list of tags to ignore when writing genres.
  • Only use my tags: Check to only write genres with tags that you personally have submitted to MusicBrainz. You'll need to set your username and password to use this feature.
  • Minimal tag usage: Choose how popular the tag must be before it is written by Picard. Default: 90%. Lowering the value here will lead to more tags in your files, but possibly less relevant tags.
  • Maximum number of tags: Choose how many tags to write as genres. Default: 5. If you only want a single genre, set this to 1.
  • Join multiple tags with: Select which character should be used to separate multiple tags.

Ratings

  • Enable track ratings: Check to write track ratings to your files.
  • Submit ratings to MusicBrainz: Check to submit ratings to MusicBrainz. The tracks will be rated with your account.

Tags

  • Write tags to files: Uncheck to disable Picard from writing data. Picard may still move/rename your files according to your settings.
  • Clear existing tags: Checking this will remove all existing metadata and leave your files with only MusicBrainz metadata. Information you may have added through another media player such as genre, comments or ratings will be removed.
  • Remove ID3 tags from FLAC files: Check to remove ID3 tags from FLAC files – Vorbis Comments are recommended for FLAC files. Picard will write Vorbis Comments to FLACs regardless of this setting.
  • Remove APEv2 tags from MP3 files: Check to remove APEv2 tags from MP3 files – ID3 is recommended for MP3s. Picard will write ID3 tags to MP3s regardless of this setting.


  • ID3v2 version: Version 2.4 is the latest and recommended version, but its support in players is still lacking. Software such as foobar2000 and MediaMonkey have no problem using version 2.4 tags, but you will not be able to read the tags in explorer.exe or Windows Media Player (in any Windows or WMP version, including those in Windows 7). Since v0.14, version 2.3 is Picard's default, and is recommended if your player doesn't show the tags with version 2.4. Other than native support for multi-valued tags in v2.4, the Picard Tag Mapping will show you what you lose when choosing v2.3 instead of v2.4.
  • Also include ID3v1 tags in the files: Not recommended at all. ID3v1.1 tags are obsolete and may not work with non-latin scripts.
  • ID3v2 text encoding: The default for version 2.4 is UTF-8, the default for version 2.3 is UTF-16. Use ISO-8859-1 ***only*** if you face compatibility issues with your player.

Cover art

You will require the Cover Art Downloader plugin available on the Picard Plugins page and you must have enabled "use release relationships".
  • Embed cover images into tags: This option will enable embedding images directly to the tags.
  • Save cover images as separate files: In the file name mask you can use any variable or function from Picard Tags and Picard Scripting. The mask should not contain a file extension; this is added automatically based on the actual image type. The default value is cover. If you change this to folder, Windows will use it to preview the containing folder.
  • Overwrite the file if it already exists: Check this to replace existing files. This is especially recommended if trying to write "folder" previews for Windows.

Moving files

This page tells Picard whether it should move your audio files to a new directory when it saves metadata in them. One use for this is to keep your work organised: all untagged files are under directory A, and when Picard tags them it moves them to directory B. When directory A is empty, your tagging work is done. Check this box, and select a destination directory, if you want Picard to move files this way. Uncheck the box if you want Picard to leave the files under the same directory.

The Rename Files and Move Files options are independent. Rename Files refers to file names, and directory names based on artist and release names, under a parent directory. Move Files refers to changing the parent directory. However, they both use the same "file naming string". Move files uses the portion up until the last '/'; rename files the part after that.

  • Move files to this directory when saving: Choose a destination parent directory to move saved files to.
    • If you use the directory "," they will be removed relative to their current location. If they are already in some sort of folder structure, this will probably not do what you want!
  • Delete empty directories: Check to have Picard remove directories that have become empty once a move is completed. Leave unchecked if you want Picard to leave the source directory structure unchanged. Checking this box may be convenient if you are using the move files option to organise your work. An empty directory has no more work for you to do, and deleting the directory makes that clear.
  • Move additional files: Enter wildcard patterns that match any other files you want Picard to move when saving files, e.g. Folder.jpg, *.png, *.cue, *.log. Using default settings, when these additional files are moved they will end up in the release directory with your files. In a wildcard, * matches zero or more characters. Other text, like .jpg, matches those exact characters. Thus *.jpg matches "cover.jpg", "liner.jpg", "a.jpg", and ".jpg", but not "nomatch.jpg2". Put spaces between wildcard patterns.

File naming

  • Rename files when saving: Check to let Picard change file and directory names of your files when it saves metadata in them, in order to make the file and directory names consistent with the new metadata.
  • Replace non-ASCII characters: Check to replace non-ASCII characters with their ASCII equivalent, e.g. á,ä,ǎ, with a; é,ě,ë, with e; æ with ae, etc. For more information on ASCII characters read the Wikipedia page on ASCII.
  • Replace Windows-incompatible characters: Check to replace Windows-incompatible characters with an underscore. Enabled by default on Windows with no option to disable.


  • Name files like this: An edit box that contains a formatting string that tells Picard what the new name of the file and its containing directories should be, in terms of various metadata values. The formatting string is in Picard's scripting language where dark blue text starting with a "$" is a function name and names in light blue within "%" signs are Picard's tag names. Note that the use of a "/" in the formatting string means that everything before the string is a directory name, and everything after the last "/" becomes the file's name. The formatting string is allowed to have zero, one, or multiple, "/".
  • Name multiple artist albums differently: This edit box behaves in the same manner as the above edit box except that it only applies to tracks from releases with multiple track artists.

CD lookup

This is where you tell Picard which CD drive it should use for looking up CDs.

Windows

On Windows, Picard has a pulldown menu listing the various CD drives it has found. Pull down the menu and select the drive you want.

OS X

In OS X, this option is currently a text field. The device is usually /dev/rdisk1.

If that doesn't work, one way is to simply keep increasing the number (e.g. /dev/rdisk2) until it does work. A less trial and error method is to open Terminal and type mount. The output should include a line such as /dev/disk2 on /Volumes/Audio CD (local, nodev, nosuid, read-only). You need to replace /dev/disk with /dev/rdisk, so if, for example, it says /dev/disk2, you should enter /dev/rdisk2 in Picard's preferences.

Linux

In Linux, Picard has a pulldown menu like in Windows. If you're using an older version with a text field, you should enter the device name (typically /dev/cdrom) here.

Other platforms

On other platforms, the CD Lookup option is a text field and you should enter the path to the CD drive here.

Plugins

For a list of plugins see Picard Plugins.

Here you may enable/disable any of the plugins you have installed in Picard. Note that some plugins have their own option page which will appear under here.

Advanced

Web proxy

If you need a proxy to make an outside connection you may specify one here.

Matching

It is recommended for most users to not change these settings. However for advanced users, it allows you to tune the way Picard matches your files and clusters to to MusicBrainz releases and tracks.

  • Minimal similarity for file lookups: The higher then %, the more similar an individual file's metadata must be to MusicBrainz's metadata for it to be moved/matched to a release on the right-hand side.
  • Minimal similarity for cluster lookups: The higher then %, the more similar a cluster of files from the left-hand pane must be to a MusicBrainz release for the entire cluster to be moved/matched to a release on the right-hand side.
  • Minimal similarity for matching files to tracks: The higher then %, the more similar an individual file's metadata must be to MusicBrainz's metadata for it to be moved/matched to a release on the right-hand side.

If you have absolutely no metadata in your current files, and you are using Scan to match tracks, you may find you need to lower Minimal similarity for matching files to tracks in order to get Picard to match the files within a release. Otherwise you may find that Picard matches the track to a release but then is not sure which track is correct; and leaves it in an "unmatched files" group within that release.

As a general rule, lowering the percentages may increase the chance of finding a match at the risk of false positives and incorrect matches.

Scripting

For scripting help see Picard Scripting and Picard Tags for variables available to script with.

User interface

  • Show text labels under icon: Uncheck to make the toolbar a little smaller.
  • Allow selection of multiple directories: Check to bypass the native directory selector and use QT's file dialog since the native directory selector usually doesn't allow you to select more than one directory. This applies for the 'Add folder' dialog, the file browser always allows multiple directory selection.
  • Use advanced query syntax: Check to enable advanced query syntax parsing on your searches. This only applies for the search box at the top right of Picard, not the lookup buttons.
  • Show a quit confirmation dialog for unsaved changes: Check to show a dialog when you try to quit Picard with unsaved files loaded. This may help prevent accidentally losing tag changes you've made, but not yet saved.