EOS SysEx not responding

[Anonymous]

Hi all.

Im making a panel for my Emu E4 -EOS but im having a hard time trying to modulate/engage the commands to do what i wish to do.
I’ve got the documentation for EOS which lists all ID# for all parameters BUT i cant manage to modulate/perform alot of the functions.

The syntax is:

Format:  <Header>,<Command>,<Count*>,<Packet1>,<Packet2>,...,<Checksum*>,<EOX>.

    <Header>

        F0h = sysex message
        18h = EMU ID
        21h = E4 ID
        xxh = Device ID 
              00h - 7Eh are Unique
              7Fh is an All Broadcast

        55h = Special Editor designator byte

    <Command> determines what function to perform, such as:

       Parameter Edit/Request
       Preset/Sample Name/Request
       Dump/Request

    <Count> Gives the number of bytes in a message, such as    
            Parameter Edits of multiple parameters.  *Only used
            in variable sized messages.  

  - Packets take several forms, depending on the command.  Some commands may
    not require a packet at all.

    <Packet> = <2 Byte ID>,<2 Byte Data>.
               The main packet has 2 parts;  An ID portion and the Data 
               portion.  This is used for editing a parameter.  The ID
               chooses the parameter, and the Data is the new value.

               Every Parameter has a unique ID.  This way, parameters can be 
               individually manipulated.  However, these Parameter ID's operate
               on a specific Voice/Group/Sample, as well as Global parameters.

               The ID Byte is the Parameter ID, a 14-bit unsigned number split 
               into 2 MIDI bytes, and sent LSB first.

               The Data is a 14 bit signed or unsigned number split into 2 
               7-bit MIDI bytes, and sent LSB first.

    <Packet> = <2 Byte ID>
               The request packet requires only the Parameter ID, or Preset/
               Sample number.  Typically used in a request for data from a
               particular Parameter.

    <Packet> = <Preset/Sample #>,<ASCII string>
               The Name packet contains the Preset or Sample number, followed 
               by the name as a string of ASCII characters.

    <Packet> = <Preset #>
               Selecting another Preset.

    <Checksum> = 1 Byte XOR(1's compliment) of the sum of the DATA bytes in the message.
                 *Only used in certain messages.  A checksum value of 7Fh means "ignore
                 checksum".             

    <EOX> = F7h end of SYSEX.

For instance,create a new Voice.– i created a uiButton and assigned a SysEx:F0 18 21 01 55 01 02 20 xx F7 but i cant get it to respond.
To display text im using uiCombo. Am i going wrong here?
Is LUA inevitable?

[Mr.ToR]

Hi 2onc,

Can Emu E4 send SysEx on parameter change? If it can, open the midi monitor and paste here a couple of lines when you change a parameter from the sampler.

Also, isn’t there a MIDI channel parameter in the SysEx implementation? I mean, if you have two samplers in the chain, one on ch7 and the other on ch8, how do you indicate which device to respond to on that SysEx?

[Anonymous]

Can Emu E4 send SysEx on parameter change? If it can, open the midi monitor and paste here a couple of lines when you change a parameter from the sampler.

I dont think it can, i looked at this before. There is no output

Also, isn’t there a MIDI channel parameter in the SysEx implementation? I mean, if you have two samplers in the chain, one on ch7 and the other on ch8, how do you indicate which device to respond to on that SysEx?

Yes there is, “MIDI Device ID”. My E4 is on “1”. The formula has the correct value.

I am able to modulate some parameters like the LFOs and ENVs but im having a hard time grasping the syntax.

[Author]

Posts