Mixxx

Bug #1831227
Comment #13

Comment 13 for bug 1831227

Revision history for this message

afalout (andrej-falout) wrote on 2020-08-16:

#13

Thanks for your reply, Uwe.

I'll provide feedback as soon as it has been merged & compiled for Alpha build.

>> 'each custom tag already a normalized "score"'
Is this to say that your implementation of custom tags does not allow any values not between 0 and 1 - including alpha characters?

Regarding number of track expected to get a custom tag - I did say "minority of the tracks", not "only a few".
In my collection is about 10000 digital media tracks; for my mixes and gigs, I plaid over the years (more then once or twice) perhaps a 1000. That is in most likelihood a maximum number of track I would ever want to custom tag. I started DJ-ing professionally somewhere around 1985 and got to know at last few hundred other professional DJ over that time. Unless there is some automated system involved in populating custom tags, I will eat my SL-1200 if more then 10 DJs I know would custom tag more then few hundred of there tracks... :) Of course, I could be wrong, but I don't think I am far off.

Looking at Mixxx 2.4 beta SQLlite db schema, I do not see any table that would hold custom tags? If you are referring to Aoide schema, keep in mind that my comments where in response to your statement that "...unfortunately, the legacy, database-centric table views in Mixxx are difficult to extend without major performance impacts". (NB - SQLite database distributed with 2.4 has no views defined).

While I do understand your motivation to create a standalone, shared and reusable repository with Aoide (that even the Traktor Product Management seems to have an interest in, see https://www.native-instruments.com/forum/threads/metadata-handling-multi-value-tags-i-e-more-than-1-genre.327465/), an API front-end on top of a RDBMS will never have performance advantage over what you call "legacy database queries" - just the opposite.

RE Managing physical tracks: you described is as I would expect it to be, and in essence similar to way Mixxx does (except that it moves all tracks it cannot find in "missing" folder, making them unusable for searching)- but how does one enter them in the db in the first place? No file, no scanning, no database entry. I currently use Bash scripts to load my Discogs tracks data directly in the SQLlite db, but they end up in "missing", and also without the custom tags they are of very limited use...

Please let me know how I can help - I'm not a programmer but have extensive experience with database design, and I'm reasonably good at scripting and testing. And I'm very keen to see custom tags implemented.

Thanks,
Andrej

Thanks for your reply, Uwe.

I'll provide feedback as soon as it has been merged & compiled for Alpha build.

>> 'each custom tag already a normalized "score"'
Is this to say that your implementation of custom tags does not allow any values not between 0 and 1 - including alpha characters?

Regarding number of track expected to get a custom tag - I did say "minority of the tracks", not "only a few". 
In my collection is about 10000 digital media tracks; for my mixes and gigs, I plaid over the years (more then once or twice) perhaps a 1000. That is in most likelihood a maximum number of track I would ever want to custom tag. I started DJ-ing professionally somewhere around 1985 and got to know at last few hundred other professional DJ over that time. Unless there is some automated system involved in populating custom tags, I will eat my SL-1200 if more then 10 DJs I know would custom tag more then few hundred of there tracks... :) Of course, I could be wrong, but I don't think I am far off.

Looking at Mixxx 2.4 beta SQLlite db schema, I do not see any table that would hold custom tags? If you are referring to Aoide schema, keep in mind that my comments where in response to your statement that "...unfortunately, the legacy, database-centric table views in Mixxx are difficult to extend without major performance impacts". (NB - SQLite database distributed with 2.4 has no views defined).

While I do understand your motivation to create a standalone, shared and reusable repository with Aoide (that even the Traktor Product Management seems to have an interest in, see https://www.native-instruments.com/forum/threads/metadata-handling-multi-value-tags-i-e-more-than-1-genre.327465/), an API front-end on top of a RDBMS will never have performance advantage over what you call "legacy database queries" - just the opposite.

RE Managing physical tracks: you described is as I would expect it to be, and in essence similar to way Mixxx does (except that it moves all tracks it cannot find in "missing" folder, making them unusable for searching)- but how does one enter them in the db in the first place? No file, no scanning, no database entry. I currently use Bash scripts to load my Discogs tracks data directly in the SQLlite db, but they end up in "missing", and also without the custom tags they are of very limited use...

Please let me know how I can help - I'm not a programmer but have extensive experience with database design, and I'm reasonably good at scripting and testing. And I'm very keen to see custom tags implemented.

Thanks,
Andrej