Maschine Plus video, showing Aux select issue

S Righteous · 2024-11-13T21:23:22+00:00

There was an error rendering this rich post.

I made a video demonstrating how it can take 3 minutes to simply select an Aux destination for a sound in Maschine Plus standalone. I think a video best shows just how painful this process is, and that it's not an insignificant problem.

I also included the advice given by Darkwaves in this thread:

https://community.native-instruments.com/discussion/4379/maschine-plus-selecting-pad-as-aux-output-destination-is-buggy-and-causes-crashes

I really hope NI see this kind of issue and fix it in their soon to be released M+ update.

here is the video link:

https://youtu.be/xtjRlUPBqhE

Find more posts tagged with

Maschine Plus

Comments

darkwaves

For what it's worth; I've tested that again on a more recent version of Maschine 2 and couldn't replicate it. So this issue has been addressed in the software at some point. I haven't tested on M3 yet.

It's soooooo painful

S Righteous

Similarly - If you want to select a source for side-chain compression (usually a kick for me), you get a list of groups, and it's clunky as hell trying to select a source. They really need to fix these basics, since they are existing features that are brutally slow.

DiosGnosis

https://community.native-instruments.com/discussion/comment/190877#Comment_190877

OP was referring to this 'bug' in standalone on the M+…

I'm not sure you would be able to replicate in Maschine 2 SW or Maschine 3 SW running through a Mac/PC? Maybe I'm not understanding the issue…

I have M+ so, in order for me to replicate, I would only be able to test currently in Maschine 2 SW running on the M+ in standalone since Maschine 3 is not currently available on the M+, correct?

S Righteous

https://community.native-instruments.com/discussion/comment/191247#Comment_191247

In older versions of the Maschine 2 SW, it was also very slow to make these selections. That was fixed, in a later version of 2. but has not been fixed in the M+ Standalone. I assume it's fine in the version 3 of the software, but really want an upgrade for the M+ hardware !

darkwaves

https://community.native-instruments.com/discussion/comment/191247#Comment_191247

I only referenced the software because in the original post OP linked to, I replied that the issue wasn't just stand alone. It also occurred if using M+ as a controller with the software.

It's very easy to replicate. Add an eq or compressor to a pad. Duplicate it to the other 15. Now duplicate that group to the other 7 in the bank. Now try to route anything to pad H16 and…. wait.

Super overkill, but it will be painfully obvious.

I find it interesting that more people don't run into the issue; but I guess people just don't route stuff as often as I do.

DiosGnosis

https://community.native-instruments.com/discussion/comment/191268#Comment_191268

Correct concerning routing on my end. I'm such a minimalist that I can generally throw whatever FX I want directly on the pad. I honestly don't think I have a project saved with 8 groups even… And even the groups in many of the projects might have only one or two sounds/instruments loaded onto a pad. Maybe except for the drum kit group…

Fortunately we got you routing junkies in here to point out the holes in our beloved quasi DAW hardware/software hybrid mutant music making box 🤪

Well I'm home now so, imma fire up M+ standalone and see what it do…

DiosGnosis

Oof… Yeah. This is atrocious in a standalone environment. I can't imagine putting faith in any kind of LIVE performance workflow…which had been the intent upon purchase of the M+ for me. Still more time on that front so, hopefully the Maschine 3 SW addresses the issue (will test shortly with M+ as controller), and that the M+ 3.0 update ships with the fix.

DiosGnosis

Okay just tested in Maschine 3 SW using M+ in controller mode. Smooth and buttery. No lagging or hiccups on my end.

M2 Mac Mini / 8GB RAM / Sequoia 15.1

Looks promising that the 3.0 port for M+ will have the fix.

S Righteous

https://community.native-instruments.com/discussion/comment/191274#Comment_191274

I do plan to use M+ live in standalone mode, but changing routing wouldn't ever be something I did live, so it's totally usable live (for me). I also do minimal stuff sometimes, but I hate song mode, and would never want to stop a song to 'load' a second one. So I have all samples for all songs loaded at the same time, which means using a lot of groups. Then I also use many scenes and edit stuff live using global macros.

If you want 10 songs loaded in the M+ at the same time, you will find you use more groups, and patterns, and well - all that stuff which will make your project seem non-minimal !

DiosGnosis

https://community.native-instruments.com/discussion/comment/191281#Comment_191281

And that's the learning curve for me currently. Its all good and well using the SW for over a decade now, but confining myself to the limitations and maximizing efficiency and workflow within a more finite ruleset is a joy and a challenge.

darkwaves

https://community.native-instruments.com/discussion/comment/191274#Comment_191274

I'm over here laughing at "Oof". It really is quite the sight to see. OPs video shows it; but seeing it in person is like, "Oh, wow. This is horrible." lol

Do the same test, but select all pads in group A and try to change the routing. It might take an hour to get down to H16.

DiosGnosis

https://community.native-instruments.com/discussion/comment/191286#Comment_191286

It's soooo finicky… I just can't. This is tedious beyond reproach.

Psyearth5

https://community.native-instruments.com/discussion/comment/191247#Comment_191247

Correct it's computer for now… the problem is not a problem it's a way more beneficial than without Sends and CUE correlation but it is in Manual and if you look up believe me you won't miss because it's the Name of one chapter. It's fastest device that can connect 16 MIDI or Audio channels, advanced routing by selecting multi Pads.

D-One

https://community.native-instruments.com/discussion/38545/maschine-plus-video-showing-aux-select-issue

Same here, can confirm… Altho it's not nearly as laggy for me as it is to you.

I think it's the same problem as selecting an interface for example, as you turn the knob M+ applies the changes during scroll to all possibilities it "passes by", so applies tons of changes on rotation instead of waiting until you stop rotating to actually make just the final parameter change.

For a knob controlling audio stuff like a filter the above is desired, but for selecting one thing from a list it might not.

https://community.native-instruments.com/discussion/comment/191272#Comment_191272

I do this too often and it's fine sometimes but you lose reverb tails on mutes/solos and use 16 reverbs for a Group instead of 1, which in a Standalone can suck up previous CPU resources.

S Righteous

I definitely hope it gets fixed in the next M+ update - whenever that will be.

Quick links

Unanswered questions