Notifications
Clear all
Questions about UNIFY
68
Posts
21
Users
18
Likes
10.4 K
Views
February 10, 2020 9:40 pm
After playing a while with "BASS SPLIT Slap Bass & Pop Piano" the bass becomes silent and disappears.
The MIDI Panic Button inside Unify GUI brings it back.
I tested if this may come from my keyboard sending CC 07 , but it still happens after a while even if my keyboard sending Volume CC07 is set to off.
February 10, 2020 11:41 pm
After playing a while with "BASS SPLIT Slap Bass & Pop Piano" the bass becomes silent and disappears.
The MIDI Panic Button inside Unify GUI brings it back.
I tested if this may come from my keyboard sending CC 07 , but it still happens after a while even if my keyboard sending Volume CC07 is set to off.
How long is "a while"?
The bass is three layers in that patch (INST3 is only active for very high note velocities). Do all 3 layers die?
Next time this happens, before hitting MIDI panic, please try removing the "mda Loudness" instance from INST1, and see if this fixes it. I suspect this might be a problem with that plug-in.
It would be awesome if you could get this to happen while capturing MIDI into a DAW, and then export and post the MIDI file here, indicating at what time the bass cuts out. This could allow me to reproduce the issue and hopefully track down the cause.
-shane
mj_prod reacted
February 11, 2020 8:42 pm
This is the testfile for Bass disappearing
If I remove mda loudness the problem does not persist.
Hmm it does not come up again. Even with my testfile.
But before I could reproduce it multiple.
I booted my PC and now the problem is back and reproducible
I booted my PC and now the problem is back and reproducible
Even with deleted mda loudness the problem persists now.. Some bass tones sound, others sound not.
I think it is because the Bass Sound is a MONO sound. The problem comes up, when playing 2 or more tones in the bass area at the same time.
This post was modified 4 years ago 5 times by pianoralf
February 17, 2020 6:17 pm
Hi John and Shane,
Finally got the Mac Pro on a fresh drive with Mojave 10.14.6. When scanning only error is the elicense app and vsl sycron player. This also means any Cubase Pro 10.5.11 plugins or instruments did not import.
chris
February 17, 2020 6:58 pm
Thanks for the report. We're still waiting for a response from Steinberg about how to support eLicenser.
mj_prod reacted
February 22, 2020 12:50 am
Not a peep. Steinberg are not exactly famous for being responsive to users, or developers, or anyone.
February 22, 2020 9:09 am
I wanted to change the Skin of the OB-XD VST to the Unify Version on macOS, but there aren't any skins in it. The AU Version has skins, but the VST doesnt, the "Skins" Ctaegory is empty:
February 22, 2020 12:08 pm
Installing the standard OB-Xd adds a folder called discoDSP to your own Documents folder, with a folder called OB-Xd inside that.
Move this new OB-Xd folder (i.e., ~/Documents/discoDSP/OB-Xd) somewhere else, and all versions of OB-Xd should revert to using our version at /Users/Shared/Documents/discoDSP/OB-Xd.
February 22, 2020 2:52 pm
@getdunne Thanks for your reply. But there is no discoDSP Folder at Users > Shared > Documents on my macOS System
February 22, 2020 3:09 pm
@getdunne Thanks for your reply. But there is no discoDSP Folder at Users > Shared > Documents on my macOS System
Well, that's why you have no skins. That's where OB-Xd is looking. If you have another discoDSP folder somewhere, move or copy it there.
February 22, 2020 3:50 pm
@getdunne Okay, I copied over the Folder from the discoDSP installation. I have Skins now – not the one I wanted but hey, it's okay. I don't care.
I am just a bit frustrated that I have to fix so much stuff with each update/every time I work with it:
– Empty Plugin Categories which I have to rebuild manually (yes, I installed all library and the updates to it and the basic stuff)
– Crashing Host due to plugin incompatibilities – sometimes only AUs work, sometimes only VSTs (brainxorx, soundtoys)
– Inserts that won't stay bypassed after saving and reloading a patch.
– Strange multicore load distribution issues in Logic Pro X, where all of a sudden a CPU core is maxed out and bringing the system down to a halt when it distributed the load evenly among the cores fine the last time a session was open.
– Macros losing their bindings if you move inserts around.
I bought this plugin for layering my synths not for presets because they don't fit my style and genre. All I wish for is a stable product that behaves reliable and as expected – nothing more.
February 22, 2020 4:11 pm
I'm sorry to hear that Unify doesn't work for you. Unify is a very new product; it may be some time before we achieve the level of stability you need.
I have forwarded your comments to John, and suggested that he offer you a refund.
-shane
February 22, 2020 10:00 pm
@klasus -
Hi Klasus - I appreciate your feedback - we are far from perfect and some of these details you are reporting are new to us. We will work to improve Unify over time for sure! Shane and I appreciate your spirit and that you wish to support our Unify plug-in. Your patience is appreciated. I'm not sure why a new discoDSP folder wasn't created with the Unify Skin - here is the skin for you to download and install if you wish:
https://www.dropbox.com/s/ghcba9fmk6tlj7g/GURU%20OB-X%20Classic.zip?dl=0
Free to use wherever you wish - looks best in Unify of course 😀
Cheers and thank you again.
Life is Sound / Sound is Divine
www.pluginguru.com
klasus reacted
February 22, 2020 10:36 pm
Updated to MacOSx Catalina 10.15.3. Logic Pro x receives this error when scanning the plug in
“Unify.component will damage your computer” and therefore not show as a plug in in Logic Pro x. Any ideas? Running standalone is fine using control and open option.
February 22, 2020 11:04 pm
@pluginguruforums Thanks you very much for sharing the Skin. It works fine. I am looking forward to watching the latest stream and the upcoming 1.0.9 update.
February 23, 2020 1:32 pm
Updated to MacOSx Catalina 10.15.3. Logic Pro x receives this error when scanning the plug in
“Unify.component will damage your computer” and therefore not show as a plug in in Logic Pro x. Any ideas? Running standalone is fine using control and open option.
Sorry about this. Please be patient; we will have a new update very soon, which may resolve the problem.
February 25, 2020 9:27 pm
I'm sorry to hear that Unify doesn't work for you. Unify is a very new product; it may be some time before we achieve the level of stability you need.
I have forwarded your comments to John, and suggested that he offer you a refund.
-shane
Hi Shane - Does Skippy offer a refund or store credit if it turns out it's not for me? I'm still not sure whether this is anything I would use, and since there is no trial, there's no way for me to evaluate it for my needs without throwing $50-60 bucks at it. Watching the videos, I honestly just don't see the appeal since I don't habitually layer tons of synths, but I mean... it's Skippy, so... Even if he doesn't offer a refund, I'd be happy with store credit for anything else. Let me know, thanks!
February 25, 2020 10:23 pm
Also note the new "v1.0.9" version of Unify Standard Edition is just to support customers upgrading from the Demo.
Customers who have already installed v1.0.6 (Mac) or v1.0.7 (Windows) DO NOT NEED ANYTHING FROM v1.0.9.
mj_prod reacted
February 11, 2021 11:45 am
Updated to MacOSx Catalina 10.15.3. Logic Pro x receives this error when scanning the plug in
“Unify.component will damage your computer” and therefore not show as a plug in in Logic Pro x. Any ideas? Running standalone is fine using control and open option.
Sorry about this. Please be patient; we will have a new update very soon, which may resolve the problem.
Hi, I have this problem with Unify 1.3.2 / Logic 10.6.1 / MacOS 10.15.7
Page 2 / 2
Prev
