Reaktor over Pro-tools (HD) on OSX uses all cpus for processing resulting in a n more processing demand than normal, where n is the number of processors you have on your mac. Look at the comparison images, same ensemble, same preset, same audio buffer: Also performance on OSX are bad compared to Windows, just to make an example, for this ensemble i have to put audio buffer at 512 samples on OSX to be sure i don't get any click, while on my 2 years old overclocked PC i can put the audio buffer to 64 samples and it's still perfect, i can even double the control rate and still no clicks. The same preset on my Vaio laptop runs smoothly at 256 samples. I've discovered also on my Laptop that to get the best performance in Reaktor stand-alone i have to boot the system using 1 CPU only, so turbo boost push the cpu constantly to the highest frequency, i can reach a similar performance assigning affinity to Reaktor process under the taskbar but is not as efficent as booting with 1 cpu only. My MAC: mac pro 4,1 XEON W3540 2,93Ghz with 6GB DDR3 using internal MOTU PCI 424 My PC E8600 3,3Ghz Overclocked to 4ghz with 4gb DDR2, using its MOBO internal AC97 audio (asus p5k) with ASIO4ALL My Laptop Vaio with core i7-720QM (1.6ghz-2,8ghz max with turbo boost) + 6GB DDr3 using both AC97 with ASIO4ALL and RME fireface 400 In addition to the not so good performance on osx it looks like Reaktor doesn't like the latest intel i7/xeon turbo-boosted cpus (like any other single threaded application i guess). We probably need a real multi-thread in Reaktor to get the best out from those cpus. Thanks for reading.

Good news Hi, collegues, I think I have better news here concerning multi threading in OSX, using Reaktor in logic + other plugins: Situation: I'm setting up a live session, on a 4core Mac pro, os 10.5.8, with 7 instances of Reaktor all processing real time frequency tracking injected into vocoders, all with live inputs, + 2 Vokators also run ready, and on top of all that, compressors, Eqs everywhere, reverbs (3) etc. Audio buffer: 128. Overall latency from mic input to outputs ass: 412 samples!

(Download test audio file here: What does logic System performance window shows me? One single CPU maxed, hiting hard the red leds! I should be worried, but everithing still works fine! The answer: I opened the OSX activity monitor, and what it shows is logic using ALL 4 CPU's very democraticaly! Conclusion: Logics System Performance window is a joke!. Here's 2 screen captures: 1- Shows the contradiction between what Logic SysPref Windows, and OSX activity monitor both say. 2- Shows, on activity monitor, how all CPU tasks drop down when closing Logic, prooving all these threads where equaly distributed by Logic.

All this might not demonstrate 100% that Reaktor itself is well distributed, but at least shows that logic erroneousely shows single CPU usage & spikes when there's none! Thank you for reading, hoping this can help. Good news Hi, collegues, I think I have better news here concerning multi threading in OSX, using Reaktor in logic + other plugins: Situation: I'm setting up a live session, on a 4core Mac pro, os 10.5.8, with 7 instances of Reaktor all processing real time frequency tracking injected into vocoders, all with live inputs, + 2 Vokators also run ready, and on top of all that, compressors, Eqs everywhere, reverbs (3) etc. Audio buffer: 128. Overall latency from mic input to outputs ass: 412 samples!

(Download test audio file here: What does logic System performance window shows me? One single CPU maxed, hiting hard the red leds! I should be worried, but everithing still works fine! The answer: I opened the OSX activity monitor, and what it shows is logic using ALL 4 CPU's very democraticaly! Conclusion: Logics System Performance window is a joke!. Here's 2 screen captures: 1- Shows the contradiction between what Logic SysPref Windows, and OSX activity monitor both say. 2- Shows, on activity monitor, how all CPU tasks drop down when closing Logic, prooving all these threads where equaly distributed by Logic.

All this might not demonstrate 100% that Reaktor itself is well distributed, but at least shows that logic erroneousely shows single CPU usage & spikes when there's none! Thank you for reading, hoping this can help. Hi, collegues, I think I have better news here concerning multi threading in OSX, using Reaktor in logic + other plugins: Situation: I'm setting up a live session, on a 4core Mac pro, os 10.5.8, with 7 instances of Reaktor all processing real time frequency tracking injected into vocoders, all with live inputs, + 2 Vokators also run ready, and on top of all that, compressors, Eqs everywhere, reverbs (3) etc. Audio buffer: 128. Overall latency from mic input to outputs ass: 412 samples! (Download test audio file here: What does logic System performance window shows me? One single CPU maxed, hiting hard the red leds!

I should be worried, but everithing still works fine! The answer: I opened the OSX activity monitor, and what it shows is logic using ALL 4 CPU's very democraticaly!

Conclusion: Logics System Performance window is a joke!. Here's 2 screen captures: 1- Shows the contradiction between what Logic SysPref Windows, and OSX activity monitor both say. 2- Shows, on activity monitor, how all CPU tasks drop down when closing Logic, prooving all these threads where equaly distributed by Logic. All this might not demonstrate 100% that Reaktor itself is well distributed, but at least shows that logic erroneousely shows single CPU usage & spikes when there's none! Thank you for reading, hoping this can help. Click to expand.For For some other things, Logic is a joke, and specialy for graffic issues. Example: Unable to show correct placement of controlers on automation, when using latency plugins, like vocal transformers and so.

Pro Tools Hd 8.0.1cs2 Update For Mac Free

Graffics are late or ahead, depending on the buffer setups. (You can read a lot about it on logic help forum.

So, I would definitely trust the OSX activity monitor first. And no, I dont have clicks nor dropouts, despite the logic CPU metter tells me it's running full max! Also, I can sometimes have dropouts and spike when tyhe logic CPU is not maxing up. So, there's a lot of contradiction inside the Logic software. Still, you bounce thing is interesting to consider.For some other things, Logic is a joke, and specialy for graffic issues.

Example: Unable to show correct placement of controlers on automation, when using latency plugins, like vocal transformers and so. Graffics are late or ahead, depending on the buffer setups. (You can read a lot about it on logic help forum. So, I would definitely trust the OSX activity monitor first.

And no, I dont have clicks nor dropouts, despite the logic CPU metter tells me it's running full max! Also, I can sometimes have dropouts and spike when tyhe logic CPU is not maxing up. So, there's a lot of contradiction inside the Logic software. Still, you bounce thing is interesting to consider. The images you have posted shows how badly multithreading is managed in osx, the same cpu load switches costantly between cpus. Try to analyze every single read vertically, you will see that is the same load but is 'jumps' from one cpu to another over time.

Windows

Pro Tools Hd 8.0.1cs2 Update For Mac Pro

Just to be clar, the workload is not splitted between cpus, it just jumps very often between those. It happened to me many times to have cpu maxed in logic but no clicks, expecially with low buffer sizes. By the way that does not mean you are in a safe situation have a nice christmas. I've discovered that pro-tools acts in the same way with ALL RTAS and not only Reaktor, so this is not a Reaktor problem, is a Pro-Tools problem, and honestly a really big problem, basically it doesn't matter how many cpu you have if you use pro-tools cause every plug-in cpu usage will be replicated on every cpu you have!

Pro Tools Hd 8.0.1cs2 Update For Mac Windows 10

For example any plug-in inserted in Pro-Tools on my 8 core macintel uses 8x more cpu as it should:/ I have not upgraded to Pro-Tools 9 yet so i don't know if this problem persists also in v9 (nobody has noticed it?), as i mainly use logic i don't care much about PT, and probably it's better if i stay away from it as more as i can.

⇐ ⇐ Pantech's Verizon Lte Modem Configured For Mac
⇒ ⇒ Intel Broadwater-g Graphics Drivers For Mac