Notifications
Clear all

MIDI device enable/disable per layer

4 Posts
3 Users
0 Likes
218 Views
(@laidbackdood)
Active Member
Joined: 1 year ago
Posts: 13
Topic starter  

Hello Shane,

I recently purchased and MPE controller and for it to work with MPE instruments, it would use channels 1-16 (one per note polyphony). This is working fine when I'm just using one layer but when I want to separate the layers for other midi keyboards, I cannot isolate them.

So for example I have a pad on layer 1 which accepts OMNI to allow MPE to function. On layer 2, I just want to use another keyboard on a single channel that will not affect layer 1 and vice versa. The only way I can see this working is if we can select the input device per layer instead of just a channel filter.

If you have any suggestions on how I can make this work together for live performances I'd really appreciate it.

Mike

This topic was modified 1 year ago by laidbackdood

   
Quote
Topic Tags
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 

@laidbackdood

Another excellent suggestion; thank you. The ability to select a specific MIDI input device for each layer has been requested in the past, and is still on my to-do list. Two thoughts:

  • I would most likely implement this by adding the names of available MIDI input devices to the MIDI input-select control on each layer, so that instead of selecting "IN" (merged MIDI streams from all input devices), you could select a single device. This is what you asked for in the text of your post.
  • What you asked for in the title of your post, however, was the ability to selectively enable MIDI devices individually, which implies that perhaps some subset of the available MIDI devices (not just one) could be selected for a layer. I can't think of a realistic case where this would be needed. Can you?

Unify was designed as a plug-in, which also happens to be able to be loaded as a stand-alone app. Plug-ins don't have the ability to "see" individual MIDI input streams, so this wasn't part of the original spec for the Unify stand-alone app either. What you are requesting would move the Unify stand-alone app further in the direction of a general-purpose "live host", which is a nice idea, but one fraught with issues for us as developers.

Many Unify customers who play live use Unify as a plug-in within a more established live host such as Gig Performer, Cantabile, Camelot, etc. This allows them to take advantage of Unify's layering, MIDI-handling, and patch libraries, while relying on the live host for its input/output and set-list management features (and a work-flow they are usually already familiar with). Although it's technically possible to add such features to the stand-alone version of Unify, it's never been clear to me that doing so would repay the effort involved.


   
ReplyQuote
(@laidbackdood)
Active Member
Joined: 1 year ago
Posts: 13
Topic starter  

@getdunne Hi Shane, you're right, multi select of instruments may be more niche. I do actually have gig performer and did also try that before which works (actually I used to use it before I found unify, still need it for audio input like guitar line in -- I think your about to release something for this =)...). It's just a more complex setup, one which Unify can greatly simplify with just the ability to select specific midi instruments per layer. I think I really just like the idea of a set up with the minimum amount of complexity needed. I appreciate you.

Mike


   
ReplyQuote
(@histakes12)
Active Member
Joined: 4 months ago
Posts: 3
 

"adding the names of available MIDI input devices to the MIDI input-select control on each layer"

Perfect! Can't wait!

Thank you!


   
ReplyQuote
Share: