Notifications
Clear all

Menu freezing & instrument not loading

6 Posts
2 Users
0 Likes
73 Views
(@rvj84)
Active Member
Joined: 7 months ago
Posts: 9
Topic starter  

I'm having trouble with not being able to select things / perform actions when using the menus in Unify, when my DAW project is busy. When I say busy, I mean there is quite a lot going on, but I'm still not maxing out the CPU. I'm able to click to open & view the menus, but once they're open, they don't respond to any more clicks.

I also would like to be able to use discoDSP's Discovery Pro in Unify, but I can't get it to load. Are there any known issues for that?

Using VST3 in all instances

i7-6700K CPU @ 4.00GHz / RAM 16.0 GB

Windows 10

FL Studio 21

Any other info required, please let me know.


   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 

@rvj84

You must set FL Studio to "use fixed-size buffers" with Unify for good performance. If you haven't done this, please do so and then check again.

What exactly is the problem with Discovery Pro? The latest v7.9 is loading fine for me in Unify on Windows, both VST and VST3 versions.


   
ReplyQuote
(@rvj84)
Active Member
Joined: 7 months ago
Posts: 9
Topic starter  

@getdunne 

"use fixed-size buffers" was / is enabled, so this setting does not help.

With the Discovery pro issue, when I select the VST from the list, the name appears in red text and in brackets, and does not open when double clicked. I'm also on v7.9.

This post was modified 4 weeks ago by rvj84

   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 

@rvj84

Is this a recent/new install of Unify? Which version? Has Unify ever worked for you in FL Studio? Does the menu-freezing only happen when FL Studio is recording or playing, or even when it's idle?

I'm not seeing this on my Windows 11 PC with the latest version of FL Studio and Unify, so I'm missing something.

When a plug-in shows in red text and brackets, this means Unify was unable to open it. It could be as simple as the plug-in having been moved to a different location, or possibly due to a version update. I advise rescanning as follows:

  1. Go to Unify's Known Plug-Ins List.
  2. Scroll down to the entry for Discovery Pro, right-click and choose "Show folder containing plug-in". If the folder which appears does not contain the Discovery Pro plug-in, that's your problem.
  3. Right-click again and choose "remove plug-in from list".
  4. Click the Operations... button and choose "Select and scan directly..."
  5. Navigate to wherever the Discovery Pro plug-in actually is, and click OK.
  6. Return to the layer-stack view in Unify, and try loading Discovery Pro again.

   
ReplyQuote
(@rvj84)
Active Member
Joined: 7 months ago
Posts: 9
Topic starter  

@getdunne 

Thanks, I was able to fix the Discovery Pro issue. It was located inside an extra folder directory in the VST3 folder.

Regarding, the menu freezing... my Unify v1.10.2 was installed in July last year and I have not encountered any issues with it before now. The freezing only occurs when the DAW is playing, not when idle.


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 

Posted by: @rvj84

I was able to fix the Discovery Pro issue. It was located inside an extra folder directory in the VST3 folder.

Steinberg made a change to the VST3 format, where each VST3 plug-in can now be a folder, rather than just a single file. You must have originally scanned an older version of Discovery Pro VST3 that was a single file, then with the update, it got replaced by a folder, so Unify's path was left pointing to a folder rather than the VST3 file within it.

Regarding, the menu freezing... my Unify v1.10.2 was installed in July last year and I have not encountered any issues with it before now. The freezing only occurs when the DAW is playing, not when idle.

I suggest you take this up with Image-Line. I did a bit of web searching, and found a few similar complaints. It might be something that crept in with a recent update of FL Studio. This is the first time I've seen this reported.


   
ReplyQuote
Share: