A quick test on 10.7.3 seems to improved things for me. What are you seeing on your systems?
Updated to Mac 12. 3 and Logic 10.7.3
My first impression is, much better performance. I will check some old songs from my 2017 iMac i7 rig which were not possible to work with on my M1Max MBPro
A quick test on 10.7.3 seems to improved things for me. What are you seeing on your systems?
Improved things here too, in a first quick look.
I notice some improvements as well. The CPU meter hasn't been maxing out for me, but I noticed yesterday when working on a 96khz session I was getting some pops and clicks and the song kept jumping back to the playhead and restarting several times even though the CPU wasn't maxed out or peaking. The only difference I can find is that I started using the PA 9000 J throughout the session and before I didn't use it because it was causing this behavior. I figured with M1 update it would be better but doesn't seem to be.
Anyone else have issues with the bx_console plugins?
I was having issues with this kind of stuff on my hackintosh a while back, though probably not quite the same. What I found out was that some plugins have an option for 'multi-core' that Logic absolutely does not support in virtual instruments. So Superior Drummer 3 was causing all kinds of havoc because I enabled this. Diva was also causing issues. Once I disabled this option I got much better performance overall. Consider disabling it in Kontakt as well? (not sure if it has it, but it wouldn't surprise me). In most of the manuals for these, it will say Logic doesn't support it. I wish it had some kind of 'daw detection' instead and would simply grey out the option somehow. This was messing me up for a good while.
In general, some plugins can just wreck havoc in certain configurations.
Another issue I've found comes down to more guesswork. I've seen some plugins need more 'lookahead' than others. For plugins that need a lot of lookahead, I think it's occasionally possible that the lookahead can exceed the maximum buffer Logic allows, which causes the whole system to get extremely sluggish and wonky. Again, I am guessing to a good extent here.
And the last issue I've encountered (not lately, but I also haven't been doing as much work) is with projects with video tracks. It seems like occasionally a 'section' of song can get corrupted when it comes to time. I'll encounter the same weird stumble at the exact same spot after this glitch occurs. Once it happens it's really hard to remove. I think I've occasionally had luck with removing the video and video track entirely, but sometimes I actually have to copy and paste all the regions into an all new project and copy paste all the settings, etc to remove it. This does seem to possibly by related to the multicore bug I mentioned, but I don't recall the specifics.
It's also been a bit since I updated etc, so it's possible these bugs have been fixed and replaced with new ones. Hopefully some of these may help.
Multi-core options, eg Diva, worked fine for me on my old Intel MBP, and gave improved performance.
On the M1, multicore doesn't work so great. Even plugins that implicitly used multicore in their audio engine (eg the latest Korg plugins opsix and wavestate), gave terrible performance on the M1, and Korg had to rework their engine to not use a multicore/multithread engine (and the performance radically improved as a result.)
As with most things, you need to play with various options to determine the best config on your system...
I'm having all of the above issues on my M1Max MacStudio - it's been driving me crazy. I've tried a full wipe and reinstall of Monterey (I had originally done the migrate assistant as recommended by Apple - which I'd assumed had caused the issues in Logic), however the fresh wipe and install made no difference.
I'm getting constant CPU spikes, running either full stock plugins, or with third party. I tried a process of elimination when I wiped it, reinstalling things one by one and testing. Stock gave exactly the same issues, in particular with Alchemy. Then when I loaded in Arturia Pigments, identical issues.
Every I/O buffer level gives the same result, bad latency, glitches, pops, crackles, playhead jumping back to the start for no reason mid playback, random channel spikes where the audio maxes. I've tried various multithreading options, lots of other tweaks here and there and combinations of each - no difference and no improvement.
I'm on MacStudio M1 Max (10 Core CPU, 32 Core GPU), 64gb RAM, 2TB SSD, running latest Monterey, with SSL 2+ (USB C), Nektar LX88+ (USB C), and plugins from Soundtoys, Arturia, U-he, Slate, Plugin Alliance, Oeksound, Kilohearts and others. All updated, all M1 Native, no Intel 64. I did try Rosetta but performance was woefully worse.
Someone on another board suggested I freeze tracks. What is the point of an M1 Max if we have to freeze tracks? My 2015 MBP had no problems running 40 tracks with plenty of third party stuff. It was only in the final few years I had to start freezing things, which was why I upgraded and invested a lot into the MacStudio. Total waste of money so far. Apple have been zero help, I've written complaints, spent hours on phone to their tech team and to the pro apps team, nothing. They've 'not had any other reports of problems' which is a total lie. They say their engineers are looking at the Support Profile I've shared, to figure out what the problem is. This has been ongoing since July!
If anyone who has had these problems has managed to sort it, please do let me know.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Recommended Posts
isaactoast
Link to comment
Share on other sites
Kaatza Music
Link to comment
Share on other sites
seewest
Link to comment
Share on other sites
ozinga
Updated to Mac 12. 3 and Logic 10.7.3
My first impression is, much better performance. I will check some old songs from my 2017 iMac i7 rig which were not possible to work with on my M1Max MBPro
Link to comment
Share on other sites
des99
Improved things here too, in a first quick look.
Link to comment
Share on other sites
SomeMusicKid44
I notice some improvements as well. The CPU meter hasn't been maxing out for me, but I noticed yesterday when working on a 96khz session I was getting some pops and clicks and the song kept jumping back to the playhead and restarting several times even though the CPU wasn't maxed out or peaking. The only difference I can find is that I started using the PA 9000 J throughout the session and before I didn't use it because it was causing this behavior. I figured with M1 update it would be better but doesn't seem to be.
Anyone else have issues with the bx_console plugins?
Link to comment
Share on other sites
Nathaniel Chambers
I was having issues with this kind of stuff on my hackintosh a while back, though probably not quite the same. What I found out was that some plugins have an option for 'multi-core' that Logic absolutely does not support in virtual instruments. So Superior Drummer 3 was causing all kinds of havoc because I enabled this. Diva was also causing issues. Once I disabled this option I got much better performance overall. Consider disabling it in Kontakt as well? (not sure if it has it, but it wouldn't surprise me). In most of the manuals for these, it will say Logic doesn't support it. I wish it had some kind of 'daw detection' instead and would simply grey out the option somehow. This was messing me up for a good while.
In general, some plugins can just wreck havoc in certain configurations.
Another issue I've found comes down to more guesswork. I've seen some plugins need more 'lookahead' than others. For plugins that need a lot of lookahead, I think it's occasionally possible that the lookahead can exceed the maximum buffer Logic allows, which causes the whole system to get extremely sluggish and wonky. Again, I am guessing to a good extent here.
And the last issue I've encountered (not lately, but I also haven't been doing as much work) is with projects with video tracks. It seems like occasionally a 'section' of song can get corrupted when it comes to time. I'll encounter the same weird stumble at the exact same spot after this glitch occurs. Once it happens it's really hard to remove. I think I've occasionally had luck with removing the video and video track entirely, but sometimes I actually have to copy and paste all the regions into an all new project and copy paste all the settings, etc to remove it. This does seem to possibly by related to the multicore bug I mentioned, but I don't recall the specifics.
It's also been a bit since I updated etc, so it's possible these bugs have been fixed and replaced with new ones. Hopefully some of these may help.
Link to comment
Share on other sites
des99
Multi-core options, eg Diva, worked fine for me on my old Intel MBP, and gave improved performance.
On the M1, multicore doesn't work so great. Even plugins that implicitly used multicore in their audio engine (eg the latest Korg plugins opsix and wavestate), gave terrible performance on the M1, and Korg had to rework their engine to not use a multicore/multithread engine (and the performance radically improved as a result.)
As with most things, you need to play with various options to determine the best config on your system...
Link to comment
Share on other sites
Picpoul
I'm having all of the above issues on my M1Max MacStudio - it's been driving me crazy. I've tried a full wipe and reinstall of Monterey (I had originally done the migrate assistant as recommended by Apple - which I'd assumed had caused the issues in Logic), however the fresh wipe and install made no difference.
I'm getting constant CPU spikes, running either full stock plugins, or with third party. I tried a process of elimination when I wiped it, reinstalling things one by one and testing. Stock gave exactly the same issues, in particular with Alchemy. Then when I loaded in Arturia Pigments, identical issues.
Every I/O buffer level gives the same result, bad latency, glitches, pops, crackles, playhead jumping back to the start for no reason mid playback, random channel spikes where the audio maxes. I've tried various multithreading options, lots of other tweaks here and there and combinations of each - no difference and no improvement.
I'm on MacStudio M1 Max (10 Core CPU, 32 Core GPU), 64gb RAM, 2TB SSD, running latest Monterey, with SSL 2+ (USB C), Nektar LX88+ (USB C), and plugins from Soundtoys, Arturia, U-he, Slate, Plugin Alliance, Oeksound, Kilohearts and others. All updated, all M1 Native, no Intel 64. I did try Rosetta but performance was woefully worse.
Someone on another board suggested I freeze tracks. What is the point of an M1 Max if we have to freeze tracks? My 2015 MBP had no problems running 40 tracks with plenty of third party stuff. It was only in the final few years I had to start freezing things, which was why I upgraded and invested a lot into the MacStudio. Total waste of money so far. Apple have been zero help, I've written complaints, spent hours on phone to their tech team and to the pro apps team, nothing. They've 'not had any other reports of problems' which is a total lie. They say their engineers are looking at the Support Profile I've shared, to figure out what the problem is. This has been ongoing since July!
If anyone who has had these problems has managed to sort it, please do let me know.
Thanks :)
Link to comment
Share on other sites
zipb
Do you also have these problems when you use internal audio instead of an external soundcard?
Link to comment
Share on other sites