adding touch sensitivity to a patch

@naokley

Please explain what you mean by "I have an Organ patch that is not touch sensitive". Where does the organ sound come from? If it's coming from a third-party organ plug-in that ignores MIDI velocity, there's nothing Unify (or any other plug-in host) can do about it, because a host is not able to set distinct volume levels for individual notes (which are processed entirely within the plug-in).

(There are potentially some things that could be done using multiple plug-in instances and PolyBox, but I'd consider that a last resort.)

Yes - more info required. If you want to do it in GuruSampler 2, you can reduce the Amp Env EG-int knob to a low initial position, and then apply the AT/Aftertouch modulation source to it, or similarly with filter cutoff etc. (More details on Gurusampler 2 modulation assignment in the user guide.)

@getdunne Thank you. You are correct it is a third party plugin (Air Organ) that does not process velocity. I was hoping there might be a simple work around but clearly there isn't. I will see if I can find an alternative patch that will work. Unfortunately it seems Organs especially Baroque are somewhat of a niche requirement. Thanks for your reply

@naoakley

Just about all organ VSTs ignore MIDI velocity, because traditional organs don't have velocity-sensitive keyboards. Just about all organ VSTs do support MIDI volume (CC#7) or expression (CC#11) so you can use a foot pedal as a traditional "swell" pedal.

If you really want a velocity-sensitive organ, I can add a velocity option to MOrgan, my open-source organ plug-in suite which is included with Unify. Do you use Mac or Windows?

Another recent thread discusses MPE and polyphonic aftertouch.. if you have an MPE controller, you can set up a patch where you duplicate a instrument to multiple channels (enabling only one voice in the plugin per instrument layer) - then you could use the per channel modulation cc data for each instance of the synth (if it supports mapping CC to some controls), and the synth might respond to channel pressure messages.. a complicated way around the problem, but it is one way to get per note aftertouch/touch control for a synth that doesn't support polyphonic aftertouch (or any aftertouch or per note expression).

https://forums.pluginguru.com/unify-feature-requests/please-add-this-to-the-modulation-destination-in-gs2-for-osmose-and-sim-controller-users/

https://forums.pluginguru.com/unify-share/unify-1-osmose-mpe-patches/

"touch pressure" was metioned, so I assumed 'aftertouch' but for converting velocity to mutliple layers you could also use a MPE controller - but it would still require some complex mapping to convert velocity to something else.. maybe hosting the plugin inside a combobox on each layer too with some extra MIDI conversion plugins (pizmidi?).. possibly more trouble than worth.. vs just using a plugin that reponds to velocity and poly-aftertouch (self promotion here again, but Hyperion synth can do nice organ patches and is poly-AT responsive as well as supporting MPE - and of course per note velocity responsive too).

UPDATE: Mac notarization issue resolved. Updated zip below. (If you already installed the first beta, and got it working, you can just keep using it--no need to download the new zip.)

The attached zip file contains an updated MOrgan Osc VST3 plug-in, in both Windows and Mac versions, and a README.txt file with instructions for installing it manually into your Unify setup. It features a new "Velocity" checkbox at the bottom left corner of the GUI. Because this is un-checked by default, existing MOrgan patches should continue to work as always. If you find such a patch that you'd like to use, load it, open any MOrgan Osc instances and check the Velocity box, then save your updated patch with a new name.