...unless there's a way to do this now that I'm not seeing. Here's a step-by-step scenario:
Let's say I have one MIDI device and I want to create an IA Button to access a preset on that device. Also let's say that the device is in an audio loop, say loop 8.
Button 1:
. . IA Link: checked
. . IA Actions:
. . . . Audio / Loop #8 off:OFF, on:ON
. . . . [Device] / PC off:none, on:[any_value]
This works. It enables loop 8 and recalls the preset on the device. If I press this button and navigate to the default Loops button page the Loop 8 LED would be lit as it should.
Then I add a second button, the only difference is the PC On value:
Button 2:
. . IA Link: checked
. . IA Actions:
. . . . Audio / Loop #8 off:OFF, on:ON
. . . . [Device] / PC off:none, on:[different_value]
This also works but since it's the same device I need those two buttons to toggle, so I put them in a group:
Button 1:
. . Group: 1
. . IA Link: checked
. . IA Actions:
. . . . Audio / Loop #8 off:OFF, on:ON
. . . . [Device] / PC off:none, on:[any_value]
Button 2:
. . Group: 1
. . IA Link: checked
. . IA Actions:
. . . . Audio / Loop #8 off:OFF, on:ON
. . . . [Device] / PC off:none, on:[different_value]
Now I have a conflict between IA Link and the Group. The actions toggle, but the LEDs don't -- when I press Button 1 the LED for Button 2 lights up as well.
I can solve that problem by disabling IA Link in one of three ways:
1. unchecking the IA Link checkboxes, or
2. making "Audio / Loop" the second action, or
3. moving those "Audio / Loop" actions into Global tab for the group...
But when I do that the LEDs on the Loops page of course no longer reflects the correct state of the loop. And because of that it takes two button presses to get it back in sync. These are the problems I'm hoping to solve.
So one idea is having button groups override IA Link so that the buttons that belong to a group won't be linked but buttons outside the group would be. That would solve this problem as long as the "Audio / Loop" action is the first in the list.
But I'm also wondering if the system could be aware of the actual state of the loop without requiring IA Link. In that case maybe a new button type, called Loop or whatever, that we could use on the Loops page. That would be great for me because I have most of my "Audio / Loop" actions in the Global tab for the groups which gets ignored by IA Link.
I think the best solution if possible would be both because button groups overriding IA Link could be used in other ways as well, and a "smart" button type would be it's own thing and wouldn't be tied to the order of IA Actions or their location.
Let's say I have one MIDI device and I want to create an IA Button to access a preset on that device. Also let's say that the device is in an audio loop, say loop 8.
Button 1:
. . IA Link: checked
. . IA Actions:
. . . . Audio / Loop #8 off:OFF, on:ON
. . . . [Device] / PC off:none, on:[any_value]
This works. It enables loop 8 and recalls the preset on the device. If I press this button and navigate to the default Loops button page the Loop 8 LED would be lit as it should.
Then I add a second button, the only difference is the PC On value:
Button 2:
. . IA Link: checked
. . IA Actions:
. . . . Audio / Loop #8 off:OFF, on:ON
. . . . [Device] / PC off:none, on:[different_value]
This also works but since it's the same device I need those two buttons to toggle, so I put them in a group:
Button 1:
. . Group: 1
. . IA Link: checked
. . IA Actions:
. . . . Audio / Loop #8 off:OFF, on:ON
. . . . [Device] / PC off:none, on:[any_value]
Button 2:
. . Group: 1
. . IA Link: checked
. . IA Actions:
. . . . Audio / Loop #8 off:OFF, on:ON
. . . . [Device] / PC off:none, on:[different_value]
Now I have a conflict between IA Link and the Group. The actions toggle, but the LEDs don't -- when I press Button 1 the LED for Button 2 lights up as well.
I can solve that problem by disabling IA Link in one of three ways:
1. unchecking the IA Link checkboxes, or
2. making "Audio / Loop" the second action, or
3. moving those "Audio / Loop" actions into Global tab for the group...
But when I do that the LEDs on the Loops page of course no longer reflects the correct state of the loop. And because of that it takes two button presses to get it back in sync. These are the problems I'm hoping to solve.
So one idea is having button groups override IA Link so that the buttons that belong to a group won't be linked but buttons outside the group would be. That would solve this problem as long as the "Audio / Loop" action is the first in the list.
But I'm also wondering if the system could be aware of the actual state of the loop without requiring IA Link. In that case maybe a new button type, called Loop or whatever, that we could use on the Loops page. That would be great for me because I have most of my "Audio / Loop" actions in the Global tab for the groups which gets ignored by IA Link.
I think the best solution if possible would be both because button groups overriding IA Link could be used in other ways as well, and a "smart" button type would be it's own thing and wouldn't be tied to the order of IA Actions or their location.