![]() ![]() I created loop-MCU and loop-Pads in loopMIDI. Now, I don’t know for sure that this is what’s happening, and I don’t know for sure that it is just like a plain controller, because I haven’t had a Maschine before the Plus, but it sure looks like this to me.ĭunno if this helps, but here’s a screen shot of the Controller Editor for the Plus: (The sound interface shows up as a USB sound device, so I could use it for play-out if I wanted.) Once you set it to “controller” mode instead of “standalone” mode, it just disconnects the internal Atom/Linux board, and runs the controller like any other controller. ![]() Regarding Maschine-Plus as controller, AFAICT, the device is actually a plain Maschine controller, wired to an Atom-based quad-core Linux board that runs the Maschine software on the inside, and a sound interface. I had really hoped that this would be a little more automatic, because I have little enough time for the music as it is, and this sounds like another day of setup So, I created a reference sheet here which may help if you want to dive deeper:. And you need that instrument button to control VSTi parameters. the instrument button is ‘save’ on the standard mapping which is confusing. As it doesn’t use traditional MCU mapping. I’ve hesitated buying one as i’ve seen no-one else doing this to confirm if it works, so please report back how it goes if you try it.Įdit: One other note, is that you’ll have to modify the default MCU control to really get the best from Cubase. Really curious what the MCU mode is like on the Maschine Plus/Mk3 - as screenshots are quite sparse on it. It sounds tricky, but it’s really simple to setup, and will work for any other DAW too once you have it running. The other option is to set the pads to MIDI Ch2 and use MIDI channel filtering within Cubase, but this method works so much better. I have a group for chord pads, one for minor scales, major scales, and another for drum mappings. (Which it will be default)Īnd you should be good to go, you can just create mappings as to which notes you want the pads to send in the NI software. Your virtual ‘Maschine Pads’ port should be showing and set to ‘all midi’. (This prevents the MCU pads from sending to each track)Ħ. Ensure that the standard Maschine ports ‘all midi’ is deselected. Set the standard Maschine ports as the IN/OUT for MCU. (I use a Mk2 so i have also applied a velocity map to my mapping too - handy if you don’t find the pads very responsive).Ĥ. Separately, and this may be better asked over on the NI forums, but is there a way to use the knobs and displays on the Machine Plus for the macros/browser UI when using the Komplete Control meta-plugin to browse and select instruments/presets? Is there some way to set this up to actually work well in this hybrid mode, or is it just “not gonna work?” In MIDI CC mode, I don’t get the feedback on the Maschine screen from the eight pots. I can turn this off by turning the Maschine Virtual MIDI off from “in All MIDI ports” in the Studio setups, but then the pads don’t send notes to the instruments (which is especially sad when using VST drum synths.) I assume the MCU is a standard that sends “controls” over MIDI notes as protocol. And the MIDI buttons end up also doing things in the editor windows. However, when it’s in MCU mode, it sends MIDI notes even for the command buttons. I can even edit buttons to map some buttons to “MCU” actions and some buttons to MIDI actions. I know how to make the Machine think it’s in MIDI CC mode and/or MCU controller mode using the NI Controller Editor program. (I also use a “regular” USB MIDI keyboard for playing chromatic instruments.) I do not use the Maschine instrument or software when using it on the computer, I use Cubase with a variety of VSTs (including NI Komplete and others.) I’m also sometimes hooking up a Maschine Plus to use it as a controller and pad player. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |