sysex: local off

timbuque · Post by **timbuque** » Sat Feb 03, 2007 4:44 pm

Does anyone know how to send "local off" by sysex? for a Korg M1.

Shooshie · Post by **Shooshie** » Sat Feb 03, 2007 5:51 pm

Will it send out the message if you choose it in the setup menu of the korg? If so, insert a SysEx event into your track, which will open the editor. Send the message and see if it receives it.

That's all I can tell you. Otherwise, you'd have to call Korg.

Shooshie

timbuque · Post by **timbuque** » Sat Feb 03, 2007 8:59 pm

No it won't. Tried that. The binary code the M1 will receive is 1011 nnnn 0111 1010 0000 0000 where nnnn is the global channel. In hex it is B1 7A 00 but DP will not accept the B1. Also, local is controller 122 which DP will not accept either, so I'm screwed it seems. But thanks. Ya know, there seemed to be more MIDI functionality in OS9, once-upon-a-time.

Shooshie · Post by **Shooshie** » Sun Feb 04, 2007 3:24 am

timbuque wrote:No it won't. Tried that. The binary code the M1 will receive is 1011 nnnn 0111 1010 0000 0000 where nnnn is the global channel. In hex it is B1 7A 00 but DP will not accept the B1. Also, local is controller 122 which DP will not accept either, so I'm screwed it seems. But thanks. Ya know, there seemed to be more MIDI functionality in OS9, once-upon-a-time.

Ok, first of all your binary and hex are not in agreement. The hex for the binary as you've written it would be, I think:

B (nnnn) 7a 00

Now, I don't know the format it's asking for the global channel. Is it ASCII? Or Hex? If it's ASCII, as is the Controller (122), then to write it in Hex will require that you precede each digit with a 3.

Example: ASCII 122 = Hex 31 32 32

The SysEx message would need to start with F0 and end with F7. I'm just guessing at this, so it's probably not right, but I'd do something like

F0 B (CHANNEL 1) 7A 00 F7

That doesn't explain where the controller number goes. Wherever it goes, if it's in Hex it will be 31 32 32.

And what's the global channel? Is it supposed to go in hex, also? If you're using channel 1 as your global channel, then it would be:

F0 B1 7A 00 F7

Next, if the 00 is supposed to be where the controller number goes, then it would read:

F0 B1 7A 31 32 32 F7

BUT, I tried entering that into the hex editor, and like yours, it wouldn't allow the B1. I changed it to 1B and it allowed that. I don't know what's wrong with this SysEx editor! MOTU needs to be told about this.

Shooshie

monkey man · Post by **monkey man** » Sun Feb 04, 2007 3:28 am

Blackboard and chalk, professor?

timbuque · Post by **timbuque** » Sun Feb 04, 2007 6:58 am

Thanks again. Your conclusions equal mine.

Controller 122 is 7A. Global ch is 1 so, B1 7A 00 seems right. I tried B0 7A 00, but still DP has an issue with "B" it seems. I have also tried a more complete string for the M1 which is F0 42 30 19 4E B1 7A 00 F0 with same result. 4E = mode change. I also tried inserting into the event list controller 122, but again, DP will not accept 122. I tried a console button, but 122 DP will not accept.

Reversing to 0B produced a format error F0 42 30 19 26 F0.

However, I'll have to be happy with just inserting "local off" in the event window. This is not what I wanted to do though.

Shooshie · Post by **Shooshie** » Sun Feb 04, 2007 3:11 pm

I was hoping someone would drop in and show us something we don't already know, which would make it all work. I guess that's not going to happen. I'm still really curious as to why it's not working. That seems like a perfectly valid SysEx code. Why would the editor even care about that B1? Maybe B1 has the potential to collide with the channel actually being used at the moment. So if your Korg was on channel 3, for instance, and that B1 got sent, maybe it could cause some serious backlash of a problem. But my understanding is that everything between F0 and F7 is taken as a "quote," and not acted upon except in the manner prescribed by the recipient machine.

I don't know the answer, that's for sure, but it's going to bother me until someone explains it or I find it. I use SysEx, and I'd like to know if this is a feature or a bug.

Shooshie

PS: you're right about 7A being Hex for 122. I assumed that 7A was announcing that the controller number was to follow, and that the controller would then be in ASCII. I figured that's why the 00 followed, as placeholder for the first ASCII digit. Guess I was wrong. I should have checked the value of 7A first. Duh...

timbuque · Post by **timbuque** » Sun Feb 04, 2007 3:54 pm

What I'm thinking, and this is a stretch, is that MOTU has outlawed 122. 121 and 123 can be inserted as controllers, but not 122. Perhaps because they enabled local control as an insertable mode change event... doesn't explain the "B" reject though.

Shooshie · Post by **Shooshie** » Sun Feb 04, 2007 4:21 pm

monkey man wrote:Blackboard and chalk, professor?

If you only knew... this is more like the day the professor didn't show up for class, and the two students on the back row started trying to figure out how to turn on the lights.

Shooshie

timbuque · Post by **timbuque** » Sun Feb 04, 2007 7:00 pm

Bien sur, mon ami.

timbuque · Post by **timbuque** » Fri Feb 16, 2007 10:30 am

Partly solved! Hex B1=greater than 127 which is not allowed in the sysex editor.

Shooshie · Post by **Shooshie** » Fri Feb 16, 2007 7:53 pm

Well, of course! Why didn't we see that before? This is how I learned SysEx, to begin with: by bouncing off the walls of my errors. Every thing I know about SysEx started with doing something wrong.

Well, on second thought, there HAVE been things like MIDI Show Control's spec sheets, and a number of books with chapters on SysEx, and manuals, and on and on... I guess it actually starts with that kind of knowledge, but it seems like to actually put it into use, you have to make a few mistakes with it.

Shooshie