Notifications
Clear all
Topic starter
November 15, 2025 9:06 pm
Recently there have been a few requests for an "audio-effect" or "MIDI-effect" version of Unify 2. This is because most DAWs make a rigid distinction between "instrument" and "effect" plug-ins, and because Unify 2 enumerates as an "instrument", they won't allow you to load it into an effect slot.
Note that a few DAWs (e.g. Reaper) and live-host apps (e.g. Gig Performer) don't make such rigid distinctions, and hence in these programs, you can use Unify 2 directly as an audio- or MIDI-effect.
Unfortunately, most DAWs aren't so flexible. I think (I don't know because I'm no longer involved in decision-making at PlugInGuru), there is a plan to make "effect" versions of Unify 2 available, with suitable modifications of the GUI and/or functionality, but this is likely to take quite some time.
For now, therefore, I have made some experimental new plug-ins which "wrap" Unify 2 so it can be used as an effect in your DAW. These are NOT official PlugInGuru products; they're my free contributions to the Unify community. They come with NO WARRANTY and no official support--although you may post questions here and I'll answer them as best I can.
Here are the download links:
- MacOS: https://www.dropbox.com/scl/fi/2gycxlhcg2t7fugvv5zxv/U2-wrappers-Mac.zip?rlkey=knn45nketsfj5d9fjz8wccvxx&st=sxeptm3d&dl=0
- Windows: https://www.dropbox.com/scl/fi/e5yu6125i7erxlkm0az4k/U2-wrappers-Win64.zip?rlkey=7tkxkze5ougzjrkofw1ya0x1m&st=82amypk8&dl=0
Each of the downloads includes a simple README file with basic instructions to get the plug-ins installed.
The Windows download includes a VST3 (and also an optional VST2, for older systems) called "U2FX" which is an audio-effect plug-in.
The Mac download includes the U2FX VST/VST3, and also two Audio-Unit plug-ins called "U2AX" and "U2MX":
- U2AX wraps the Unify2 Audio Unit as an audio-effect or MIDI-controlled effect.
- U2MX wraps the Unify2 Audio Unit as a MIDI-effect (MIDI-in, MIDI-out, no audio at all)
You'll have to understand Unify 2 well enough to know how to set up audio-input and MIDI-output to and from layers. Furthermore, you'll have to just accept that Unify 2 was not designed for use as an effect plug-in (so e.g., you'll still see AUX and MASTER layers in U2MX, even though you can't use them), and you'll just have to deal with that.
I can't promise these will work in your specific DAW, or that they will function in exactly the ways you would like. This is simply an experiment to see what works and what doesn't, and perhaps gather some feedback which John and Paul may find useful in the future. As I said, I'll answer questions here as best I can, but please appreciate that I work full-time on something else now, and no one is paying me to do this.
Topic starter
November 15, 2025 10:18 pm
The current version of the Unify AU doesn't allow you to set a layer's MIDI to go to MIDI-out. Paul apparently already has a fix for this, so the problem will go away with the next update (in a week or so), BUT in the meantime I have a workaround:
Setting an INST layer's instrument to "Hardware Synth" enables that layer's MIDI to MIDI-out.
You'll need to do this if you're using U2MX. Once the upcoming Unify 2 update is available, you wont' need to anymore.
November 17, 2025 9:32 am
Awesome - thanks so much for this. I'll take a look, could be the next great add to my live set - different effects on audio tracks per performance track.
November 17, 2025 10:04 am
Thanks Shane, initial testing:
VST2 adding crashes Live
VST3 works great, just added A Reaktor 6 effect to Send A and routed audio in and works like a charm.
The reason I chose VST2 first was the lack of program change limitation on VST3 in Ableton, because that would be a key need for this functionality for me. A quick test on Reaktor FX on the Send A, native actually seems to use more CPU than within the wrapper (for VST3, 12% vs 10% in wrapper...so that's good). Also sending program change to the Audio effect does change the preset (for VST2).
SO really interesting first look, I'd love it if the VST2 wrapper was working, I'd be interested if others can get it to work on other systems, because then I could have a bunch of audio effects set-up in Unify and switch from one to another depending on what track I was playing live...super useful.
Topic starter
November 17, 2025 3:07 pm
VST2 adding crashes Live
VST3 works great...
This is very interesting. The U2FX plug-in is simply a wrapper, which itself loads the Unify2 VST3. The U2AX audio-unit plug-in is similar, but it loads the AU version of Unify2. It's not at all obvious why Unify2 has issues loading certain other plug-ins while inside one of my wrappers.
Which of my wrappers were you using, and on which platform (Mac or Windows)?
November 17, 2025 9:03 pm
I'm on Ableton LIve 12.7, Windows 11, and I was using the VST2 version of the windows wrapper U2FX. VST3 version of the wrapper works fine.
I just tested again this morning in case it was a once off, and dropped the VST2 wrapper on a midi track in the audio section and got the same error. Last night I had put it on a send track.
November 24, 2025 10:43 pm
Hi Shane, great to correspond with you again. I was one of your Unify 1 beta testers.
My question today involves Unify STAND ALONE 2.00.2 public release version.
Is there any chance that installing your wrap plugins could cause Unify 2 stand alone to loose its ability to route External Audio through itself?
Yesterday, In unify 2 stand alone I was experimenting with running 4 external input channels of audio to any of 8 external outputs. Then Later, I briefly tried adding your plugins to see them in action in Logic. Today, returning to my work with the stand alone version I notice that its routing ability is completely gone. To troubleshoot I've tried 2 different interfaces, deleted and reinstalled the latest Unify 2.00.2 other recent versions, and even deleted the wrapper plugins from my M4 MacMini's library/audio/plug-ins folder. I probably messed something up on my own here but thought it wouldn't hurt to ask if the wrap plugins could cause this loss of routing.
(disregard my system info below, it is out of date and don't see where to change it)
This post was modified 11 months ago 3 times by Mark R
Studio system: M2 Mac Mini, 16GB, Ventura
old system: 5kiMac from 2014, quad i7, Big Sur 11.6.4
Topic starter
November 25, 2025 12:57 am
Is there any chance that installing your wrap plugins could cause Unify 2 stand alone to loose its ability to route External Audio through itself?
No. Simply having additional plug-ins installed on your system won't affect Unify 2 or any other application. If you're having trouble with audio routing in Unify 2, you might try going to its Audio/MIDI Setup, switching to a completely different audio interface (e.g. built-in speakers on a Mac), then switching back to your main audio interface. If that doesn't help, you'll need to get more detailed advice from PlugInGuru. I'm not familiar with any programming changes @wavesequencer has made since I handed Unify 1 off to him many months ago, so I can only offer general suggestions.
November 25, 2025 3:32 am
I've not really changed any of the underlying piping regarding audio in/out or midi out - it's pretty much the same as before.
November 25, 2025 4:50 am
Thanks Shane and Paul, just thought I'd check about the possibility of some kind of interaction there.
I'm thinking Audio/MIDI setup might be acting up. Back several years ago there used to be some dance we could do to - to clear some caches somewhere?
I will install Unify 2 on my wife's laptop tomorrow and then see if I can fix my studio's M4 MacMini setup. I'll let you know if I find a cause.
Studio system: M2 Mac Mini, 16GB, Ventura
old system: 5kiMac from 2014, quad i7, Big Sur 11.6.4
November 25, 2025 5:33 am
You do need to enable one or more inputs and multiple outputs (these must be 'checked') in the audio device settings in standalone - otherwise the options for the IO won't be shown in the UI layers. It's possible those settings have been lost somehow.
(Ref - page 40 in the current user manual, and page 60)
November 25, 2025 9:15 pm
Quick update on some further testing I did with the U2FX wrapper in Live 12.3 (just updated).
I thought I'd test out this again with Live (it previously would crash my system if I dropped the VST2 wrapper in a track or Send). This time I did not have audio enabled when adding the U2FX VST2 wrapper, and it 'landed' ok and I could access the interface. However, as soon as I enabled an audio interface (I tried Push3 Audio and Xone K2), Live still crashes, so there's something there it does not like.
November 25, 2025 9:42 pm
Solved -> Unify 2 losing External Audio input.
Hi again Shane and Paul.
I found the problem inside macOS System Settings:
Security > Microphone > Unify 2 was set to Off
I don't think I did this, I obviously know better than to do that!!? 🙄
I would rather blame it on LoopBack.app - where I was getting carried away with creating all kinds of additional creative routings. Or...
it was those two free standalone plugins from Shulz.Audio that I had installed right around the same time the issue occurred. Ya that's it...
Or maybe macOS was getting tired of my occasional feedback loops and decided to shut down my microphone. 🤔 Anyway - thanks for your responses and suggestions. If anybody else has this particular problem. The Mic Security setting is a pretty likely suspect.
This post was modified 11 months ago by Mark R
Studio system: M2 Mac Mini, 16GB, Ventura
old system: 5kiMac from 2014, quad i7, Big Sur 11.6.4
Topic starter
November 25, 2025 9:46 pm
VST2 adding crashes Live
VST3 works great, just added A Reaktor 6 effect to Send A and routed audio in and works like a charm.
There may well be an unpleasant interaction between a VST2 wrapper and a VST3 plug-in. The solution is: use the VST3 version of U2FX. The VST2 version was just an experiment, and it now looks like a failed experiment.
The reason I chose VST2 first was the lack of program change limitation on VST3 in Ableton..
If Ableton isn't able to send program changes to Unify 2, U2FX won't be able to either. This is an entirely separate problem that may take a long time to track down.
February 7, 2026 3:09 pm
Hi Shane,
Just came across this, thank you!! I just added it as a feature request before I saw it LOL
Stupid question, so this will call up (reference) Unify2 when you bring it into a DAW? If Unify 2 gets updated, this wrapper will use the updated version?
April 17, 2026 9:43 am
I have tried to use the rx2 drum midi file in UNIFY to be used as a metronome just doesn't play. Says- "not a valid midi file" thats the error. Not sure how to fix this error which seems Unify can't play Rx2 midi built into the system. Unify on iys own cant play these midi files.
This post was modified 6 months ago by IronMan1013
April 17, 2026 10:43 am
The wrapper worked with both unity stand alone and using Unity in the daw. I also download and installed a audio mac driver which opens up the use of Rx2 as a midi file built in internally. I guess it gives better understanding to any software that Rx2 is a valid midi fie. The drivers name for mac is "RX2_M_4.0.1.dmg"
Thanks for your response. I really do appreciate your help with this.
Topic starter
April 17, 2026 2:47 pm
RX2 files (aka ReCycle files) are not MIDI files. They are audio files that have been split into sections so an RX2 player program or plug-in can play them. Unify does not have a built-in RX2 player, but there are several RX2 player plug-ins available (including some free ones). That's probably what you found.
If you can, please share some information about the RX2 player you found, and where others can get it.