Sascha Franck

Space Designer Manager is a (non free) third party utility to create Space Desiger presets (along with the audio files) so you can access them from the preset menu or library tab easily. But you don't need it for a start. If you want a free, pretty much no fuss IR loader, you might want to check this: https://www.igniteamps.com/#nadir or this: https://lancasteraudio.com/shop/plugins/pulse/ They're basically pretty much the same (perhaps even using the same code base). Oh fwiw, those two allow you to mix and match 2 IRs at the same time, which you might find useful.

And btw, make sure to mute the dry output of SD.

As in routing them to a dedicated mixer channel? - Load it as a multichannel instrument (choose the best version for you, there's a bunch). - Right click onto a cell and look at the "output" options at the bottom of the appearing pulldown. - Expand the mixer tracks in Logic by clicking on the "+" button of the main Battery channel until you see all available channels. You can later on delete individual ones should you not need them.

As this is a Logic forum, how about Space Designer? In case you're dealing with many IRs, I highly recommend getting Space Designer Manager, though. Most excellent piece of utility software, creates SD presets out of wave-files so you can browse through all your IRs using Logic's library functionality.

No worries about that from my side at all. At least not for the stuff I'm doing atm. In general, I could keep using my MP until the end of times and wouldn't miss much (others than it not being able to run any up to date software). The only thing I sometimes wish for is more single-thread "oomph" - and the M3 should deliver that in spades, at least compared to this aging Xeon machine. And it wasn't ever much about that anyway. But I'm having quite some concerns about QA in Logic land (admittedly nothing new, at least not on my side). We shall see...

Fwiw, I ordered a MBA, so I can see for myself what's going on with the E-cores.

I did exactly nothing. As soon as a track is not in live mode anymore (hence not selected and/or record enabled), it automatically becomes "distributable". Since ages already. If you want, I can post a video. Or a GIF. Whatever.

I have absolutely no idea. That is simply not true. I tried with DOZENS of instrument and audio tracks - Logic splits them all onto two threads in playback mode (which is the relevant situation for the E-cores being able to work properly). Every single one of them without even just one exception. I have a very good idea what it looks like because I've seen it in person. And I've said so multiple times already.

Very unlikely. And even if it was like that, Logic seems incapable of doing so (see Reaper/Cubase). From all that I can see, Logic can split individual channel loads onto different threads in playback mode just fine. Nothing else is needed to "beam" a task from a P-core to (multiple, if needed) E-cores. And for the umpteenth time: With the M1 CPUs that just seems to work fine.

I'm not sure what this is supposed to demonstrate. Doesn't seem like E-core utilisation has much to do with Logic here.

Sorry but again: This is completely irrelevant. This thread is about: - Logic not supporting E-cores on newer machines anymore when it has before. - The competition supporting E-cores and making Logic look bad in comparison.

I wouldn't call that a "fair bit" - and it's very likely (so likely I'd pretty much bet on it) they're not used within Logic. I mean, that screenshot is taken pretty much the moment before Logic is crapping out, so the E-cores are defenitely not helping it in balancing the load. And then, as said numerous times already: It's totally different in Reaper and Cubase. No matter how you put it, 105/104 vs. 64 tracks on the same machine is a most significant difference. So, Logic not using the E-cores directly translates to its overall performance.

Again: This thread is not about what I need. And I defenitely don't need advice.

Sorry to say so, but all that is pretty much irrelevant, @vondersulzburg. The relevant thing is: Logic was using the E-cores fine on the M1 Macs I tried with (a Mini and a MBA), load distribution was pretty even. This can as well be seen in some YT videos. Now, with the event of the M2/M3 CPUs, the E-cores are almost not in use at all - which results in roughly 40% loss of overall computational power. That's a whole lot. And fwiw, this thread isn't about the CPU power I need right now. Or about what I may need next month. Or next year. I was just about to buy a new machine when I stumbled over that video, so I thought it'd be a good idea to inform myself whether it's true. Nobody needs to tell me what I should possibly buy instead, that the CPU juice would be fine anyway and what not. Hence, this thread is entirely about Logic not utilizing the E-cores anymore. Which, in my book, is an absolutely inacceptable thing (especially given all of Apples marketing blurb a la "more Pro than ever", "get more done in less time" and what not - also including the praise the efficiency of Logic always gets). And btw, in my book Logic isn't exactly cheap. Simply because you need to buy a Mac to run it. And you need to do so more often than the hardware would possibly require (I'm only purchasing a new machine now because the lack of support for my Mac Pro is really starting to show). Anyhow, even that isn't relevant. Logic was doing fine with M1 CPUs, so it should as well be doing fine with M3 CPUs. But it isn't. It's even way less efficient than the competition - which is a first.

Well, doesn't need to be realtime/live. It's fine in case they're available for playback purposes. Really, just as things were with the M1 CPUs.