Hey Keith,
I'm not sure if you've already run across this, but I'll point it out in
case you haven't:
http://blog.beatunes.com/2011/03/introducing-ok-notation.html
It seems that the company that sells 'Mixed In Key' has a patented system
that they call "Camelot notation" for assigning numbers to keys. Luckily,
their system is pretty arbitrary and I don't think it's worth considering
paying the licensing fee to use it. It starts with 1 as Ab minor and goes
through the circle of 5ths with all the minors indicated by an A and their
relative major keys denoted with a B. It seems kind of counter-intuitively
set up if you ask me (maybe that's what they were going for).
*Un*fortunately, it seems to be the standard for non-musician DJs.
I'd say this is where the dilemma is. For those with libraries already
tagged with Camelot, will Mixxx run into issues? Should there be some kind
of user preference? If there is, does Mixxx have to license that? It seems
like something that should be considered. I'm not totally sure about the
OK-notation either (from the above blog post). They claim it's a free and
open notation, so that's good I suppose. I'm not sure how many people would
be interested in it or how many already use it though.
To summarize, a) the Camelot thing should be taken into account one way or
the other and b) there is a choice to be made between a purely key based
approach as you suggested vs. a system designed for non-musicians.
Personally, as a musician, the notational system would only be a hindrance,
so I'd prefer either just explicitly saying the key or making it a user
choice. Obviously that would complicate the code to some degree...
Godspeed!
Joey
p.s. I also read (below) about someone wanting to take both beginning and
ending key into account, but Traktor (and possibly the ID3 tags
themselves?) didn't allow for it. Maybe we can leap ahead of the pack with
this one? Just a thought ;)
http://www.mixshare.com/cgi-bin/yabb2/YaBB.pl?num=1303900473
> Message: 5
> Date: Fri, 23 Mar 2012 02:56:28 -0800
> From: "keithsalisb...@gmail.com" <keithsalisb...@gmail.com>
> Subject: [Mixxx-devel] Harmonic Keys - Strategy for defining keys in
> the library
> To: mixxx-devel <mixxx-devel@lists.sourceforge.net>
> Message-ID:
> <CAEwsHoXu4n95fOGHgyd+GdBK6_Enm-_B3pj2MbT=c5alz8k...@mail.gmail.com
> >
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi All,
>
> I'm looking into strategies for marking the key for each track.
>
> For lack of better insight I propose the following:
>
> 1. Major is implied. therefore C == CM == C Major
> 2. Small m denotes minor key, therefore Cm == Cm == C minor
> 3. # == sharp, therefore C# = C#M == C sharp major and C#m == C sharp minor
>
> Can anyone provide more info - is this acceptable? - is this what
> other people use? Will the "key" code accept/produce these values?
>
> cheers
> Keith
>
>
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> 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 software Today
> http://mixxx.org
>
> Mixxx-devel mailing list
> Mixxx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
>
>
> End of Mixxx-devel Digest, Vol 70, Issue 27
> *******************************************
>
------------------------------------------------------------------------------
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
