Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow output events to target different MIDI buses #73

Closed
jtackaberry opened this issue Aug 11, 2019 · 2 comments
Closed

Allow output events to target different MIDI buses #73

jtackaberry opened this issue Aug 11, 2019 · 2 comments
Labels
design Issue contains design details enhancement

Comments

@jtackaberry
Copy link
Owner

jtackaberry commented Aug 11, 2019

Output event should allow specifying bus in addition to MIDI channel. Routing behavior should work the same way as channels, except now targeting across different buses.

The GUI will need to clearly flag conflicts when bus 16 is used and control surface feedback is enabled, since bus 16 is used for feedback.

Bits 8-11 of slot 1 in the output event is reserved for this.

@jtackaberry
Copy link
Owner Author

Proposed syntax is [channel][.bus]. As with channel, bus would be indexed from 1.

Has these behaviors:

Either channel, bus, or both can be specified. Examples:

  1. o=cc@12.3:11,127: send CC11/127 to channel 12 bus 3
  2. o=cc@.10:11,127: send CC11/127 to bus 10 on the bank's target channel

@jtackaberry
Copy link
Owner Author

Connect Vadium on VI-C to validate VEP use-case. Ref.

@jtackaberry jtackaberry added the design Issue contains design details label Aug 12, 2019
jtackaberry added a commit that referenced this issue Oct 7, 2019
Also ensure an error is raised if controller feedback is enabled
and bus 16 is used by a bank.  This is required for #73
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design Issue contains design details enhancement
Projects
None yet
Development

No branches or pull requests

1 participant