Sysex command in ascii

Question

I have a device that I try to do a little nifty controlsurface to. The problem is that it needs to recieve the sysex message in ascii values because it is actually a network device with implemented midicommands and sysexes.

The Syntax

What it wants to recieve(ASCII): SysEx header ID type MI * 56 01 00 10 # end

The Green is ordinary sysexcommand that makes the connecting possible, so that is manually input.(hex)

Where the Red parts are the start and stop of the command string. And are as the command manually written.

The Black is the command, the blue is "channel" and the Magenta the data in this case sort of a MSB & LSB command combined. This in ascii characters

The translation I need is as follows

Text SysEx header ID type MI 2A 35 36 30 31 30 30 31 30 23 end

So is this possible to do in any way? To make a checkbox for replacing the 2-bit hex values with a 4-bit ascii translated hex value. I understand that this is a question for the developers and not for the common user. But maybe somebody else sits with this request as well.

Comments

Thanks for your suggestion. I don't understand it yet. Can you provide some examples of JUST the sysex you want to produce, please?

Answer 1

I will try. But i guess it will become very hard to come up with code to do that.

And I found a workarond for most of my problem there. However there is a more problematic issue with the sysex editor in MD. You can't write hex values greater than 7F(127) in the editor it automaticly rezise it to 7F and there are parts in the sysexcode that require bigger values: for example 'B0' and '9E'. And that was actually my workarond.  =)

What's it for? Well if you write

F0 <sysex reciever ID> B0 00 01 20 01 7F

B=command for sending controller message
0=midi cannel 1
00=Bank select msb 01=value
20=Bank select lsb   01=Value

And that solves a lot of problems for people who want to make a nice and easy controller for bankselect on a specific midi device that is in a single chain and shares the same midichannels.

I would actually use that if it was possible. And if you write:

F0 <sysex reciever ID> 90 3C 3A 40 78 3C 6E 7F

9=command for note on
0=midi cannel 1
3C=Note(C3) 3A=velocity(58)
40=Note(E3) 78=velocity(120)
43=Note(G3) 6E=velocity(110)

And that actually plays a C-charp chord with different velocitys on each tone. On a specific mididevice. And I would use that as well.

The thing is I'm doing a controllsurface with MD to control and eventually be able to make easy programming on my DMX lightningdesk.(Lanbox LCX). And I figure that this must be possible to do with MD and it's potential with supercontrollers.

The thing is that it would be easier with ascii possybilities as I mentioned in the first question. but not nessesery. Those commands that are only based on ascii coding are not that much in need of realtime value shifting. But that would be extremely useful if I could use the real sysexcommands. For example I need 3 different cc's to set a lightningscene(cuelists (9999) of them)  and make it active in a, so called, engine. And thereafter I need only 1 cc to change the cues(99) in that cuelist. The thing is that there are possibilities to use a lot if engines to control different lightningscenes. In my case I have 8, this to be able to use midi channels to control them. And since there are only 16 and I want to have 255 lighningchannels it becomes 8. Well... you get the point it would come to a lot of sub and supercontrollers to manage that...  well this should be a mail conversation or even on the phone if your interested.

Still the problem persists, and perhaps it's not that hard to unlock the hex value limitation in the sysexeditor? If its not a bug?
I understand why youl don't want the values it controls to exeed 127, but it should not(and isn't nessesery as I understand) apply to the manual input capabilitys.

 

//Sigge

 

Comments

Hi, first of all can you make this a comment on the question, if you can do that when editing... ? Also: hit me up over mail via midiDR/contact please. This is pretty dense and I'm having a bit of trouble grasping it.

---

"Hi, first of all can you make this a comment on the question, if you can do that when editing... ?"
Please feel free to do it (edit) for me.

"This is pretty dense and I'm having a bit of trouble grasping it."
If you have any question and I can help, please feel free to ask.

♪♫♪

Answer 2

I will try. But i guess it will become very hard to come up with code to do that.

And I found a workarond for most of my problem there. However there is a more problematic issue with the sysex editor in MD. You can't write hex values greater than 7F(127) in the editor it automaticly rezise it to 7F and there are parts in the sysexcode that require bigger values: for example 'B0' and '9E'. And that was actually my workarond.  =)

What's it for? Well if you write

F0 <sysex reciever ID> B0 00 01 20 01 7F

B=command for sending controller message
0=midi cannel 1
00=Bank select msb 01=value
20=Bank select lsb   01=Value

And that solves a lot of problems for people who want to make a nice and easy controller for bankselect on a specific midi device that is in a single chain and shares the same midichannels.

I would actually use that if it was possible. And if you write:

F0 <sysex reciever ID> 90 3C 3A 40 78 3C 6E 7F

9=command for note on
0=midi cannel 1
3C=Note(C3) 3A=velocity(58)
40=Note(E3) 78=velocity(120)
43=Note(G3) 6E=velocity(110)

And that actually plays a C-charp chord with different velocitys on each tone. On a specific mididevice. And I would use that as well.

The thing is I'm doing a controllsurface with MD to control and eventually be able to make easy programming on my DMX lightningdesk.(Lanbox LCX). And I figure that this must be possible to do with MD and it's potential with supercontrollers.

The thing is that it would be easier with ascii possybilities as I mentioned in the first question. but not nessesery. Those commands that are only based on ascii coding are not that much in need of realtime value shifting. But that would be extremely useful if I could use the real sysexcommands. For example I need 3 different cc's to set a lightningscene(cuelists (9999) of them)  and make it active in a, so called, engine. And thereafter I need only 1 cc to change the cues(99) in that cuelist. The thing is that there are possibilities to use a lot if engines to control different lightningscenes. In my case I have 8, this to be able to use midi channels to control them. And since there are only 16 and I want to have 255 lighningchannels it becomes 8. Well... you get the point it would come to a lot of sub and supercontrollers to manage that...  well this should be a mail conversation or even on the phone if your interested.

Still the problem persists, and perhaps it's not that hard to unlock the hex value limitation in the sysexeditor? If its not a bug?
I understand why youl don't want the values it controls to exeed 127, but it should not(and isn't nessesery as I understand) apply to the manual input capabilitys.

 

//Sigge