User Details

Username: mike8040
Website: None provided
Facebook: None provided
Twitter: None provided
Soundcloud: None provided
Account Status: enabled
Member since: Jul 19 2019
About mike8040:
(report this profile)

Devices by mike8040

No devices have been posted by this user.

Comments by mike8040



You're right. I never toggle mute that fast to be honest. More bar wise. But your solution is definitely working better in that regard. Just as simple as that. Thanks for the share! In the meantime I reduced the plugins interface as I have lots of stuff going on on my master channel and the space is tight.

Ok, for anyone or those 1% that has this annoying Mute toggle bug I found a solution. Deactivating my midi/mackie services did not solve the issue so I opened up the plugin in max as last try. Having some degree in webdesign and php I was like, fuck it cant be rocket since.
This is a 5 minute fix so bear with me as I dont know the fuck about max coding basics. It just works and I can go on. The bug made me nuts..

The screenshot I made is pretty clear. Just open it up in max4live and save it afterwards. You can do it while you're running Live too, but save you project first maybe...

Same goes for an empty Live set on my side too. Possible things that might help in a direction.
I'm speaking for sole key mappings in Futility here which I want to use.
I got Mackie protocol running (could interfere)
I run Studiomux (midi/audio connection for iOS - but not using this for the actual cases but its active)
NOB and Powermate controller that emulate mouse behavior (less likely)
I try to test the scenarios disabling those tools when I got time.

Thanks for response. Yes unfortunately the plugin has a weird behavior. I found out the mapping browser/arrangement/device mapping doesn't work at all. I mapped a dozen different keys but nothing happens besides Live refreshing the interface. Nothing fancy running here and the latest Live GM release.
For now the plugin unfortunately not usable for me. Hope you can find a fix for it. Greetings

Argh can't edit. I installed it now. The mute behavior is strange. I mapped it to the key M. One click to mute but I need 2 clicks to unmute the track.

Arm and solo doesn't have this issue. Whats wrong?

Thanks for the reply Crampe. Then it goes straight to the cart :)


I used the V2 frequently the last years. Thanks for the tool. One thing that bothered me a lot was that after reopening the project all my mute/unmute stats where gone. In other words all tracks where unmuted even if that wasn't saved in that state. In the composing stage I mute a lot of different ideas and leave the main groove working. Opening up you have to guess again what was muted as backup or different version.

Is it still the case with 3.2?