Bretherin,

Im on M1 Max MBP 2021 Sonoma and thought myself to have a decent machine and running into CPU overloads with logic a fair bit, and I'm wondering how much the cracked stuff is playing a part, I do use some heavy legit stuff but I've had these issues over the years with various machines,

Im considering looking at studio one for a trial to mix and master in, I saw there is a increased buffer size that looked promising and I saw a review on YT touting they had no issues, but am I being stupid here as its the same machine and same plugs in all essence so surely it cant make that much difference? Thoughts?

 

Most of the k'd software for Mac is identical to the real releases, just patched. None of them use more resources than the original retail versions. You should include some examples that you think might be different.

How much memory do you have in the laptop and what buffer are you using in Logic? Are you recording audio in? What audio interface do you have?

You should add "Mac" to the thread title before people want to discuss completely unrelated off-topic stuff.

 

Last edited: Dec 30, 2024 at 2:10 AM

Thats handy to know...

I as I've been buying a lot of stuff I feel Im going to try to rid what I don't use and run lean, but to your point It might not make a difference

my guts telling me:

Waves complete
Fab Filter Bundle
Izotope Ozone (Currently on 11)

part of the problem is I've got so damn much its hard to pin down lol

 

A witch says,

* Our release loads faster and uses less RAM than legit version.

 

Not exactly sure if Mac audio works similar to Windows ASIO, but ain't you running a buffer size that is just too small? On Windows, at least 512 samples or more is stable enough for mixing tasks. Pushing 128 or lower buffer sizes will undoubtedly turn into overloads at some point.

 

plugins that aren't running have 0 effect on cpu load, so it should be more straightforward to identify what (if anything) is causing issues, especially if you freeze/turn off tracks one by one

 

Last edited: Dec 30, 2024 at 4:47 AM

No. Just like with cracked video games, cracked plugins are less resource-intensive.

 

This is why I asked if he was tracking or not. We've discussed this one before. If you are not tracking live instruments; the bigger the buffer you can put up with, the better. In Logic, latency compensation actually works correctly. Insufficient memory can slow the performance more than people often give it credit for.

 

Last edited: Dec 30, 2024 at 4:59 AM

at least for properly cracked things yeah, there is an occasional poor quality crack that is worse

 

k'd plugins also make fye beatz

 

It's likely the Waves complete.

On my old Intel macbook, i installed the full Waves complete crack earlier this year - just so i could test out some of their plugins in Logic/Plugindoctor and see if any were worth looking into (very few were, btw). I instantly noticed that my machine was running slower and laggier especially upon loading the Waves plugin(s). I didn't actually care, since this was my old computer i don't use anymore. And perhaps i'm the only one encountering this. But i have plenty of warez installed on my main macbook (not Waves), and I have zero complaints/issues. So yeah it's probably the Waves, if anything.

 

You can always say this about Waves, especially when you try to run a "latest and greatest" version of them on a somewhat outdated computer. New versions of plugins are often less optimized, and even a simple plugin can use way more resources than it ever should.

There is plenty of bad software that runs poorly, even when cracked perfectly. You have to directly compare the performance of the cracked product vs legit. If there is a need to compare, you can often do it with a demo version. Obviously, you do not want to do that with Waves.

 

Cracks have electrolytes.

 

if you have peaks/spikes/overloads because you use plugins in a session, try an interface that is quick enough to deal with that, preferably with thunderbolt connections....that should make the difference. If you have spikes/peaks it's because the system can't calculate fast enough what it needs to do next. Imagine it needs to read the audio, apply whatever sound manipulation you want it to perform, and then playback that result in real time.....so the quicker the connections are, the less likely it will peak or spike. If you still have issues, increase the ram memory. Your M1 should be able to handle running a daw like Logic without too much hickups.

 

Excuse me in advance, do drugs harm our body and our brain? Or on the contrary does it open doors or lock us into bad habits? The answer is quite obvious it is the dose that makes the poison, and in general having a healthy system or body with regular physical and software optimization allows you to avoid all risks, I am under Windows, my old bike is 12 years old and obsolete as far as possible hardware optimization question, cpu.gpu however in a simple mixing session with ableton I had huge CPU problems or even crashes with example the AA I could not not use several instances per track etc., now that I have abandoned legit and switched to full AA of r2r I can easily put as many instances as I want per channel and even make rather complex chains which was not not even possible before with my old bikes, so yes the cracks are not ever only good, but sincerely when the wizard/witch cleans and rearranges plugins full of bloatware and other joy, the cpu breathes like after a hike in the mountains in winter without abuse of cheese melt.

Happy New Year to everyone and see you soon in 2025

 

What questions really ...

 

Best if you download a DAW (just for testing plugins) that lets you monitor CPU-usage per plugin and then replace the worst offenders with more efficient alternatives.

 

Slightly off-topic: I made a custom action in Reaper that turns all fx on selected tracks and their children offline. Merely muting them would do the job of cutting down on CPU use, but making their fx offline also zeroes them out on loading time when opening the project. For many tasks, I can turn every track and bus off but one. This simple trick has made my work flow easier and faster!

 

Unfortunately, not in Ableton. (unless, as you said, you freeze/flatten), turning off doesn't kill their cpu use, obviously it could be less if it's an instrument that is not playing notes of stacked complicated polyphony like a serum/pigments patch or some Kontakt scripting large library etc kinda thing having more immediate fluctuating demands re cpu etc), and also even when off, they are still reporting their latency as if on etc.

Part of that, or what they use as an excuse on that, is that hey, Ableton 'Live' is intended to be used 'live' so everything is primed and ready to go all the time.... but they really gotta do something about that, or develop another 'mode', similar to other daws, in which you have say, a 'tracking'/live' mode, and a mix/production mode etc....(but those options usually have more to do with toggling pdc latency and whatnot)

(and they really don't want to do what many speculate the problem is, in their underlying engine they have been putting off for a long time)

Sorry, early in day for me, and if I typed something that was slop, my apologies, still waiting for coffee...

 

Last edited: Dec 30, 2024 at 1:51 PM