Device Number And Note Recording Receive Channel; Midi Transmission Delay; Remote Button Set-Up - Peavey PC 1600X Mode D'emploi

4. Use the up/down buttons or the data wheel to select which button the footswitch will emulate.
The polarity of the footswitch is automatically determined on power-up. If a footswitch is installed after the PC
1600x is powered up, or if the footswitch is depressed during power-up, the polarity of the footswitch may be
incorrect. Simply switch the power off, wait a few seconds, and turn the power back on with the footswitch installed
but not pressed. This will correct the polarity.
Note: Assigning a footswitch will automatically disable the CV 2 input.
DEVICE NUMBER - NOTE RECORDING/RECEIVE CHANNEL
This screen allows the assignment of a global device ID. Many MIDI products use system exclusive command
strings that have a device number as one of the bytes. These numbers are used to differentiate the unit from an
identical unit on the same MIDI stream. Being able to change these numbers globally allows you to use one set of
PC 1600x presets for multiple units of the same product. Instead of hard-coding these values into the strings, it is
possible to designate a 'dv' (device number) byte in the strings, then adjust this parameter to function as the global
setting.
The RecChn parameter is used when recording note messages into button strings. The Note Recording Receive
Channel parameter simply determines which channel notes will be accepted on. For more information, check out
the Note Stream Recording section on page 28.

MIDI TRANSMISSION DELAY

Sometimes a device can't handle MIDI data as fast as the PC 1600x can generate it. This can happen when
sending scenes, dumping presets, or during any other operation that sends large amounts of data. There are two
types of MIDI delay available to you. They both default to zero, and shouldn't be set otherwise unless a problem is
occurring with a receiving unit.
The first is a per-SysEx message delay, which is inserted after the PC 1600x sends an EOX byte (F7h). This puts
delays in between SysEx messages. The delay can be set from 0 to 100 ms. Try raising this number in 5 ms steps
if a unit chokes on SysEx data from sending scenes. (By "choking" we mean that the unit got a MIDI receive error,
got hung, or just didn't do everything that it should have.) Don't set this number higher than needed. The maxi-
mum value of 100 ms will make a scene with 16 SysEx messages take almost 2 seconds to send.
The other type of delay is a per-byte delay, which is inserted after every byte that the PC 1600x sends. This delay
can be set from 0 to 1000 us (1 ms), in 10 us steps. If a computer or MIDI librarian is getting a buffer overflow
when you're backing up your PC 1600x data, try setting this delay between 100 and 500 as needed. (A value of
320 will essentially split the MIDI speed in half.) You'll probably want to lower the delay when you're done, and
only raise it when needed.
The Delay screen is displayed as follows:
NOTE: These delays only affect MIDI data that the PC1600x generates internally. Data that is
echoed from MIDI IN to MIDI OUT is not delayed.

REMOTE BUTTON SET-UP

The 16 programmable buttons are useful for sending any type of message to just about any MIDI device. You can
access the button messages remotely by sending simple messages into the PC 1600x. All you need is a MIDI
keyboard, pedal board, or any other MIDI controller that sends Program Change commands or MIDI Note On/
Note Off messages (e.g. "MIDI-fied" foot pedals). For example, use your note pedals to play chords instead of
UTIL: DevNum RecChn
000 001
MIDI: PerMsg PerByte
DELAY 000ms 0000us
15