Quote:
Could you please clarify what you meant by that?


It means that when changing chords, it will minimize transposing various RealTrack patterns and always use one recorded using that chord or closer closer to that particular chord. It results in fewer possible artifacts, but at the expense of fewer available riffs. I don't know how the engine intelligently selects the patterns, but this setting will try to use a closer chord instead of transposing a different chord to achieve the result.

When creating RealTracks, they don't record the all the same riffs for every single possible chord, and especially for some of the more esoteric chords. So, if the RealTrack has a C69add13 (I'm just making stuff up here) recorded, but you need an E69add13, instead of transposing the C version up to E and keeping with the same basic rhythmic structure of the C chord, it will find a recorded chord at or closer to E to use or transpose instead; however, there may be fewer riffs available on that closer chord than just transposing the the C chord up.

Hope that made sense, and it really is all magic.

John

Laptop-HP Omen I7 Win11Pro 32GB 2x2TB, 1x4TB SSD
Desktop-ASUS-I7 Win10Pro 32GB 2x1.5TB, 2x2TB, 1x4TB SATA

BB2025/UMC404HD/Casios/Cakewalk/Reaper/Studio One/MixBus/Notion/Finale/Dorico/Noteworthy/NI/Halion/IK

http://www.sus4chord.com