Waveform new features requests

[chico.co.uk]

Midi map the same controller button / knob to different plugins in a way that it is only effective when the plugin is on screen. I've tried to assign the same knob to 2 different plugins and even if one of the plugins was hidden, the knob was moving on both. This is a big deal when you only have one controller. Is there a way to do this?

Usually you'd create banks on the controller that map the same hardware knob to different midi channels and CC numbers, and switch between the banks on the controller, depending on which plugin you're trying to control. Not hide the gui of the plugin, in the DAW, to change which plugin you control.

You might *want* to use one hardware knob to move two plugin knobs at the same time, in which case you would map the same CC number and channel to both plugins, like you've done. You *don't* want to do that, so look into how you get your controller to send different messages for the DAW to map to the two different plugins.

[scalawag]

Thanks, but, imagine 16 tracks with 2 plugins on each (vst and vsti). It's not the best way to do it. I think there should be an option to only send midi to the plugins that are on screen. just my 2 cents
Anyway, i came from Renoise and Ableton, and so far i'm liking Waveform. Keep up the great job guys!

[dRowAudio]

If you use the "Control Surfaces" settings page to setup a new controller and then assign some CCs to "Plugin" -> "Automatable Parameter" numbers, you can control the selected plugin. As you change selected plugin the CC will get sent to the currently selected one.
I know this isn't exactly the best solution however as this only gives you access to the first N parameters but we're working on improving that for a future version.

[ArtemK]

Hey. I would very much like to see the dockable spectrum analyzer in the built-in plug-ins. Also the m/s mode in equaliser would be great addition i think
Anyway waveform is great and become a secret weapon to me

[scalawag]

I think there should be an option to only send midi to the plugins that are on screen.

I think the solution is that only the visible plugins should receive midi messages, or better yet, the plugin frame should have a button to enable or disable midi messages.

[ArtemK]

Step-Clip with its own Window (dockable) like the Midi would be nice

+1

[Rock]

I wish that Novation Automap users had the option to assign "track select" as a parameter (like arm, mute, and solo).

[solomute]

I insist on allowing more filters on the master out. Why only 4 filters? That's ridiculous! A normal person would want eq, comp, limiter, reverb and a spectrum analizer and even more. We can disable them by F button if needed. I would like to have 20 filters on master out.

[solomute]

Is there a possibility to process right and left channels separately? For example i want to apply different values of pre-delay to the right and left channels. I don't know any vst which could do it. So the idea is perhaps to create a rack, put 2 copies of the same vst inside the rack and then route left ch to one vst and right ch to the other vst. But this way seems non-rational because of using 2 copies of the same vst. any other ideas. Generally i would like waveform to have a set of 2 built-in plugins like split stereo to 2 mono, and assemble stereo from 2 mono.

[solomute]

ArtemK, m\s mode in my opinion and according to some confessions on the net spoils space of the mix making it sound totally flat and\or unnatural. So far i have not found a single case where m\s would give any benefit over stereo processing... The same concerns doublemono processing. Unless you create some electronic crap you would want to avoid using m\s by all means. Though there is one trick to improve space that is if you pan side and mid the same way you do it to L and R. In other cases i would totally ignore those annoying silly advises to convert to M|S and equalize or otherwise process them this way. If you can't get what you want from a vst in a stereo mode, it means that vst is not good, not well developed.

[chico.co.uk]

I insist on allowing more filters on the master out. Why only 4 filters? That's ridiculous! A normal person would want eq, comp, limiter, reverb and a spectrum analizer and even more. We can disable them by F button if needed. I would like to have 20 filters on master out.

Chuck a rack on the master output, if you're that keen.

[chico.co.uk]

Is there a possibility to process right and left channels separately? For example i want to apply different values of pre-delay to the right and left channels. I don't know any vst which could do it. So the idea is perhaps to create a rack, put 2 copies of the same vst inside the rack and then route left ch to one vst and right ch to the other vst. But this way seems non-rational because of using 2 copies of the same vst. any other ideas. Generally i would like waveform to have a set of 2 built-in plugins like split stereo to 2 mono, and assemble stereo from 2 mono.

I don't understand how you could process left and right channels separately, without using two instances of a plugin, one for left, one for right. Could you explain how that might work?

[solomute]

Chuck a rack on the master output, if you're that keen.

I have tried that with tracktion and had some buggish behaviour namely when the vsts inside the rack were bypassed they still coninued effecting the sound. That's why i had to remove the rack from master out.

I don't understand how you could process left and right channels separately, without using two instances of a plugin, one for left, one for right. Could you explain how that might work?

That's true. There is no other method. I succeded by using two copies of a vst in the rack. All separate processing of individual channels can be done within a rack but you can't do automation. So useless.

[solomute]

We need the feature to be able to automate vsts placed inside a rack. Otherwise I can't process right or left channel separately where I want to use automation.

[solomute]

One more feature i would like to have is that each vst filter would have bypass automation option so that I would not have to automate via wet and dry automation lines.