Amarok/Manual/Organização/Analisando coleção

Other languages:

Analisando coleção

Sempre que o Amarok está mostrando uma coleção, as informações sobre as faixas e álbuns precisam ser obtidas a partir de uma origem. A origem pode ser um dispositivo portátil, um serviço na Internet ou um banco de dados. Para as faixas que estão armazenadas no sistema de arquivos, o Amarok está usando um banco de dados para ter um acesso rápido aos metadados necessários. Na primeira vez é necessário importar esta informação para o banco de dados, o que é feito normalmente com a análise das pastas da coleção a procura de arquivos de áudio. Este processo é chamado de análise da coleção.

É útil compreender o processo de análise para poder utilizar melhor o Amarok.

Análise incremental / Atualizar coleção

A análise incremental irá procurar nas pastas da coleção por atualizações. Isto normalmente é feito a cada minuto, mas também poderá ser acionado manualmente se escolher a opção Atualizar coleção no menu.

A análise incremental irá verificar apenas a data de modificação de cada pasta da coleção, em comparação com a última data de modificação conhecida. Isto tem algumas implicações:

Você pode acionar a reanálise de uma pasta se modificar a sua hora de modificação (por exemplo, se usar o touch na linha de comando).

If files inside a directory are changed the scanner will not notice, because changing a file updates its modification time but not the time of the parent folder.

If the collection folders are on a very slow partition the process of checking all the modification times can take some time. Usually this information is cached by the operating system but with large collections that might not be possible. In such a case the scanner might appear to scan continuously. With collections above 5000 tracks or when collections are stored on a network drive or an NTFS partition it is recommended to switch off the Watch folders for change option.

If you have problems with deleted tracks still appearing in the collection, or you want to update album covers (which are not updated by a mere "update collection") then you can use the Full rescan option in the settings dialog. Full rescan will not care about modification dates. It will not delete your statistics; it will, however, restore rating and playcount if stored inside the file.

Progress bar / scanning time

The progress bar will show the progress of the scanning. Up to 50% the scanner will scan the file system and just buffer the result. Times above 50% indicate that the scanner is committing the results to the database. Usually the second step is much faster than the first so don't be surprised if the progress bar seems to jump. Up to 50% aborting the scan is possible. After 50%, the committing of the files can not be stopped.

The scanning time depends on your disk speed and other factors. Usually the first scan is a lot slower than subsequent scans where the files are cached by the operating system. A scan of 10000 files should take around three minutes on a modern computer. 50000 files should be around 13 minutes.

Backup of collection

With the default settings Amarok is storing all the collection information in a directory called ~.kde/share/apps/amarok/mysqle/ . It can be a good idea to make a backup of this directory from time to time, especially when you didn't enable the writing back of statistics information.

About unique ids

Amarok is tracking files by an id that is either stored in the audio track or computed by the artist, album title and track title meta information. This id helps Amarok to identify tracks that are moved to other locations so that statistics informations (rating, score, playcount) are not lost. Currently Amarok will not import tracks with duplicate unique ids. This leads to the surprising behavior that copied tracks still appear only once in Amarok.

In some circumstances even different tracks can end up with the same unique id. That is very uncommon and usually the result of running years of unstable Amarok releases. Such a problem can be seen by the debug output (start Amarok with the --debug option) while scanning.

If you are using 2.4 beta you might run into a case where most of the collection is not imported. This can be easily seen by the failing sql commands in the debug output. In such a case just use 2.4 final.

About Albums

The scanner can only read single tracks but Amarok will display those sorted by album and compilation (an album without one specific artist). Amarok can't rely on the directory in which the files are located, since directory organizational schemes vary so widely.

The scanner is therefore doing the following:

Tracks without an album artist or an artist (or a composer in case of a classical track) are placed in a compilation.

Tracks that have the compilation flag set or an album artist other than "various artists" will be placed in an album.

Tracks that have the compilation flag set to 0 are placed in a compilation.

Albums called "Live", "Greatest Hits" and a couple of other names are always regarded as an album.

If we end up having tracks with several different artists left over they are placed inside a compilation, or else we make one album out of them.

This process is quite complicated. However usually the outputs of the scanner can help in figuring out why the tracks are sorted as they are.

In such a case try executing (on a command line)

amarokcollectionscanner -r ~/Music/directory

Look for "compilation" tags and tracks with different "artist" and "albumartist" tags.

You can remove the tag from mp3 files with the following command:

id3v2 -r TCMP your fileename here