View Issue Details

IDProjectCategoryView StatusLast Update
0007020ardourfeaturespublic2019-06-13 09:02
Reporterahellquist Assigned To 
PrioritynormalSeverityminorReproducibilityN/A
Status closedResolutionfixed 
PlatformAnyOSAnyOS VersionAny
Product Version5.X git (version in description) 
Summary0007020: Option to make active midi inputs mutually exclusive
DescriptionWhen using Ardour as an advanced midi plugin host similar to what people use Mainstage for. It would be very handy to set Ardour to only allow one active midi strip at the time. Most of or at least some daws automatically activates "current" selected strip afaik but making ardour optionally change active midi strip when clicking the midi symbol in mixer would be very handy when gigging.


Today, you have to toggle of one strip and toggle on the new one when going from a verse to a solo part.
TagsNo tags attached.

Activities

paul

2016-09-11 21:18

administrator   ~0018599

I'm working on that. The nascent Push 2 support already follows the (first) selected MIDI track, and I plan to expand the same logic.

As usual, presenting this to the user is MUCH harder than actually implementing it.

ahellquist

2016-09-12 23:01

reporter   ~0018618

Excellent

ahellquist

2016-09-13 11:18

reporter   ~0018620

Protools seems to have a mode called "Solo xor mode" for quickly beeing able to solo one track at the time.

Options > Solo Mode > X-OR(Cancels Previous Solo)


Maybe this midi input "mode" could be called something similar and be selectable by right clicking the midi toggle

Are you planning on having selected track actively listening to midi in or is the midi toggle the trigger ?

paul

2016-09-13 13:45

administrator   ~0018626

Ardour also has such a mode ("Exclusive Solo"), controlled via the Monitor section.

It isn't the correct way to approach this, however.

ahellquist

2016-09-13 13:53

reporter   ~0018627

I think you misunderstood me. I was not suggesting mixing in solo logic but only suggesting using similar naming and similar logic.

For me as end use, having x-or logic applied to currently activated (green midi symbol of) wold accomplish what I personally think I need for live gigging.

paul

2016-09-13 13:57

administrator   ~0018628

The situation is far more complex than that.

We need a way for the user to designate WHICH inbound MIDI ports are treated in this fashion, for a start. There's also the problem that a user will frequently want note data and possibly (though not necessarily) CC data too routed with this rule, while other messages (for the control surface part of a MIDI device) are left alone.

ahellquist

2019-06-13 09:02

reporter   ~0020676

This "Midi follows selection" type of behavior has been implemented now, Closing

Issue History

Date Modified Username Field Change
2016-09-11 13:11 ahellquist New Issue
2016-09-11 21:18 paul Note Added: 0018599
2016-09-12 23:01 ahellquist Note Added: 0018618
2016-09-13 11:18 ahellquist Note Added: 0018620
2016-09-13 13:45 paul Note Added: 0018626
2016-09-13 13:53 ahellquist Note Added: 0018627
2016-09-13 13:57 paul Note Added: 0018628
2019-06-13 09:02 ahellquist Status new => closed
2019-06-13 09:02 ahellquist Resolution open => fixed
2019-06-13 09:02 ahellquist Note Added: 0020676