[FEEDBACK] Show more song tags in a dropdown list.
1. What were you trying to do? I tried to pick a song from the dropdown list.
2. What did you like? Everything actually, just got one visual thing I think needs to be improved.
3. What was confusing or could be improved? I know that at some point Navidrome or Jellyfin authors will add this, but right now I am using web-ui of AudioMuse-AI to use all the features.
I got multiple versions of the same song, it's included in tags such as album name or some additional tags, but when I select artist, ui offers me to choose the song, but since song name is the same, song can be from different albums (LP, live version, demo, etc - they sound different), so I gotta guess which one I need to choose.
My idea is to add album name under the song title in dropdown list or some way to let the users know what album is song taken from.
Example:
When the song have exact same Title and Artist my expectation is that the song is the same. This means that also the embbeding vector used for the sogn path is the same (or very near to be the same).
This means that selecting one, or the other, should not make the difference. Even because in song path, similar song or song alchemy those song are then deleted as duplicated.
Maybe a possible improvement that I can do is remove same Title&Artist duplicate from the menu to avoid this kind of confusion. What do you think about?
I noticed the same thing where I had 5 or 6 entries show--one was the studio version and the rest were live versions. They all show up on somewhat different spots on the Music Map (one live performance being more acoustic than another, for example). I was just messing around and not actually trying to do anything, so didn't really impact me but figured I'd chime in that in my case the songs are (somewhat) different fingerprint wise. So maybe bringing in Album title in the dropdown would help clarify in that case? I can imagine if someone was a Grateful Dead fan that they might have almost a hundred versions of the same song title depending on how many live albums they have.
Again, just thought I'd add my perspective in case its of any use. Great tool and thank you for this!
Hmm, I guess just differentiating based on title and artists isn't sufficient then. @NeptuneHub having multiple albums with the same track title (but representing different recordings/versions) sounds like valid metadata (e.g. albums from different concerts, where the concert name is not included in the title), but duplicate tracks is just a user error. So I guess maybe we should only filter based on the vector, and not based on tags at all. Or keep filtering based on the current tags (to avoid two different live recordings playing in a single mix), but definitely show the album in the dropdown too.
Thanks for the feedback, I have additional question:
Are you testing on jellyfin or Navidrome ?
Different studio version/remix/instrumental and so on, have some wording in the title of the original file ?
Like NeptuneHub - My super song [Remix].mp3 ?
I’m thinking that maybe jellyfin/navidrome look at the metadata and not at the name of the file itself, so when AudioMuse-AI ask for title it have only “My super song” without “remix”, and for this reason all appear the same.
Just to recap, if is the same exact song that appear multiple times because you have in multiple album is one issue. If there are actually different song (a remix, an instrumental version, so something that relally play different) and then appear with the same title is a different issue. In the first case we need to try remove the duplicate, in the second case we need more data in the title.
Can you help in understand better this?
@Chaphasilor any idea and suggestions on your side? Now I have my homelab down and I have difficulty to get two version of the same song to test (also I don’t have Jellyfin or Navidrome running xD)
In my case, my library has all been tagged with MusicBrainz Picard, and many live albums are named without anything special in the track titles, because the standard there is to put in the disambiguation field, which at least for me does not go into the file name or tags. So A Pirate Looks At 40 is the name and title tag on both the studio album and the live album, but they are different recordings. So really using the built-in metadata tags, Album is the only field I can think that would allow you to easily differentiate based just on tags. But I’m just providing info, so whatever you think is best 😄
I just migrated to Navidrome a few days ago, but my naming worked the same on Jellyfin and when I was on Plex as well.
I'd be interested in helping with this feature. Showing more song tags in a dropdown seems like a nice UX improvement.
A few questions to clarify the scope:
- Which tags should be displayed in the dropdown (genre, mood, tempo, etc.)?
- Should the dropdown be sortable/filterable?
- Is there a specific component library being used for the UI?
Happy to take a look at the codebase and propose an approach.
Hi! Thanks a lot for looking into this, I always appreciate your help.
The main challenge is that the same track can appear in multiple albums, and sometimes the title alone doesn’t show whether it’s a remix, instrumental, etc. So instead of displaying Artist + Title, we should show Artist + Album + Title to help users distinguish them.
Key points:
- We need to check how each media server (Jellyfin, Navidrome, Emby, Lyrion) returns album info and update the corresponding mediaserver.py integrations. We may already have some of this data since the analysis seems to work per-album.
- The search-related features should use a shared component that also displays the album. I haven’t built a reusable component for this yet, so creating one and using it across the different features would be great.
The hardest part for me is testing across all media servers to avoid regressions. It’s important that missing album data never breaks functionality, if the album isn’t available, it simply shouldn’t be shown.
This is the minimum needed for the feature, but if you’re able to make the field sortable/filterable or add extra details, that would be a great bonus.
And if the implementation requires storing more information like the album name (it’s not stored for now), please add a new album table instead of modifying existing ones with the same id as a key. On startup, the app should check if the table exists and create it if needed.
Thanks again for your help!