PatchWork eating all the CPU on PT11

Official support for: bluecataudio.com
Post Reply New Topic
RELATED
PRODUCTS

Post

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.
Hey guys.
I just purchased PT 11.
In PT11 I'm using Behringer FCA1616 interface.

I had problems right away when I opened one session. The CPU usage was around 80-90% so the PT crashed very soon and shortly after playback the sound became distorded .

I had only 2 VI's on my session (Trilian Bass and SSD4) and even if I inactivated them, the CPU usage was the same.. around 80-90%.
Then shortly after that I found out that because I have Patchwork on couple guitar tracks, the patchwork was eating all the CPU. The CPU usage drops to 30% when I inactive these.

Damn!! I've read from many places that people are running dozens of Patchworks without any problems in PT11 or 12.
So what's the case? The PatchWork version is 1.72. (So haven't updated yet but I don't believe that is the case).
Also In PatchWork I have turned the meters off to save some CPU.
My OSX's Activity Monitor says I'm using only 2Gb of RAM when running this session on PT11.

I'm running the same session so nicely on PT 10.3.9. without crashes or anything (buffer size 512)..All the plugins active. CPU usage is around 40%.

My session has 15 stereo and 24 mono tracks with some basic plugins like stock EQ and and Waves compressors. And then in Auxes I have just couple different Reverbs, delays and basic stuff.

here I found some information (if this is the case):
https://www.bluecataudio.com/Blog/ti...d-lightweight/ (https://www.bluecataudio.com/Blog/ti...d-lightweight/)
"Also, the 64-bit binary is bigger, so it should indeed take more RAM than the 32-bit version (up to twice the RAM)."

And I really want to use PT11 because of some different features and cause it's 64 bit.. But I need also the Patchwork to use the guitar sound that I like.
I wanted to even update to PT12 (because of the Freeze options and stuff) but I will not do it before I will solve what's the problem with this one.

I have also considered of processor update to 6 core 3,46Ghz on my Mac Pro.. or RAM update. But I can't be sure if it solves any problems in this case.

Please help me guys..

Here's more information:
Mac Pro 5,1 (Mid 2010) 2,8Ghz Quad Core (Westmere)
24GB of RAM (1066Ghz)
OSX: 10.8.5. (I have tried even Yosemite but it made my computer so much slower so will update little later)
ProTools 11 version is 11.3.2.
My sessions are on seperate SSD drive and also my VI librarys are on second SSD drive.

EDIT: Found something interesting too.. The plugin called LeCab for example.. the AU version is eating about 8% less CPU than the VST version. Unbelievable.. Or maybe it's not. Can someone explain me this?
Top

Post

Hi,

It is likely that there is one plug-in that is loaded inside PatchWork that causes the CPU overload. PatchWork itself does not use much CPU, and maybe one of the plug-in is having a compatibility issue in 64-bit mode. Are you maybe using a bridging application to load a legacy 32-bit plug-in? Bridging may have a pretty high cost in Pro Tools.

For the specific plug-in you are talking about, it may indeed happen that either the VST or AU version uses more CPU in a particular host application: it depends how both the host and the plug-in have been implemented (and in this case there is also PatchWork in between them).
Top

Post

Blue Cat Audio wrote:Hi,

It is likely that there is one plug-in that is loaded inside PatchWork that causes the CPU overload. PatchWork itself does not use much CPU, and maybe one of the plug-in is having a compatibility issue in 64-bit mode. Are you maybe using a bridging application to load a legacy 32-bit plug-in? Bridging may have a pretty high cost in Pro Tools.
I'm pretty new to Patchwork plugin anyway.. but how can I make sure if there is bridging application on? Can't find it on settings..
Top

Post

If you don't know, you are probably not using one :-). PatchWork does not have any particular setting for this and does not propose bridging, so if you have not installed 32Lives or jBridge, you are not bridging anything.
Top

Post

Found some interesting things. For example LeCab 2 impulse loader (VST and AU version both) is eating 10-15% more CPU than for example NadIR loader :O
Wow.. so I think I just have to stick to other impulse loader.. i just love LeCab cause its easy to try multiple cabs in same window..
So it looks like there are differences between the coding of these different plugins. Maybe that's why other plugin is not perfectly compatible with 64bit DAW as you mentioned.

And then I also compared those guitar amps.. I love to use Nick Crow Labs 8505 guitar amp.. when I switch it to ReValver4 for example.. there is no differences in CPU usage. They doesn't use so much CPU. If I want to reduce CPU usage even more.. I can click the HQ mode Off on NC 8505.. and actually I dont hear any differences in sound quality.

So looks like LeCab was eating A LOT of cpu when using with PatchWork.

I also tried huge sample libraries with Kontakt 5 and they doesn't CPU barely at all.. which is nice. So this far looks like these guitar plugins are eating the most.

Because same time I'm using Patchwork on many other tracks.. with different reverbs and some other EQs.. and they are not using CPU barely at all.
Top

Post

If you are using many amp simulations and convolution cabinet sims, it may indeed quickly increase the CPU usage. It is strange that there is a big difference between 32 and 64-bit versions, but it could be also due to the changes they have made to the audio engine in PT11.
Top

Post

Blue Cat Audio wrote:If you are using many amp simulations and convolution cabinet sims, it may indeed quickly increase the CPU usage. It is strange that there is a big difference between 32 and 64-bit versions, but it could be also due to the changes they have made to the audio engine in PT11.
But honestly.. I'm using only 2 guitar amps.. one on left and one on right guitar channel.
And then one stereo IR loader on guitar bus. So there's not many of those plugins. But still they are eating pretty much. But I think I just have to live with it :)
Top

Post

JayRay wrote:Found some interesting things. For example LeCab 2 impulse loader (VST and AU version both) is eating 10-15% more CPU than for example NadIR loader :O
Wow.. so I think I just have to stick to other impulse loader.. i just love LeCab cause its easy to try multiple cabs in same window..
So it looks like there are differences between the coding of these different plugins. Maybe that's why other plugin is not perfectly compatible with 64bit DAW as you mentioned.

And then I also compared those guitar amps.. I love to use Nick Crow Labs 8505 guitar amp.. when I switch it to ReValver4 for example.. there is no differences in CPU usage. They doesn't use so much CPU. If I want to reduce CPU usage even more.. I can click the HQ mode Off on NC 8505.. and actually I dont hear any differences in sound quality.

So looks like LeCab was eating A LOT of cpu when using with PatchWork.

I also tried huge sample libraries with Kontakt 5 and they doesn't CPU barely at all.. which is nice. So this far looks like these guitar plugins are eating the most.

Because same time I'm using Patchwork on many other tracks.. with different reverbs and some other EQs.. and they are not using CPU barely at all.
This is good to know. I also use Torpedo Cab, but with Reaper rather than PT. I plan on picking up Patchwork soon, so I’ll see how it shakes out.
Top
Post Reply

Return to “Blue Cat Audio”