Wow, great! I was checking cloud profiles but there was only few EN16 profiles and nothing useful for me. Your profile seems to be what I need to start, I’ll check it - thanks!
BTW: This could be updated with global midi channel change and “somehow” extend every profile with option to change 1-12 midi channels (12 push buttons).
I checked this profile and it actually works - there are four virtual settings within one page 
I only saw that such a setup can be uploaded in each of the four directions, which basically theoretically suits my needs:)
…but there is a “but” and I don’t know if it can be overcome. I wanted to program my own CH/CC for each encoder of the four virtual pages, but either I misunderstand something or it’s not possible.
Changing the settings of the first encoder after setting the channel and CC to are hardcoded propagates to all four virtual sides. Or maybe I’m doing something wrong? Is it possible to set my own CH/CC for every 64 encoders?
I made the Profile so that you could hand-craft the CCs and MIDI channels you need, but the idea of the setup was for a singular module.
Setting the individual CCs should happen under System Init with each bank having 8 ccs.
Setting the ch per bank happens similarly.
Change a,b,c,d values for switching out the CCs per bank of a,b,c,d.
Change chbanks values for switching out the MIDI Channel for each bank.
Hope this helps explain it!
Thank you very much!
I have one more question. I would specify two parameters per every 64 knob. Since I work with few instruments, I would be able to set CC and CH for every page. So for example
but:
Just an example.
I use this system on Faderfox and it’s central controller for all gears, but I would change it to two, connected EN16 controllers. So with 8x4 encoders (by 4 pages), I would control 8 gears (4 parameters on PAGE1, and another on PAGE2,3,4).
Is it possible to do that?
You would have to customize the CHs the same way as CCs are customized and shove them into a table.
The CH table should look like this when called: chbanks[bank_number][self:element_index()]. In the current iteration this is done by just calling chbanks[mem[1]] which is always the bank number, but of course this is why it’s limited to one CH per bank.
Tbh this is very much doable, but we’re quite character constrained on the system init already, so some trickery would have to be done for it to fit in there like initing the CHs on the timer event.
If you’re not feeling up for this task let me know, I could update the profile early next week!
I would be very grateful! Unfortunately, I don’t understand programming Intech code yet. I used to program a bit and I understand more about what it’s about, but it’s hard for me to do these modifications myself.
And - is possible - some more questions / wishes:
If I could use it in controllers, it would be a mega step forward for me! I really liked the capabilities of these devices, but I was a bit overwhelmed by the programming issues.
THANK YOU!
Just updated to profile to V2!
V2 Features:
colfeed to 1 to turn it on)!Visual aid for setting up 64CTRL V2:
I admit this is quite a complex configuration, but I hope the final product is worth it.
P.S.: for now, this config might not fit on older EN16 modules, I’ll try and fix that…
Thank you! Yes, I have older and newer EN16 and there was problem with uploading profile. After few times, it did work. I didn’t change configuration yet, but thank you for update! I’ll start testing it 
One more thing as well, for now you’ll have to use the nightly firmware version for the global bank switching to work because it uses immediate_send() (explained here).
Nightly firmware has been patched and now older D51-based modules should be able to switch banks as well.
Great work on this. Would there be a way of storing the parameter value as well as the midi channel and cc number at all?
Thank you!
What do you mean by storing parameter value? Like making a snapshot of current controller states?
Yes, exactly that. 
I made a version of the 64CTRL profile that swaps around the same 16 mappings and makes it act as a snapshot machine.
The problem with it is, that if your turn off the controller, the “saved” snapshots are gone, because they are stored in volatile memory and will disappear on a reboot.
Even then, I would advise you to try the profile called “64CTRL, but it’s a snapshot machine”!
Ok, thanks very much, will have a look.
Cheers!
So I’m not sure how you set the midi channels in this one or the parameter values. I must study harder.
Howdy. I am learning the Grid Editor, but it is a challenge. Right now I am trying to set my EN16 up with Control Surface Studio. I would like to use the profile that is being discussed here, since it suits me. However, I cant seem to get relative encoders to work when I load this profile. I have tried to insert an encoder mode element in the setup and in the encoder slot. When doing this in the “demo” profile, it works fine, but not in this profile. Any assistance would be nice.
Hi there,
So the point of profiles and pre-made configurations is that they have everything the developer put in there for you to use possibly extending the features of the base configuration in ways not normally possible for the average user.
It also has a big downside because of this, they are very hard to customize for the everyday user.
In this case however I could easily create a relative mode version of the 64CTRL or a setting in the profile itself to let you easily switch between the two versions.
Would this be something that you guys would be interested in?
I’m not sure what is happen, but I used 64CTRL 2.2 and in midi monitor it was ok. Then I have changed CH to 9 for all encoders - and it’s fine. Then I have updated the code for encoders CCs in config 1, but EN3 (cc 38 in configuration in code) had problem - instead of CC it sent strange values (last column - according to midi monitor). When I changed CC number to other random values - it works as expected.
And it was happen to second EN16 too, the same CH9, for EN3 (cc 98) - but this time it sent NPRN messages (according to midi monitor). I did not check if it sent correct values to the devices, only midi monitor was used.
PS. I have checked it with other MIDI monitor - i think this problem comes from grid midi monitor.
And one more strange thing - CCs in code are the same in external midi monitor, but channel numbers are wrong - in CH configuration (in times) is 9, internal midi monitor shows 9, but external shows 10.
Sadly MIDI monitor is bugged!
A known issue you can check here, it should be fixed in 1.3.9!
I also made the switch to enable relative encoders @user132 , but in my testing it defeats the purpose of the controller as the displayed values and the LEDs on the EN16 will not be able to stay in sync like this.
If you would still like to test drive the profile, let me know!
