I have really nothing to add to Hendrik's post except that -- it really is a lot easier if you either use a spreadsheet or else a table. That way you can list in separate rows the data values that need to be sent together and what they do; and in the columns what those data values are trying to do. >And I >did read the Help notes. I'm not a stupid person, it's just too much info >and not enough absorption. Nobody is accusing you of being stupid. The major problem here, actually, is the completely unhelpfulness of manufacturers' and the information they provide. Which is understandable given that only about 0.01% of users every want to try anything like this. So ... as Hendrik said ... you would soon notice that every single chunck of sysex you tried to send had certain repeating values. This also means that when you read something in the manual you can immediately put it in your table in the appropriate place. You will also see the device id being constantly repeated so you would know what it is. Hendrik has already explained everything to you better than I could: But although it was kind of Hendrik to explain to you how to do those hexadecimal calculations, you don't actually need to do any!! Just go to the environment in Logic, and create a new fader. Set either of the in or out definitions to 'sysex' and a window will spring up in which you can create a sysex message. Now (I'm on Windows) right-click on the little button that says 'SysEx'. A little basic sysex string should spring into being in the event window display. It should read: Sysex 4 0 Moog. Now, with the sysex window still displayed, go to the View window and click on View in Sysex. The display should immediately change to $F0 $04 $00 Moog If you go back to the decimal display and change the 4 to 24 (just click and scroll) you should see the display change to: Sysex 24 0 Emu Systems Again click on view in hex and you should see: $F0 $18 $00 Emu Systems. Bang. One instant decimal to hexadecimal converter. Tedious but it works. There's also a converter in MIDI-OX. So, as Hendrik told you, if you want to change the crossfade directions to a given value, you could put all the decimal values into a fader, hit view in hex, and you would get your immediate conversion. This makes it very easy to produce your string of F0 18 id dd 03 3C 00 27 00 F7 since the Emu manual seems to be giving you the decimal values anyway and they're a lot easier to think with. Some manufacturers don't bother and just give you the stuff in the H column with no decimal equivalents. The principle is that if you put all the information for a short string like that into one of Logic's faders and send it to your Emu, you should get the response you want and see the crossfade direction change to that value. SHOULD being the operative word. They say that hell is full of people eternally damned to working out sysex strings -- with a particularly wicked group of people doing it from out of Logic Audio. Have fun. Kool Musick Keep Musick Kool _________________________________________________________ Do You Yahoo!? Get your free @... address at http://mail.yahoo.com
Message
Re: [L-OT] Understanding SYSEX
2001-04-19 by Kool Musick
Attachments
- No local attachments were found for this message.