When a recording some chords for example after the count-in the first chord will get cut short. This doesn’t happen in scaler 2 and had been happening since scaler 3’s release.
Hi @djjlava would you mind elaborating on what you mean here? When you say ‘recording some chords’ do you mean recording do a user track? Are you triggering bound chords etc?
You also say ‘This doesn’t happen in scaler 2’ however Scaler 2 did not have user tracks or internal recording. So maybe I’m not understanding. If you could elaborate that would be much appreciated. Thanks.
for example in Ableton
step 1: I open a midi track an put scaler 3 on with no instrument selected.
step 2: I open another midi track this time with serum for example
step 3: I do the necessary routing to allow serum to play scaler 3 chords (that works as expected)
step 4: I hit record and the very first chord I play gets cut short after the count in.
note: its only the first chord.. the rest of what I’m playing registers. even the midi show the chord being cut short.
If the go into the midi and stretch out the first chord and set a loop, the first time the loop starts even tho the chord is stretched out it won’t play the whole chord but when the loop come back to the top it would play as expected. the moment I stop to start over the loop the first chord again gets cut short again.
Hi @djjlava . Thanks for the update, however I’m still not entirely following what you are doing.
Would you mind elaborating on the above?
Presumably you are pressing Ableton Live’s main record button and recording to Arrange view. Is that correct? So are you recording the MIDI output from Scaler 3 to the MIDI track hosting Serum in Ableton Live? Have you programmed MIDI trigger notes into Ableton Live, or is Scaler just playing the Main Track in DAW sync mode?
If using trigger notes with bound chords in Scaler 3, be sure to disable DAW sync mode, and this can conflict with trigger notes resulting in behaviour similar to what you are describing.
Hi, I was able to reconstruct the issue. Open Scaler 3 in any Ableton arrangement track. Bind any scale in B section of Scaler. Now, if you press C2 key on your MIDI keyboard, you should get a chord as an output. That is all ok.
Now create MIDI clip with only one longer note C2, which is placed at position 1.1.1. (touching left edge of the clip). If you start playback from beginning of this midi clip, note will be played “staccato”. It seems that note length is not propagated correctly to the instrument.
Walkaround:
Place short empty midi clip in front and play from there, or extend the clip to the left, so first note is not at position 1.1.1. If you are recording, you also need some time to pass between pressing record and playing first notes
As this is happening only with first notes which are played immediately after Scaler is getting active, IMHO this could be Scaler initialization issue or timing issue with first midi commands.
This have been an issue for me in a very long time, tested this now again in 3.3.1, yes the problem is still there, but also just now found out why. When you have an Ableton midi clip on the scaler track play binded chords in section B, (C2, A2, G2, F2 for example), scaler doesn’t pick up the first chord at 1.1.1 as mentioned. (Many forum posts about this in the past). When the 4-bar scaler track clip then loops the first cord is played in every pass of 1.1.1. Same if you bind cords in section C. Some timing issue in scaler when you start the clip I suspected (workarounds in previous forum post works) Same if you bind section C. I noticed this for a long time in scaler 3, and scaler 2 didn’t behave like this at all. BUT - disable Daw sync in preferences then everything works as expected! Both in section B and C. At some time this preference must have been changed when playback for section C was developed? I have been so bugged by this… especially when rendering quick ideas and some midi notes from Scaler didn’t get played.
@Tristan This is seems to be the only work around.
Step 3: scaler 3 on midi track routed to serum on another Midi track capturing the midi played from scaler.
Step 4: I hit record on Ableton.
this wasn’t an issue in scaler 2 funny enough.
disabling the sync def worked. Thanks!
disabling DAW sync worked thanks.
Thanks to everyone for the input and feedback here. It sounds like the issue is that Scaler 3 is set to DAW sync mode, meaning it is trying to play the main track chord progression when your DAW plays. If you are also trying to manually trigger individual chords via MIDI, this creates a conflict. So the simple solution here is to disable DAW sync mode when manually triggering chords. Keeping in mind that DAW sync is enabled by default in Scaler 3.
Note there is a very nice update in development which should greatly assist those who do like to manually trigger chords using bound notes, rather sequence chords on Arrange page. Hopefully we will have more to share on this soon.