Yes you can do that to, just remember the incoming timers on any presets that are not activated, will not do anything
Yes, that is a relative encoder . Here is a tutorial on how they work and perhaps how to convert to absolute.
And to convert to a keystroke.
Steve Caldwell
Bome Customer Care
Sorry I should have known that by now. It was years ago when I first did relative to absolute.
Iām kind of hitchhiking right now. Faster than walking tho.
I set it up like this:
Thatās pretty standard. Got it working, but itās really jittery. Probably because the device requires touch sensitivity to allow the knob torque to actually send anything. Itās really bad design.
Anyway, I changed my mind and would prefer it to be the same as it is in the vanilla factory mode.
In that mode the knob simply tells the software knob āforward or backā so I donāt have to wait for FLSās pick up mode. It moves the knob wherever it is, and also doesnāt snap the value.
Can I get it to send -1 +1 absolute values? So that would make it absolute to absolute, but converting 1/127 to -1 +1. Donāt know if Iāve ever come across this puzzle beforeā¦ ĀÆ_(ć)_/ĀÆ
Forgot to say, I tried using two translators. Down translator triggers at value 1 and rules is pp=pp-1. Output value is pp. Up triggers at value 127 and pp=pp+1. Output is pp.
This doesnāt work at all. I get the output value of 2332423432432 or something.
FLS has an āincrementā knob type. But doesnāt matter if the knob sends 1 or 127, it still increments up. The inverted increment formula does reverse it.
Ok so I made two translators. One triggers at 127 and sends 127 on cc 60. Default formula.
The other triggers at 1 and sends 127 on cc 60. Inverted formula.
Itās a bit jittery at times, but seems to be working.
The FLS velocity envelope actually helps a little with the problem of having to hit the pads too hard.
Have it set to this on the MTP 1 port that my drum notes come in on.
So the higher values are triggered a little easier. The softest hits are brought up a little bit. The pads canāt send a velocity less than 32. Thatās not too bad though. You can see in the pic the vertical line is hitting at the softest (32). I brought it up a touch and the med hits are louder because they are hard to hit.
I got the full on velocity figured too. And I added a 100 velocity to it.
So I used this formula on a dedicated button, that lights up when the flag is on:
Put another button with pf=pf^1 for my 100 velocity toggle.
So every padās note-on translator has this rule:
If both toggles are off, the velocity is free to flow from input to output. If one of them is on, it sends at exactly that value. Each one cancels the other one out when hitting the button, and cancels their light on the controller. Done. Now onto transposing.
The forum is giving me crap for posting too much. 
Iāll be out of your hair soon enough. Just real excited about this.
These new discoveries are turning my frown 
upside down 
Hi, youāve posted a lot but Iām having trouble figuring out the questions.
Are you looking to limit the velocity of the pads to something less than 127 when pushed?
For relative encoders. What output do you want to send when
Steve Caldwell
Bome Customer Care
The knobs work now. I posted above how I got it. Basically FLS can convert the incremental message for me but it only goes in one direction. So I did two translators per knob, with one being inverted.
Getting there, Iām about 3/4 done this controller. Last one.
Since the pads are brighter when a pad button is pressed, Iām trying to see if I can get FLS to send the MIDI note data back to MTP (that is pre-recorded to the FLS piano roll grid) and then send it to the controller, so during playback, the controller will be animated by the MIDI score in FLS. Is this possible? I tried all the routing possibilities I could think of. FLSās output has a āsend master syncā button, but Iām pretty sure thatās just for the clock.
I believe you have to route the outgoing MIDI Track back to your AkaiPro Fire (or through MT Pro back to Fire if you want to modify the return velocity).
Steve Caldwell
Bome Customer Care
I was renaming things fast and hit some kind of key combo that made it look like this when renaming a translator:
I went through all the windows 10 options and tried pushing a bunch of things, but I canāt tell what happened here.
Try going into the field. and typing control-A (Select All) and then hit the delete key.
Then you should be able to assign it another name.
Steve Caldwell
Bome Customer Care
Ya that didnāt work. I donāt know, itās some kind of alternate typing input thing. Itās stuck like that. You can see itās different than the regular rename way.
Anyway, I got it all figured. Each padās output is remapped how I like and has its own dedicated global variable as its velocity. Have two buttons on the side that toggle-lock the velocity on all pads to either 100, 127 or off. When both are off, the pads are velocity sensitive going out to FLS.
To get velocity sensitivity light feedback I used this formula on each pad light input.
Each pad light translator needed the corresponding global variable to work.
The light offās are note off any velocity, no rules, same input.
So now if the velocity is 100, they blink orange. If 127 they blink red. Otherwise they blink white.
Got the playback light feedback too. FLS has a plugin called MIDI Out and sends MIDI data out from FLS. It wasnāt working for me before because I forgot about the octave difference between FLS and MTP. This is before I found the option in the settings.
These playback lights also had some bad latency on the note off. So I changed the note off inputs to note on and gave them a 100 ms delay. It works because itās just telling the light to go back as it was before. The nice thing is these also respect the velocity. So it will blink the lights at whatever velocity the notes are on the piano roll, according to the same rules.
The problem is MIDI Out canāt be linked to a plugin for its input. You have to copy over the MIDI score from the plugin pattern to MIDI Outās own pattern. I made a macro for that, but itās still super annoying.
Iāll make a quick vid showing it, but when I lost everything on my comp, my video editor went too. I canāt get that version back, so Iām trying davinci resolve, but that has a ridiculous learning curve.
Could you tell the forum to stop giving me crap for using it.
You have ue for input variables for the second set of rules, but I donāt see the input to see if you are looking at the right variables.
I suggest before using FL Studio to control LEDās you first do local feedback from MT Pro to make sure you understand the values that control the LEDās. It sounds like some values might be blinking. I canāt test because I donāt have your controller. If you donāt want the nag messages, perhaps start a new thread with the specifically the issue you are trying to solve, this thread seems to be meandering between different topics. I donāt think I can turn the nag screens off. You might want to try VideoPad Video Editor from NCH Software. Davinci Resolve does indeed require a significant learning curve.
I also think the simple Editor from Icecream software is free but with quite limited editing capabilities.
Steve Caldwell
Bome Customer Care
Maybe any value greater than 9 is blinking for that color.
Steve
The weird text thing corrected itself after closing and reopening MTP.
The translator that wasnāt firing with a timer had the āstop processingā checkmark enabled. I was experimenting with that while trying to figure out that hold down sequence. Cloned it to reuse some of it but forgot that was checked.
Sorry the ue variable is just a random pic to show the rules. All the variables are lined up. I did have some mistakes but fixed them.
And sorry, I meant by āblinkā it just turns the pad light on and off kind of quickly. The pad lights are set to send a different light when pressed down and return to the presetās colour when released. So when the note triggered is only a step or so long, it looks like a blink. I made the āonā brightness only last 100ms for drums because if not it looks kind of laggy, like itās drunk. For the melodic instruments I have the note off as a normal note off so the lights stay (brighter) however long the note is. Itās working good.
Iām almost done. Doing some more note presets with different scales and colour themes. Itās a lot of work. Thanks for all the tips. 
Hey would you know how to send messages to the oled screen? Itās the same issue I had with the sysex lighting. Reading the Segger blog post I figured out the messages themselves, but not * how to send them. That was the tricky part. The guy that wrote the blog is working with C++ code, not a program like MTP. I see the map he made to show what message goes to what pixel. I tried copying over his example block of sysex messages, but that didnāt do anything. ?
Hi, since the screen is bitmapped, it would likely be very difficult with MT Pro. You would probably need some sort of helper program to translate ASCII characters to the bitmap. Very involved and probably not worth the effort. If there is a way to send ASCII characters to the OLED, it would be much easier.
Steve Caldwell
Bome Customer Care
Ok. That saves me a bunch of time doing experiments that wonāt work anyway. Thank you.
I noticed when changing presets, the MIDI ports toggle the phrase (implicit) on or off. Donāt know what that means; itās not explained in the manual. MTP doesnāt open and close ports based on if presets are active, does it?
If you check them at the project level, then all ports should always remain open. If you only check them at the preset level, I believe they open and close depending on whether the preset is active. Consequently you should always define the ports you want input to and output to at the preset level or translator level to override the project level if you want all of your ports always open.
Steve Caldwell
Bome Customer Care
Ok thank you. Iāll have another look at them. I assume (implicit) doesnāt really mean it was changed. ?
Just a shot in the dark here, since Iāve been at this new issue for four hours now with zero progress:
Would you happen to know why FL Studioās MIDI Out plugin is reading 100 velocities off the piano roll, but sending 120 velocities out?
My velocity lock is supposed to make pads orange when hit but this implacable problem is making them all white when they clearly should be orange. There is no reason for it to not send out 100 when it is reading 100. After four hours Iāve checked every thing imaginable, and am just giving up.
