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.
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!