Cancun - FAQs

All files and documentation are offered on an *AS IS* basis and you assume full responsibility for using them.
SysEx - using - Advanced
Using the Cancun SysEx messages:
--------------------------------

Effect parameters such as Reverb, Chorus, EQ and Spacializer can be controlled
by sending SysEx messages (System Exclusive Messages) to the Cancun board. 
This is done via MIDI Orchestrator Plus' SysEx window. A number of SysEx files
have been provided as examples. You can load these as are, or modify them to 
create custom versions. More details on editing these SysEx files are provided
below. 

Although working with SysEx messages is somewhat of an advanced MIDI
technique, you should not be afraid to experiment. You can't hurt the board or
change any settings permanently. All settings are restored when you reboot the
system.

To send a SysEx message using MIDI Orchestrator:

1. Select the SysEx window from the Window | New menu.
2. Click the load button and select one of the provided SysEx files.
3. Select the MIDI port for the Cancun. (the sound cards' MIDI Header port)
4. Press Send

More on working with SysEx Messages:

The SysEx files provided are pseudo-messages.  That is, they contain embedded
MIDI control messages. These are designed to work with Digital Orchestrator.
If your sequencer does not allow values greater than 7FH (127 decimal) 
in a SysEx string, you'll have to use the NRPN controls to change the EQ.

Each SysEx message begins with an F0 and ends with F7.  In between are the 
numbers that correspond to MIDI controllers.  All values are in hex.  

Example:

f0 b0 63 37 b0 62 00 b0 06 60 f7 

The above example is the sysex message to set the low band eq level to +6 dB.

Here is a breakdown of each number:

f0 - beginning of message
b0 - code for MIDI controller
63 - NRPN MSB
37 - value of MSB (in this case, special NRPN controls)
b0 - code for MIDI controller
62 - NRPN LSB
00 - value of LSB (specifies low band eq)
b0 - code for MIDI controller
06 - data control
60 - value (0-7FH, -12dB - +12dB)  NOTE: a setting of +12dB may result in 
                                   audible distortion, set the NRPN for the 
                                   Master Volume to a lower level to
                                   compensate.
f7 - end of message

From this, you can see that it is relatively easy to take the NRPN values
from the table in the Cancun MIDI Specification and construct your own
SYSEX messages.  Note that each MIDI controller starts with b0.

For example, look up the value for Master Volume in the Special MIDI Controls.
You'll see that it is NRPN 3707 with a value range from 0 to 7FH.  
Let's make the SYSEX message:

Remember, start each message with f0 and end it with f7

f0 - start
b0 - code for MIDI controller
63 - this signifies the NRPN MSB value is next
37 - the first two numbers from the 4 we got from the table
b0 - next MIDI controller
62 - this signifies the NRPN LSB value is next
07 - the last two numbers of the 4 we got from the table
b0 - next MIDI controller
06 - data, this signifies the next value is our volume
xx - any number from 00 (no sound) to 7f (full volume), 4d is good for EQ
     gains of +12dB.
f7 - don't forget to end the message with this

That's all there is to it.  You can string together multiple controllers, 
like EQ frequencies and levels in one SYSEX message.  This has been done in
eq_dflt.syx
To see the values in any file, just load them into Orchestrator's SYSEX
window.

1/11/99
Voyetra Turtle Beach


                            ********************

NOTES:
This info is offered on an AS IS basis. Improper use of SysEx commands may 
result in a synth being reset or patches deleted!  Please contact the 
manufacturer of the device in question to obtain the proper SysEx messages.
We cannot assume any responsibility for lost data.

SySex data implementation is not supported by our support staff. The USB and 
the Standard 15 pin Joystick MIDI Cable - as well as our Software programs -  
are capable of delivering SySex Data or any MIDI information, however, when 
it comes to importing or exporting SySex, things get easily complicated as 
they there are too many parameters that can go wrong. 

Customers are responsible on their own for configuring advanced concepts 
such as SySex or PatchMaps.  
______________________________________________________________________________