|
Post by mrholmes on Feb 26, 2017 15:53:37 GMT -6
I am frustrated with Logic X and its CPU Peaking when using multi-out Software instruments. It makes a ongoing arrangement /mix / composing project impossible, because I get always the Error messages and the project stops playback.
I cant understand why they code Logic in that way that a Multi Out Instrument, and all depending plug ins including the mixbus-plug ins, is calculated on one single core. We have 2016 and there is a reason why I bought an 8 core Macintosh computer.
It does not makes sense to buy a new Logic Version if this is not solved!!
My hope was that they solved this in Logic 10 but no its the same BS. 12 years is not enough to solve a stupid problem?
What is Apple thinking? No one will use multi out instruments in 2016/17??
Anyway I am not the only one. If I google for it all users with MOI sessions are frustrated like hell. All workarounds are just empty talk by Apple... nothing cures the problem.
My idea is to jump over to Reaper. Is Reaper addressing all cores, or is the same shit going on in Reaper?
|
|
|
Post by Mister Chase on Feb 26, 2017 23:55:21 GMT -6
To the best of my knowledge reaper uses all cores. Between Harrison mix bus, studio one and pro tools, reaper is the best when it comes to CPU for me. Download it and try and see.
|
|
|
Post by NoFilterChuck on Feb 27, 2017 1:11:22 GMT -6
Can you cite an example of how you use this? Are you talking about something like Omnisphere/Superior Drummer being set up as multi-out? Why not just instantiate new plugins for each output needed?
The best way to alert apple about this bug is the "Provide Logic Pro Feedback" menu item from the Logic Pro X menu. If enough people report it, it'll get dealt with.
|
|
|
Post by mrholmes on Feb 28, 2017 4:03:38 GMT -6
Can you cite an example of how you use this? Are you talking about something like Omnisphere/Superior Drummer being set up as multi-out? Why not just instantiate new plugins for each output needed? The best way to alert apple about this bug is the "Provide Logic Pro Feedback" menu item from the Logic Pro X menu. If enough people report it, it'll get dealt with. Sorry my rude tone but WTF millions of times people have reported this. On GS you can find complete detaild descriptions about it. And thats not the only bug they transport from year to year, they also have massive automation bugs... In the past for me the point about Apple was that they offerd perfect hardware in conjunction with optimized software. If this is not the case anymore. So what ... why not a PC next, special because Windows turns into unix derivate .... step by step. For the money they charge its just stupid to not rewrite the audio engine to splve those bugs one time and forever.... Jupp it seems they will loose me on Reaper, simple because this bug makes arrangeing in Logic x impossible...its a great software as long you do not use 3 rd party multi ouput software instruments. Cheers Holmes
|
|
|
Post by b1 on Feb 28, 2017 5:27:43 GMT -6
Reaper, Reaper, Reaper! Low Cost Small file size for humongous features Continual updates 64 outs on Kontakt
|
|
|
Post by NoFilterChuck on Feb 28, 2017 6:17:06 GMT -6
Lol your "sorry"a sounds more like "sorry, not sorry". I've never experienced this bug, nor am I on gearslutz. I was just trying to understand what you were experiencing...
|
|
|
Post by mrholmes on Feb 28, 2017 9:34:32 GMT -6
Lol your "sorry"a sounds more like "sorry, not sorry". I've never experienced this bug, nor am I on gearslutz. I was just trying to understand what you were experiencing... If I use for example addictive drums 2 as multi output instrument the whole calculation of AD2 and all the mix plug ins, including submixes, as well my 2 bus plug ins are calculated on the last of the 8 CPU. Sure this leads to the point where no power is left on that CPU. Logic stops the playback. Apple addvises diffrent workarounds, bussing out the 2 bus plug ins to get a better CPU distribution, but its not working.... I dont understad Apple, this bug is OLD.
|
|
|
Post by popmann on Feb 28, 2017 10:28:04 GMT -6
First: Owner of both Logic 10.2 and AD2 (whatever the latest update was when I bought the last lib Black Friday'ish) --AD2 has consistently on BOTH Windows and OSX....on BOTH Cubase (both OSs and v 6 and v8.5) and in LogicX presented performance challenges. The challenges present themselves as this kind of CPU peaking. Where it's sitting playing, using 15% of the CPU, then comes some I dunno-middle tom hit and OVER(CPU)....then back to 15%....I've troubleshot it to try to find which feature it is** and been unable to isolate it.
Perception of Logic's multithreading prowess aside (and you DO have that all checked in the preferences....right?) aside--if you remove AD2 for the equation is there a FUNCTIONAL problem? I don't mean what do you see on the cores in the silly Logic CPU meter....I mean....do you experience the engine overloads?
**as an example, in Alicia's Keys piano, the half pedaling IR is responsible for 80% of it's CPU use--turn it off and you can play it at low latency on a Pentium 4.
|
|
|
Post by mrholmes on Feb 28, 2017 13:39:28 GMT -6
First: Owner of both Logic 10.2 and AD2 (whatever the latest update was when I bought the last lib Black Friday'ish) --AD2 has consistently on BOTH Windows and OSX....on BOTH Cubase (both OSs and v 6 and v8.5) and in LogicX presented performance challenges. The challenges present themselves as this kind of CPU peaking. Where it's sitting playing, using 15% of the CPU, then comes some I dunno-middle tom hit and OVER(CPU)....then back to 15%....I've troubleshot it to try to find which feature it is** and been unable to isolate it. Perception of Logic's multithreading prowess aside (and you DO have that all checked in the preferences....right?) aside--if you remove AD2 for the equation is there a FUNCTIONAL problem? I don't mean what do you see on the cores in the silly Logic CPU meter....I mean....do you experience the engine overloads? **as an example, in Alicia's Keys piano, the half pedaling IR is responsible for 80% of it's CPU use--turn it off and you can play it at low latency on a Pentium 4. Ok maybe its AD2 fault... who knows I also have had this with BFD for example. Anyway I asked the AD support about it already... told them what happens after a few e-mail silence no answer. If that is true what you write please write them about this issue. We are two in this case already. EDIT... Yes I have checked the preferences and I did check my drivers etc. BTW yes I can provoke the peaks over and over again.... AD2 is running fine alone, as soon as I use plug ins to mix it there comes the peaking and over and out. I don't know if its Logic's fault or AD2 .... They both should find a solution for it...
|
|