Forum Jump
Hello,
I've been using VE Pro with Logic X in the past with a small process buffer as advised by the community on here so i don't run into many difficulties.
My question is, now that 10.2.1 is released with a key multithreading feature, is it reccomended/neccesary to change the process buffer to normal or large?
Many thanks
|
|
|
|
|
|
Originally Posted by: jobuk55 
Hello,
I've been using VE Pro with Logic X in the past with a small process buffer as advised by the community on here so i don't run into many difficulties.
My question is, now that 10.2.1 is released with a key multithreading feature, is it reccomended/neccesary to change the process buffer to normal or large?
Many thanks
I would recommend you run your sytem as-is until you start to have issues. There isn't a lot of information available on what exactly the new multi-threading feature does or how it works. I haven't come across any performance bumps yet, although I haven't really gotten to experiment with it.
Anyone else see any differences since the update? Mac Pro 4,1 2.26GHz 8-core - 32GB RAM - SSDs only - Mac OS 10.10.5
Logic 10.2.1 - Vienna Ensemble Pro 5 - installed locally
Kontakt 5
|
|
|
|
|
|
Hi,
The main difference is that the load is now shared between CPU cores. Before the upgrade, only one core of my iMac i7 was used (usage on that project: near 100%). I removed every I/O plugin instances (about 115). Now all cores (8) are used and the load is very low (5-10%). See screen capture (Logic is playing).
In this project 20 instruments are already playing midi notes (about 40 instruments when the project will be more advanced).
My setup: Logic on iMac with 116 instruments/tracks ready to use (3 VEP instances, each with 48 ports/midi inputs) on a slave (MacPro). Each track is using AM Pro Kit for Scripter plugin (articulation switching on automation with visual; see clarinet track on screen capture).
Best,
Claude File Attachment(s):  ScreenCapture Logic 10_2_1.png (798kb) downloaded 35 time(s).You cannot view/download attachments. Try to login or register. C.B.
|
|
|
|
|
|
Thanks for that Claude,
I notice that you're using the event input and I suppose this ties in as well with the changes.
When I set everything up last year, I experimented with using the event input but the one core thing seemed to make performance suffer so I just ended up using multi-output channels as the AU plugin in Logic connected to Multitimbrel instances in the slaves.
That was of course before these changes to Logic 10.2.1
Now I wonder if I should reconsider using the Event Input solution instead.
Would appreciate your thoughts.
Thanks,
Joe
|
|
|
|
|
|
Hello Joe,
As I'm using a slave for VEP and VIP, I chose the VSL Event Input plugin approach. The load was high, but manageable.
I made a mistake in my previous post. I didn't realized that 2 of my 3 VEP instances weren't working without I/O plugin instances... I don't know why. I suppose VSL programmers are working on this.
The consequence is that only 4 cores are used now. So the load is about 20-25% with some short incursions in the 40-60% range.
Claude C.B.
|
|
|
|
|
|
I've upgraded. The CPU distribution is indeed better, but the Script plugin has a bug where it suddenly hogs the CPU during any use, which requires restart of Logic.
|
|
|
|
|
|
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.