Unify by PluginGuru; The next big thing?

[Examigan]

nvm

[tuzemec]

Any idea if it is possible to sell my license? I've tried to contact the author through their website, but I didn't get any answer.

I'm sorry to hear you didn't get an answer via the web contact form, and I'll take this up with my partner John immediately. In the meantime, please contact John directly at UnifySupport@PlugInGuru.com, and he or Taylor will get back to you.

May I ask why you want to sell your license? Are you dissatisfied with Unify? If so, you can request a full refund.

Thanks for the quick response.
There's nothing wrong with the product - it was just an impulsive buy based on the positive reviews here, but it just doesn't fits my current workflow.
I bought it in February and I guess it's not right to ask for refund. I'll just put the license for sale, if that's ok with you, and we'll see what happens.

Cheers!

[NTO]

...please note there's a "1.2.2" coming.

So that will be all that is required? No need to do ".0" or ".1"?
TIA

[getdunne]

The v1.2.2 updates should now be available at pluginguru.com (log in, click "my account" and scroll down to "libraries you own") and also direct downloads from https://ilio.com/unify-updates.

Thanks everyone for your patience. @NTO You can install the v1.2.2 update directly over v1.1.10 or any older version. If you do have an older one, though, I'd suggest using the "full install" download, because it includes the full Unify Standard Library with all updates back to day one.

[getdunne]

There's nothing wrong with the product - it was just an impulsive buy based on the positive reviews here, but it just doesn't fits my current workflow.
I bought it in February and I guess it's not right to ask for refund. I'll just put the license for sale, if that's ok with you, and we'll see what happens.

Makes sense. You're welcome to a refund if you wish; you need only ask. As with any musical instrument, though, I agree it's nicer to find it a new loving owner

When you do find a buyer, please have them contact UnifySupport@PlugInGuru.com so we'll get their contact info and get them set up to receive notices about updates, etc., and to make sure their license gets set up without any problems.

[Kalamata Kid]

Thanks everyone for your patience. @NTO You can install the v1.2.2 update directly over v1.1.10 or any older version. If you do have an older one, though, I'd suggest using the "full install" download, because it includes the full Unify Standard Library with all updates back to day one.

I installed Unify 1.1.10 but I suspect I did not do it properly.
IIRC I did not do a two part installation.
I have yet to play with it.
Is there a way to tell if I installed it properly?

Would it be prudent to un-install V1.1.10
Then watch the video then Install the full Unify 1.2.2?
"Unify Video Manual 1/5: Installation"

[getdunne]

I installed Unify 1.1.10 but I suspect I did not do it properly.
IIRC I did not do a two part installation.
I have yet to play with it.
Is there a way to tell if I installed it properly?

Would it be prudent to un-install V1.1.10
Then watch the video then Install the full Unify 1.2.2?

"Two part installation" simply means you run the installer first, then run Unify and load the .guru file to get the patches and samples.

You do not need to uninstall any older version. Just do the "full" 1.2.2 install and you're good.

(The only difference between "full" and "update" is the size of the downloads, because the "full" one contains the complete .guru file. The "update" has a smaller one with just what's changed since 1.1.10.)

[Chipi]

Hi Shane, could add the 'undo' function with the layers? It happens that when you add one, and then another and another, and then use 'revert' it returns to the original sound losing the layers before the last one. Hopefully you can program it! Thanks Shane!

[trusampler]

Shane,
Earlier in this thread, you mentioned there was going to be support for hardware synths in Unify.. Is that going to ever happen?

[getdunne]

Hi Shane, could add the 'undo' function with the layers? It happens that when you add one, and then another and another, and then use 'revert' it returns to the original sound losing the layers before the last one. Hopefully you can program it! Thanks Shane!

Undo is definitely on the to-do list, but it's a very complex function, so may not appear for some time.

In the meantime, "save early and often".

[getdunne]

Shane,
Earlier in this thread, you mentioned there was going to be support for hardware synths in Unify.. Is that going to ever happen?

Yes! Live audio-in and MIDI-out will definitely be part of the Expanded I/O add-on pack for Unify, but work on Unify 1.2 has meant that this may not come out until sometime in the new year.

[Chipi]

Hi Shane, could add the 'undo' function with the layers? It happens that when you add one, and then another and another, and then use 'revert' it returns to the original sound losing the layers before the last one. Hopefully you can program it! Thanks Shane!

Undo is definitely on the to-do list, but it's a very complex function, so may not appear for some time.

Today it happened to me that I was editing some layers that sounded wonderful and without wanting to select some of the sounds of the sound panel and goodbye the one I was editing. Tell me you can add a --- > ''Are you sure you want to leave the current sound '' ? < --- I couldn't redo the one I was editing unfortunately and I lost it. That's critical.

[getdunne]

Tell me you can add a --- > ''Are you sure you want to leave the current sound '' ?

I can add this, it's on the list, and I realize how important this is.

What's held me back is that actually detecting when the patch has changed is not simple. Unify has to have a way to detect changes you make inside individual plug-ins as well as changes it will know about automatically (such as adding or removing layers). I know how to do this now, but it will take a while to implement.

The safest approach, in the meantime, is to save everything you do in a "work in progress" library (where you don't worry about fancy patch names, tags, etc.), and keep hitting Option/Alt + Save often. Then if you accidentally select another patch and it all disappears, you can just load it again (maybe minus the last couple of edits).

Another useful trick is to add a single Unify layer and use that to audition new sounds. You can open the embedded Unify's GUI and change patches, etc., and the rest of your main patch will be safe.

[WatchTheGuitar]

Tell me you can add a --- > ''Are you sure you want to leave the current sound '' ?

I can add this, it's on the list, and I realize how important this is.

What's held me back is that actually detecting when the patch has changed is not simple. Unify has to have a way to detect changes you make inside individual plug-ins as well as changes it will know about automatically (such as adding or removing layers). I know how to do this now, but it will take a while to implement.

The safest approach, in the meantime, is to save everything you do in a "work in progress" library (where you don't worry about fancy patch names, tags, etc.), and keep hitting Option/Alt + Save often. Then if you accidentally select another patch and it all disappears, you can just load it again (maybe minus the last couple of edits).

Another useful trick is to add a single Unify layer and use that to audition new sounds. You can open the embedded Unify's GUI and change patches, etc., and the rest of your main patch will be safe.

As an interim measure could you maybe create a visible lock at the global and layer levels which when on means you can't load in a whole new overall preset or delete an existing layer, only add new ones or update ones that aren't also locked?
I have loaded a number of presets which wiped everything when I meant to add as a new layer and it is really frustrating.

[getdunne]

As an interim measure could you maybe create a visible lock at the global and layer levels which when on means you can't load in a whole new overall preset or delete an existing layer, only add new ones or update ones that aren't also locked?

That's a terrific idea, thank you. I'll look into this.