Depends probably on numerous internal factors in LogicPro about load balancing or whatever algorithms they are using, which might not make sense with my frankenstein cpustressor plugin that just turns on a simple load and never stops. LogicPro is definitely not always allocating new threads for each new track and it doesn't make sense to me at all, not all cores were always being used.
At some point last night I had 24 tracks in Logic Pro, each with an instance of that plugin and some strange things happened when I moved the sliders around. I have been starting to put together a JUCE plugin that does nothing other then apply a CPU load in a controllable way, with a slider to choose how much load. Did he accidentally have the MBP in live mode by any chance? That would make a difference. There could be other reasons and could have been the way he was running the test too, he didn't show us his screen. Generally plugins will not be taking advantage of AVX512, which is an actual instruction set, the plugin would have had to have been compiled with that in it. Well that struck me as odd too and inexplicable, I didn't pay that close attention at the moment to investigate what possible hardware differences exist between the two machines, but I think the stuff about AVX is pure speculation.
0 kommentar(er)
