Scaler 3 Arranger Frustrations

It’s quite possible that I’m not doing things the right way to achieve what I want with Scaler 3, but I’ve noticed some difficulties with the Arranger section - particularly when adding a ‘Bass’ lane. Here’s my scenario:

Scenario 1 - Swapping In a Different Bass Motion

I can add a Bass lane fine - (i.e. click the ‘+’ icon and choose something from ‘Expressions > Bass’ group). Scaler 3 adds the lane and the appropriate Motion.

This is where things get weird. Once a Bass Motion has been chosen, it cannot be swapped for a different Bass Motion, which doesn’t seem consistent with other Motion lanes (e.g. a Rhythm Motion lane) which provide a button to change or select a replacement Motion at the top of its MIDI Editor details panel. The Bass lane won’t let me do this - unless I first use the scissor tool to cut the Bass MIDI in half, delete the first half, then drag the second half back to the beginning of the MIDI lane, then the ‘new’ Bass Motion MIDI item does provide an option at the top of the MIDI Editor details panel that will allow swap in of another Bass Motion.

I’ve found the same behaviour with Sequence Motion lanes, too.

Scenario 2 - Auditioning Motions with MIDI Out for Lane

If I have a Motion lane that has a MIDI Out channel defined any Motion MIDI Items on that lane are played out to that channel as expected. However, if I want to swap in a different Motion (of the same type) then I can open the Motion selection dialogue from the button at the top of the details panel for the MIDI Editor and I’m restricted to only Motions of the same type for the lane (which I’d expect) but if I then audition a Motion by click-and-hold it is played back from the Main Track. The audition for the Motion lane uses the Main Tracks MIDI Out channel (if defined) and not the channel defined for the Motion lane (which is what I’d hoped - so I can audition the Motion against the external instrument that will play it.

Are there settings I’m missing here, or am I doing something wrong?

Scenario 1 is a known bug that was introduced in the latest release and they will be fixing it.

Scenario 2 is a design decision that, frankly, is completely bananas. Hopefully they will address that at some point but I don’t think they have made any commitment to doing so.