Unify by PluginGuru; The next big thing?

[getdunne]

awesome!
I've been wondering... have you all found a UI designer yet?

Yes, several. How good/experienced/helpful they will be remains to be seen.

[SciFiArtMan]

Unify 1.0.6 Update is NOW Available!

Thanks for the update! The key trigger selection in Guru Sampler is greatly appreciated!

Someday I'd like to see an Auto LFO w/Attack function (so great for pads!), if possible. Thanks again!

[getdunne]

Someday I'd like to see an Auto LFO w/Attack function (so great for pads!), if possible.

Do you mean something like a vibrato with delayed onset, or something else?

[SciFiArtMan]

Someday I'd like to see an Auto LFO w/Attack function (so great for pads!), if possible.

Do you mean something like a vibrato with delayed onset, or something else?

Well, yes, in it's most common form = a vibrato that fades-in automatically. But a fading-in pulse/ramp/other shaped LFO could also be nice. And auto so it's the same on every trigger, and therefore becomes part of the patch, so to speak. Nice on some leads, but extra cool on longer pads, IMO.

But if there's a way to auto-fade-in a vibrato right now, I'd love to know!?

[woodsdenis]

Unify 1.0.6 Update is NOW Available!

• Log Into your PlugInGuru.com Account to update!
  • Download links are found on the "MY ACCOUNT" page.
  • You need the installer (Mac or PC), plus the Library UPDATE 1.0.6.guru file.
  • Drag the .guru file into the Unify GUI AFTER updating to 1.0.6, and you're good to go!
  • First-time buyers will need to download the Unify Standard Library.guru file instead of the smaller UPDATE file.

• PLEASE READ THE ENCLOSED READ ME for details on this update.

• Our VST folder and PlugInScanner application now live in your system's Applications folder.
  • The Data folder will now only contain Libraries and Presets.
  • Please don't move or delete anything from the PlugInGuru Application folder
  • The PlugInGuru data folder can be placed anywhere.

• Official Change Log is now at https://pluginguru.net/unify/change-log.html

Have fun and thank you to all of your support!

Hi Shane

After installing 1.06 I get the following

Screen Shot 2020-02-06 at 22.13.16 (2).png

I can't access the xml file that held the bundled Unify instruments/FX or midi fx .They have disappeared from the shared/pluginguru folder. This means for example if I load an init Guru sampler the only thing I can exchange it for is one of my own plugins, Also I can't access any of the Unify fx either. However they do load if they have been saved with an existing factory preset. Any ideas

OSX 10.12.6

Update.... I had them on a time machine BU and coped them into the shared folder again and all is back too normal, strange.

[DrumAddict]

Unify 1.0.6 Update is NOW Available!

• Log Into your PlugInGuru.com Account to update!
  • Download links are found on the "MY ACCOUNT" page.
  • You need the installer (Mac or PC), plus the Library UPDATE 1.0.6.guru file.
  • Drag the .guru file into the Unify GUI AFTER updating to 1.0.6, and you're good to go!
  • First-time buyers will need to download the Unify Standard Library.guru file instead of the smaller UPDATE file.

• PLEASE READ THE ENCLOSED READ ME for details on this update.

• Our VST folder and PlugInScanner application now live in your system's Applications folder.
  • The Data folder will now only contain Libraries and Presets.
  • Please don't move or delete anything from the PlugInGuru Application folder
  • The PlugInGuru data folder can be placed anywhere.

• Official Change Log is now at https://pluginguru.net/unify/change-log.html

Have fun and thank you to all of your support!

there is also a bug if you install Unify to another HDD as C: , Like D:\Program Files\PlugInGuru\Unify

the PlugScanner can not be found . the Helper Folder with the Plugscanner needs to be installed on the main drive C:

[DrMEM]

Did "macro knobs can send midi cc" not make it into this release?

[emasters]

Plug scanning is better with 1.0.6. But, it still takes a long time to effectively rescan plugins that have already been scanned. Trying to add a new plugin today on OS X High Sierra, takes an hour to rescan everything (AU, VST, VST3) to get the new plugins scanned. No doubt this is an over-simplification -- but couldn't one create a table of plugin filenames with time-stamps when the file was written. If the time-stamp hasn't changed, don't scan it. It seems so much of the time is spent rescanning files that haven't changed. I appreciate if a file has changed, it needs to be verified before adding to the list of plugins. But if it hasn't changed, can't you just ignore it? Other apps are so much faster at scanning - but it seems they only rescan the plugins that have changed. As I mentioned, seems like the structure in 1.0.6 is much better and one can better cancel scanning manually. Now if it only went faster.....

[getdunne]

@woodsdenis

Please report this issue to UnifySupport@PlugInGuru.com and we'll follow up.

Have a look at this manual page: https://pluginguru.net/unify/manual/dok ... es-mac-106. It explains exactly where the installer is supposed to put everything, and how to tell if something is missing or didn't get updated properly.

Unify v1.0.6 changes where Unify looks for the bundled plug-ins; they are no longer in the /Users/Shared folder at all, but rather are in /Applications/PlugInGuru/Unify/VST.

[getdunne]

there is also a bug if you install Unify to another HDD as C: , Like D:\Program Files\PlugInGuru\Unify

the PlugScanner can not be found . the Helper Folder with the Plugscanner needs to be installed on the main drive C:

Correct. I have added a note to the Windows install instructions at https://pluginguru.net/unify/manual/dok ... installing, to say that Unify must be installed on C:.

I wasn't aware that our installer would even offer the option to install on another drive, because this never showed up in my testing. I learned this morning that Windows installers only show this "Select Destination Location" page on new installs, and I did all my testing on PCs where I had already installed a previous version of Unify.

Installers on Windows are like a rigged game-show, but on MacOS Catalina they're more like being publicly disemboweled.

As always, I thank everyone for their patience as I climb all these learning-curves at once!
-shane

[getdunne]

Did "macro knobs can send midi cc" not make it into this release?

It certainly did. Macro knobs send on the same CC number that has been assigned to control them externally. Please check by starting with an INIT patch and swapping out the Sine Wave Synth for a MIDI Monitor (Swap > Unify Standard > Special > MIDI Monitor). If you don't see CC messages when you adjust a macro knob (which has been assigned a CC number) using the mouse, let us know at UnifySupport@PlugInGuru.com.

[getdunne]

Plug scanning is better with 1.0.6. But, it still takes a long time to effectively rescan plugins that have already been scanned. Trying to add a new plugin today on OS X High Sierra, takes an hour to rescan everything (AU, VST, VST3) to get the new plugins scanned. No doubt this is an over-simplification -- but couldn't one create a table of plugin filenames with time-stamps when the file was written. If the time-stamp hasn't changed, don't scan it. It seems so much of the time is spent rescanning files that haven't changed. I appreciate if a file has changed, it needs to be verified before adding to the list of plugins. But if it hasn't changed, can't you just ignore it? Other apps are so much faster at scanning - but it seems they only rescan the plugins that have changed. As I mentioned, seems like the structure in 1.0.6 is much better and one can better cancel scanning manually. Now if it only went faster.....

The plug-in scanner doesn't re-scan plug-ins that have been scanned already, but it does display their names. It should blitz through the already-scanned ones, and only slow down once it starts in on new ones. It DOES create a list such as you described.

That said, you may be dealing with some issue that needs more careful investigation. Please report your experience to UnifySupport@PlugInGuru.com, and provide as much detail as you can.

[DrMEM]

Did "macro knobs can send midi cc" not make it into this release?

It certainly did. Macro knobs send on the same CC number that has been assigned to control them externally. Please check by starting with an INIT patch and swapping out the Sine Wave Synth for a MIDI Monitor (Swap > Unify Standard > Special > MIDI Monitor). If you don't see CC messages when you adjust a macro knob (which has been assigned a CC number) using the mouse, let us know at UnifySupport@PlugInGuru.com.

I see. Yes, that works, but I was expecting a lot more. I see I was a bit imprecise when I asked my question about macro knobs and cc data last week.

I am hoping to be able to use a macro knob to send *any* combination of cc data to *any* selection of instruments using a custom cc curve for each send. Right now you can set up sends to instrument parameters like this (with custom curves for each send), but some instruments do not expose parameters and respond only to cc data so I need to be able to send cc data like this as well. (I’m looking at you, EW Play.) Ideally the macro knob would *not* send along the midi cc data used to control the knob itself (or would give the user the choice as to whether to send it along or not.)

For instance, I’d like to set up macro 1 to be controlled by the mod wheel, which sends ccs 2 and 11 to instrument 1 (with custom send curves for each send), sends cc 3 to instrument 2 (again with a custom curve), and sends cc 1 to instrument 3 (again with a custom curve).

Does that make sense?

[getdunne]

I am hoping to be able to use a macro knob to send *any* combination of cc data to *any* selection of instruments using a custom cc curve for each send.

That's definitely on our road-map.

Thanks for the detailed request. We appreciate all these suggestions and will get to them as soon as we can. Just now we're having to deal with a flood of much less-interesting technical issues with things like installers, file management, host/plug-in compatibility, etc., but we'll get there, I promise!

-shane

[DrMEM]

Understood!

I'm guessing you already have most of the infrastructure there to make it happen, so hopefully it won't be too hard to implement when you are able to get to it.