Hey, could someone please explain what shift chords in chord track actually does. The Manuel doesn’t really give much away.
From what it says if a midi note starts early or late that should change it’s position in relation to being triggered by the chord track.
But it does not seem this is the correct function… 
It says less then that, just
Shift Chords
If you enter a negative number of ticks, the chord events affect the MIDI notes that have been triggered too early.
Exactly. I’m trying to test this in my workflow >
But no matter what I set the ticks to the midi notes don’t seem to be affected at all. Am I missing something super simple?
I think this feature is only relevant when another track is set to follow the chords on the Chord Track, is it not?
And then the tick setting would basically mean: Position of chord event + tick setting = area that notes still get affected by the chord.
So if a note is 45 ticks earlier than the chord event and you set Shift Chord to -45 ticks, the note would affected by that chord event.
That’s what I thought…which is how I have it set up. Omnisphere is following the chord track with some notes adjusted to start slightly ahead. But it has no effect that I can audibly detect…
On your screenshot the ticks are set to 100. That means 100 tick later than the position of the chord event. If your notes are earlier the tick setting would have to be negative.
Yes. Right now I’m switching between -100 and +100 just to see if my ears can detect anything…and nothing
Ps (sent wrong screenshot)
I’ve been on this for 3 hours now lol
Could 100 ticks be so small that ears would struggle to detect?
As per Cubase default settings 120 ticks = 1/16th note. So it’d be a bit less than a 1/16th note.
Please kindly note:
Sorry for my mouse handwriting. But you can easily try for yourself if you can notice 100 ticks.
Mines worse lol.
I’ll give it a go when I get home. What about on your end. Do your ears perceive the difference?
It’s more for your eyes than ears. If you are in the Key Editor and have the Notes colored by the Scale & Chords it will impact how the Notes are colored & potentially manipulated.
In the pic below the chords are alternating between C & F over 4 bars. Bars 9 & 10 are how you want it to look. But in bar 12 the F Note got played a bit early and Cubase thinks it is not part of the F Chord because the Note started in bar 11 and an F Note doesn’t belong in a C Chord. The setting controls how early a Note can be played and still be considered Part of a subsequent Chord Event. I have mine set to -20 Ticks. If that F Note were 18 Ticks before the bar it would be part of the F Chord and colored green. But it is over 20 Ticks early and belongs to the C Chord on bar 11.
This also controls more than just some colors. For example if you told the Track to follow the Chord Track the F Note would be changed to an E Note to be part of the C Chord on bar 11.
3 Likes