Notifications
Clear all

MIDI Notes to Audio Effects

9 Posts
2 Users
0 Reactions
548 Views
hallenberg
(@hallenberg)
Irritant
Joined: 4 years ago
Posts: 154
Topic starter  

For audio effects which may be triggered and/or controlled by MIDI gate and/or pitch, it would be useful to get discreet MIDI to those devices.

For example, some effect devices have built-in LFOs, envelopes and maybe sequencers which can be triggered by MIDI gates. Other effect devices take cues from MIDI pitch.

Presently it seems MIDI notes do reach insert effects on Instrument layers, but unsurprisingly they are the same MIDI notes as fed to the instrument itself. With that in mind, one might either want to stop MIDI notes reaching the effect device, or one might want to send totally different notes to the effect device.

Basically, wherever one can put an effects device in Unify, it would nice to control a delivery of MIDI notes to that device somehow.

 


   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4432
 

@hallenberg

Good point. I'm looking at the manual page on this, and I think the MIDI routing is not quite as described. I think it's the Instrument's MIDI OUT which is distributed to the Audio plug-ins, not the MIDI IN. I will look into changing this and/or revising the page.


   
ReplyQuote
hallenberg
(@hallenberg)
Irritant
Joined: 4 years ago
Posts: 154
Topic starter  

Of course I neglected to check the manual before posting.

Posted by: the Unify Manual

In Unify v1.0.x, MIDI data is not routed to audio-effects layers (either AUX or MASTER). This may change in future.

Hooray for the future 🙂


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4432
 
Posted by: @hallenberg

Basically, wherever one can put an effects device in Unify, it would nice to control a delivery of MIDI notes to that device somehow.

Somehow? Detailed suggestions please.


   
ReplyQuote
hallenberg
(@hallenberg)
Irritant
Joined: 4 years ago
Posts: 154
Topic starter  

Logically every audio effect device should (ideally) have options for its MIDI input.

The obvious first option would be to prevent any MIDI reaching the device at all. For now this would only apply to audio insert effects on Instrument layers (since Aux devices can't receive MIDI anyway). Conversely the default behaviour could be changed so audio insert effects on Intrument layers don't receive any MIDI unless user deliberately chooses it. If user wants MIDI to the device, a MIDI source for that device should be selectable. The potential range of selectable sources is beyond the scope of this paragraph 🙂 but the usual suspects would be in there; a MIDI layer, a MIDI interface (if Unify is in standalone mode), Instrument layer MIDI IN or pass-thru etc.

A similar scheme may apply to effect devices on Aux and Master layers, where MIDI options for any effects device are configurable from the context menu of the device itself. Whether it would make sense to instate Aux layer MIDI options more generally, I'm not sure.

In general I think MIDI-to-effects-devices is a more advanced feature which needn't clutter the UI; it would be ok to tuck it away and simply have a small LED on the device slot to indicate that it has MIDI options enabled.

In the greater scheme of things I imagine all routing configurations could be managed from a separate window. I haven't given this too much thought but I'd suppose one tabbed pane for the 'macro/modulation matrix' and another for 'MIDI routing'. I guess this is ambitious but it could be one of the championing aspects of Unify..?

*duck*


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4432
 

I agree it should be possible to enable/disable MIDI input to individual plug-ins, and to have some control over how they are connected.

Unify uses a specific internal structure, which would not allow entirely arbitrary connections. The simplest approach would provide 3 MIDI sources for each plug-in on a layer would be

  • no connection
  • daisy-chain: connect to the MIDI-out of the previous plug-in (default for chains of MIDI effects and instruments)
  • parallel: connect to the layer's MIDI input (default for audio effects)

At some point in the future, I intend to provide a "node-based" GUI, similar to e.g. Kushview Element (itself a clone of the JUCE AudioPluginHost demo), KX Studio Carla, etc., for individual layers. This would provide for every other conceivable topology, for audio as well as MIDI, within a single layer.


   
ReplyQuote
hallenberg
(@hallenberg)
Irritant
Joined: 4 years ago
Posts: 154
Topic starter  

I was aware of Carla but not Kushview Element - thanks for that. Yes to the availability of nodey patchbays for advanced setups, that would be great, but I also think they shouldn't be necessary for the more obvious connection possibilities. I find Carla and Element a bit too nodey for general purposes. I think Unify looks to be striking a good balance.

I appreciate your 3-option suggestion for audio insert effects, I think that would be helpful.

Having thought about this a bit more, can you forgive me for asking about the feasibility of adding MIDI input to Aux layers? I'm just curious. If that were feasible using the current internal structure (more or less, I understand it would be a kind of Instrument/Aux layer hybrid) it could go a long way towards the goal I had in mind.


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4432
 

@hallenberg

There's no fundamental reason why audio layers should not have MIDI connected. It's simply that I would have to add new MIDI controls to them, which would clutter the GUI layout with controls that will get used extremely rarely.

I plan to rework aspects of the GUI layout in future, in ways which will make this more feasible.


   
ReplyQuote
hallenberg
(@hallenberg)
Irritant
Joined: 4 years ago
Posts: 154
Topic starter  

I had thought about that. I was thinking maybe alt/option-click New Aux Layer.


   
ReplyQuote
Share: