There is a separate page that explains the tagging process.
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.
If you get "Couldn't load album errors" for releases in Picard, this can occur for a number of reasons. Check the following things:
Try waiting a minute or two, or even a bit longer and then try again with a right click, "Refresh". Sometimes the servers are just overloaded and temporarily reject requests.
If you are re-tagging files previously tagged with Picard, and get this error, the release has possibly been deleted. Try to right click and use the "Lookup in browser" option to view the release on the website - if you can't find it, it may have been deleted. This could be because you tagged a pending release that was voted down, or tagged against a release that was deleted because editors decided it wasn't a valid release. (Can happen for homebrew compilations, bad torrent or pirate rips, "advance" releases or very poorly added releases.) Usually there will be an alternate release you can tag against which you can find by searching or doing another clustered lookup from Picard. If you can't find a replacement and believe it has been deleted unfairly, submit a new release, supplying evidence of the tracklisting and as much information as possible to prove it is genuine and it may be accepted again.
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.
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.
Picard supports the following file formats:
WAVs cannot be tagged due to the lack of a standard for doing so, however, they can be fingerprinted and renamed.
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
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:
This process should work in both panes.
Acoustic fingerprinting in Picard uses a tool called
fpcalc, which is not available in Fedora. You can get it by installing the
chromaprint-toolspackage from the
RPM Fusion repository.
This functionality is not contained in the main Fedora
picardpackage because it requires the
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.
On Windows, GNOME and KDE, Picard uses the standard browser for these systems.
On other systems, you can use the
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.