Feedback on Unify 1.06

hey all

installed the last update, Ableton Live don't see the VST anymore. 

Audiounits and Standalone works fine, osx10.12

anyone else with same issue?

After upgrading to 1.0.6 the application fails to start in both standalone and AU mode. I am running Logic Pro V10.4.8 and Mac OS 10.15.3.

Please can you let me know how to get this working again.

Neil.

@christian_h

Are you on Mac or Windows?

If Windows, the 1.0.6 installer would have asked you where to put the Unify VST; you have to make sure Ableton knows to look in that folder. Please check that the Unify.vst file was actually installed there; see https://pluginguru.net/unify/manual/doku.php?id=check-files-win-106 .

If Macintosh, definitely check to see if the Unify.vst got installed; see https://pluginguru.net/unify/manual/doku.php?id=check-files-mac-106 . Some users are finding that the Mac installer skips installing one or more of the plug-ins. I have absolutely no idea why this is happening, but I hope to get to the bottom of it eventually. If your Unify.vst file is missing, there's a link on that manual page to a Dropbox URL where you can download all three Unify plug-ins, so you can pop any missing ones in manually.

Please follow up and let us know what you find.

-shane

Posted by: @christian_h

hey all

 

installed the last update, Ableton Live don't see the VST anymore. 

Audiounits and Standalone works fine, osx10.12

anyone else with same issue?

@christian_h

I note in the Unify Manual under "Problems and Solutions" that there is a known problem for Abelton Live Macintosh not recognizing VST or VST3, but working with Standalone and as an Audio Unit. Shane says while he works on the problem to use the Audio Unit Version. I guess you did not get bitten by this bug in the earlier version, but see it now. Hope it works well for you as Audio Unit for the time being.

Posted by: @neilfarrimond

After upgrading to 1.0.6 the application fails to start in both standalone and AU mode. I am running Logic Pro V10.4.8 and Mac OS 10.15.3.

Please can you let me know how to get this working again.

 

Neil.

I'll need more detail to track this down, Neil. When you say "fails to start", what happens exactly?

The Mac maintains an Audio Unit cache, which might not get updated sometimes. Restarting the Mac will usually fix this.

For the stand-alone Unify app, if you get an error report popping up, please copy the full text out, save to a text file, and attach that file to a posting on this forum. That will help me determine why it's failing.

-shane

Updated to 1.0.6 on Windows 10 with standard file locations. No problems (just to confirm a standard Windows install).

Hello @getdunne and all,

I updated Unify from 1.0.3 to Unify 1.0.6 on my Mac mini MacOsX 10.14.4, tested in

Reaper 6.0.3/64, (AU, VST, VST3)

Ableton Live 10 Suite (10.1.7 Build:2020-01-06_f7eb4c8e0a)      (AU, VST, VST3)

Logic Pro X 10.4.8 (AU) and Mainstage 3.4.3 (AU)

Harrison Mixbus32C-5 rev 5.3-22-g497baee (AU)

Reason 10.4.1d4 (build 10.700) (Stable-Kanal) (VST)

Reason 11.1d9 (build 10.888) (Stable-Kanal) (VST)

 and standalone. No more problems...thank you.

Greetings and God bless, Marius

I am a Catalina OS user 10.15.3 

Firstly my cubase 10.5 pro recognises the VST3 and the Unify standalone works. 👍 

I have selected the standard place for installation :  users/shared/pluginguru/unify

I have lost all of the preset options from the built in synths and MIDI from the add layer (Audio / MIDI effect or instrument) option.  

The only things that show up now are the ones I added from my VSTs (Equator, M Power Synth and NI Kontakt) which these are stored : MacHD/Users/Shared/PluginGuru/Unify/Libraries/:ayer Presets/Instrument Layers

The built in VSTs are stored here : MacHD/Applications/PluginGuru/Unify/VST

But note that if you load a preset which uses any of the built in MIDI/Audio FX then these work normally when playing them.  So it seems to be a 'preset' availability issue.

- same goes for Master Effects : Replace layer from preset

-same goes for Aux Effects : Replace layer from preset

-add layer : MIDI effects : then selecting 'Ripchord' says you need to download.  I followed the link and dragged the VST download and copied it to the same folder as the VST folder :MacHD/Applications/PluginGuru/Unify/VST.  When the VST3 (File version 1.0.6) is scanned it says 'error developer cannot be verified' but you only have two simple files to drag into your VST folder ( Ripchord.vst3 and Ripchord.component )

-Macro editing windows appear on top of each other and do not remember their moved positions.

Playing unify normally and all working with my presets.

Best Regards,

Posted by: @larry-ludwick

Updated to 1.0.6 on Windows 10 with standard file locations. No problems (just to confirm a standard Windows install).

Thank you. Reporting successful updating at early stages of a software life is (imho) as useful as mentioning problems.

@chrisg-uk

It sounds like you might not have drag/dropped the Unify Basics.guru file into Unify after installing, or perhaps you moved the main Unify data folder somewhere else after doing so.

Have a look at https://pluginguru.net/unify/manual/doku.php?id=check-files-mac-106 , which explains what should be where on a Mac.

-shane

Posted by: @jabbawocky

If I call up Unify as a plug-in in my DAW, create a preset with 1 or 2 VST plug-ins (ARCADE from Output) - save the whole thing and then close the song in the DAW and call it up again, there are no more plug-ins in Unify!

Unify does not call up the plug-ins contained in the saved preset.

Why not?

Mac Pro 5.1 OSX 1013. Studio One 4. 

 

I'm sorry to hear that Unify is not working well for you in Studio One. You're not the only one.

The good folks at Presonus have just granted us NFR licenses for Studio One, so we'll be working on reproducing this, and trying to track down whatever the problem is. Please be patient; we hope to have an answer for you soon.

-shane

Posted by: @larry-ludwick

Posted by: @christian_h

hey all

 

installed the last update, Ableton Live don't see the VST anymore. 

Audiounits and Standalone works fine, osx10.12

anyone else with same issue?

@christian_h

I note in the Unify Manual under "Problems and Solutions" that there is a known problem for Abelton Live Macintosh not recognizing VST or VST3, but working with Standalone and as an Audio Unit. Shane says while he works on the problem to use the Audio Unit Version. I guess you did not get bitten by this bug in the earlier version, but see it now. Hope it works well for you as Audio Unit for the time being.

Thanks guys, even after deleting the VST and reinstall, Ableton didn't recognize it anymore so I force Ableton to rescan my VST folder and now it works fine!

@christian_h

Good News!

@getdunne

I am having the same issue on Mac OS 10.14.6  No Plugin Guru instruments nor MIDI effects showing when adding new layer.  All my other VSTs show.  Followed your link:   https://pluginguru.net/unify/manual/doku.php?id=check-files-mac-106    Everything checks out. Reinstalled- same issue.  

All Plugin Guru instruments & effects show up in Known Plugins; not in main GUI

Note: When pulling up a preset patch, all the Plugin Guru  instruments and effects load

@steve-moxi

This can happen if files and folders aren't in quite the right places. Please have a look at https://pluginguru.net/unify/manual/doku.php?id=files-folders-106 and check your machine again. In your case it sounds like your Presets folder isn't being found.

One thing you can try is going to Unify's Known Plugins view. You don't have to actually do any operations there; just open that page once, then go back to the layer-stack view and see if Unify can see the built-in plug-ins.

If all else fails, you can do a complete uninstall: https://pluginguru.net/unify/manual/doku.php?id=uninstall-106 , but that's a real sledgehammer. Don't forget to back up your own patches (in the User Library folder, or wherever you keep them) before doing that.

@getdunne

Uninstalled. Restarted. Installed fresh.  Same issue- see screenshot attached.

@getdunne

After fresh install, Presets folder not in Users/Shared/PlugInGuru/Unify.  See attached.  Could this be the issue?

@steve-moxi

Did you drag/drop the Unify Basics.guru file into Unify? If not, please do so.

Where is your Unify data folder located? Can you please open it (use the "Open..." button on the Unify Settings view) and post a screenshot of its contents?

@getdunne

Aha!  That worked.  I was following the instructions from the product web page for updating.  When I updated to the new version, it must have blown out all the Basics.  Should have read the RTF.  My apologies.  Thank you!!

https://youtu.be/9AEhiCJW4Xk

In case any of users against RTFM policy 😀

Hi,

- OSX Catalina 10.15.3

- Installed version 1.06 (had a previously installed version already on my system)

Version 1.06 does still not have acces to Synsopos application, which results in Synsopos error window

popping up when Unify (standalone) scans a plugin which has its license on e-licenser usb dongle.

Plugin scanning starts over again after it tries to scan such a plugin, resulting in a "scan loop" : it never reaches 100%

I had hoped this issue would be fixed in version 1.06 cause releaselog stated: improved plugin scanning.

Hope to see some feedback !

One thing about the install process of version 1.06, when you go this way:

- First, put the 2 .guru files in a folder of choice, let's call that folder X.

- Run version 1.06 installer.

- The installer asks if i want to set a custom location for its content.

- I say yes and point to folder X.

Now, when installation is ready and i open Unify standalone,

there are no factory presets, also not after doing "rebuild patch database"

I still have to drag drop the 2 .guru files onto Unify's user interface for all the paches to be scanned.

This makes no sense to me, i would assume that the patches would be automatically scanned after

i choose for custom patch content location.

Is this (illogical) behaviour by design or is it a bug ?

OSX 10.15.3 

The crash problem which I had reported on Version 1.02 still occurs in 1.06. 
This is inside "BPM - PAD chord Dance 2a".
The part which affects this is the Blue Arp preset 26 which can be changed in the top right corner.
It is number 26 which causes the whole application to stop an quit without error message.
This happens after playing  about 1 or 2 Minutes on one MIDI channel with sustain pedal.
If I change to number 25 or 27 the problem does not occur. So it must have something to do inside the program 26.
I am on Windows 10 (newest patch) with ASIO.
I already tested in other mode (windows audio with internal onboard audio) , but it still crashes after after 1 minute.
If playing very much notes, it does not crash earlier. 

For me, the installer did update the AU and VST but not the standalone App. It still said 1.0.3 after the Installation and there was not flash Icon for refreshing the Database. So I just extracted the App using Pacifist, replacing the Original which worked fine.

System: macOS 10.13.6 (High Sierra)

@getdunne

Thanks Shane.  I received the email update and watched the video.  I forgot to drag the basics file into unify.  All good now. 😎 

Back to playing endless hours of fun lol.

Cheers,

Posted by: @vanhaze5000

I still have to drag drop the 2 .guru files onto Unify's user interface for all the paches to be scanned.

This makes no sense to me, i would assume...

Assume all you want, but drag/dropping the .guru files is an important step of the update. That's why it was specified in the instructions.

I don't recommend moving the .guru files, and certainly not into the folder ("X") into which Unify unzips their contents. Just leave them in your Downloads folder, and delete them after use.

Posted by: @steve-moxi

...I was following the instructions from the product web page for updating...

I just checked the product page, and I see what you mean--there was no mention of the Unify Basics.guru file. I'll update the page.

Thanks for mentioning this. I'm so sorry our instructions weren't clear!

Logic crash.  See attached.  

Loaded 3 instrument layers:  Kontakt, UVI, Pianoteq

2 instances of Izotope 8 Imager.  Crashed when loading 2nd instance

@steve-moxi

Thanks for including the crash report. It looks like a null-pointer bug when updating the GUI right after adding the instance.

I have Izotope 7, and tested adding 2 instances of Imager here, trying both AU and VST versions. No problems. This might be a bug in the new version 8 Imager.

Could you please try repeating the experiment using the stand-alone Unify app, and let me know if that crashes? In my experiment, I started with an INIT patch, duplicated the one INST layer (with just the Sine Wave Synth), and added Imager on each of the two INST layers. Could you try the same with Imager v8, and let me know how that goes?

@getdunne

I don't know if this means anything in the discovery on this problem. I am not using Logic, but on Windows 10 in Sonar. I did the two instances with Ozone 8 Imager without any problems.

@larry-ludwick

Thanks, Larry. It would seem this is a Mac-only issue.

If anyone else has trouble with the Izotope plug-ins, please let us know.

@getdunne

Tried that in standalone.  No crash.  Also tried a version with the instruments I used initially.  No crash.  Maybe isolated to Logic with Izotope 8?

Posted by: @steve-moxi

@getdunne

Tried that in standalone.  No crash.  Also tried a version with the instruments I used initially.  No crash.  Maybe isolated to Logic with Izotope 8?

Possibly. I just re-did the test using Unify running inside Logic Pro X, and it works fine. Note I'm using MacOS High Sierra 10.13.6 on the Mac that has the Izotope plug-ins installed. That pre-dates all the high-strung security nonsense in Mojave (10.14) and Catalina (10.15), which may have a bearing on this.

@getdunne

Performed some variations in Logic:

1. 3 layers: Sine Wave Synths; Izotope 8 Imagers on each layer-  No Crash.
2. 3 layers: Sine Wave Synth; UVI; Pianoteq 6; Izotope 8 Imagers on each layer- No Crash
3. 3 layers: Kontakt; UVI; Pianoteq 6- as soon as Izotope 8 Imager added to Pianoteq layer, Logic Crashed

@steve-moxi

I did my best to reproduce this here. I have Kontakt 5, UVI Workstation, Pianoteq 6 (latest), and Izotope 7 Imager. I set up your scenario #3 in Logic, but no crashing. I think this might be an Imager 8 issue.

I have noticed MIDI hanging notes after a while playing normally complex patches. For example Key Hydra Rhodes.
To reproduce that I play 30 notes at one time with the elbow for 3 times. This is not normal of course, but on normal playing the application should not produce hanting tones. A single instrument will not cause hanging tones. So it has no cause on the incoming MIDI Data. 

Posted by: @pianoralf

I have noticed MIDI hanging notes after a while playing normally complex patches. For example Key Hydra Rhodes.
To reproduce that I play 30 notes at one time with the elbow for 3 times. This is not normal of course, but on normal playing the application should not produce hanting tones. A single instrument will not cause hanging tones. So it has no cause on the incoming MIDI Data. 

Thanks for the report. I'll try to reproduce this and study it.

After updating to 1.0.6 a lot of my custom plugin lists are empty now. See attached screenshot

System: macOS High Sierra 10.13.6

@klasus

Did you drag/drop the Unify Basics.guru file into Unify after updating to 1.0.6? Our instructions weren't clear about that (but have been updated).

You may also need to re-scan your plug-ins. Go to the Known Plugins view, click the Operations button and choose "Clear List". Then click the button again and choose whatever scan option you need, e.g. "Scan for new or updated VST plug-ins".

in the bpm Split thrill of dance preset there are no midi effects show so i can not edit the arp. if that work on others i can add a screenshot

I have install basic and unify std lib 1.06 update. 

Posted by: @user476565

in the bpm Split thrill of dance preset there are no midi effects show so i can not edit the arp. if that work on others i can add a screenshot

 

I have install basic and unify std lib 1.06 update. 

Unify cannot find BlueARP for some reason.

Please see my instructions to the previous post. You may need to re-scan your plug-ins. The "Clear List" step is very important, as it will eliminate old references to where the BlueARP plug-in used to be.

If this does not work, you may have to check for missing files; see https://pluginguru.net/unify/manual/doku.php?id=files-folders-106

I have try clear list and add new plugin. the blue arp is load correct, because the sound use arps and sound good. i only can not edit the midi effects. the problem i see in 1.0.2 too but i thought before i report i wait for new version, maybe it is fix. most other presets work ok, midi effects can edit.

another preset not work is grosse bass gross pad and crowd control. i do rebuild database. you can see that i do it because before it show no favourite select icon.

@user476565

Maybe a stupid question, but do you see the midilayers at all?. If so, try to click the layer button and pick show Midi, see Attachment.

ah yes thanks. this was the problem. i did not notice that show or show not midi layer can choose per preset.