keyboard controller focus

[Rock]

I have a very similar wish, in fact at first I thought you were requesting it.

I want to be able to have my control surface actively follow window focus. Also, please add to that the ability to setup a default configuration for each plugin. I want to control each plugin the same way anytime an instance of it takes focus, The control surface's signals will automatically flow to it in a predictable way.

[FigBug]

What control surface do you use?

We were talking about being able to pick your favourite parameters for each plugin and they would appear on the control surface first, and then the rest would appear in order. Would that be useful?

[abrickwall]

We were talking about being able to pick your favourite parameters for each plugin and they would appear on the control surface first, and then the rest would appear in order. Would that be useful?

I would definitely use this.

[zzz00m]

The first issue came up a few times at NAMM while I was doing demos for people, it's also come up on the forum in the past. We talked about it and I think we have a plan to fix it. How does this sound?

- In MIDI / Audio settings we will add a option to set default midi / audio input
- We will add two options: midi input follows selection / audio input follows selection
- When you select a track or plugin it will move the default input to the track
- If the track is routed to a MIDI output or contains a synth, the MIDI input will be moved to track, otherwise audio input
- If the track already contains an input, the input won't be moved

Should the setting be global or per edit?

Cool idea! But what would happen if you select two tracks at the same time? Would they both get the input?

[FigBug]

First track will get the input.

[zzz00m]

First track will get the input.

Would it be possible to do an "Echo MIDI input for all selected tracks"?

In other words, first track gets the input.

Then optionally, any concurrently selected tracks can receive the MIDI input too.

[Peter Widdicombe]

THAT would be nice, and a behavior that many have had to work around for years (with virtual inputs).

This would sort of also satisfy the desire of those that just want to use Waveform as a simple "live performance" VST host

[chico.co.uk]

V10.0.17 beta has this functionality now.

[Rock]

What control surface do you use?

Sorry it took a while to respond, but it took a while to think the issue through. I use several: Tascam DM4800 which does emulation of 3 Mackie Control units, Novation ZeRO SLMkII, Novation Launchpad, Softube Console 1.

We were talking about being able to pick your favourite parameters for each plugin and they would appear on the control surface first, and then the rest would appear in order. Would that be useful?

Honestly, I don't think it would be nearly as useful as what I am suggesting. With a few additions, I think you could have a much more powerful system of managing automation and control surfaces.

First you would need to add two new icons to the vst plugin title bars. (Including rack plugins!)



The new icon on the left would turn automation autoflow on and off on a per plugin instance basis. If turned on, when the plugin's window takes focus, the control surfaces' automation would be immediately re-routed to the plugin. When the plugin's window is not in focus, the control surfaces would be released to any other assignments that may have been set. Of course, if it is turned off, automation signals would not be rerouted. In the graphic below, the De-esser has autoflow activated. The UAD Neve plugin does not.



Plugins could have this setting turned on or off by default using a new option in the Control Surface settings menu.



The second icon would give the user the ability to select a default control surface patch or to open the plugin's automation settings.



The editor already exists, so this would only require adding the ability to load, save, and delete surface control patches (as automation settings associated with specific plugins). Automation patches would be managed the same way that plugin presets are.



This system would allow users to continue using automation unchanged if they wished. However, users would have new tools at their disposal that would allow them to create and manage complex automation routing in an easy way.

[Rock]

Good idea, bad idea, difficult to implement?