So, I had a sit down with Joe from the Bome’s team a few weeks ago, and more recently with Bento and my problem can’t seem to be solved.
I have completely mapped my VCI-100, including the reset commands and all, in Bome’s. I have it broken up into sections. The always on includes the Master, Booth and preview controls, the master effects and the crossfader. I have each half of the VCI broken down, so I have Deck A and Deck B mapped in their own presets, including effect controls, and the looping sections. I then copied Deck A and Deck B and created Deck C and Deck D respectively, except all controls are set to send on channel 2 instead of channel 1.
This is where things get really weird. I built the tks from scratch (that was fun) in Traktor for Decks A - D. I have the top white button and the bottom white button of the looping section set to switch presets from A to C and B to D respectively. When I checked the message monitor thing (that shows what commands are being sent, can’t remember what it’s called) it shows all messages being sent, instead of one or the other, as is MIDI-Ox.
In Traktor, though, it’s even weirder. I double checked all the channel assignments, A and B on ch1, C and D on ch2. When I hit play for A, though, nothing happens. When I hit play for C then both A and C play. The deck assignments (volume, gain, effects) are moving properly, though. It’s just the transport commands (Play, Cue/Play, Cue/Pause). I don’t have MIDI-Thru on in Bomes.
Any idea what I can do?
Also, is there some sort of MIDI to Hex guide so I can learn how this stuff works? It kinda goes over my head right now
The hex is pretty easy Bomes has a built in Hex → Dec calculator
its layed out like
XX YY VV
XX = Channel Number
YY = Controller Number
VV = Velocity Value
sooo
90 5D 7F
90(HEX) = 144(DEC) = Channel Number - in this case channel 1
5D(HEX) = 93(DEC) = Controller Number - in this case the note is A6
7F(HEX) = 127(DEC) = Velocity Value - how hard the note was pressed.
XX = Channel Number
YY = Controller Number
VV = Velocity Value
[/quote]
In your example, you’re KIND of right. But it’s a little different than what you’ve outlined.
The MIDI information as presented in BMT, MIDIOX, etc is in HEX and is in the form of 3 groups of 2 digits (except in the case of things like SYSEX, but I’ll leave that alone for now). But the first pair together doesn’t only designate the MIDI channel, but also the TYPE of data. Specifically, the first digit in that pair tells you what kind of data is it, and the second digit gives you the MIDI channel. So if the first pair is BA, then you know that it is controller data on channel 10. The second pair gives you data based on what kind of message it is. In the case of a note on or off, it would be the note number, and the third byte is velocity. But if the first byte tells you it’s controller data, the second byte is giving you the controller sending the message, and the third byte gives you the value of that controller.
I actually wrote that right before heading out the door to work trying to keep it simple, but thanks for the extended version i am sure people will find that helpful.
)
)