Catalogs are the core of Ampache. They are a logical container for all of your music files and other records. There are two main types of catalogs currently in Ampache, Remote and Local. Remote catalogs are only for use with XML-RPC and reference other Ampache servers. Local catalogs reference a base directory on the local file system of the server. To create your first Catalog login to Ampache as an administrator and go to the Admin Menu and click on Add a Catalog
Any administrator can maintain their catalog through either the web interface or the command line script /bin/catalog_update.inc. Below are a list of operations that can be performed on an existing catalog and how they behave
You can alternatively maintain an existing catalog through the command line interface.
The above command will take all catalogs in order and perform a full update on them. If you specify one or more catalog names as arguments, then the update will be performed.
Alternatively, you can specify different arguments if you do not want a full update to be performed. For instance, if you've recently added another artist's songs to your database, then running an 'add' function on the database is going to be far faster. These 3 arguments are -c, -v, and -a. The order that this is performed in is always the same:
This is intentional as you don't want to run a verify on files that are going to be deleted right after and you don't want to run a verify on the files that just now got added because they're still accurate.
Always Enable Logging when troubleshooting your catalog
Ampache's catalog builds are done in such a way that even if it breaks in the middle of any one of the operations your Catalog is still perfectly intact. So, even if you encounter an error do not worry! If you are having trouble getting your tags recognized correctly by Ampache, or are confused as to why Ampache interrupted something as it did visit Tag Reading / Meta Information. The three most common causes of issues during a catalog build are:
Ampache must have Read access to all the files in the catalog, and Read+Execute to all the directories. If you run into issues where Ampache is saying it is unable to read a file or directory please double check the file permissions. The below two commands will set the correct file permissions for your files and directories. It is very important that you cd to the base of your MP3s first as these commands start at your current directory and recursively change permissions. Please note that these below commands cannot be ran in a Windows environment.
chmod -R u+rwX,go+rX /path/to/your/catalog/*
Make sure the PHP's Open Basedir isn't set, or if it is it includes the directory of your music. Also make sure that there is not a specific deny listed in your IIS/Apache config prohibiting the script from opening the directory with your music.
For mount points you should make sure that the user / group that your webserver is running as has read access to the mount, and that the mount is using the correct character set. Something like
mount -t smbfs //[computername or IP]/share /media/Storage -o uid=username,gid=users -o iocharset=utf
For windows network drives you will need to make sure that the user that apache is running as is the exact same user that is mounting the network drive, and has sufficient privileges to read the network drive and the files it contains.
Also note that selinux may default to not allowing apache to read cifs or nfs mounts. See the man pages for booleans(8), getsebool(8), and setseool(8). Selinux should log the violations to the system log (/var/log/messages usually).
Accessing shared folders and drives is possible, but requires a little work to get going. Here are the things you need to watch out for:
Getid3() should never take up more then 32MB of ram if it is working correctly, however every now and then it stumbles upon a file it can't parse correctly and uses a very large amount of Ram, and appears to hang the catalog process. The only way to solve this is to either re-encode/re-tagging the file in question or simply remove it from your collection. To figure out which file is causing the problem enable logging and look for the last file processed.
You can also use a varity of tools to autmatically check and repair your files. A far from complete list can be found under Third Party Tools
As of 3.4-Beta2 Ampache forces the filenames of the files being added to the catalog to contain only characters from the character set defined in the /config/ampache.cfg.php under site_charset. If some of your files are not cataloging correctly and are reporting a Charset error you can either rename them manually or use the provided script in /bin, fix_filenames.inc.