It does touch on one thing though, which is how does it currently work for hardware synths for which there’s no out of the box mapping? Is the only way to create a mapping with the software on a computer? That would be quiet disappointing Regarding CC control, AFAIK this works, and can also be automated just like for internal synths (see for example ). Thanks for sharing your experiences with it! So at the moment I am actually only using the filters and lofi fx in the unit. The most basic delay it has is always synced to the tempo and does not self oscillate. is no ‘normal’ delay in the device at the moment. And I would really like if NI added some of their studio fx to the Maschine+, as there e.g. make tiny helper plugins in Blocks to overcome the limitations of the software. Only the Moog emulation (I forgot the name) can be used rather easily, as it just has that classic signal flow. You have to know the plugin and its signal flow by heart and then still don’t get all the parameters of the software version.
Maschine library 1.3 Patch#
But making a patch from scratch is almost impossible. I believe the idea is to just load up presets and then fiddle with the values a bit. You are just given a bunch of parameters that are often not clearly named. The screens don’t show you any information about how the instruments are layed out. Regarding software instruments, I don’t find the implementation of the available NI plugins very good. More free approaches can be done, but you have to work against the unit in many ways, which can be tiresome or rewarding, depending on how you see things.įor sequencing other gear, keep in mind that at the moment, there is no CC control. So if that is your thing, you might want to consider it. The actual Maschine and how it is structured really wants you to stay on grid and make beat driven music. I love the hardware, how it feels and looks. It is a piece if gear I feel somewhat conflicted about.
0 kommentar(er)
