カタログはAmpacheの中枢部です。これらはあなたの音楽ファイル及びその他レコードの全ての為の論理的な格納庫です。現在、Ampacheではリモート、ローカルの2つのカタログタイプを持っています。リモートカタログはXML-RPCで使用して他のAmpacheサーバから参照をするだけです。ローカルカタログはサーバのローカルファイルシステム上のディレクトリを基に参照します。最初のカタログを作成するには、管理者としてAmpacheへログインをして、管理メニューへ行き、カタログを追加をクリックします。
Any administrator can maintain their catalog through either the web interface or the command line script /bin/catalog_update.inc. The /bin/catalog_update.inc take a catalog name as its first argument and performs an “Update” operation on the specified catalog. If no catalog is specified all local catalogs are updated. Below are a list of operations that can be performed on an existing catalog and how they behave
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 and error do not worry! The three most common causes of issues during a catalog build are. If you are having trouble getting your tags reconized correctly by Ampache, or are confused as to why Ampache interrupted something as it did visit Tag Reading / Meta Information
Always Enable Logging when troubleshooting your catalog
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.
cd /path/of/your/catalog
find . -type d -exec chmod 755 {} \;
find . -type f -exec chmod 644 {} \;
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 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.
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:
Although Ampache uses set_time_limit(0) to attempt to override any built-in PHP execution time limits during catalog processes some PHP configurations do not allow these commands to be run. If you are running into Out of Memory (32MB) or Execution time exceeded please modify your php.ini manually and increase the appropriate options. If you are running PHP as a module this will require a restart of your web server. Don't worry if it runs out of memory in the middle of a catalog action. You do not need to delete and start over, simply run the same process again and Ampache will pick up where it left off. For more information on timeout issues and the possible causes please read the following resources.
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.
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.