Feedback from a Navidrome 0.64 → AudioMuse-AI Provider Migration

[brunescio]

I just completed the Navidrome 0.64 ID migration with AudioMuse-AI. Overall the provider migration worked, but I ran into a few issues worth reporting:

• Source paths: I had to enable Navidrome’s Report Real Path first, then start the migration. With real paths available, most AudioMuse tracks matched cleanly by path. Without that, several thousand tracks fell back to metadata matching or stayed unmatched.
• Setup config after migration: after executing the migration, AudioMuse redirected me to Setup, but the Navidrome server had lost its URL, username and password. “Save Configuration” appeared to do nothing. Re-entering the server details fixed this.
• Artist mappings: the migration completed successfully and track mappings were correct, but artist_server_map was empty and no server_sweep task had run. As a result, /api/similar_artists returned 404. Running a server alignment sweep rebuilt artist mappings, after which similar artists returned 200 and worked normally.
• Final result: Instant Mix works, similar artists works.

So the migration itself seems solid, but I think the post-migration setup/config preservation and automatic server sweep need some attention.

[NeptuneHub]

Hi and thanks for the feedback.

About your point I can clearly say that:

• Report real path is off course an useful precondition of each provider migration where Navidrome is involved;
• After the migration also executing an analysis could be useful to update the index, you probably solved this the other way around by trigger the sweep.

About the setup config and credential lost I need to check.

Do you have the possibility to share the full log from flask and worker container ?

Which version of AudioMuse-AI do you have ?

Edit: meanwhile I think that the new credential was empty because in the provider migration you don’t specify them. The functionality is usually needed to migrate from one provider to a different one.
The issue I think that is:

• you didn’t write the credential of Navidrome;
• the system should have write an error and wrote you to write instead of proceed;
• Proceeding with blank credential just override the credential with blank.

could be this the case ?

[brunescio]

I am on version 3.6.0. And yes, I think your explanation about the credentials is correct. I did not enter credentials for the target server during the provider migration. I was so focused on the fact that I was migrating onto the same Navidrome instance that I implicitly assumed AudioMuse-AI would continue using the existing server configuration.

So what probably happened is:

• I left the target credentials empty;
• the migration still proceeded;
• the blank target credentials overwrote the existing Navidrome server credentials;
• afterward the track mappings were present, but artist_server_map was empty and no server_sweep had been queued;
• after I re-entered the Navidrome URL/user/password, I manually triggered a server sweep;
• that rebuilt 338 artist mappings, after which /api/similar_artists worked again.

The provider migration itself had completed successfully and the track mappings were correct (23634 entries), so the main issue seems to be that blank target credentials were accepted and then replaced the existing working credentials.

From a user perspective, it would be helpful if the migration prevented proceeding with blank required credentials, or at least warned clearly that the existing server credentials are not reused automatically.

[NeptuneHub]

Yes off course I need to put a blocking warning in case the credential are not fully entered and correct. Was just to identify the bug that at this point seems very scoped.

Thanks for your report!Yes off course I need to put a blocking warning in case the credential are not fully entered and correct. Was just to identify the bug that at this point seems very scoped.

Thanks for your report!

[NeptuneHub]

For all the procedure, as alredy wrote a while ago is to do a provider migration Navidrome to Navidrome.
In details:

• first do a backup of both AudioMuse-AI and Navidrome;
• Update AudioMuse-AI first if you don’t have to the last version following all the instruction of the version you update (and if you skipped some version give a look also to the version skipped)
• then update Navidrome and leave it the time to do is stuff like update the id;

Doing this you will have ID of AudioMuse-AI that doesn’t match the ID of Navidrome. At this point you had to do a provider migration on AudoMuse-AI form Navidrome to Navidrome.

BE sure that on Navidrome you have enabled the real path (so in Navidrome, in the player list, there is the possibility to show to the player the real path of the song, this is needed).

After the provider migration do another analysis it will be needed to recreate all the index and in case some track where not migrated successfully.

Important: during the provider migration put the credential of Navidrome again. This because the functionality was initially designed to migrate to a NEW provider. So you need to put even if you’re migrating versus the same server.

[ForeignWelcome]

did the steps work perfectly just a tip dont forget to enable real path

[chr0m]

I did the migration it matched every single track based on path, But now I'm doing a rescan and it's reanalysing lots of tracks. It looks like the migration did some sort of dedupe and now it's rescanning all of the tracks that had dupes. Like I check my duplicates list and it's way tinier than it was before with the max song dupe count of 3, when I know I had some in the teens. In my backup I had 76,000 rows in track_server_map and now I only have 68,000, so it's redownloading and scanning the missing 8000, which all seem to be duplicates

[NeptuneHub]

Thanks for the feedback. Which version of AudioMuse-AI do you used for the provider migraiton? is the last v3.6.0?

I'll do a check because I remeber already addressed a similar situation related to the duplicated song in the past, but probably was related to adding a new Music Server with song in commons.

Anyway for your actual situation will be fast just to leave it analyzing those 8000 songs.

[chr0m]

yeah I used the latest version. I'm just going to leave it re-analyzing, my server is slow, only an 8500T, but should only take half a day or so I guess

[NeptuneHub]

So first thanks for the feedback, it helped me in discover this issue. I'll fix in future realease: basically provider migration do a 1:1 match, and when one song is matched leave from the list of the possible matchable.

Anyway yes, just leave it reanalyzinvg those song is the best approch.

[ffffionn]

I enabled real paths for Audiomuse-AI player as advised here, but still got "653 unmatched tracks (153 albums)" when running automatic matching. Some of these look to be full albums, but the majority are just a couple of tracks per album.

[NeptuneHub]

Hi and thanks for the feedbakc. The song marked as duplicated we discover that for the moment stay unmatched (this will be fix in future release).
Anyway talking about 635 songs the best solution is just continue and run a re-analysis.

If tyou noticed any bug (in the log?) related to this you can share and anyway I'll check and try to fix in future release.

[ffffionn]

I ran the automatic matching again, and logs in flask/worker dont flag any error.
I will run the migration and do a re-analysis- thanks for the response!

[bliks06]

I updated Navidrome to .64 over the weekend but I did not update AudioMuse from 3.4.0 because I’m dumb and forgot. I also have AudioMuse set to do an analysis over night.

I woke up this morning to AudioMuse reanalyzing my library, which is because of the Navidrome ID change. And that’s cool, I’m fine just letting it run through again.

My question, will I need to do anything after the new analysis is done or will Audiomuse remove the old file analysis when it’s done? Hopefully that makes sense and thank you for a super cool program!

[NeptuneHub]

You are not following nothing that I tested or analyzed.

If you let the new analysis finish and then you run Administration > Cleaning functionality enabling the orphan cleaning you should return at a stable situation assuming that the new Navidrome id are totally different from the old one.

[joshp23]

This went very smoothly for me. Updated Audiomuse-AI plugin and server to the latest versions, backed up both databases, updated Navidrome, enabled Real Paths and then began the migration. I ran a full scan and then a database cleanup. Very nice. I had a handful of albums not migrate, no big deal.

Thank you for your work!