Big Audio Mute and Lock Funktion Issue

Mac-Kee · 2024-12-12T14:56:57+00:00

There was an error rendering this rich post.

I have a big problem with the Maschine 2 software, which is a real hindrance when playing live. I have turned off the “Audio Mute” on all tracks of my project so that sounds do not stop suddenly when muted.
If I now perform with the Maschine and use the Lock (Parameter Lock) function and then release it, the Maschine switches all tracks from Audio Mute off to Audio Mute on and my performance is impaired as a result.
What am I doing wrong, who can help me?

Find more posts tagged with

Comments

Rilkecat

+1 it happens the same to me.

At the same time, after using the Lock function Sounds slots that were empty (no color) get crowded with a Name "Sound No.x" and color.

Mac-Kee

maybe you should just realise that Native Instruments is not able to bring a flawlessly running software to the market. Just tested it with Maschine 3. same problem.
If this is supposed to be a feature, then someone please explain to me what it's supposed to be good for.
I am so done with NI.

Rilkecat

Maybe its a sort of reminder that automatically sets Audio mute ON, supposing you forgot it ;D

Looks like a bug - logical error, let's see if anyone alse reports this issue

YellowCake

I have the same problem.. has anyone found a solution?

YellowCake

Okay, the only one solution is to make an audio mute automation on the sound..

Rilkecat

Not yet…

Audio Mute seems to be a good function but imperfectly implemented.

We have this bug, and also lack of Audio Mute OFF at GROUP level :(

D-One

This issue has been around for ages, IMO anything that cancels parameters we set for no apparent reason can be considered a bug.

Psyearth5

https://community.native-instruments.com/discussion/comment/209527#Comment_209527

Solution is simple, I am using Lock States for multi parameter Modulation but if you don't make them in In chronological order, then the newer channels will be out of Control, so Lock State should be created after the change, because everything that is after and is not an update will not be under control.

Quick links

Unanswered questions