Ableton Forum

I can't find an explanation for this problem. Could someone do this test?

Ableton Live 11 updated
And I have the -EnableArmOnSelection option activated

The MIDI controller is an Arturia MiniLab 3 and is configured correctly.
Checking the MIDI control I have ruled out that it is a double-click problem.

In Arturia Minilab 3 remote script for Ableton the MIDI controller PADs work as follows:
1.- Select the track
2.- Perform the action that each track has in the selected scene.

For example:
- Track 1 is selected
- Press PAD 2: Track 2 is selected + The action of Track 2 for that scene is executed (for example Play, or record if the track is armed)

I'm trying to do live looping and the procedure (learned on YouTube, there are many examples) consists of choosing the track with the PAD, and then making a second press on the PAD to start recording:

Example:
- I select track 1, and the track is armed
- Press PAD 1 > the track enters recording mode
- I record sounds
- I press PAD 1 again > The recording stops and the track remains in Play

And now:
- Press PAD 2
- Track 2 is selected
- Thanks to EnableArmOnSelection the track gets armed but does NOT enter recording mode
- I press PAD 2 again, and start recording


However, 50% of the time there is an unwanted operation:
- I end the recording on track 1
- Press PAD 2
- And all 3 things happen at the same time: The track is selected, armed, and recording begins.

For the way I work, I prefer to select the track and then decide when I'm going to record. I don't like that selecting the track starts recording directly.

Why does this happen randomly? Do you think it is a timing problem between executing the Select+Action and then EnableArmOnSelection? I think that sometimes the EnableArmOnSelection is executed after Select but before Action, and other times it is executed at the end. Makes sense?

SorroG wrote: ↑

Sun Oct 15, 2023 7:21 pm

Do you think it is a timing problem

I might to read again the details of your post, but yeah that was my 1st thought.

Please, would someone do a test?

Surely this problem occurs with more control surfaces, not just the Arturia Minilab.

Surely other surfaces have this same behavior in the pads, which select the track and also make the interaction (play, stop or record, depending on the state of the track in the selected scene).

In such a case, and together with the use of EnableArmOnSelection, I think that more people could try and contribute to find the problem.

Anyone up for it?

Hey
sorry , I didn't take the time to read again your post in details and try to reproduce.
Just a quick word though to say that the -EnableArmOnSelection option (like most options available in the Options.txt) is not officially supported. So if you come across a weird behaviour don't expect it to be fixed. Just a word of caution.

I'll try to have a look, though.

[jur] wrote: ↑

Fri Oct 20, 2023 12:13 am

Hey
sorry , I didn't take the time to read again your post in details and try to reproduce.
Just a quick word though to say that the -EnableArmOnSelection option (like most options available in the Options.txt) is not officially supported. So if you come across a weird behaviour don't expect it to be fixed. Just a word of caution.

I'll try to have a look, though.

Many months later, and with Live 12, I have tested again and everything is still the same. Did you have a chance to do the test? It would be of great help to me, because I can't find anyone else complaining about this problem, and it seems important to me.

Thanks!!!