Initial Key, BPM updating in Cross Library when told not to

[branchh]

My Cross 3.3.10 settings:
Track Analysis:
Key - off, Gain - on, BPM - off, Peak - on
Save changes in Tags - unchecked

source content:
video MP4's
Mixed In Key sets Initial Key & Energy tags
Tracktor sets BPM; this is standardized between audio & video source libraries (Traktor is used with AIF & MP3 320k audio content)

When I "add MP4's to Cross collection as track"
Then drag that new track to a deck
it goes through analysis process which establishes:
updatee BPM, updatee Key but looks to be only save in Mixevibes database and nothing appears updated in MP4 file tags (which is desired)

But, I still have to manually go through and change the Initial Key values back to originating value from MP4 file tags which is annoyingly manual

I understand that you need to establish your own beatgrid for the MP4, so revising the BPM is understandable in your database

Any comments regarding this behavior as I have not told Cross to analyze Key or BPM, but it appears to do it anyways

[DJ Vintage]

Not 100% sure, but I think that if you drop a new track in your collection in your deck BEFORE it's analyzed, it will analyze everything.

The settings for analysis that you mention are for the "user-defined" option of analyzing.

What you can try is loading a few new tracks into your collection, selecting them (you can easily do that by sorting on the "analyzed"-column) and then right-clicking while the tracks are selected and chosing "Analyze (user-defined)" from the Analyze option in the drop-down menu.

It should now analyze the tracks according to your personal settings (i.e. no key and BPM) and when a track is now loaded, it will not re-analyze it, but use the analysis data that was stored when you analyzed them.

[RoJeC]

Cross will always do all analyses when a track is loaded to deck (if not analyzed for all features before).

The settings you refer to only apply to manual selecting to do analyses. In that case there is the option to only analyse the selected properties.

The key detection is part of what Cross needs to have the 'match key' feature work. The algorithm Cross uses is known to be pretty good. Though it's also known that any key detection will have a certain percentage of results that are off, just like human ear won't always result in the same key.

If you have a specific purpose for modifying the Cross key result it may be annoying, but else I would suggest to leave it, as the key found usually isn't really wrong but a result of consensus in the algorithm, which in the end can only present 1 result. When you mix you'll notice that the key will blend with similar keys.

BTW if you go to the downloads section you can download version 3.3.11 which is the latest.

[branchh]

Even when I analyzed the track before putting into the deck; the move to the deck still wanted to do analysis; confusing behavior

I fully understand how key matching works, I just want to utilize another program for that establishment to ensure consistency between my audio & video content which many of them are essentially the same songs; it screws up my audio vs. video playlists if Cross is ignoring the pre-existing Initial Key field and doing its own thing

If an Initial Key value exists then Cross should utilize it! Unless I tell it to analyze for Key.

I don't understand why Cross can't utilize a pre-existing Initial Key value.

[DJ Vintage]

Ok, THAT is definitely not standard behavior. I just did a check on my own collection. If I load an existing and analyzed track into a deck, it shows up with the color waveform, cue points and everything in place. If I load a file that is new to the collection and hasn't been analyzed into the deck it WILL analyze. So far correct behavior.

When your system is behaving like that, things are as I described in my previous reply.

If your system does what you say, this is not correct!

I recall having similar problems over a year ago (there might even be a post about it still) when I changed PCs or external hard drives or something. I would run analysis on everything, then load a track and it would analyze it. Next time I'd load the track, it would still analyze it.

At the end of the day it turned out that due to some shady privilege thing in my (then Windows) OS Cross could not write to the metadata files. After I corrected that (think I reset root ownership for my Cross folder) I ran another analyze run and this time I could drop a track in a deck and it would behave properly.

Personally I use Mixed in Key and have for a long time and I have absolutely no interest in using the algorithm in Cross. I too do user-defined analysis which leaves key alone (and gain I think as I also use platinum notes). I have never had Cross change keys on me as far as I know.

[RoJeC]

First upgrade to 3.3.11. It pretty likely solves your reanalysis problem when loading to a deck.
If not it may have to do with write access to your tracks.

[branchh]

I upgraded to 3.3.11
not seeing the odd re-analysis behavior so far...
Thanks RoJeC