- 1 Using Picard
- 2 File Formats
- 3 Configuration
How do I tag files with Picard?
There is a separate page that explains the tagging process.
The green "Tagger" icon has disappeared from MusicBrainz.org, how do I get it back?
This icon shows up when a manual lookup is performed via Picard (using the bottom "Lookup" button).
Alternatively the parameter
?tport=8000 can be added to the end of almost any MusicBrainz URL and the green tagger icons will continue to show up from then on.
I'm using Windows Vista or Windows 7, why doesn't drag and drop work?
It's a known problem when running Picard from the installer. Restarting Picard should fix it.
For the technically minded, this is because the installer runs with elevated privileges; but your Windows Explorer does not.
I'm using OS X, where are my network folders or external drives?
These should show up OK in the add file and add folder dialogs, but they aren't visible by default in the file browser pane. If you want to see them in the file browser pane, right click in the pane and select "show hidden files". They should then be visible in the /Volumes folder.
What formats does Picard support?
Picard supports MP3, Ogg Vorbis, FLAC, MP4 (AAC), Musepack, WavPack, Speex, The True Audio and Windows Media Audio.
WAVs cannot be tagged due to the lack of a standard for doing so, however, they can be fingerprinted and renamed.
What formats will Picard support?
Picard is intended to eventually support all formats (including fingerprinting), but this is a complex (arguably never-ending) process, and will take some time.
Please realise that Picard is not designed as a general purpose tag editor. Its primary goal is to get community-maintained MusicBrainz data into your tags. Some secondary goals include
- allowing rule-based (scripts, plugins) customisation of that data
- encouraging users to create an account, fix and update data via the MusicBrainz website, thus sharing their work with the rest of the community - rather than fixing their tags locally.
To that end, Picard is likely to never have as much development focus on manual bulk editing of tags as other general purpose editors (e.g. Jaikoz, Mp3tag, foobar2000 or even many library managers such as iTunes, Windows Media Player, MediaMonkey). That doesn't mean that the team won't welcome patches in this area!
Having said all this, it is still possible in Picard:
- Click and select several files with CTRL or SHIFT
- Right click on one of them, then click Details...
- On the popup dialog you can see the tags, with entries that denote where tags are different across files. You can edit or add new tags here.
- On exiting the dialog, you have changed the tags in memory. You need to click Save in order to persist these changes to your files.
This process should work in both panes.
I am using Fedora, why doesn't acoustic fingerprinting work?
Acoustic fingerprinting in Picard uses a tool called
fpcalc, which is not available in Fedora. You can get it by installing the
chromaprint-tools package from the RPM Fusion repository. This functionality is not contained in the main Fedora
picard package because it requires the
ffmpeg package which cannot be distributed by Fedora. After enabling the "rpmfusion-free" RPM Fusion repository, install the package using (as root):
yum install chromaprint-tools
Firstly, you need to force iTunes to re-read the information from your tags and update its library. This is discussed in the iTunes Guide.
Additionally, iTunes has a known bug in its ID3v2.4 implementation, which makes it unable to read such tags if they contain also embedded cover art. As a work-around, you can configure Picard to write ID3v2.3 tags.
Prior to version 0.14, Picard's default settings were to write ID3v2.4 and ID3v1 tags to files. WMP can't read ID3v2.4, so it falls back to ID3v1 which has a limitation of 30 characters per title. To solve this on versions prior to 0.14, configure Picard to write ID3v2.3 tags instead.
Starting with version 0.14, the default settings have been changed to ID3v2.3 and this should no longer be an issue.
How do I tell Picard which browser to use?
On Windows, GNOME and KDE, Picard uses the standard browser for these systems. On other systems, you can use the
BROWSER environment variable.
export BROWSER="firefox '%s' &"
Another approach that works in some GNU/Linux systems is the following command:
sudo update-alternatives --config x-www-browser
This should present you with a list of existing browsers in your system, allowing you to select the one to be the default.