I’ve just broken Scaler and I think it happened after duplicating a track in Ableton with an instance of Scaler. What I mean by broken is that the transpose function completely stopped working for that preset, which is now fundamentally broken I will have to do that work a third time now, and certain chords inside the progression are just flat out wrong.
Has anyone else experienced this issue?
Hi @CreativeNorthMedia duplicating an instance of Scaler 3 may not retain your selected scale, which may mean your main track chords do not look correct. If you have a chord set in Section A for example, the new Scaler instance will detect the scale of those chords, not your main track chords. So try selecting your main track chords in the new Scaler instance, then right clicking and choosing detect to see if that resolves anything.
Instead of duplicating a Scaler 3 track, you can try putting Scaler 3 into Lead Live Sync mode, then creating a new instance of Scaler 3 on a new Track. The new instance should enter Follower mode and inherit the main track chord progression as well as the selected scale from the Live Sync Leader.
Oh ok that’s useful to know! So you’re saying one instance can follow another across the DAW? That’s very cool.
So it actually ended up corrupting the preset completely. The instance itself was fine (I could load another preset and everything worked again), but that preset was damaged regardless of if I loaded it into another fresh instance.
I’ve mentioned it to the guys in ticket SCLR-51648 off the back of a separate issue. Sorry, I know that means having a fractured case trail so I’ll try to replicate and report back.