Notifications
Clear all

Converted Omnisphere Patches


Anto
 Anto
(@anto)
Eminent Member
Joined: 2 years ago
Posts: 24
Topic starter  

Hi Shane, auditioning the newly converted Omnisphere patches are taking 15 seconds and more

inside Unify standalone and in my daw, Cubase 10.

Adding on patches load pretty much instantly. 

Any thoughts or fixes?


Quote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2954
 

@anton

We don't have an answer for this yet, still gathering information.

Some people experience these delays; others don't.

 


ReplyQuote
Nico Fyve
(@nico)
Eminent Member
Joined: 2 years ago
Posts: 47
 
Posted by: @anton

Hi Shane, auditioning the newly converted Omnisphere patches are taking 15 seconds and more

inside Unify standalone and in my daw, Cubase 10.

Adding on patches load pretty much instantly. 

Any thoughts or fixes?

Just curious, are you also running Unify on Windows? See also this thread from a couple of days ago: 
https://forums.pluginguru.com/questions-about-unify-v1-0/o2-unified-libraries-slow-to-load-when-replacing-patch-in-single-layer/

Cubase 11 Pro, Win 10 Pro (x64), several different midi controllers


ReplyQuote
Lowell
(@lowell)
Trusted Member
Joined: 2 years ago
Posts: 92
 

I was wondering something sort of related to this. Like, if I change one patch (single Omnisphere or whatever other longer-loading VST) to another patch that uses the same VST, Unify has to re-load the VST. This is like most other similar products. But one product that I use for live performance called Cantabile has a "pre-load" feature that loads all the VSTs for all songs in the background when you open the set. Then switching from one song to another is instant.

This isn't the same thing of course. But what if, in some future update to Unify, when switching to a second patch that used at least one of the same VSTs it would keep that VST loaded and not have to completely reload it? Might not be possible due to other things like sending parameters to that already-loaded VST but just a thought.


ReplyQuote
Anto
 Anto
(@anto)
Eminent Member
Joined: 2 years ago
Posts: 24
Topic starter  

@nico Hey, yes i'm using Windows 10


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2954
 
Posted by: @lowell

But what if, in some future update to Unify, when switching to a second patch that used at least one of the same VSTs it would keep that VST loaded and not have to completely reload it?

I've looked into this already. It's possible, but very difficult.


ReplyQuote
Nico Fyve
(@nico)
Eminent Member
Joined: 2 years ago
Posts: 47
 

@anton @lowell - Just in case you're interested, I've experimented with a workaround, and posted my results (so far) in the original thread about this issue:

https://forums.pluginguru.com/questions-about-unify-v1-0/o2-unified-libraries-slow-to-load-when-replacing-patch-in-single-layer/#post-4344

Cubase 11 Pro, Win 10 Pro (x64), several different midi controllers


ReplyQuote
Share: