Upgraded to Maschine 3 - extreme CPU memory consumption issues

jeff619
jeff619 Member Posts: 4 Newcomer
in Maschine

Recently upgraded to Maschine 3 after years of stability on v2. Setup below. Basically when I go to a session I had no issues with previously, it is maxing out CPU, slowing down, crackling, etc. No exaggeration, no issues to can't play through. Even upgraded RAM to try and solve, didn't work. Mostly happens when running Ozone when mastering, but was never a problem before.

Anyone else having this issue when upgrading? I've reinstalled Ozone, even pushed latency to the max - no luck.

Mac Mini, 3 GHz 6-Core Intel i5, 64 GB RAM, OS 15.4.1 (now 15.5)

Have run all the small fixes. Disabled energy saving, making sure USB hub is powered, quit other applications. Still can't use without bouncing all tracks down before mastering which is not fun.

Answers

  • AdelV
    AdelV Member Posts: 448 Guru
    https://community.native-instruments.com/discussion/45274/upgraded-to-maschine-3-extreme-cpu-memory-consumption-issues

    I’m experiencing the same issues with Maschine 3, but only when I use Ozone or Tonal Balance 2 along with any other Ozone processor on the master channel. It’s very important to remember that Maschine doesn’t have plugin delay compensation (PDC), so any heavy plugin—even if used only on the master bus—can cause CPU spikes and increased usage.

  • D-One
    D-One Moderator Posts: 3,698 mod
    edited May 20

    @AdelV said:

    It’s very important to remember that Maschine doesn’t have plugin delay compensation (PDC), so any heavy plugin—even if used only on the master bus—can cause CPU spikes and increased usage.

    PDC (Plugin Delay Compensation) does not reduce the computer's resource usage or prevent CPU spikes at all; it just delays all tracks so they match the same delay caused by the ones with a plugin-induced latency, so everything plays at the same time in perfect sync… The name PDC is kind of self-explanatory.

    Lack of PDC for Mastering is a non-issue, since the plugin-induced latency there will affect all tracks equaly.

    https://community.native-instruments.com/discussion/45274/upgraded-to-maschine-3-extreme-cpu-memory-consumption-issues

    Interesting… for me Maschine v3 can handle more instances of Ozone 11 than Maschine v2. Are you using a high sample rate or something?

    It's important to distinguish memory/RAM from CPU. If the CPU is maxing out, buying more RAM will do nothing… Unless your RAM is also maxing out. Plugins such as Ozone use very little RAM, about 400 MB from my experience, but a considerable amount of CPU.

    It's also worth noting that Maschine will reach it's CPU limit wayyyyy before your total computer CPU limit, this is true for most Audio SW, I think Reaper is the only notable exception (at least with Mac, no ideia about Windows)

    With a M2 Pro Mac Mini with only 16GB of RAM (600$ on the used market at the moment) I can load 3 Ozone 11 in Maschine V3 with a buffer of 64, things fall apart with a 4th instance, in Maschine V2 it falls apart with the 3rd.

    Personally, I wouldn't go using Ozone on an Intel i5 on the same project where the production is, I'd export the .wav and Master it separately as Mastering engineers do.

  • AdelV
    AdelV Member Posts: 448 Guru
    https://community.native-instruments.com/discussion/comment/227168#Comment_227168

    You're absolutely right. But there's one important thing you're missing — Maschine has never been great at handling plugins, and that hasn't changed in Maschine 3. ;-)

  • 2A2E
    2A2E Member Posts: 50 Member

    I do not have a CPU issue on my Mac M1 or M4, but when I look at the RAM I can see it is using sometimes more GB than I physically have. Like 9 or 15GB or even more. On several Macs. I even got a note that my computer was out of memory. Only thing to was cmd-alt-esc and kill Maschine.

    And it always crashes when I quit Maschine. Every time with all version of Maschine 3.

    There must be a severe memory leak issue with the software.

    Maybe you can check your memory consumption when the issue occurs.

    I am using a lot of Arturia plugins, maybe I have to test with no plugins and see if that improves it.

  • D-One
    D-One Moderator Posts: 3,698 mod
    https://community.native-instruments.com/discussion/comment/227264#Comment_227264

    I have never had such an issue. When it happens, take a screenshot of the activity monitor and write down which project, so you can report it.

  • 2A2E
    2A2E Member Posts: 50 Member
    https://community.native-instruments.com/discussion/comment/227364#Comment_227364

    Wow strange, this is on several computers as well, all the same. Mac mini M4, MacBook Pro M1 and MacBook Air M1. It always crashes when quitting.

    I will do some more testing, like not using any plugins except the internal ones.

  • jeff619
    jeff619 Member Posts: 4 Newcomer

    Thanks, all.

    1. I've had similar crashing issues with v3, but it appears, for whatever reason, to be happening less.
    2. Appreciate the conversation re plugins and mastering with audio files vs VSTs. My frustration is I literally went from v2 with a full mastering session with ozone with no issues (actually never had any issues with performance with that setup), upgraded to v3 and instantaneously, without any changes, cannot even play through the exact same projects that were perfect before… now slowing down, chunking, etc. No crazy sample rate (actually was at 44, but moved to 48 based on NI guidance). In my v2 setup, was running full ozone suite over non-bounced tracks. While ozone may be part of the issue, I noticed a new project with 3 kontakt instruments running and it started to choke. This was never an issue with v2.

    Thanks!!!

    -J

Back To Top

Categories