Cool, so it is possible without messing up "the rest of" Axoloti
I dont really worry about that. If they like to use it, they could just do the same? What I really like about Axoloti is that it is customizable in almost any possible way. And i Like to take advantage of that And thanks for that btw
Ive made a bunch og custom ctrl/i objects like 0-15, 1-16. 1-64, etc..... And adjust value to what I need, cause I prefer that you can not drive the ctrl/i beyond the maximum value needed. For example if you use the ctrl/i to select position of a sequencer with 64 steps. Then you dont want the ctrl/i to go beyond 64 steps, cause everything beyond is not used. There are many situations were this could be applied to(And that is also one of the reasons I also mentioned that a "dynamic version" of the ctrl/i would be nice, where you can set minimum and maximum value, maybe from axolotis own editor or something like that).
A little more explaining about this: This version doesnt have to go to rangeless. It just needs to stay within 128 steps... 0-127 .. with in midi range, That is perfect. and if you change the minimum value to 60, the midi cc value would probably still be 60. I am pretty sure if the ctrl/i CC object(i call it for reference) is set to send out 0-127 value it will still send out the correct values by defalut, even though you change minimum and maximum value. Like for example set minimum to 30 and max to 60 then it would probably also send out those midi values. But that is not so impotant, you can always adjust the output with math to give the values you need. The most important part is that it is midi cc assignable, so you can see the exact values when edited from external device or modulated from internal mod source.
That is stays within 0-127(probably easier to make cc compatible)
setting minimum and maximum can be done externally so I dont worry about that. DOesnt have to done inside, but would off course be welcome.
Another example of why I think the ctrl/i is a better choice than the dial.
Accurate display of value:
I am using a homemade step lfo made from sel/sel i to trigger some drumloops.. Basically for slicing them. And to choose which exact step of the step lfo that is selected I use the ctrl/i. If you use a ctrl/dial you would have to guess from what position the dial exactly has. You can not see the exact value, like with the ctrl/i where you see it visually. For example 64 steps covers 16th notes over a range of 4 bars. If I want the loop to start from step 16(2. bar of the loop) and not 1(1.bar of the loop) it is way easier to set the value with ctrl/i in a live situation than doing it with a ctrl/dial. You can always see the exact value.
I also use the ctrl/i instead of the radio obejct.. cause the radio object are very big. /again here the "dynamic" version would be very nice.. still within 0-127).
Come to think of it.. A ctrl/dial, but with a different visual than a dial could do just fine. Maybe it is easier to make a version of the dial with a diffrent interface that shows values instead of a knob? THen it willl stay with in 0-127 no matter what