pedro.turbay

No. My Native Instruments plugins and VST's are already compatible with Sonoma according to this statement. What is not yet certified is my hardware Arturia KeyLab MK2 61 (apparently it stopped being recognized on Sonoma acoording to this post. Also Soundtoys plugins are not yet attested with Sonoma. I sent them an email asking about that and they answered: "We haven't had the chance to fully qualify that OS with our plug-ins yet, so we recommend holding off on updating macOS until we've thoroughly tested our plug-ins. You may want to consider a downgrade if possible or waiting till our next release V5.4.2. We will likely send out an email or post about compatibility with macOS Sonoma, but you can always find out up-to-date compatibility information at the link Soundtoys 5 Compatibility". I understand what you said about taking time do devs incorporate this changes and I'm looking forward to updating do Sonoma as soon as possible. Thanks a lot!

Hello! I have no more than 200 3rd party plug-ins installed. About that loading on separate threads/processes, I know that fact and that's exactly what bothers me. How does it load aparted from Logic's threads taking much larger time? Shouldn't it be faster, since it's an exclusive thread for the 3rd party plugins? About the saving issue, that's what I do indeed. I always have to remember to close all plugin windows (pressing V as you said) and saving. But sometimes I accidentally save with a plugin window opened and I get the beachball for like one minute. I don't think this should be considered normal. PS: I said I was going to update to Sonoma but apparently the compatibility of some of my plugins are not yet attested. So I'll have to wait a little longer for that unfortunately.

Hello everyone! Thanks for the interest on this subject again. What I did was to reinstall my OS from scratch and install everything again. That did work for the beachball problem. Apparently the cause was some issue regarding iLok. But even with the fresh reinstallation of evertyhing I still observe a few things that in my opinion shouldn't be happening: 1. When I load a project, 3rd party plugin take a relatively long time to be loaded. Compared to my old macbook pro 2015 they load much more slower. 2. If I save the project while having any 3rd party plugin window opened I will get beachball spinning for a lot of time (like one minute) until it saves. Also I can't do anything on the project while that is happening (not even stop the playhead). Apart from those 2 issues, I really think this mac is a great machine. I use it with a lot of other applications opened and it works fine. It really looks like there's some kind of issue with 3rd party plugins. Hi, Thanks so much for this input. I'm still on Ventura and now that I've read this I'm upgrading today to see if things improve. Thanks a lot!

One workarround I've found was to save the Channel Strip Settings as User presets and only load them when I need the plug-ins to be active. But that's not the ideal scenario for me. What I wanted was to make them inactive/disabled so that Logic wouldn't interpret them as something that has to be loaded when opening the project.

Hi, sure: mac Studio M2 Max 96GB macOS Ventura 13.6 Logic Pro X 10.7.9

Hi, I created a project template with 400+ tracks and a considerable amount of plug-ins. My Record Project Settings are configured to "only load plug-ins needed for project playback": The arrange window is totally empty. No audio or MIDI region or files were ever inside the project. I also disabled and muted all tracks on tracks: Turned off all plug-ins on the mixer window and it seems that Logic loads the plug-ins on tracks that have something coming from another bus: Also I noticed that any sends on the template that goes to a channel that has plug-ins it loads will have that plug-ins loaded as well, even if the send is deactivated (gray and not blue): What I would like is to know is if there's a way to mantain my bus structure and sends but preventing Logic from thinking that this is necessary for playback? Since it doesn't have any regions on them and they are turned off and muted I would like them be treated as really inactive especially by not having their inserted plug-ins loaded when opening. Is that possible? Thanks so much!

That worked! This one is a bit hard to find. Thanks a lot!

Hi, I reinstalled Logic Pro on my mac and even enabling Complete Features the option "Ascending" is not being shown when I create new tracks (Command+Option+N): I tried disabling and re-enabling complete features and restarting the computer. None worked. Has anyone have a solution for this? Thanks!

Hi, on my case I got 48 kHz which is the correct sample rate for my audio interface: Audio MIDI setup: Logic Pro Audio Settings and Audio Project Settings: Thanks a lot for the input!

Yes, I'm using one USB-A dock where I plug my mouse USB wireless and a Faderport Production Controller. I've tested rebotting the computer with nothing pluged (even audio interface) and didn't see any changes regarding excessive beachball. On the other hand, under Rosetta it seems that 3rd party plugins are more efficient. Using it for one day and the beachball only appeared during the startup of Logic (which still intrigates me btw).

Thanks for the reply. I read this post you sent and tried to launch Logic under Rosetta. I still get the same beachball when opening the DAW and I still can't accept this is expected behaviour. I'll keep on working on mixes under Rosetta mode (even though all the plugins I'm using are native) and I'll update this post asap with observations. Thanks so much for your help!

Hi, I tried all options! But the thing is: for a light project with not more than 10 regular plugins (Waves CLA76, SSL Channel, SSL Comp, basically) the project should be running easy even on 32. It worked flawlessy when I was using a macbook 2015 so I assume on a macstudio M2 Pro with 92GB it should too! Thanks my concern.

Forgot to say that I also uninstalled all plugins and installed again but nothing changed.

Hi, everyone! I'm trying to understand one thing here. I just upgraded from a 2015 macbook pro with a Intelchip to a mac studio M2 Pro with additional features like 92gb RAM and 2TB HD space. The computer is good. It handles multiple applications ah the same time at a very fast pace, but unfortunately on Logic I'm not having good results. I'll list down a few bugs and unexpected behaviour I've been observing: Spinning wheel too many times: I get the spinning 100% of the times when I open Logic Pro and it's scanning audio units. I get it also a lot of the times when I save the project. Lag or delay: on light projects with no so many plugins Logic takes a while to execute my command. For example if I change a parameter on a plugin it kind of freeze and then move the parameter a few moments after I did it with the mouse. Even if I increase the buffer to 1024 I still get all the problems above at the same rate. It seems that this issue is somehow related to 3rd party plugins. I've seen that especially iZotope and Melodyne seems to cause some kind of lagging when I use them. I tried reinstalling them all but I didn't work. I've reached Apple too. We reinstalled Logic Pro and it didn't work neither. When I started using the new computer I didn't use Migration Assistent. I did a fresh clean install of everything on the computer. But there were only 3 things I copied from my old macbook. It was Channel Strip Settings (.cst files for bus, instruments or tracks), patches (.patch files) and project templates. Another thing that I should mention is that I did a big upgrade in terms of operational system as well. I went from Logic Pro 10.4 on macOS Sierra 10.12.6 to macOS Ventura 13.5.1 and 10.7.9 Logic. So my big question here is: shouldn't I been experiencing a faster workflow with this upgrade? Is it normal that a macstudio m2 with 92GB ram shows the spinning wheel when opening Logic? And is it normal that things are not faster than it was on a macbook 2015 with old operational system? Would you guys have any kind of advise on how I can tackle this issues in order to have a better experience? Thanks so much! Pedro

That worked perfectly! It seems that the surface preference file was bugged! Everything is ok now. I'm also backing up the file as suggested. Thanks a lot!