EMXP version 3.

07 build #1 (c) 2006 - 2017 by E-Synthesist

Important notes:
---------------

1. Read the manual (EMXPv307_referencemanual.pdf) and the disclaimer in the manual

before using EMXP.

2. Read the EMXP Mac OSX/Wine manual (EMXPv307_MacOSXWine_manual.pdf) when using

EMXP in Wine
on Mac OSX

3. Problems with RS422 communication

The stability and speed of the RS422 communication with the EMAX-I, EMAX-II,
Emulator-II and DPX-1
is determined by a set of communication parameters. These parameters can be changed
in the
Communication Preferences menu (see section "10.6 COMMUNICATION PREFERENCES" in the
manual).
The out-of-the-box values of these parameters may not be the best for your specific
set-up.
The values that should be used depend on the speed of the computer and on the
reliability of
the USB ports. The most important ones are the "Delay time ..." settings.
** Don't worry or get angry if the communication fails when using EMXP with the
initial
(factory) communication preference settings ! **
Just go to the Communication Preferences (option 6.5 from the Main Menu) and change
the values of
the "Delay time ..." settings:
- Decrease these values if you have an old or slow computer, or if you want to
increase the speed
of the data transfer. The communication will be faster but could be less
reliable.
- Increase these values if you have a fast modern computer. The communication will
slow down but
could be more reliable.
If the communication fails and additional attempts result in EMXP errors saying
that no data could
be written to the RS422 port due to reason code 31, you will have to unplug the
RS422 port and
plug it in again. Then retry sending or receiving the data in EMXP.
If the EMAX-I or EMAX-II was still in a "sending or receiving data over RS422" wait
mode, it will be
interrupted by the next data transfer attempt saying a bad packet has been
received. Don't worry.
A next data transfer attempt will probably be accepted again by the EMAX-I or EMAX-
II.

4. Problems with MIDI communication (especially with SP-12)

The SP-12 MIDI protocol is pushing the MIDI interfaces and drivers to their limits.
You may have to
adjust the "Delay time ..." and "Timeout ..." parameters in the Communication
Preferences (option
6.5 in the Main Menu) in a similar way as described in the previous section
(RS422).
You may have to increase the Data Packet Size as well.
** However it's also very important to use the most recent MIDI drivers available
for your MIDI
interface. Avoid old drivers as well as standard (generic) Microsoft Windows
MIDI drivers **
** If you are using a MIDI interface with the standard (generic) Microsoft Windows
MIDI driver
you may have to set the Data Packet Size to either 293 or 298. Other values can
result in
communication errors or can result in EMXP freezing during communication **

5. Problems with a correct display of the EMXP screens

By default EMXP automatically adjusts the size of the Windows Command console
window, and whenever
one or more characters or symbols on an EMXP screen change, EMXP by default
performs a positional
screen update only (= updating the changed part of the screen only instead of
reprinting the whole
screen).
If this default behaviour of EMXP causes problems for one reason or another, you
should adjust
the Look&Feel preferences related to these screen modes. If you even can't get into
the Preferences
menu, you can start EMXP from the command line with flags -NOSIZING and/or
-SCREENREFRESH. This will
start EMXP in a basic console mode and will allow to get access to the Preferences
menu.
For more information, see the Reference Manual chapter "1.7 STARTING THE EMXP
SOFTWARE".

EMXP - software for EMU vintage samplers (for Windows XP or higher)

-------------------------------------------------------------------

New features in version 3.07:

- Support for SCSI2SD partitioned SD cards. EMXP can directly access (read, write
and format) any
of the SCSI partitions (devices) on an SD card which is used in a SCSI2SD board.
All EMXP capabilities for EMAX-I, EMAX-II and Emulator-III/IIIX hard disks and
hard disk image
files are available for SCSI2SD partitions now as well. See Guided Tour #5 in
EMXPv307_GuidedTours.pdf for a quick introduction about SCSI2SD support in EMXP
- Loading Emulator-II banks to the Oberheim DPX-1 via RS422. If your Oberheim DPX-1
consists of
the optional CDROM interface, you can use EMXP and an EmuSer now to transfer
Emulator-II banks
to the DPX-1. This is much faster than using floppy disks or using an HxC floppy
disk emulator.

Optimizations applied in this version:

- The detection of EMAX-II and Emulator-III/IIIX file systems on hard disks and
hard disk image
files has been made more reliable.
- Physical formatting of EMAX-I, EMAX-II and Emulator-III/IIIX hard disks and
memory cards
 (CF, SD, ...) is supported now, and disks can be formatted to any size now. In
previous versions
of EMXP, only logical formatting was supported, and disks could only be formatted
to a fixed
number of file system sizes.
- Conversions of Emulator-III and SoundFont2 sound banks are much faster now. This
is also true
for audio playing their samples and for converting their samples to WAV files.
- Sampler hard disks and hard disk image files larger than 2GB or 4GB are supported
now.
- An preference option has been added to change the information displayed in bank
overview screens
for EMAX-I, EMAX-II and Emulator-II sound banks. It's possible now to show
include the number of
sequences in the overview screen.
- When generating Akai S1000 floppy disk image files, it's possible now to
immediately save an
operating system to the file as part of the generation process.
- After copying or converting a selection of items (banks, files, ...) EMXP is now
returning to
the selected items overview screen again instead of to the parent menu screen.

Bugs fixed in this version:

- When converting sound banks only consisting of empty or invalid presets, EMXP
could crash
instead of returning a proper error message. This was especially true when
converting SoundFont2
banks. This problem has been resolved.
- After having formatted a disk in EMXP and immediately trying to use that disk
without returning
to the Disk Manager, EMXP did not take into account the new file system saved by
the format process.
This problem has been resolved.
- If the console buffer size of the Windows command screen which runs EMXP was
larger than 64KB
(e.g. 785 lines and 80 columns), a wrong warning screen was shown when starting
EMXP.
This has been replaced by the correct warning screen.
- In some specific cases it was possible to press Enter in a selection screen even
when selecting
at least one item was mandatory but no item had been selected yet. This problem
has been resolved.
- Deriving the path (folder) in which EMXPN.EXE is stored did not work properly if
EMXPN.EXE was
renamed by the user. This problem has been resolved.
- When trying to replace an existing file with a generic extension like .IMG or
.ISO, EMXP created
a new file instead of replacing it if the file's extension differed from the
default file extension
for that file type (e.g. EZ2 for EMAX-II hard disk image files). This problem has
been resolved.
- The bank/preset report did not show the hard disk or hard disk image name on its
first line if the
first bank on that disk or disk image is corrupt. This problem has been resolved.
- The ACK/NACK processing for MIDI communication with the EMAX-I and EMAX-II can
deal with MIDI
channels which differ from the basic MIDI channel of the sampler
- When starting audio playing WAV files from the WAV menu, it was impossible to
leave the audio player,
the WAV file was played over and over again. This has been resolved.

Build notes:
- Build 3.07.1 - 2017-06-28: Initial build.

2017-06-28
///E-Synthesist