Comment 11 for bug 1831227

@Uwe - I noticed your work on aoide (https://gitlab.com/uklotzde/aoide-rs and https://github.com/mixxxdj/mixxx/pull/2282) - thank you for your efforts on this.

Screenshot looks like what I'm hoping for, but I am not sure how it works, as I dont know how to try/enable it - is this included in current 2.4 alpha builds from http://downloads.mixxx.org/builds/master/release/ ?

My use case is similar to what OP described - managing timbre,color,energy,style,mood and similar attributes, for example, as defined here: https://developer.spotify.com/documentation/web-api/reference/tracks/get-audio-features/

Extending existing SQLite schema without impacting performance would also be relatively easy to do, by adding an additional table with a PK/FK relationship using "id" - that would be created only if user enabled a feature "Custom tags" in settings. Users that do not explicitly enable this, would not even know it's there. Performance can be further protected by adding a flag field to the "library" table, that would indicate if the track has any custom tags set. If it does, a single SQL query would be executed on the indexed "id" field when reading data for the track - with minimal performance impact. If the flag is not set (eg. the user did not enter any custom tags for particular track), no query is executed, and there is absolutely no impact on performance. It is also reasonable to expect that minority of the tracks in most users collections would have any custom attributes set, even when the feature is enabled.

I design databases for living, please let me know if I can be of assistance.

But if I understand correctly, your aoide work is intended to (one day) replace current SQLite database completely?

I agree that displaying additional/custom tags/fields as separate columns is not feasible for several reasons. Possibly showing them on mouse-over would be an option? In a window, or as an overlay over the next track in the list...?

Releted to the library work, and also custom tags, is another use-case I have as a both digital and a vinyl DJ. I have over 5000 records, that obviously don't have a audio file to be scanned. But I have almost exactly the same need to manage my collection of records. Do you see a possibility in the future to be able to add a physical media to the Mixxx library? If the custom tags are implemented, I could then manage attributes such as location, format, etc.

Thank you,
Andrej