StevenTOAST

Back with new results: I activated hyperthreading for my i9-9900K (8 + 8HT cores). I can run exactly 158 tracks at buffers 32/small.

(posted in wrong thread, my apologies)

Makes no difference. The entire chain gets processed to a sigle core. I tried by routing from track to aux via send knob and via output routing but the result is the same. What makes a difference in my case is using Vienna Ensemble Pro on the same machine, it can distribute efficiently a single AUi to multiple cores - with minimum latency.

Perhaps you can spread the load over a chain of Aux channels. Maybe you could also spread the load over several instances of the VI? Each instance with a different note range. With u-he Diva I don’t even need to play chords in order to get a fairly high core usage. Regarding serial auxes, in my experience they still share the same core, I never noticed an improvement. Fun fact, on my Macbook Pro, in the summer, my winter projects would stop playing due to CPU thermal throttling (22 Celsius indoor during winter vs 24-28 during the summer). 3.1 throttled to 2.6 Ghz. So I learned that 400 MHz can make a huge difference

28 stable tracks on MacBook Pro retina late 2013 (i7 cpu, manages to clock up to 3.1 GHz with the fans set to max otherwise it throttles). 1024 & large buffer. Stable means running the entire loop without errors. 110 tracks on a i9 hack at 5 GHz and hyperthreading disabled (so 8 real cores). Same bufer settings.

Thaks. I thought so...

Did anyone tried to test if Logic can spread a track load on multiple cores? Aka new project, create a single track, place a heavy-hitting CPU instrument (like oversampled Serum, or u-he Diva), then place a bunch of insert plugins that support oversampling and max them out and see if a single track - that with older Logic versions would instantly overload the audio buffer - now gets processed over multiple cores and avoid overload? I can’t test it right now, I’m on vacation. But if it does, it would be the first DAW to do that (apart from Reaper I think).

Just rename that folder (with Logic closed) to "Logic__" then fire up Logic and see if it creates a new one. It may prompt you to install the content again, install the minimal. And after, you may get back the library relocation feature and consequently you may be able to install the rest of the content straight to the external drive.

Certain kinds of meteorological events that can displace large amounts of silicon dioxide in the form of quartz are known to produce such disruptions

Logic Pro 11 with monthly subsciption plan.

I have a SORT OF fix that goes like this (most of the time I use the kick for ducking via sidechain, but it works for any other sound sources, I usually make a group of 16 busses just for these chains): 1. Send the Kick (Inst 1) to a bus, let's say Aux 1 2. Aux 1 settings: output=none, add a Sample Delay 3. Send Aux 1 to Aux 2 4. Aux 2 settings: output=none 5. insert ducking compressor onto desired track, Side Chain to Aux 2 6. on compressor, switch the sidechain to "listen" and use the Sample Delay on Aux 1 to sync both clicks (original source kick and the one that passes through the sidechain path) 7. repeat later in the project, the latency will be different as we add plug-ins 8. don't forget to check the sync before rendering the final mix 9. that's it 10. tip: you can adjust the delay to feed the sidechain kick with few ms earlier, so the sound "pre"ducks - to be honest even if Apple will correct this, I will use the same method, I find this tip pretty awesome in getting a nice, bouncy, ducking

Weird stuff happening. I installed the previous version of Logic from the backup (essentially I overwritten the app), then reinstalled the latest version (4th time was the lucky one). I'd say everything works. I've restored the keycommands file from the laptop, the only thing I lost are various settings (like the checkboxes in Record and Mix menus). Overall, I'm almost 100% recovered so thank you all for chipping in. Still no idea what could have done such level of corruption (and olny for Logic) but for the moment it works as expected. Cheers!

Well, as I said, the file saved there it is named as I named it but the contents is Logic's own default key commands so nothing to restore from (well, I did not update my laptop so is all there, but the point I am trying to make is that Logic simply cleaned that file). Reboots daily, reinstalled once, same things happen. Never had this kind of issues with Logic until now. On desktop I run High Sierra HFS+ but I doubt this is the problem. System running fine, if some sort of corrupution occurs I should see it in other apps too. I'll finish the current project and most likely downgrade.

This latest update basically erased all my custom keycommands (I have my own profile name populated with default key commands), midi regions often overlap instead of snapping properly on the grid (I make a 4-bar region, I repeat it, then in the middle of the project I see certain parts overlapped - drives me mad!!) and now the automation selector inside the midi region (which previously was updated automatically with whichever knob I turned) does not update automatically. Also the cycle, no matter what setting I use, either catches notes outside the loop zone, either doesnt properly catch first notes and region automation parameters. This update broke bread & butter things I use

not an LX issue in general, but one you're having. maybe someone here can help? meanwhile, the HS alphabetical issue is fixed, and my templates (for example) are again in order...) Well thanx for getting back to me. I completely deleted the app and reinstalled and now it works. I customized some default templates and they changed the layout of the template picker menu and probably some things at deeper level. Any way, it's all sorted out.