Extended And Consolidated Midi I/o Settings...

It would be welcome for the MIDI tab in preferences to be improved, essentially becoming a table-like setup page that includes all global/project MIDI settings options for each MIDI port.

Example mockup:


The MIDI ports, as on the MIDI tab currently, would be the rows and the following would be column headers:
Focus MIDI, Sync/clock MIDI, Scene MIDI (with option for project overwrite), Lock MIDI (with option for project overwrite)

This would allow much more flexibility, control, and understanding of how MASCHINE deals with and can be used with external MIDI. For focus and clock in particular, I deem this essential.

Spoiler: Original Post

I use all my external synthesizers (8 of them) in midi focus input mode. I really find it hard to work like that since every knob I move on EVERY synthesizer, external midi controller, etc will affect the SELECTED GROUP or PAD.

I need to choose what midi devices send data to the devices that are in midi focus input mode (and focused, of course), otherwise I need to turn off the device on the midi input menu under preferences in order to prevent unwanted parameter tweaking on the selected pad.
For example: I want the Kontrol s49 to be the only midi device that "talks" to (selected) pads that have FOCUS as its midi input mode. At the same time, I still want to be able to tweak any parameter on any synth or midi device without affected that selected pad (which is in focus midi input).


PLEASE, PLEASE... Thanks

 

It´s not only with external synths.
I want to arrange the patterns manually on a Maschine Jam and play a synth live via Komplete Kontrol S, but each time I touch a pattern pad, the instrument in the browser is set to the focussed GROUP of the de-/activated pattern.
So I can´t step through the synths presets anymore because of the changed instrument in the browser.
It would be very helpful if you could deactivate the focus change when triggering a pattern by pad.

 

I use multiple controllers and synths all the time and I really don't see your issue... simply do not use FOCUS mode and manually assign the inputs

 

So you don´t use a Komplete Kontrol Keyboard then?
It does auto-connect to Maschine when you add the MIDI in.
Turning off FOCUS has been my first attempt to solve the problem.

 

Turning off focus won't help with your particular issue with KK. It will allow the keys to stay locked to a particular sound/group but will not stop the focus on the knobs and screen from following. The KK Keyboards could use an independent focus feature that you could toggle to break the sync. Also, Jam could benefit from a preference that allowed you to select patterns without auto focusing to the group of that pattern.

 

MIDI focus could really do with having an assignable port/channel in preferences (like 1.x had), which would make it so much more useful for users with multiple controllers who want to use just one to be the "focus" controller.

 

I (and many other it seems) really need to be able to select one midi input devices as an exclusive device for the Focus midi input mode.

In my live setup, I would like to have a number of dedicated controllers assigned to specific sounds/tracks, while using my Komplete Kontrol 88 for playing different sounds using the track select up and down arrows in the Navigation Section.

I imagine that this could be achieved by having the possibility to select one of the active midi input devices as an exclusive device for the Focus midi input mode on the midi input preference page. That way, when set to Focus midi input mode, the track will only receive midi messages from the exclusive midi input device. And in the case that no exclusive device is selected in the midi input preference page, Focus mode would receive midi messages from any active midi input device, such as is the case now.

Without this feature, you virtually need one controller for every sound/track you want to play live in your session, which doesn't make much sense.

 

For flexibility, I'd rather it allow the user to add one or as many inputs that work with focus as they want, as opposed to limiting it to just one. But certainly, a pretty basic filter like this is needed for focus to be truly useful.

 

You're right.
Should be possible to select multiple inputs to operate in Focus mode.
Could be as simple as having the option to select each input device for Focus mode in a separate column next to the device in the Preference -> MIDI page.

 

Absolutely. I think that tab could do with a bit of a spruce and perhaps allow focus, MIDI clock, Scene, and Lock settings be part of it too. Consolidate and tidy the MIDI settings while making Maschine much more flexible with external MIDI.

 

It would be welcome for the MIDI tab in preferences to be improved, essentially becoming a table-like setup page that includes all global/project MIDI settings options for each MIDI port.

The MIDI ports, as on the MIDI tab currently, would be the rows and the following would be column headers:
Focus MIDI
Sync/clock MIDI
Scene MIDI (with option for project overwrite)
Lock MIDI (with option for project overwrite)

Inputs and outputs would still be split across two pages. For each MIDI port and function, there would be an option for the port to be enabled/disabled, the MIDI channel it receives (input page) transmits (output page) on, and (where applicable) which message type(s) it allows.

This would allow much more flexibility, control, and understanding of how MASCHINE deals with and can be used with external MIDI. For focus and clock in particular, I deem this essential.

 

Something like this: (?)


Not sure where the "project overwrite" toggle could go or where we set these project specific settings though...
Maybe a save/load ability just for this?

 

Absolutely, though I'd also like to see an option for whether the port is listened to for MIDI mappings and options for setting specific channels for each port/element too.

Possibly. The main part is the different options for the different ports though and, to me, the project overwrite option would be a non-essential cherry on the top.

If the first part could be done, that would be a massive step forwards in my opinion (in this area anyway).

 

I'm lost now... What mappings?

Your think locking a port to specific channel globally like this is a good idea? Wouldn't it be better to add a drop-down with a selectable channel to the stuff that doesn't have that option? Like the "MIDI Change" Scene/Section/Lock menu for example.

 

MIDI learnt mappings from external MIDI sources e.g., MIDI controllers.

However, NI would also need to fix an issue with those MIDI learnt mappings that ignores the MIDI channel e.g., CC36 on channel 4 is received, treated, and used exactly the same as if it was CC36 on channel 11 = ridiculous.

To be clearer, I meant that each of the ports and functions would have the option to have a specific MIDI channel assigned (or just all/omni or off) e.g., "Virtual MIDI port 1" could be used on channel 4 for Locks and channel 7 for Sections, while also receiving messages for MIDI learnt messages on channel 12. The lock, Scene, and Section options would also need the option of note or program change, as per the MIDI change dialog.

 

Got it, (i think) an extra collum for "MIDI Learn" aka mapped stuff...

Not everyone is as smart as you and in order to have feedback these requests need to be easy to understand senpai!
MIDI change dialog already has channel selection so... would it be something like this: ??

 

Yes, I think something like that would do nicely. As the thread title says, extend and consolidate the settings, so there would be no need for that MIDI change dialog and all MIDI settings would be in the same place, but with the precision many users (not just me) need. For instance, the option to only have certain ports respond to the "focus" option, CCs only on certain ports would trigger MIDI learnt parameters, MIDI clock is only sent on certain ports, locks will only respond to notes on a certain port/channel, and Section changes will only respond to program changes on a certain port/channel etc.

 

Oh, so no more MIDI Change menu.
You dream big my friend, this would be an amazing step forward for general MIDI control.
+1

Hopefully, the mockup helps others understand how cool this would be.

 

In the grand scheme of things, I really don't see this as a big thing at all (significant and helpful, though, yes), but in the context of Maschine and its development, I fear you are correct.

Thank you for doing the mock-ups )here and on other threads), by the way. Very helpful and not in my sphere of expertise (and not something I have the time or inclination to learn at the moment).