Serious issue with Atom with scenes - Can it be fixed with a script?

[johnsq]

Hi, Not sure how Atom 2 managed to make it to production with somebody noticing this issue but here we are.

The issue. I create a row of three Atoms in AUM and draw in some simple midi notes to tigger loops in a sampler. I connect a Launchpad Mini Mk3. All works great bringing them in and out and playing the whole scene.

Unfortunately, as soon as there is a second scene in play, there is a big problem.

Please imagine that in slot 1:1 there is a single note on C0 with a length of four bars. I duplicate this into slot 2:1. I am using the default "Launchpad" Launch mode. The expected behaviour when switching from one scene to the other (or simple tapping between said clips) is that the sample restarts at each switch. The reality is that the sample is triggered by the NOTE ON message but is abruptly stopped. Why is this happening I thought?

After viewing the output of the Atom instance with a Midi Monitor app, it is obvious. The midi events occur in the wrong order.

Instead of correctly doing this..

Start clip 1:1.. NOTE_ON C0 Switch to clip 2:1.. NOTE_OFF C0 > NOTE_ON C0 Switch to clip 1:1.. NOTE_OFF C0 > NOTE_ON C0

.. it incorrectly is doing this..

Start clip 1:1.. NOTE_ON C0 Switch to clip 2:1.. NOTE_ON C0 > NOTE_OFF C0 Switch to clip 1:1.. NOTE_ON C0 > NOTE_OFF C0

The NOTE OFF messages triggered by the clip END actually occur after the next NOTE ON message triggered by the clip START which explains why my samples were triggering but abruptly cutting off.

This a big issue and should not be in production software. I had to abandon a project yesterday when I discover this and couldn't work around it.

I can send a video of my explanation is not clear enough.

Please offer me a solution/fix via an edit to a script or simply fix and update the Atom 2 app.

Thanks, John

[johnsq]

Eleven days since I reported this. My email was ignored also. Abandonware?

[victorporof]

I'll have a look.