…I can finally switch over to Traktor Pro now that the mix comp is over. I started working on my keyboard layout last night. I wish NI had added modifiers to the Keyboard settings. I guess I’ll continue to my secret Bomes Midi Translator Pro weapon.
Good news though. I’m not going to keep it a secret any longer. Once I get the Traktor Pro version done, I’ve decided to share the work with you guys. I’ve implemented my Bome’s Translator Pro rules to do essentially the same thing for my keyboard. It’s fantastic for loading, cuing, looping, moving all four decks. I’ve also been able to make it so you can operate on 2 decks simultaneously… like start/stop, loop in/out, etc. Right now I can’t do that for 3 or 4 decks due to limitations in Bomes but I’m still working on a workaround.
Anyhow, I’m kinda posting this to motivate myself to due a tutorial. You know… once you say you’ll do something you actually have to.
and, b33son, very well done, in all regards. i just spent about 30 minutes rewinding and re-watching to try and figure everything out. it was very complex and came out sounding clean. i just wish u were mixing internally so i could see on the screen caps what, exactly, was going on..
nice tunes, and creative editing - audio and video. good luck!
I saw your question on the Bomes board when i was doing a little research into recording loops in Ableton Live(my latest project in the works). You know you could have just asked me
So anyway to answer that question you put on the Bomes board you can set a global variable when a button goes down, then change it back to its original value when the button goes up. With that you can check to see if the button is depressed inside of the rules of other translations by just checking the global variable.
can’t wait to see what you’ve come up with. I like the fact your sharing your tricks too, always good to share and see how other people can push your ideas.
Yeah that’s what I have now. Basically, I think Bome stops processing rules when have more than two keys held down.
Here’s the scenario:
Create 4 rules: SetA, SetB, SetC, SetD and assign to the keydown of separate keys and have each set a global variable to “1”. For example, press the key for SetA then ga=1, SetB then gb=1, SetC then gc=1, SetD then gd=1.
You can also add 4 more rules to set the global variables back to “0” on key up.
Now, if you open the Log Window, you’ll see that after holding down the first 2 keys, if you attempt to hold down the third key, nothing happens. The other rules are not processed and the additional global variables are not set until you let up the first two keys.
This is probably kinda hard to follow, so let me know if you have questions.
)