The embedded Flash player only plays audio.
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.) To work around this limitation, you can enable transcoding in config/ampache.cfg.php for each existing file type.
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.
Either your Ampache is too old or your Amarok is too old. Ampache must be 3.5 or higher and Amarok must be 2.1 or higher.
When Amarok 2.x was first released, it did not recognize .m3u playlists. This was fixed in later versions.
Your ACLs are not set up properly. Ampache/Amarok don't lie.
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.
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.
This is a known limitation; the alternative is for Various Artist albums to display as multiple albums, which is unacceptable. If your files are tagged with the correct year this will help cut down on the frequency of occurrence, but not 100%. There is no way for Ampache to programmatically determine from the standard raw metadata whether “John Farnham, Greatest Hits, 1987” and “Richard Marx, Greatest Hits, 1987” are genuinely supposed to be separate albums or not, since ID3 (for instance) doesn't encode a concept of “Album Artist” which we could key on. Even if it did, it still wouldn't be 100%; I have seen cases where an album and an EP by the same title were released in the same year by the same artist.
With 3.6 and newer there's an additional constraint based on unique IDs from MusicBrainz metadata that will split them correctly if the albums were tagged using a tagger that writes the MBIDs to the file (such as Picard).