Harmonic Mixing... Seeing Key Adjustments in the Deck veiw

Yes, but since there is no "camelot key"-field, and as it is *not* the key, I don't see why it should be written into that field in the first place.

 

MIK writes Camelot keys to the tag so I don't think it's forbidden.

 

If MIK doesn't obey the specification, that is not a reason for others to do the same. Specifications exist for a reason; so that everyone knows what to expect.

 

It can also write into the Comments field. However, there is no 'Camelot Key' field. If MIK writes it to a private tag, you'd then have to rely on every other piece of relevant software picking it up. I have MIK write Camelot to the Key field, then I can sort Key and Comments seperately.

ID3 is an 'informal' standard, and as such, specifications are being broken all the time. It would be great to have better standardisation. Tracks could come with all flavours of key attached, an accurate bpm, even cue points that are transferrable between different apps. Can't see it happening anytime soon, though.

 

So are things like HTTP, FTP, SMTP, POP3, IMAP and so on, but still developers generally opt in to supporting what the informal specification says instead of doing things "the way they like" (although, for the sake of accuracy, there are still those who couldn't care less about the informal specifications say - for some reason their software tends to be the ones that generally don't work).

 

There seems to be some movement by the MIK guys to fix their wording on their licensing page:
"Good catch on the wording guys, I can see how that is confusing. I'll be sure to let Yakov know."

Lets see if they fix it ..

As for writing into the key field. People should stick to writing the key as per the standard and software like Traktor should just offer a switch to change the visual representation (take a look at beatunes for an example).

 

Go for camelot!

 

I feel that this thread needs to be revived.

Has there been any feedback from NI regarding any legal issues?

+1 for ...

1. Show the key or Camelot number under the key knob (not +/- number)

2. Show the realtime adjustment of the key/Camelot number of the track. The adjustment made would be based on the Key/Camelot number entered into the Key field ie. a simple calculation.


3. Key +/- ...... allow changes only in full key steps.

 

Other points on your post are right on cue, but I have to disagree with this one.

It is not too unusual (for me at least) to need to change the key of the currently playing song. With full key steps, this is very noticeable change. Even with the current minimum setting of 0.1 steps, "sliding" from key to another is easily noticed by the audience unless it is done over a longer duration like 1½ minutes or so. The human ear is such a magnificent piece of aural perfection that it is very hard to fool it.

What I would enjoy, though, would be a "double setting" like we have at the moment for grid positioning; left clicking would advance the setting like a "fine tune", while right clicking would advance full steps.

Furthermore I would like to comment that I find the rotary control to be very unintuitive way for modifying the key. If/when you're using an external controller, I can understand it, but if you're mainly using timecode control and need to do this sort of thing with a mouse... well - using the rotary as "a rotary" control is a pain to begin with and the +/- buttons on it are (on my opinion) way too small... I've included a mockup of something I'd find a bit more "usable".

 

Sorry there was one word too many in the last point.

3. Key +/- ...... allow changes in full key steps. This would be an option in the preferences or above the knob.

Actually I have just found out that by changing the rotary settings on my BCR2000 to
Sensitivity -- 21%
Acceleration -- 14%
I can change the key in jumps of 1.02% which is close. It does take a very fine adjustment though. It would be much better to have an option to do this easier.