The global variable g0 controls the on/off state of the FX and not it’s value.
There are 6 on/off switches controlled by individual bits of the global variable g0 but not their values.
If you want to also control their values and retain them after turning the switch off and then back on again, you will need to capture and save each value in separate global variables. Then when turning a switch on again you need to send the stored value of the FX back to the DAWs. I was assuming that the DAWs were structured the same way like a light switch with a dimmer.
You turn off the switch but the dimmer value remains so that when you turn it back on again, it knows which value you wants.
If you DAW’s do not behave this way then you are essentially using a dimmer and a switch together where turn off the effect sets the value to 0 and turning on the effect sets the value to 1.
So in essence, every time you set a bit to 1 again and if the DAW doesn’t remember the value, you must remind it where it was when you turn it back on by.
1- Capturing the on value when you turn the switch off (in a global variable)
2- Send the value back to the DAW when you turn the switch back on.
Does this make sense?
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Hi
The translators in presets 1 and 2 just manipulate certain bits of the global variable g0 which being global is visible to all translators. They do not send any MIDI values
Presets 3 and 4 have a single translator each with an outgoing action of perform ‘ClearAllFX’. Preset 3 takes its incoming trigger from the K2 and preset 4 takes its incoming trigger from the Push. There are rules in there to call Perform ‘AbletonClearFX’ and Perform ‘TraktorClearFX’ which are translators 5.1 and 5.2. Each of those translators send the note-on message to Ableton Live and Traktor respectively by defining the target location of the proper DAW in each translator’s outgoing action.
The key to Perform within rule can be found in this tutorial.
Device Selection for incoming triggers and outgoing actions can be found in this tutorial.
As far as bit manipulation, you can look at this posting.
The Bome MIDI Translator Pro documentation discusses the fundamentals but indeed does not provide programming examples. This is where I (and other users) contribute to the forum and posted the example that I provided you.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz