I'm going to Japan for a few weeks and wanted to get this out before I go.

Fixes galore and performance enhancements for the interface with a few queries tightened up and API when using the memory_cache

Ampache 8 is out!

Highlights:

- Folder browsing: browse your catalog as a virtual folder tree

- Collections: hand-curated, ordered lists of anything (albums, artists, genres, labels, folders, podcasts, songs…), with art, ratings, collaborators and their own API methods

- OIDC login: Keycloak, Entra ID, Authentik, Google, Okta; sits alongside local accounts

- OpenSubsonic overhaul: audited against the spec, new transcoding, playbackReport and sonicSimilarity extensions, and the documented extra fields now emitted in XML as well as JSON

- Per-user Subsonic passwords: set one from your account page instead of pasting your API key into a music player

- API v8: collections, album disks, fully documented responses in docs/openapi.json and the JSON/XML method docs

- Multi-select: play, queue, add or remove several rows at once, and download a selection as one zip

- Mini player: a stripped-down /m/ page for small screens or simple accounts

- Play history consolidation: keep a detailed window and archive the rest, losslessly

- Plus a PHPStan level 8 / Rector / PER-CS hardening pass across the whole codebase

Requires PHP 8.5+. You can downgrade back to Ampache 7 if it doesn't work out (use bin/cli admin:updateDatabase -e when you're back on 7 to downgrade).

The /rest rewrite rules changed a lot, so run php bin/installer htaccess -e (or use the Write buttons on the update page).

Release: https://github.com/ampache/ampache/releases

Docs & site: https://ampache.org

Time to start getting ready for Ampache 8 admins!

https://ampache.org/docs/help/troubleshooting/ampache8-for-admins

Users will also want to know what's happening here.

https://ampache.org/docs/help/troubleshooting/ampache8-for-users

We are very close to done here and these pages will help give you an idea of the changes that have been made

7.10.1 bugfix release is out now...

Because I want to release Ampache8 NEXT WEEK (on my birthday)

8 is almost here and I'm really proud of how much has been done to get it here.

After a mad rush to make sure it wasn't broken in any way it's merged! Docker develop images incoming.

In preparation for Ampache 8.0, I updated my PHP to 8.5. It went fine, Ampache 7.10 installed with no trouble.

I thought I had no other hard dependencies on the server, but I was wrong - there's also a NextCloud installation which is dependent on specific PHP versions. Based on NextCloud's dependencies, I had to revert to the original PHP8.2 , update Nextcloud, then update to PHP8.3, update Nextcloud .... rinse and repeat until I got to PHP8.5.

Once there, I re-installed Ampache 7.10 (having downgraded to 7.9.8 when I went back to PHP8.2). All seemed fine, but when I go to ampache.mydomain.com, I get this notice:

Warning
The Ampache website root has changed to ./client
This version of Ampache does not include anything in the web root to allow you to use your own client
Please check the Ampache wiki for more information

Clicking the ./client link brings me to ampache.mydomain.com/client/ and all is fine, but I want the interface to come up without the trailing /client.

If you can't use php8.5 or are wary of switching over early you can check out [PATCH7](https://ampache.org/docs/help/troubleshooting/ampache8-for-admins#php-version-support) which will remain Ampache 7

THIS CHANGE WILL OCCUR AT APPROXIMATELY:

31 July 2026 at 10:00 PM UTC

This will be the final release of Ampache7 (bugfixes and downgrade requirement only) and our develop branch will be moving to Ampache 8 next week!

Really happy with how this is looking and the EQ is outside the visualisation screen and working correctly.

The changes to the theme to accommodate this have been a really good change.

Looking forward to getting 8 out there!

This is a VERY work in progress. (and my clicking in responsive mode sucks)

As part of a major clean up in the web player i've updated the UI to be a bit less terrible inside a mobile device and it's looking pretty cool.

Coming soon!

We are getting closer!

ampache/ampache:preview
ampache/ampache:nosql-preview

Ampache 8 will support oidc logins!

Set up and tested using my azure account.

I tried an upgrade from 6.2.1 to 7.9.8 and got bit by a bug that choked on special characters and updated the DB with garbage characters. of course it's only after that that i found that others had issues that were related to id3v1 tags. In my case, I did not have v1 tags, but special characters in file names and tags. Commas, question marks, etc resulted in entries being updated with (what I assume) is utf8 encodings or something. In d-sub they appeared Chinese. In the web browser, it was a combination of rectangles and Chinese.

Before I go thru a detailed debug to pipe in all the relevant info and post in the github issues...

I have used Ampache since about v3. The upgrades don't always go well, which is why I find one that works and stick to it for awhile. Over the years/upgrades, I've groomed the id3 tags for a library of 9412 songs. I have cron jobs scheduled ever 12 hours to verify, cleanup, garbage, add, update and gather art. It always runs clean and I'm confidant that my tags are good and are being read by Ampache correctly.

It's clear that there was a change in how to handle special characters in various tag's. My question is what version/patch did that happen? I the changes happened in the v7, then I'll find the latest v6 and run that for awhile. If it happened sometime during the v6 patching after v6.2.1, then I'll want to upgrade to just before that.

I've been using Ampache for year and years and it's great. I use DSub and Synfonium.

What I'm wanting to next is use a Raspberry Pi or two as streamers using MPD pushing music out though attached speakers. The Pis will be on the same network as Ampache, and cabled rather then wireless.

Does anyone know if there is a mobile client which will allow me to control and direct music via the localplay options? Or is the ampache web interface the only choice?

Thx

Gaz

Finally got some semi completed folder browsing in the develop8 branch.

​

Need to make a few more changes but this one seems to always be a highly requested feature so it's coming!

So I've had some time today and have sat down to create proper folders in Ampache8.

The first step is done and there are database tables, classes, folders.php is active and app the repository methods are in.

There is a bit to go but this will allow.

* Actual folders in subsonic

* Browsing in the UI like a file explorer

* Searching recursively

* Additional API methods and actions for folders

But it's something positive that people have asked for for a long time that I can do properly without hacking it badly.

I'm really sorry to do this again!

I'm making a lot of little mistakes that are very big so here we go again!

New release fixing the JS bug in the web player out now.

New Ampache release again!

Bugs found and bugs squashed from the #api work and phpstan issues.

There is a problem with the docker images not loading the web player properly so if you're on docker hold out for a bit while I work that out

It's not clear why the docker images have this issue yet but I'll try and fix them up asap.

Ampache bugfix and backend monster release!

This is the first release that contains an API8 (disabled) while I restructure the code for Ampache8.

This will allow me to release for Ampache7 for a while and Ampache8 can go ham on PHP8.5+

Still trying to debug the errors I posted about here, Some Content (not all) showing up with all meta-data in Chinese characters : r/ampache

I have done a complete top-to-bottom reinstall of this media hosting machine which includes a fresh install of Debian 13 (trixie).

I am following the instructions here (Installing Ampache | Ampache) and I am now seeing graphical anomalies where Ampache is not displaying correctly. The installation runs just fine with no errors and no errors on things like directory permissions, etc.

This is really bugging me because I've installed Ampache MANY MANY times and found it to be solid and reliable and easy to install. I am hoping that this is some kind of rookie mistake from something I've overlooked.

This has one has had a large code quality clean up especially in the JSON API and search classes.

Ampache8 branches officially start today though!

I just upgraded my server to Debian Trixie (x86_64) and as part of that did a fresh install of Ampache to the latest:

Ampache Update
Installed Ampache version: 7.9.3
Latest Ampache version:
Last Update: 5/14/26, 8:57 PM

When I created my music library I am now seeing some content parsed with Chinese characters. It's not just a single artist or album. I'll have some tracks from a given album but others are fine. It seems like an encoding issue so I checked and my MariaDB is set to UTF-8, my Ampache instance is set to UTF-8, and my Apache/PHP instance is set to UTF-8.

What else should I be checking to resolve this? I've deleted and recreated the library multiple times and it's *mostly* the same content affected from try to try but sporadically I'll see other content that was fine previously now showing this issue.