The Logic Off Topic list

Kool Musick wrote:
> Why or why do I always get myself into these situations?????!!!! (Nothing
> personal to you!!).

   The reason is probably that you are a kind, helpful person with knowledge
that can assist others. I'm am grateful!! And I'm sure it takes up some of
your valuable time. And also, no offense taken.

> The F0 means roughly 'Hey guys, look out, operational message coming'.
> The 18 after the F0 means 'if any of you are made by Emu systems' --
> because their manufacturer number is 18 inhexadecimals, or 24 in ordinary
> numbers', then sit up and take note because the rest applies to you.
> Anything else, please ignore this.

   I'm sorry, I should have been more clear. I know about these bytes.
Thanks to the Environment Toolkit and the E-mu manual.

> As for what comes in the middle -- I really have absolutely no idea
because
> it could be anything at all. It all depends on how Emu have decided to
> create a concert grand sound. Honestly and truthfully, decoding sysex data
> is a thorough pain in the neck. Those who do it like to protect their jobs
> by making it incredibly difficult to fathom what their up to.

  See this is what I was trying to figure out. I thought that maybe there
was some kind of standard or something. I thought that it was more
accessible than this. In my E-mu manual it says that set up parameters may
be edited individually using system exclusive commands. The value of a given
parameter may be changed by sending a parameter value command. That command
happens to be F0 18 id dd 03 pl pm vl vm F7
  It says pl =parameter # LSB  pm=msb vl=value lsb vm=msb
  So then if I look in the chart for the preset parameters for say crossfade
direction it says this: Parameter # 60   Then in a column under (H) it says
(3C 00) and under parameter name it says crossfade directions. This is what
I'm having a hard time piecing together.

> Also, if you get MIDI Ox you will notice that it has monitors. You can
then
> go one step at a time and tweak a knob and watch exactly what data the
> synth spits out as you do so. Record that data either by writing it down;
> or else creating a little file for it and saving it.

  I downloaded MIDI Ox as soon as I got the link from you. But I couldn't
get it to show the info for what I was tweaking. The only thing I was able
to do is send a dump for a preset to MIDI Ox. The reason I'm most certain is
because I don't know what I'm doing yet and I'm a little overwhelmed. And I
did read the Help notes. I'm not a stupid person, it's just too much info
and not enough absorption.

> I am not trying to be difficult but beyond the first two data bytes and
the
> last one, I simply do not know what the rest of the data means, and
> probably only the manufacturer or someone who works for him does or else
> who has created an editor does.

  That's O.K. I didn't know there wasn't a standard.

> Without owning the synth it is impossible to know how the data is
organized.

   I completely understand.

> Sorry not to be more helpful.

   You were more helpful than you realize:)))
                      --Roger