Frequently Asked Questions

001. Why does nothing happen when I try to play a video using the Flash player?

The embedded Flash player only plays audio.

002. Why does nothing happen when I try to play flac/ogg/wma/m4a/ape/mka audio files in the Flash player?

The Flash player currently only able to play mp3 format audio files. This is a limitation of Adobe Flash and not Ampache. (Accurate as of Flash 10.) If you want to get around this limitation, you can enable encoding in config/ampache.cfg.php for each existing file type.

003. Why is my music too slow/fast when played through the flash player?

Adobe Flash has a limitation of only being able to play mp3s at 44 khz sample rate. If your music is encoded to play at 48 khz for example, your music may play slowly. If your music is encoded at a lower sample rate such as 40 or 42 khz, your music may sound sped up. This is a limitation of Adobe Flash. Use the transcoding option if you experience this.

004. I'm attempting to use Amarok with Ampache using the xmlapi|XML API and I get an invalid handshake error.

Either your Ampache is too old or your Amarok is too old. Ampache requires version 3.5 or higher and Amarok requires 2.1 or higher.

005. I'm trying to get Amarok to open my .m3u playlist generated by Ampache, but it doesn't play.

When Amarok 2.x was first released, it did not recognize .m3u playlists. This was fixed in later versions.

006. I have my ACLs set up properly, but when Amarok plays music over the XML API, it says "ACL Error"

Your ACLs are not set up properly. Ampache/Amarok don't lie.

007. I'm getting errors about memory limits being reached.

The most common cause of memory time-out issues (assuming you've already bumped the max memory in php) is a file (or files) with corrupt or malformed tags. Enable Logging to find the file causing the issues. This is only the most likely cause of a memory limit being reached, this is not the only reason it happens.

008. I'm getting errors about Execution time-outs.

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.