Hi everyone.
When using Scaler with Logic’s Chord Track, Logic always detects a different inversion to the chord I’m triggering in Scaler and in some cases, it adds additional notes to the chords.
Does anyone else have this issue? Is there anything I can do about it?
Thanks.
Logic’s chord track, in order to ensure compatibility, always has to interpret chords and voicing in a predetermined way. Should still all be 100% compatible. Works we’ll for me thus far.
So strange Davide. I started a fresh project just in case and the same thing happened. Logic detected all the chords correctly, but none of them were in the correct inversions and again, some of the chords had doubled notes 
Hi Davide/everyone.
I’ve linked to a video below of me triggering the chords on Scaler’s UI. The blue notes on Scaler’s piano keyboard show the notes being output when triggering each chord on Scaler’s UI. You can also see the black dots on Logic’s piano roll showing what Logic is receiving/detecting, which is different to what appears in the region in Logic’s Piano Roll, that was created when I dragged the Chord Track to the Instrument track. Does the Chord Track add these extra notes for some reason?
In this simple example, at least the notes it detected belong to each chord. When the chords are more complicated, the detection goes a bit bonkers, adding in notes that don’t even belong to some of the chords.
Note: If I drag the chords from Scaler’s UI onto a track in Logic, they contain the correct notes.
It would be great if someone could double check to see if the problem is specific to me. Thanks.
That’s normal, it’s just like I said before, Logic has to standardise all chords to ensure compatibility with its players.
Thanks Davide.
Is there any way I can get Scaler’s voicings into the chord track exactly as they are in Scaler?