Hello folks,
When I put a chord progression on the host timeline (studio one) and do a Detect MIDI, Scaler3 puts the detected chord progression at the start of Bar 1 instead of the bar you positioned the chord progression to be detected! This causes obvious problems with keys lock, as you have purposefully chosen that position on your host to put the chord progression so you can then do an improvised section based on the detected chord progression…
The work-around is to (tediously) drag all these chords (113 bars in my case) to the correct position on the Scaler3 timeline so it matches the intended position. Please fix this… HERE is a video showing it in action.
I fighting with this also and determined that the issue is the chords are detected on a bar-by-bar basis so a chord change within a bar is not detected…
I use StudioOne also and tried to “time-stretch” to get all the cords to start at the beginning of the bar. In my case, I "half-tempo"ed it a couple of times, and now they match, but that opens up another “can-of-worms”..
Hi folks. Just to clarify, it isn’t exactly accurate to say chord changes within a bar are not detected. Scaler should detect any incoming chords regardless of duration, however chord duration is not acknowledged and detected chords all share the same default length/duration. Dragging these chords to your main track results in the default chord duration of one bar for each chord.
There have been many requests to preserve the duration of detected chords which is something we are hoping to implement in a future update.
1 Like
Hi Tristan, correct relative to DAW “position” of the detected chords was the primary concern in my post, but I suppose “duration” would have to be detected for the correct positions to be maintained.
thanks, Mark