Bug with Arm exclusive when using Remote events

[marshworks]

Here's a bug (in 8.0.4, unknown if still present in 8.2.1): When using an external MIDI track events, the track enable doesn't follow the 'ARM exclusive' preference setting.

For example: if the ARM exclusive is checked, and you click in each arm button, the other armed tracks disarm. But if you send a midi event or a keyboard event to arm a track (which works fine), the other armed tracks do not disarm. This makes it very difficult to keep my audio signal going into just the track I desire.

To work around this bug, is there any event/button that will explicitly disarm (not toggle) either a single track or all tracks? You might think about a way to do this if there isn't.

FYI, I'm on Windows 7... this is making the external control very difficult.

[hoffman2k]

You need to update. This has been fixed ages ago.

[marshworks]

I've upgraded to 8.2.1 and still experience the problem. it is easy to reproduce with using remote KEYs on the ARM buttons.

Any other ideas, please?

[hoffman2k]

Weird, must be a windows issue.
When Arm Exclusive is enabled, you shouldn't even be able to arm multiple tracks without control-clicking the Arm buttons. Every time I Arm a track using a Key, it will be the only armed track.
If you hit 2 keys at the same time, 2 tracks are armed.
I definitely can't reproduce this problem in OSX using 8.2.1 and the latest Live beta.

[sqgl]

I have this problem in XP also. If sending the MIDI remote control message via MIDI Yoke there are some topologies that work and others that experience this bug (there seems to be no pattern though).

[hoffman2k]

Weird, must be a windows issue.

It could be a Mac thing too considering Pitch black is also experiencing it. I tested it in a fresh set but didn't know that the results are different depending on how long you're using Live.
Probably some crucial info for Ableton. It means a specific action may be breaking this.

If you see it happening again, immediately go to the help menu and select "Get Support".
This creates a status report which Ableton can use to verify and reproduce this bug.

[sqgl]

Weird, must be a windows issue.
When Arm Exclusive is enabled, you shouldn't even be able to arm multiple tracks without control-clicking the Arm buttons. Every time I Arm a track using a Key, it will be the only armed track.
If you hit 2 keys at the same time, 2 tracks are armed.
I definitely can't reproduce this problem in OSX using 8.2.1 and the latest Live beta.

Perhaps you cannot reproduce it because you are using a qwerty key rather than a MIDI key.

[sqgl]

If you see it happening again, immediately go to the help menu and select "Get Support".
This creates a status report which Ableton can use to verify and reproduce this bug.

http://forum.ableton.com/viewtopic.php? ... e#p1185806
"I contacted support about his and they say it's not a bug but a feature request."

Ableton have a strange sense of humour.

If you look atound the forums you will see this "feature" is already implemented but stops working after a while. If that isn't a bug I don't know what is.

[hoffman2k]

Weird, must be a windows issue.
When Arm Exclusive is enabled, you shouldn't even be able to arm multiple tracks without control-clicking the Arm buttons. Every time I Arm a track using a Key, it will be the only armed track.
If you hit 2 keys at the same time, 2 tracks are armed.
I definitely can't reproduce this problem in OSX using 8.2.1 and the latest Live beta.

Perhaps you cannot reproduce it because you are using a qwerty key rather than a MIDI key.

Still having the same results with MIDI too. Judging by some reports, it seems to depend on which type of device is sending the MIDI. I think it might be how the toggle button reacts to Release Velocity that may be the problem. On a keyboard this will be variable (or default 64) and with toggle buttons it is 0 I think.
The only scenario I've seen with unpredictable results so far is if there is a hanging note. Which might explain the cases where it messes up over time.
But clearly a lot of people are experiencing this issue judging by those threads. I'll talk to Sheluser and see if it can be figured out. If it is the variable velocity thing, it might explain why we are all getting different results.

[sqgl]

If it is the variable velocity thing, it might explain why we are all getting different results.

I am sending the MIDI note via Midi-Ox and I have forced it to 100 (yeah, not 127. Should not matter). I am sending MIDI notes via my QWERTY keyboard using a Windows utility caled Virtual MIDI Controller. I can see if there are stuck notes - There are none.

A moment ago I reloaded Ableton and it worked for a few keystrokes then misbehaved again.

[hoffman2k]

If it is the variable velocity thing, it might explain why we are all getting different results.

I am sending the MIDI note via Midi-Ox and I have forced it to 100 (yeah, not 127. Should not matter). I am sending MIDI notes via my QWERTY keyboard using a Windows utility caled Virtual MIDI Controller. I can see if there are stuck notes - There are none.

A moment ago I reloaded Ableton and it worked for a few keystrokes then misbehaved again.

Honestly, despite what you think of Ableton Support, you'll find that making a "Get Support" pack really helps to solve this. The thread you linked has a quote from support from September. Since then they have switched to those bug report snapshots and a ticket system and have gotten far more efficient in fixing these things.
If you can reproduce this within a few minutes, you'll have a much smaller event log for them to analyze. Support can get one wrong too, but just tell them again.
I've tried reproducing this following the comments made so far, but without some specific details and a step by step process to the problem, a bug report snapshot is the only option.
I used the same testing method like you, but with OSX equivalent apps.