2.1 midi input bypass record…..record arm/disarm for each group

It may not be a bug and it may of been in 2.0.6 but as midi drag and drop was hardly usable in that version
I doubt hardly anyone would of used used it.

Now they have fixed the drag to single midi file it may be that it has exposed a design floor that needs fixing, or made to behave the way it did in 1.8

Or else simply the only way to use midi export in maschine 2.1 is to use 1 instance of the plugin per group.

Or keep all midi internal and export at the end of a song. Which of course is a total workflow killer.

 

I guess the only way I can use it right now is to set it up like I do for the drag and drop method, then record into my DAW using midi mode. I was really starting to get comfortable using the drag and drop method though. It worked so well! Thank you b-righteous for contacting NI. I guess I'll have to work around it. I have never been upset with NI until this.

 

after another try just now there really is no workaround.

what is needed is a record arm/disarm for each group. right now record is global for all groups. (confused as to why)

 

I could be wrong, it might have done the same thing before 2.1 but I could have sworn that it didn't. I haven't had any problems with it until now.
For now we'll just have to either record from midi mode or we'll have to drag and drop after we finish every pattern inside a particular instance of Maschine.

 

Okay I got a chance to play with this. Topaz is correct that the issue is avoided in 1.8 due to the way it works. In 1.8 you can remove the pattern for the group receiving midi on a specific channel then select a new group. The first group that is now unselected will not automatically load a pattern when you hit record while it is receiving midi data. Therefore, any midi data coming in on that group will not be recorded. Further, in 1.8 it will not automatically shift focus to the group receiving the midi.

This issue is not new to 2.1 and is present in 2.06. Still, it is undesired behavior and I can't see any benefit to what it is doing. It seems to load a pattern to an unselected group if it is receiving midi data when you hit record. This should only happen for the selected group. Further, groups should not be auto selected when you hit record just because of it's midi settings or if it is receiving midi.

This issue was just recently brought up in another thread and can have a bad side effect even when you are running stand alone.

 

Thank you sir, here's hoping for a fix ASAP. Thanks for all your time, and sorry if I got a bit ratty ;-) ( I am frustrated beta tester/designer)

 

AS stated this bug has been totally ignored and I am not happy at all waited and waited since april and finally 2.2 arrives and nothing has changed.

My maschine is now on ebay, not because I don't like it but because the issue has been totally ignored.

I have again tonight as one last ditch attempt tried to hack this using bidule as a sub host. but NO WAY.

 

I cannot BELIEVE this problem has gone unaddressed.. Literally ran into it my FIRST DAY using maschine.. How is this not a more common complaint? It makes it IMPOSSIBLE to record in maschine, export the MIDI to Logic, then create part in maschine.. I love maschine' sequencer and want to use it like a sync'd module (as I'm sure lots of others do) but then keep my recorded MIDI in logic after getting the sequence just right, nudging, quantizing, etc with the controller, but that's impossible. This is absolutely ridiculous, serves no benefit, and makes it impossible to take advantage of Maschine's sequencer in a DAW. How has this not been fixed??? 4 year customer and this is my first time totally flipping out.. Even created a forum account just to express my utmost disappointment in this.

 

It won't ever be fixed, I sold my maschine.

If this was komplete software it would of been fixed by now. I can only assume the maschine team don't feel this is an issue
And the majority of their beat maker only users are happy so what you really need is another expansion pack.

 

But it's ridiculous, seems like such an easy fix... Make it so maschine DOES NOT jump to any group receiving MIDI, and instead record MIDI only to selected group. I can't believe they can be running a project that has these bugs. And they ARE bugs.. There's no reason that this could be beneficial to any workflow.

 

Or even just have a simple way to turn off recording of incoming MIDI (i.e. Local record mode) where incoming midi plays sounds but does not record.

 

The only way you can work like that is to go back to 1.8 x

Because this bug was introduced in 2x, if it was going to be fixed it would of been by now.

It never will as far as I can see, ( even after being told many times it would be after lengthy email dialogues with support team)

 

Wow terrible customer support.. Always been happy with NI products and have been a Komplete owner for years, this is just ridiculous. Honestly can't even believe it, and can't believe 90% of users aren't running into this issue.

 

No, everybodys having the same issue. People may be sick of being ignored by NI and choose to sell their maschines or live with the workarounds.

Midi drag&drop function is broken in maschine and NI is ignoring this. Only way to use it is if you finished with recording in maschine, now you can drag&drop. And anything further comes to your mind and hit the record, everything in DAW will be re-recorded into machine!
Remember "midi batch" was broken, too. Fixed only recently.

I never drag&drop. Never record anything into maschine sequencer (when VST). Make patterns in standalone, open in DAW, drag my patterns and keep recording into DAW, not maschine.
A workaround for drag&drop may be opening 2 instances of maschine.

 

Well said

 

And there you have it.

Maschine is one big " workaround ".

 

The only use I really have for maschine is for the sample functions and a DAW synced loop recorder/sequencer that corresponds with the sampler. I have much better sequencers (cirklon) and much better samplers (Kontakt) so the reason I really have Maschine is for a jamming bridge/hardware loop-recorder which communicates with my software projects. Shame that I can't get what I need out of it. Makes it prettymuch useless to me. I wouldn't mind the effort if there was a workaround, but currently no, there is none that will let me record new parts in maschine once I have the MIDI inside logic, so there is no work-around. I can use it for something that is NOT what I need it for, but there is no workaround that will achieve its intended purpose in my studio.

 

Add me to the chorus of users thinking this is a shame that this has not been addressed.

 

Unfortunately create music is becoming less important thing for native instruments

NI became a shopping useless gifts. music a fun hackers more interested in " news" than in really new.

The communication between DAWS and Maschine Software for exemple is an infinite universe of tutorials that alienates people of creativity and invention.

If you create an airtight logic which is the opposite of the word freedom.

We get stuck when we imagine otherwise.

simplicity...

 

• Problem is known since more than 2 and a half years. Check.
• A lot of people are affected. Check.
• Apparantly many contacted customer support about this. Check.
• There are multiple possible fixes that all should be super easy to implement. Check.
• 5 minor version updates later issue remains completely ignored. Check.

I'm losing my faith in NI. It seems like they've fallen victim to their success. I would much rather believe they actually care about loyal customers and making their products more awesome. But at some point it becomes too obvious that all is about marketing and flashing lights, sponsoring sucessful artists to promote their toys, and make potential customers believe that musical skills are bought with money.
It's just sad for all the lost potential.