If I create a new empty project and them import the old project - it opens but the playback speed is slow - sounds like its being played back at half speed. If I open an old project (contains a modest 24 audio tracks) created on the old iMac 2017 Intel machine (which worked fine) - it fails to open and I get s spinning beach ball - I have to crash it - it never completes loading. If I create a brand new project with Logic - it works fine. I am having a hard time moving my music production from a 2017 Intel iMac to a brand new 16" MacBook M1 Max - 32GB RAM 1TB SSD. I see all these reviews online about the amazing the speed of Logic is on an M1 - but it's not working for me. This feels really amateurish, and maybe it's why we experience poor performance.
ARTURIA PLUGINS CRASHING WHEN CLOSING WINDOW PRO
While i can understand this process would show up for plugins that are NOT native, why does it handle CPU performance for native ones ? Can't logic handle this by itself ? Can someone explain ?Īs a few other people here, i've been having issues with my M1 macbook pro in logic, and i'm wondering if the Logic we've been using is just a bad beta version.
If you run Logic Pro in rosetta mode, the AUHostingService process never shows up, no matter which plugin you run. It actually uses more CPU than Logic in my last session. This process is the one using the CPU for the third party plugin, not Logic Pro. Now i've noticed something in activity monitor : as SOON as you launch a M1 arm native third party plugin, a process appears, named AUHostingService (Logic Pro). This feels quite bizarre, like there's some conversion going on behind the scene, even though the plugin is native.
When i put a native M1 plugin in logic, a lot of them start with a small window that expands to a big regular one.
0 kommentar(er)
