Has anyone come across or know of any tutorials on setting up the Intech (En16 + others) midi controllers with the Octatrack MKII? I’ve been looking through the Elektronauts forum and quite a few mentions about the controllers but no tutorials here or on Youtube.
I’m also going through the Intech guides. The software is a little more challenging to use since it’s so customizable (not a bad thing) but just unsure of how to get this mapping to work. since the fields are very custom.
It’s pretty straight forward once you look through some of the Grid documentation:
I’ve done custom stuff for Digitone and Loopy Pro. I have 2x EF44, and EN16 and a PO16. I can post some code and instructions if you have an idea of what you’re looking to do.
It’s getting late here though and I’m super bagged from spin. Car’s in the shop tomorrow so I’m working from home. Give me an idea about what you’re looking for and I’ll see if I have time to script something up.
Even a screenshot of your setup in the grid editor and a simple explanation of what it’s doing. I can then reference the Digitone manual’s midi setup table to understand what you’re doing.
In the Octatrack I know each track is a channel. I’m having trouble where to place the Channel Number, CC value (from the manual table) and so on. I’m a little confused by the fields “Channel” “Command” “Parameter 1” and “Parameter 2” and what to put in for the values and which ones to leave as 0, null or something similar.
‘Channel’ is the MIDI channel. They go from 0 to 15 instead of 1 to 16.
‘Command’ is a numeric value that sets the type of message being sent. If you use the editor, select the drop down to set the type. CC is the most common (176 is the value I think?)
‘Parameter 1’ is the CC number if sending CC. Note number is sending note etc.
‘Parameter 2’ is the value you want to send.
You should see some variables declared at the top. Something like ‘val’ = encoder_value(). When you set parameter 2 to that variable, it basically sends the value of that encoder as the CC value. I can give examples tomorrow with the proper code and screen snips. I can also break down what each of the tabs does in the editor amongst other things.
Where is ‘val’ defined? It should either be in the ‘Locals’ section of the ‘Encoder’ tab or on the ‘Init’ tab. Click on ‘Locals’ to expand it and attach the screen snip here.
I’m just updating my Grid Editor then I can post an example.
This is just a quick example of an encorer setup. You can see 4 local variables defined at the top and one MIDI block that’s referencing 3 of those variables (The variable ‘num’ is assigned the value of self:element_index() which is the physical position of the encoder. This is used for the LED).
The ‘MIDI’ block breaks down as follows:
‘ch’ is set to ‘0’ (which is MIDI channel 1. Grid uses 0 - 15 for MIDI channels).
‘176’ is a numeric code for ‘CC’. This sets the data type to be sent.
‘cc’ is set to ‘20’. This is the ‘MIX’ parameter for the A and B operators on the Digitone.
‘val’ is set from 'self:encoder_value(). This is the current encoder value. It changes as you move the encoder.
So, every time there’s an encoder event, the MIDI block executes. This is all pretty straightforward. But, it can do a lot more than just send CC. You can get pretty sophisticated with things.
I learned pretty quickly that I prefer to just erase all of the ‘easy mode’ action blocks and just put one big ‘Code <>’ block in and script in straight LUA. I have no coding/scripting background apart from some super basic noodling over the years. But, once you take those action blocks and convert them to code, you can pretty easily see how it all pieces together.