Has anyone managed to connect an Empress Zoia to grid modules to control Zoia parameters through MIDI CC? I am guessing that in addition to one or more Grid modules (which I already have), I would need a Knot module, and then I would be good to go? Or do I also need cabling that is not packaged with the Knot in order to have the right size inputs to connect the Zoia to Knot? Thank you for any pointers!
The Zoia has the same TRS MIDI connector as the Knot, so you only need a stereo (TRS) jack cable to connect it.
OK, thank you Greg-Orca!
Having received my knot, I can confirm that my Grid modules work very well with the Zoia Empress. Given that the Zoia is a full modular synth in a tiny (14 cm by 9 cm) box, and the Grids are small as well, one can have a full modular setup within a very small footprint and weighing almost nothing. Further, with Grids connected via the knot, one has a dedicated knob for every parameter in the modular setup. So full control of a modular synth in a tiny space…amazing!
Happy to hear that, sounds like a nice compact and powerful setup!
It is, this is as close to my ideal setup as I have ever been!
1 Like
Hello. I’m a new Zoia owner and a new ES16 owner. I was hoping to garner any insightful tips on the best approach to mapping the controller to the Zoia for ease of use and control. I’m most focused on using the ES16 as an on-the-fly in-performance setting adjuster in a guitar/synth pedal board chain, rather than as a deep-dive programming module, but I would be grateful for any tips, considerations or examples that people are able to share on either of those use models. Many thanks for your time.
I am going to guess that you have an EN16 rather than an ES16? I have been using a Zoia for the past few months with an EN16 (and when I need more control, also attach a PO16 and a PBF4). It is a great combination for exactly what you want, a guitar and synth board with MIDI CC control. I will not claim that what I am doing is optimal in any way and perhaps much of what I am saying it completely obvious, but will outline how I am using my grid modules with the Zoia in case it provides any ideas you can use.
First, I suggest bring super-organized within each Zoia patch, and aim for consistency between patches whenever necessary. So, for example, if you have an EN16, you might set it up to send up to 16 MIDI CC messages to 16 different parameters on your Zoia patch (really 48 since the EN can have two layers of 16 plus 16 push buttons, but for simplicity I am just considering the first later encoders). So you can organize them in a 4 by 4 layout, and track which CC’s are mapped to which encoders, something like:
EN16 Layer1
32 33 34 35
36 37 38 39
40 41 42 43
44 45 46 47
Then in your Zoia patch, you can map each of these encoders to control a Zoia module parameter. I like to organize things in rows or columns, one Zoia module per column or row. So if I have a Zoia patch that has, say, a delay and a reverb, then I might use the first row for the delay parameters, and the second for reverb.
So I might choose the 32 33 34 35 CC numbers to control delay time, delay feedback, delay mod rate and delay mod depth, and use the second row, the 36 37 38 39 CC numbers to control the reverb parameters, such as reverb time, feedback, mix and resonance. And so on through out whatever you want to control in your Zoia patch.
To connect the EN16 to your Zoia you will probably need a Knot module. Once you have the Zoia connected to the EN16, you can program the Zoia to receive the EN16 cc messages. For example, connect a “value” module to your delay time button on the Zoia, and then use a “MIDI cc out” module to connect to the “value” and make sure you have the “MIDI cc out” module transmitting on CC 32. If this is all set up correctly, then turning the top left EN16 encoder should change the delay time in Zoia. And so on for all other things you want to control in your Zoia patch.
I hope that helps a bit, and I would love to see what patches you end up with!
In the above, “MIDI cc out” should have been “MIDI cc in” … sorry for any confusion this may have caused!