Notifications
Clear all
Questions about UNIFY
17
Posts
4
Users
2
Likes
994
Views
Topic starter
January 23, 2021 4:34 pm
I was playing through the new patches in the new BBC discover library, when I noticed a lot of distortion. This was particularly true of patches that made multiple use of orchestral sounds and were playing back what I assume were midi files. When I checked into the source of this distortion I noticed that these very complicated patches were over-driving a single core on my machine. I have a 15" 2015 MacBook Pro with 2.5 GHz Quad-Core Intel Core i7 with 16 gb ram. Is there a way I can get Unify to distribute the processing over more cores on this machine. Sorry if this a dumb question.
January 23, 2021 8:14 pm
Which patch(es) cause the problem? Unify will normally distribute over all available cores.
Are you running stand-alone or in a DAW (if so, which one)?
What else is your computer running?
Check Activity Monitor in macOS, to see what your CPU cores are actually doing. Do you see some pegged while others are near-idle?
Topic starter
January 23, 2021 10:05 pm
@getdunne Hi Shane,
I’ve already talked to John a bit about this. I am running a six-year-old MacBook Pro. It has an i7 processor which translates to 8 cores 2.5. and 16 gigs of ram. Until recently, everything has run fairly well. Most of the multiple plug-in discovery library patches it only processes on a single core and it maxes out that core so I get a lot of distortion. I’m referencing the logic CPU metre here. The real problem is I need a new computer. I can run about 12 instances of diva on this before it craps out, and that’s just the diva by itself and not with any additional added effects. So it’s time to upgrade. I would’ve done that before Christmas but then Apple released the M1 computers. None of the current offerings will do so I’ll wait for a new M1 X iMac. That and the fact that most of my third-party plug-ins are not yet ready for Big Sur or the new M series chips. I will try the things that you suggest but it’s OK if it doesn’t work well. I was also having some problems with Plasmodic patches nearly maxing out single cores too. Time to upgrade.
Topic starter
January 23, 2021 10:08 pm
Oh, and I was running it within Logic.
Topic starter
January 23, 2021 10:11 pm
And I was only running Logic. No other programs apart from the finder.
January 23, 2021 10:11 pm
@tkboomer Have you tried turning on Low Latency Mode in Logic? That fixed it for me!
January 23, 2021 11:18 pm
Logic's CPU meters don't show Unify's usage of other cores. Don't go by Logic's meters to assess Unify performance.
See https://pluginguru.net/unify/manual/doku.php?id=cpu-meters.
don1thedon reacted
Topic starter
January 24, 2021 5:08 am
@getdunne Thanks for the link. I'll see what if I can understand the problem better using Unify's own meters as you've shown me.
Topic starter
January 24, 2021 10:17 pm
Hi Shane,
Definitely a computer problem. The main CPU meter in Unify is going into the red when using most of the more CPU intensive plugins in the library. Adjusting the buffer sizes in the BBC plugin only helps marginally. Time to upgrade the hardware. But I was going to do that anyway. 🙂
January 25, 2021 3:54 am
Hope this gets resolved, but many DiscoverStation DEMO Patches do not work at all here, yet some are fine. This is on Win10 Pro Desktop PC, latest Update. 🙄
January 25, 2021 3:36 pm
@doubtingtom37 Are you using an audio interface with a pro-level ASIO driver (not ASIO4all)?
@doubtingtom37, @tkboomer What buffer size are you using for Unify? I recommend 256.
Topic starter
January 25, 2021 4:04 pm
@getdunne Hi Shane. I have an Apogee Duet 2 (latest edition). I'm not sure I remember buffer size I have in Unity. I'll check.
January 25, 2021 4:18 pm
@getdunne Saffire Pro14, 512. Stable, functional for years. Wired 60Mbs home network no download issues. Will try another drag & drop into UNIFY standalone, but use (2) separate Win10 Pro Desktop PC DAWs and same issue on each.
Topic starter
January 25, 2021 4:22 pm
Hi Shane, Changing the buffer size to 256 within Logic gave a marked improvement. Not perfect, but I can certainly live with it until I get a new machine. Thanks.
January 25, 2021 4:29 pm
@doubtingtom37 This most likely has nothing to do with downloads.
If your Saffire Pro 14 works with your DAW, and your buffer size is indeed 512, I can't think of any reason why Unify should be unable to keep up, even with the most demanding patches in DiscoverStation, unless perhaps the BBC Symphony Orchestra plug-in (BBCSO) is having trouble loading samples.
What type of disk-drive are you using for BBCSO's patch data? Does the BBCSO plug-in work directly in your DAW? Can you run a dozen instances of BBCSO in your DAW simultaneously, with all sounding at once, with no issues?
January 26, 2021 12:49 am
@getdunne Just went to Spitfire Audio App and Discover appears as needing (2) Updates. SFA never seems to notify of these updates .... as several VI-C members have complained. This is the likely issue and will advise when Updates are Discover installed. Maybe need to rescan in UNIFY as well. THX!
January 26, 2021 1:46 am
All working properly. Issue definitely SFA BBCSO Discover Update issue. My Bad. 😪
pluginguru reacted
