Key Text Overwrite Issue

This issue plagued many and it was impact many users here.

Was this issue supposedly resolved on 2.8.0? The release notes does not specifically mention this. I did not test for this on 2.8 but in testing 2.8.1 i did notice the Key Text were being overwritten and the problem is still present.

 

This is on 2.8.1 I did more testing and can confirm the Key Text field which is being overwritten when the track is loaded. Very disappointing.

 

Yep, still doing this in 2.8.1... So annoying, I spent a LONG time keying my 11,000 strong track collection manually and it is just ******* it up...

 

I am using 2.8.0 and Traktor does not overwrite my MIK keys when loding into a deck.

My order is:

Analyse in Traktor -> Analyse in MIK -> Consisty check in Traktor -> Traktor uses MIK key instead of it's own analysis

 

This was happening to me on 2.6.5, maybe 2.6.1 from memory too... So annoying... I have been using the key text field as I originally processed my collection with MIK... Had stopped using MIK as I found it more accurate to do it myself... Then noticed that all the files I had keyed myself or re-keyed of traktors had been overwritten... sometimes when i loaded a track, sometimes just opening traktor... basically, there is no consistency or pattern that i can see... frustrating to say the least... especially as the key algorithm is not very accurate in traktor... so a lot of my files are now just flat out incorrectly keyed...

 

I confirmed the Key Text overwrite issue still plagues 2.9. NI continues to ignore widely reported bugs from past releases.

 

n.i. does not surprise me

 

Hey so I have been back and forward with NI about this issue... It seems that it is a user selectable preference... I will post their response so that you can all check what you have it set to... There is a way to get the changed keys back too, but that depends on if you have a decent back up to go back to...

Cheers,
Yogi

FROM NATIVE INSTRUMENTS...

Traktor offers key detection.

The feature is explained in the manual chapter '5.10.2 Analysis' and from there
links to '13.21, Analyze Options' & '15.11, Harmonic Mixing'.

Depending on your current Traktor settings, Mixed in key tags may be shown, not
shown, and eventually even overwritten.

You can actually configure this behavior freely, but you cant get back old key
tags once they were overwritten (so in this case you need to re-analyse those with
your prefered key analyser).

You actually can configure this behavior, but you don't get back lost tags caused
by using the wrong configuration.

In order to preserve tags generated by any 3rd party analyzer, please refer to
your manual.

Citing from your Traktor manual page 200:

--
Musical Key

TRAKTOR now automatically detects a track’s key which can be displayed in either
classical musical notation or Open Key format. Which notation form is best suited
can be controlled via the below settings:

▪ Displayed in Traktor:
Select the notation to be displayed in the Key column of the Browser from this
drop-down menu. This option can be changed at any time and will change the way all
Keys are displayed in TRAKTOR. Available notations are:
◦ Musical
◦ Musical (all sharp)
◦ Open Key

▪ Written to FileTags:
Select the notation to be exported with the metadata of a track when
exporting it. Available notations are:
◦ Musical
◦ Musical (all sharp)
◦ Open Key
◦ Key Text

-------------------------------------------------------------------------------
If you have previously utilised third party software applications to identify the
Key of your tracks, it is recommended that the Key Text option is checked to
ensure that your ID3 information is unaltered when exported from TRAKTOR.
-------------------------------------------------------------------------------

So you need to use 'KEY TEXT' for the 'written to file tags' setting, otherwise
your 3rd party key tags get overwritten by the ones Traktor detects.

 

Thank for trying to help.. when did support tell you this? Did you try it and does it work for you?

I looked at this many times in the past as i believe this was brought by support in the past. I can assure my setting does have written to file tags set as key text and yet i still get the keys of songs randomly overwritten.

 

Yeah it has definitely solved it for me, that I am aware of anyways... I have not noticed any more changes in the 'key text' column. I was able to get my old collection back too (the old key text inputs), I simply imported a back up collection previous to 2.8 (2.6.1 I think?), I went to a back up collection about year old... So I still have about 1 years worth of keys to manually fix, but thankfully it is only 500-1000 tracks or so, not 11,000+ songs like it was before I was told about this...

Silly question, are you using 'key' or 'key text' column? If you use the 'key' column, there is no way to avoid Traktor being in control of that column... If you use 'key text' column, then as long as that is set correctly in the preferences it should work... Theoretically...

Hope this all helps you anyways. Such a major pain in the ass as I DJ quite a few gigs in different styles so need my collection to have some sort of order, ha ha lol

Best,
Yogi

 

Yes i am looking at the key text field ... glad it worked for you. I am gonna reset all keys and give it another try. Just does not make sense why sometimes the key text field gets overwritten and other times it does not. There is gotta be something wrong.

On another note... i also have seem the comments 2 field get overwritten with the comments 1 field. In my opinion there is a huge data base issue that could impact a lot of other things as well as the keys.

 

I am using Traktor Pro 2 ver 2.9.0 on a 2009 Mac Book Pro with 8gb of memory, also installed on this laptop is Serato DJ 1.7.8. The problem or question is, Traktor is overwriting my (Key Data) in Serato DJ, how can I prevent this from happening?

 

let me get this straight.

we have been reporting this issue in the forums on countless threads. no solution was given or found.

some of us have reported it directly to support via tickets. no solution was given either.

it was reported in the 2.7.5 beta and supposedly addressed by removing that routine that began "writing tags" whenever you accessed a history playlist in the archive node. it was not killed completely, but improved a lot, i've seen much less keys "overwritten". i put it between quotation marks because i still think it's not overwritten but recovered from somewhere else.

anyway, now i read in this post, that the solution to avoid traktor overwriting key text, is by specifying in preferences that it has to write the key tag in the field we want to keep safe?

i don't know how do you guys see it, but to me it makes absolutely no sense. i've tried to change that setting anyway, just for the sake of trying, but what the f***?????? what's the logic behind this? seriously i don't get it.

 

This was an issue for me on 6/8/15 and I called their number and waited 15 minutes to be told by the person on the phone that I need to contact Mixed In Key as it is a third party issue and basically it was an error on their end. Essentially NOT OUR PROBLEM WE CAN'T HELP YOU. I started to dispute it and magically got disconnected. After writing an email to them remind them of the amount of money I have spent on their products and reminding them this is an issue I have seen repeatedly in forums yet no solutions.... this was the response I received:

------
When you are analyzing a track (async instead of importing), you will need to
disable the analyze feature and select Special. You can select what Traktor will
analyze (uncheck Key to retain the Mixed in Key tag)

This is the current work around for the issue you are experiencing.

Benjamin
Native Instruments Support Team
------

they they know it is an issue because there is a "work around"

I did get it to work by following the above (after deciphering the half ass response of directions I received).

The only reason I am posting this now is because I just re-installed everything and having to to do it all again and I forgot how to do it.

So point being... THE ISSUE HAS YET TO BE FIXED. Thank god for work arounds

 

This issue has been around for years now. Its actually much more than just the key text. Other parts of the date base have been overwritten as well.

Basically NI has some major database issue that they do not want to admit too . Many of us on this thread have opened Tickets on to be give the same run around by support. This is a clear example of poor support that should be improved.

My last communication with support in augusts was this from Stefan:

"Your satisfaction in this case clearly gets measured in a fixed bug and I fully
understand your frustration if you don't see the desired result. I'm with
Native Instruments for more than 10 years, so I know all colleagues who are
supporting Traktor as long as they work here. I can assure you that all of them
are burning for their product. They carry on the torch from you as a customer
into the rounds that have to decide what's happening next. In a perfect world
we wouldn't see any bugs in a software but that's not reality. So things have
to be prioritized, this means that other things might get postponed, for
several reasons. So as you might notice, I can't provide you with any further
information regarding specific bug fixes as there has nothing been announced"


What the above probably means ...They don't know how to fix it.

 

Only it's not a workaround if you've already analysed the vast majority of your library with key switched on, as most of us who are having the issue will have. It's only a workaround for any new music added to your library.

To me it means they can't be bothered fixing it. It's not a performance related bug and it's not going to affect Traktor profits either way. It can't be that difficult to resolve. It's a propriety Traktor tag and system populating fields it shouldn't be.

 

Sorry to have to ask here, but bow do we start a new thread topic?

 

Here the thing about this issue that concerns me. It clearly a data base issue. It may not on the surface look like a major performance issue. But if things like Key text and comments are being overwritten than there could also be other import data field that are impacted by this bug that are not obvious and perhaps cause you to crash or freeze.

Perhaps this database issue is also the same issue that causes the well know Freeze on load issue that cause many users to crash.

 

I don't see it to be honest. The key text issue has been present since key detection was introduced. The performance issues are only present in more recent version of Traktor from what I can tell.

 

Anyone know if the key text issue was resolved? I been spending more time on other software and finally have some down time to test 2.11.

Been on 2.6.8 all this time. I hope the key text issue was resolved in 2.11.