MuTools

andstwo · Post by **andstwo** » Mon Aug 19, 2024 9:30 am

Hi,

I am using 9.5.34 on MacOS Sonoma 14.6.1.

The sound often crackles, hangs then continues. It is quite annoying, and seems to be connected to number of audio threads. It is the least probable to occur with 1 thread, and occurs almost instantly with 4 threads.

I created logs & screenshots, it did not occur with 2 threads within ~2 mins (but in practice, it does). Very rarely also with 1 thread. When it occurs, the CPU load goes up to almost 9000%.

Can I do something about this in Preferences? Is it a known problem?

Thanks.

andstwo · Post by **andstwo** » Mon Aug 19, 2024 9:55 am

It's an M1 CPU, I forgot to add.

MuTools · Post by **MuTools** » Mon Aug 19, 2024 7:14 pm

I see that you're using the Pigments VST plugin. Could it be that it has multi-core capabilities itself and that the MuLab multi-core and Pigments multi-core are fighting? Try disabling the Pigments multi-core.

Protocol_b · Post by **Protocol_b** » Mon Aug 19, 2024 8:53 pm

M2 Pro, 32GIG, Ventura 13.5.2 - using MuLab Plugin, latest version. It happens with just a couple of Kontakt instances, Phrasebox and DrumComputer running. The Kontakts indicate minimal CPU usage. Out of nowhere, zippering, buzzing, it's not recoverable without closing the project and restarting it. The channel strips indicate ongoing music, but all I get from the master channel is noise. It may happen after 5 minutes, it may be an hour. But it is becoming a regular occurrence... Oddly, when restarted, there is still residual zippering that fades after some moments.

Protocol_b · Post by **Protocol_b** » Mon Aug 19, 2024 10:10 pm

In my case, I'm not savvy enough to provide logs, stats etc. I have no idea if multithreading is my issue... I was just hoping that my description might trigger a thought, or stimulate someone else to add their experience.

MuTools · Post by **MuTools** » Mon Aug 19, 2024 10:20 pm

Protocol_b wrote: Mon Aug 19, 2024 10:10 pm In my case, I'm not savvy enough to provide logs, stats etc. I have no idea if multithreading is my issue... I was just hoping that my description might trigger a thought, or stimulate someone else to add their experience.

Does MuLab Plugin's CPU meter go to maximum?
If yes then it's too many plugins for the single core MuLab Plugin is using.
You could try to solve that by using multiple instances of MuLab Plugin, and then the host can use its multi-core engine to optimize the processing of the multiple MuLab Plugins.

If it's not a CPU issue then maybe there is a plugin signal distortion somewhere.
Try switching off or removing plugins one by one to find the bad one.

Protocol_b · Post by **Protocol_b** » Mon Aug 19, 2024 11:45 pm

Good pointer - I'll have to check that CPU meter. I'll be back

. Multiple instances sounds like it would complicate the mixing / recording tasks, though. Not that I ever get around to actually recording anything.

andstwo · Post by **andstwo** » Tue Aug 20, 2024 9:31 am

MuTools wrote: Mon Aug 19, 2024 7:14 pm I see that you're using the Pigments VST plugin. Could it be that it has multi-core capabilities itself and that the MuLab multi-core and Pigments multi-core are fighting? Try disabling the Pigments multi-core.

Sadly no, I also got these in an audio only project.

I made a test with an empty, default project and I could also reproduce. I attached a gif about the event, as you can see I was playing the empty project for about 1:30 when it happened.

Protocol_b · Post by **Protocol_b** » Mon Aug 26, 2024 3:55 pm

Alright - in my case, Mulab is not reporting any overload. But once it strikes, my host suddenly runs at 60% CPU, even with notes and transport stopped, and is reporting that my audio interface is running late. Possibly a bad cable or god forbid a bad interface.

andstwo · Post by **andstwo** » Mon Sep 02, 2024 7:40 am

Can a bad cable cause this? I have a Scarlett 2i2, never had problem like this but I'll check without it.

MuTools · Post by **MuTools** » Mon Sep 02, 2024 8:16 am

No, surely not a bad cable. But maybe something system specific. I wonder whether there are any other MuLab 9 App for Mac users experiencing this? I'll also doublecheck it here with MuLab on Mac soonish and will report back.

Protocol_b · Post by **Protocol_b** » Thu Sep 12, 2024 3:50 pm

OK, I opened the Plug and same Project in Reaper. I left it playing away for several hours - not a glitch to be heard. It indicates a problem with how Liveprofessor 2 and the Plug are communicating audio betwixt themselves I guess.

Protocol_b · Post by **Protocol_b** » Mon Sep 30, 2024 5:14 pm

Is there a way to place an official support ticket? I've been asked to by the developer of LiveProfessor2, 'Audiostrohm'. Nikolai Bergstrohm will test using Mulab Plugin, but wants something to reference if he needs to reach out to you...

MuTools · Post by **MuTools** » Mon Sep 30, 2024 6:21 pm

Protocol_b wrote: Mon Sep 30, 2024 5:14 pm Is there a way to place an official support ticket?

No explicit place, but you can report things here at the forum, as you did.

I've been asked to by the developer of LiveProfessor2, 'Audiostrohm'. Nikolai Bergstrohm will test using Mulab Plugin, but wants something to reference if he needs to reach out to you...

As a plugin dev Nikolai can also email me directly via

. I'll be happy to give him a temporary MuLab 9 user key so to ease testing this case.

From my side i'll also do some specific tests when the next new MuLab version is compiled on Mac. Taken note about that. That will be in a couple of weeks i estimate.

Michael L · Post by **Michael L** » Mon Sep 30, 2024 7:39 pm

I’ve used MuLab Mac for many years & heard crackling a few times only when I overload the CPU with certain plugin settings (eg polyphony & long release) or have other applications open. I see LiveProfessor is a host with many features, and chains plugins in series /!\ Try building your signal chain piece by piece to find the overload point.

MuTools

KVR Audio

8600% CPU load on MacOS