Show missing tracks

[Leo1906]

I have quite some tracks missing in AudioMuse that are present on my Media Server (Lyrion). I found some of them by accident and they look good and play well.

`
"[2026-07-19 09:42:43] Found 34315 total tracks on media server",

"[2026-07-19 09:42:43] Fetching all track IDs from database...",

"[2026-07-19 09:42:43] Found 33914 tracks in database",

`
As you can see there are almost 400 Tracks missing.
Is there an Option to find out which songs are in the Lyrion DB but not indexed?

[NeptuneHub]

Hi and thanks for the feedback. First of all, can you confirm that you have audiomuse-ai 3.0.1 ?

The point is not missing track but about unique track: AudioMuse-AI is start counting the unique track and not all the tracks.

To check that a track is unique in 3.0.1 it had to pass both this checks:

• Cosine Distance on Musicnn embbeding, it should be less than 0.01 to be similar (This was introduced from v3.0.0)
• Duration of the track, it should have not more of 7 second difference (This was introduced from v3.0.1).

So in short if a track SOUND similar, and DURATION similar, it counted once.

This is needed because from v3.0.0 you can potentially attach more than 1 music server to the same AudioMuse-AI instance and we want to avoid to re-analyze twice tracks that are already present on another music server.

This is also a first step to possible implement a centralized catalogue.

In short, if you have v3.0.1, those 400 tracks should be:

• Most of them just same song, maybe in multiple album
• Some error could still be present, like different song but very very similar => With the v3.0.1 this error should be very minimal.

[wirrunna]

Back in MIP there is an option to list duplicates.
A typical case is when you have an artist "Best Of" album and several of the albums that feature the originals.

A function or plugin to list duplicates would be useful.

[NeptuneHub]

I’ll think about a way to list for future release, if you think it’s important.
For now I’m improving the dashboard to better show that does song are not disappeared but only marked as duplicate.

[wirrunna]

Thank you for your explanation, I do understand that for a music playlist making system duplicate tracks are a minor nuisance and should be ignored.
A list of ignored duplicate tracks is more for music library housekeeping than an AudioMuse-AI concern and is certainly not a show-stopper, just a nice-to-have.
My background was mostly in factory and mine accounting and engineer's stores systems and I inherently feel that duplicates should at least be reported in an exception log.

[Leo1906]

Ok I just updated and the number of songs went down drastically:

Lyrion is my only connected server.

While I was expecting a lot of duplicates this seems way too high for me.
Is there a way to manually check some of the "duplicates"?

Also I still dont know how to identify tracks that Audiomuse has not analyzed for what ever reason.
I came across some tracks in my library which I cant find in Audiomuse

[Leo1906]

I saw that you pushed another update. Looks better now:

3k duplicate songs - yes I believe you, sounds reasonable.
But what about the now missing 8k songs? They have not returned to the "unique in catalog" section. Do I need to re run the analysis?

Edit: I just read the release notes again. I think I missed that part.
I am running a analysis run now again and it seems to do something. Unfortunately it also seems to need to do a real re-analysis for the files it falsely flagged as duplicate. So this may take some days ..

Also what is really considered orphan? This are only files that are present in Audiomuse and none of the servers right?
But this is the wrong way. I need to know which files are present on the server and not in Audiomuse and a way to trigger a scan of them again.

And I am wondering how did those orphans even spawned? Must have been through the latest updates because the music on the server has not changed since some time.

[NeptuneHub]

Thanks for your feedback. First step before an update I always suggest to take a backup.

After that the step are:

1. after the update the flask containers startup take around 5 minute (sometime less, sometimes more depending from hw and library size) and it update what it think is a duplicate;
2. after the startup, also a run of cleaning task can help in remove that orphan song;
3. Re-run the analysis: the dedup algorithm work by deleting the data of song that think that are duplicated, so now that the fix of the algorithm mark less song as duplicate, the false duplicate (not the entire library) need to be re-analyzed.

unluky this duplicate result are very library dependant, so I didn’t had the chance to discover that on some library there was so many duplicate before rhe release.

This 3.0.* release is a transition release where we introduced many architectural change. I remember again to everyone to make backup, and to have patience, I’m working for improve this.

Just a legend in the state:

• duplicated song are song that the algorithm found as similar;
• orphan are song without data. It can happen that a song become an orphan OR because is not finended on the music server OR because need an analysis.

Also:

• analysis functionality solve the orphan for missing data;
• Cleaning solve orphan if not linked to any music server anymore.

[Leo1906]

I did not mean that offensive at all. I have all my Docker Containers backed up regularly but somehow it did not work the last time .. and I just did not check if the backup was successfull. So that totally on me.
I appreciate the work you do and I will report back when its done with the result :)

[peterbuga]

@NeptuneHub I updated docker with every release, despite this since update post 3.x.y I have orphan tracks. is it possible to just re-attach the songs to the only server that was setup before? the newly listed songs are the ones that were analyzed after 3.x.y update.

i'm interested if only a sql update query could re-link the orphan tracks.
(removing orphan and re-analyze is not quite an option, took a long time to get here, everything was cpu-analyzed)
thanks!

[NeptuneHub]

Unlucky not, the only way to get them back is restoring a backup.
Can you share some examples of orphan track or if they are of same particular genre? It’s quite strange that it removed so many.