Hi guys,
to clarify all this stuff, the new analysis preference ha no effect on track loading. At load, Cross will analyse all the missing data that are mandatory (BPM, key, peak), whatever the pref.
If a key is in the tag, Cross won't analyse it again.
The new pref only changes the behavior of the Analyse button in the collection.
However, ezmicken, i haven't perfectly understood your issue (Cross doesn't re-analyze keys when a valid one already exist) but if you have a reproducible scenario that lead to it, please share

ezmicken wrote:I switched back because it kept choosing sample deck C as the master instead of switching between A and B and this was really annoying.
What do you mean exactly...?