Last seen: August 20, 2026 1:09 pm
@ssquared I wasn't involved in the development of Guru Sampler 2. @Wavesequencer can you answer this question about lag times?
@ssquared Unify does indeed run incoming MIDI past the macro knobs before sending what remains through the layers (including MIDI effect layers). He...
Yes, that should be all you need. If the drive with your Unify files is the same as before, you might not even need to rebuild the database. After c...
Muting layers (using the "M" buttons) simply reduces their output volume to zero; CPU usage will be unaffected. Disabling layers (by clicking the gr...
This sounds like a permissions issue on MacOS. Basically, the Unify stand-alone app has write access to your patches, but your DAWs do not. Try sett...
I've lost count of the number of times I had to re-download and re-install the LABS instruments, because of some glitch in their plug-in. Spitfire mak...
I can answer this in three ways: You can achieve most of what you want by changing the shape of the individual response curves. See 1st paragraph ...
It looks like John uploaded a .zip file to Dropbox, forgetting to rename it to .guru first. If you have downloaded the file unify2_smd_u2_6_27_updat...
@ermatlock Thanks for letting me know your results. I have passed this on to John and Paul. We may need to discuss this with U-He directly.
@ermatlock I'll let John know about the Subsonic Artz libraries. Have a look at the layer-reuse page in the old Unify manual. It should still be r...
I checked, and the patches in the unified Diva library on the PlugInGuru web site were not saved with multi-core on. If you haven't re-saved them, wha...
Both Unify and DAWs like Ableton Live make use of multiple cores. In some cases this means that a plug-in's own multi-core processing doesn't work wel...
The "x64" is included in the plugin name because the unified library was almost certainly made on a Windows PC, where many VST2 plugin file names ende...
Good thought. @Wavesequencer please take note. While CC lanes would be useful, individual parameter-automation lanes (and perhaps macro-parameter lane...
I think you just answered your own question, but I can add two thoughts: The original SuperMacho Drums was driven by MIDI sequences, some of which...
Renaming libraries is actually quite complex, because there are several places where the library name can appear within patch data. I created a utilit...
@Wavesequencer Manual creation of .guru files is error-prone. Unify probably needs an "export library as .guru file" function.
@wavesequencer No ideas about the display glitches, but if they're occurring only for plug-ins hosted in ComboBox instances, not in Unify itself, I'd ...
Unify has never handled sleep/wake fully on the Mac. I suspect there's something it has to do, to reconnect to the audio driver on wake, which it does...
@Wavesequencer please note--possible installer issue. @unifyman2024 are you installing on a PC or a Mac?
I do this kind of thing frequently for John, using a C++ program I hack at the source level for each situation. This can definitely be done using Pyth...
For some useful background and some Python scripts, see/p> Within that GitHub repo you'll also find a C++/JUCE program called PatchReformer that can...
None of this is my responsibility anymore, but I should mention that you are talking about "unified" patch libraries, which are basically gifts provid...
@ironman1013 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 p...
Unify macro parameter links are based on the parameter name, not the index (aka ID). I understand now that this is opposite to how most DAWs/hosts wor...
@northwood I lived in Toronto briefly in the early 80s. I grew up in London, ON and have spent most of my time in Kingston since 1997.
Very nice! I've been to that park with all the flowers, and I think I recognize some of the street scenes at the end.
Thank you for trying these tests. This is beyond what I can help with. @wavesequencer please step in. I can't tell if there have been any other c...
This certainly sounds like a MIDI issue rather than an audio issue. Is this happening on every patch? Does it happen on an INIT patch? Have you e...
OK, those are the primary troubleshooting steps for audio output, AND you have already verified that you hear a tone when using the test button, which...
@caldera If I were you I'd start by rebooting the PC, in case the ASIO driver got into an invalid state. If the problem persists, try switching to t...
@chasapple Yes, this is exactly the intended behavior. The load-mode icons at the bottom allow you to specify what happens when you LEFT-click on pa...
@chasapple The usual workflow in this case is: Open the new embedded Unify (the one that has the patch you don't like), and use its patch browser to...
@caldera Make sure you don't have another program running (e.g. a DAW), trying to use the same device.
That's the correct behavior in MIDI/Latch mode. I confirm that Unify 2 doesn't do this. [/quote]
Unfortunately, they don't. It would be wonderful if the "latency" reported by instrument plug-ins were consistently equal to the time it takes the ins...
If I understand correctly, your problem arises because you're layering multiple virtual instruments, but some "speak" more promptly than others in res...
Email UnifySupport@PlugInGuru.com and Taylor will work through this with you.
@joerollerblade I agree, the ability to select specific hardware input/output ports per layer in the Unify stand-alone app is probably the most impo...
Consider using the free Snapshot plug-in.
This is as intended. The embedded Unify's transport will normally follow that of its host--which is the outer Unify. It has nothing to do with how the...
@mannyrdi This kind of bug is very hard to track down based only on the high-level crash dump. The best approach is to try to find a recipe to make ...
That would be nice, but it may be a long time getting there. Unify has always been primarily an instrument, not a live-performance host. If you're s...
Perhaps, but we have the source code (which includes modifications specifically for Unify), so it might be better to fix it ourselves. I'm pretty sure...
