This is great to start talking about this! 1. "key analysis" -
As Albert points out, there's various tools to do this automatically, so I think a good summary of them, and what strategy they notation they use, and where they store it would be a good resource. Its also worth remembering that these tools are roughly 40/50% accurate at best, so along with that, many users may choose to manually update their library. As this summer's GsoC project includes a key analysis proposal which seems highly popular, its quite likely Mixxx will have its own automatic contribution in the coming months - this resource would be of great use for this project. Perhaps we will need to have an option in preferences which supports the various strategies, in a similar way that most mp3 software supports different directory structure strategy? 2. "storage and display" - Mixxx already shows a "key", so I'm personally happy with that - it would be nice of course, if the "key" is stored in the files metadata somehow so in the event of corrupted database, or even just transferring some files, the information goes with it. And similarly with display, I'm happy with the current solution, which is just a string - this leaves it open for the user/other software to define. On a side note, I've just installed RE3 (which works on linux!) and I'm running it on my library - so far looks like its using a notation like the one I describe above. Maybe we need to do a poll of everyone on the mixxx website to find out what notation they're using, and if enough people are using the A1, B1 Camelot notation, then we can add an option in preferences? On 23 March 2012 10:48, Jens Nachtigall <nachtig...@web.de> wrote: > Hi, > > Am 23.03.2012 16:45, schrieb Joey Dodson: >> >> I'd say this is where the dilemma is. For those with libraries already >> tagged with Camelot, will Mixxx run into issues? > > As long it is stored in id3-tag, I think, this must be the musician > style anyway: > http://www.id3.org/id3v2.4.0-frames#line-385 > Of course, programs like Mixed in Key do also allow to write the camelot > key in front of the title, e.g. "10A - songtitle", but in order to be > useful for "automatic" key suggestions/searches and such, mixxx must use > the "key" field (database or id3) anyway, I think. > > As for how to display it, I think that there should be an option for > allowing the musician notation as given in the id3 tag or camelot system > or OK notation: http://www.beatunes.com/open-key-notation.html > Doing so with a "delegate" class as Albert suggested seems to be a > pretty straightforward way. > > > regards, > jens > > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > http://mixxx.org > > > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel -- keithsalisb...@gmail.com ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
