Thank you! A lot of that does help but, I guess I’m getting lost at: “Since in the above example ga was the last calculated absolute value of the encoder, and in my example rr was negative 1, it would be a subtraction operation.” Maybe this is super basic, but what example? where is ga defined as the last calculated absolute value of the encoder?
Oh, I was reading back through your other comments and I think I get it now. Its because we are converting a relative encoder to an absolute encoder. So the last known value is just where ever the knob was last?
ga is the global variable that holds the last calculated value of the output.
Every time you move the knob then incoming value if positive will be 1-64 and if negative will be 127-65 which is really -1 to -64.
What we do is look at the new value coming in and then with the rules, calculate the new value of ga.
If the incoming value is 1-64 then we add that value to ga to get the new value of ga.
if the incoming value is 127 to 65 then we will subtract 1 to 64 from the value of ga to get the new value of ga. We do the intermediate calculations for negative values to adjust what we need to subtract. So for instance, if the incoming value is 127, first we subtract that from 127 to get a value of 1, but since it is negative, we multiply by -1 which makes the new value -1. Then we add that to the last known value of ga to make the new ga one less than the last value of ga.
Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz
Hi Steve!
These explanations are really fantastic! I really appreciate all the help.
I have another parameter that I was trying to map from the same controller to the same software. This controller is also on my Push 1 and it is a Knob controller, except this one is notched, so every time you turn it, it clicks into multiple grooves as you turn the knob.
I tried to map this controller to my subcycle parameter and noticed that it was going from 0 to 128 with every click similar to what was happening with the other controllers. I imagined that this is a relative encoder as well and so I tried to use bome to convert the controller with the rules you gave me for other controllers.
I copied all the rules and changed the output variable to gc. It almost worked, except now it will only set my subcycles to odd numbers as I move the knob. it goes from 1 to 3 to 5, ext… but I don’t get any of the even numbers unless I go all the way up to 128 and then come back down. Then it will still go every two but even numbers on the way down if I go I the way up to 128.
Thanks again for any help you may be able to provide.
Best
Rick Brenner
Hi Rick,
Can you post your project file and maybe shot me the log when you move the knob?
Steve
Hi Steve,
My current project file is attached and I attached a screen shot of the log after moving the knob a few clicks
Thanks again
Rick
Attachments:
1567896925782_08-28-2019_Ableton-Mobius-Actition-and-launch-pad.bmtp
](https://www.bome.com/wp-content/uploads/cma_attachments/1567897062479_Screen-Shot-2019-09-07-at-6.56.06-PM.png){kind=link}
Please check MIDI IN Also and repost the screen shot. It appears that one of your MIDI paths is passing through note messages as well. We need to figure where they are coming from and perhaps stop them. I sense the note messages may be interfering with the controller messages.
At first glance it doesn’t look like your encoder is sending out relative numbers so once we fix the extraneous notes message, we might not need a relative to absolute translator for this one.
Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz
I selected midi in and attached a new screen shot. The controller does send midi notes with the touch and release of each knob.
Thanks,
Rick
It doesn’t look like the new screen shot was there so I’m sending it again. Sorry if you are getting it twice. the Ableton Push 1, is the controller I am using and it does send a note on/off message when you touch or release any of the knobs on the controller, so just touching the knob to turn it does generate a note on message as well as the CC messages.
Adding the rules definitely helped cause with out that each click/turn CW of the knob would go full to 128 or one click/turn CCW of the knob would go all the way to 0. Adding the rules made it much better and now as I turn it CW every click/turn only moves my subcycle parameter by 2 instead of all the way from one end to the other.
Attachments:
](https://www.bome.com/wp-content/uploads/cma_attachments/1567907278724_Screen-Shot-2019-09-07-at-9.34.54-PM.png){kind=link}
OK, try this.
I added a translator to suppress the touch Note from your controller. Otherwise the MIDI through path will let the message through and I suspect this is what is messing things up.
I disabled the translator for the CC since you already have a MIDI through path set from Actition 2 MIDI 5 out to Bome MIDI Translator Virtual 1
Attachments:
1567912114806_Ableton-Mobius-Actition-and-launch-pad-sjc.bmtp
Thanks for looking into this. I really appreciate it, but the new translator didn’t seem to change anything. Disabling the translator for the CC makes it so I can only set the parameter to 0 or 128. At least with the translator it just jumps by two. I also tried to supress touch from “Push to Midi 3” from the same note cause that is actually the controller I am touching. Not sure why Bome is recieving Midi in from “Actition to Midi 5” because I’m not even touching that device.
I think a bunch of my issues may stem from the fact that I am using an app called Midi Pipe that is routing my Push from Midi channel 1 to Chan 3 and my Actition foot controller from Midi Channel 1 to Ch 5. I had issues because both controllers are set to channel 1 and can’t be altered. I had started using Midi pipe before I purchased Bome. When I started setting up Bome I just started using it on top of Midi Pipe because a bunch of other stuff in my system was already set up. Now that I think I understand more about Bome, I should probably re-do my Bome Project without midi Pipe. I’m going to try and do that soon and see if I can figure out the best way to set things up. Before I start, can you recommend the best way to translate every message from a controller from one midi channel to another? Or do you have to do it per message with bome?
Thanks again!!!
Hi, yes, I generally organize my project inputs and outputs by preset. For instance at the project level, I can define all inputs and outputs. Then if you organize by preset, you go just define the inputs and outputs for that preset that you want and MT Pro will ignore anything else (unless you have a MIDI thru path set).
We have a tutorial on this:
If all you want to do is translate all MIDI messages coming in from one channel to another, then we have a tutorial on that too:
For me, I like to not define MIDI thru paths and do everything in translators instead (unless I’m in a hurry). This is a personal preference for me as often when I define a thru path eventually an unintended MIDI message gets through that I didn’t want and mucks up the works. I then have to go through like I did on your project and put a translator in (setting swallow) to suppress the unwanted message from getting through. So in summary I define all possible inputs and outputs at the project level. Then For each preset I override with the inputs and outputs I want for that preset to override the project defaults. Then on an exception basis, I can override both project and preset inputs and outputs at the translator level (usually when there is only one translator that doesn’t warrant creating a whole new preset just for one translator).
Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz
Oh and from your incoming log, it doesn’t look like it is jumping from 0 to 128. In fact MIDI can only go to 127 unless you are using a 14 bit NRPN or pitch bend in which cases, the value is split across 2 7 bit bytes. Maybe if you post a log of just incoming message and sweep the knob from far left to far right slowly, I can tell you more about its behavior.
As far as I could tell it was going up and/or down but some controllers if you move the knobs quickly will skip sending some MIDI messages to reduce traffic.
For instance on one of my controllers (Nektar LX25+) if I move left to right fast, it may skip up to 10 outputs but moving slowly it will send every messages. When you stop moving though, it always sends the latest value. Again I think some manufactures do this to simply reduce the MIDI traffic their controllers send.
Hi Steve,
Hope you are well. Sorry to bother you again with more questions but i have somehow broken my setup and I’m not sure if it has something to do with Bome or not.
In the thread above you helped me get my expression controller and my ableton push controller to control the same CC. You helped me by creating rules for the push controller that you told me was “a relative encoder and puts out -127 (7FH) when moving to the left and 1 when turning to the right”
In preset 6, Line 1 and Line 2 are outputing the same CC. Line 1 is from the push controller and line 2 is from an Actition foot controller. They are both controlling the output level of Mobius VST looper inside of Ableton. Ableton is midi mapped to Chan 5 CC 70. This works as it should. I can control the level from my push controller or my expression pedal connected to the foot controller.
Also in Preset 6 Lines 3 and 4 are supposed to be the same way so that I can control Chan 5 CC 71 from the push or the expression pedal. The push controller is working correctly and controls Chan 5 CC 71 as expected. The expression pedal that is connected to foot controller and is converted in line 3 to also control Chan 5 CC 71 does not work anymore.
Wondering if you would be willing to take a look at my uploaded config and see if you notice and issue that would cause this not to work anymore?
Thanks!
Hi Steve,
Sorry to bother you again. Should have researched this more before emailing you. Based on my midi log I believe I’m having an issue with midi foot controller.
Please disregard the previous message.
Best
Rick
OK, let me know if you need any help.
Steve
Thanks Steve! You actually did help me. I imagined you would ask me to look at the log of the input from my expression pedal. It looked odd in the Bome log so I quit all my midi apps and just looked at the input stream from a Midi Monitor program. That led me to discover that the expression input of the foot controller itself does not seem to be holding its calibration to any expression pedal. I emailed the manufacture hopefully they get back to me with some suggestions.
Is it a new expression pedal? Does it send MIDI or do you have it connected to something that translates to MIDI? Not all expression pedals are created equal so perhaps it is incompatible some have the wiring reversed and some use a different size potentiometer.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Thanks Steve! I was using two separate Expression controllers before. Now I am using only one Expression pedal with this mission engineering expressionator As it turned out, I was missing a part of the setup instructions for my Actition midi foot controller where I am attaching the expressionator. After I got the full setup instructions from the manufacture and got the input calibrated for the epxressionator everything was working as expected again. Thanks for the help!
Best,
Rick
Glad to here you got it working!
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz