MicroTonicMaxed

Comments (4)

• braduro · March 25 2017
  Always happy when someone throws some love towards µtonic.
  Now customarily, I can control it with CC's or configure the plugin in native control, then have it map to Push or any User Settings for encoders. As for randomization, I can use µtonic's own Piku scripts, and as for save, I can just save the preset or bank for the device.
  So what advantages are there in using a M4L device? For one, I wish there was a way of selecting a Pad other that clicking it so it was immediately ready on a per channel basis. But I do like that I don't have to map a repeat of every per-channel parameter.
  Also, the values jump in any case when switching pads, but that's no biggie. So how do you work whereby you concluded that the M4L approach was the way to go?
  Cheers!
• mothergarage · March 28 2017
  well, I have microtonic sitting in a drumrack (as provided). I find it easier to manipulate each pad this way. randomization and loading of presets are (afaik) not availabe via push.
• braduro · March 29 2017
  interesting. Seems to me, I'd want just one instance of this device. Either I delete all the ones before the External Instrument router and leave it at that, or drag the one instance before the drum rack entirely. Then I can just control which pad is in focus on the microtonic with the drum pads on the Push. The settings will then apply to whichever pad is highlighted in microtonic. Sure this tosses out the preset slots used the device, unless I use one column for a specific pad, for example. And there might be some nuisance in maintaining the blue hand on MicroTonicMaxed in device view while tapping different pads. But worth pursuing...
• mothergarage · March 29 2017
  yeah, that works for sounddesign. but what when a clip is playing and you want to change parameters to record them or manipulate them in a live set?