                    


   
                  =========================================

                           GenEdit 2.02 Tutorial

                           A Guide to GenEdit ST
                             The Universal MIDI 
                              Editor/Librarian

                                 Prepared by 
                                 Joe Hlifka
                              November 15, 2003

                  =========================================









TABLE OF CONTENTS


CHAPTER 1:
INTRODUCTION ....................................................... 

About This Program .................................................
About This Manual...................................................
How This Manual Is Organized .......................................
Suggested Study Habits .............................................
System Requirements ................................................
Terminology.........................................................
The Menu Bar........................................................
Info Line ..........................................................
Click...............................................................
Key Commands........................................................
Combined Mouse Click & Key Commands ................................
Left Click..........................................................
Right Click.........................................................
Alternate Click.....................................................
Exiting.............................................................


CHAPTER 2:					

GETTING STARTED	.................................................
Checking Your Package .............................................
Package Contents ..................................................
Disks Contents ....................................................
Making A Backup ...................................................
Formatting Disks ..................................................
Double-Sided Drive Users ..........................................
Hard Disk Users ...................................................
LGSELECT Installation .............................................
Single-Sided Drive Users ..........................................
Connecting Your System To MIDI ....................................
Loading The Program ...............................................
		

Tutorial...........................................................
A Fast Introduction To Using GemEdit as a Patch Librarian .........
Saving your sounds ................................................
Loading Your Sounds................................................


CHAPTER 3:				
CONFIGURATIONS					

Configuration Basics ..............................................
What Are Configurations ...........................................
Loading Configurations ............................................
What You Can Do With Configurations ...............................
Organizing Your Configurations.....................................
Reorganizing A (configuration File.................................
Saving Configuations ..............................................
Combining Configurations From Several Files........................
AUTOLOAD.CNX.......................................................
More Ways To Manipulate The Configuration List...3-19



CHAPTER 3A:
STUDIO SETUP.........................................................

Studio Setup Basics..................................................
What Is A Studio Setup...............................................
Loading Configurations...............................................

Global MIDI Options..................................................
Thru.................................................................
Port.................................................................
Transmit Speed.......................................................
Patch Bay............................................................
Receive Filters......................................................

Devices..............................................................
Clearing A Device....................................................
Editing A Device.....................................................
Rearranging Devices..................................................
Saving And Loading Studio Setups.....................................
Using Studio Setups..................................................




CHAPTER 4:
ORGANIZING YOUR PATCHES .............................................

A Tour Of The Main Screen............................................

Moving Banks Around..................................................
Saving A Bank Of Patches from Your Instrument .......................
Sending Patches Back To the Instrument...............................
Transferring Banks Using Left/ Right Windows.........................
Dragging Icons Using the Keyboard....................................
Backup Files.........................................................
Moving Individual Patches............................................

Scrolling Around A Window............................................
Window Locking.......................................................

Selecting Patches....................................................
Renaming Patches.....................................................
Moving Patches.......................................................
Exchanging Patches...................................................
Sorting Patches......................................................
Finding Duplicate Patches ........................................... 
Printing A Patch List ...............................................
Window Information ..................................................
Auditioning Patches .................................................
Patch Change Sends Patch To MIDI.....................................

Multi-Block Files....................................................
Managing Multi-Block Files.................,,,.......................
Using Multi-Block Files..............................................

Configurations Within Data Files.....................................
Attaching A Configuration To A Window................................
Load/Save Configuration/Data ........................................

Library Files........................................................
Ways To Use A Library File...........................................

Non-GenEdit/GenPatch Files...........................................
Loading Files In Other Formats.......................................
Exporting Raw Data ..................................................



CHAPTER 5:						
EDITING .............................................................  

Editing Basics ......................................................
What Can You Edit ...................................................
Learning How To Edit ................................................

Preparing To Edit ...................................................
Files Needed For Editing ............................................
Entering The Editor .................................................
Manually Loading Template Files .....................................
About Template Scaling ..............................................

The Editor...........................................................
The Editor Info Line.................................................
Exit ................................................................
Undo and Compare ....................................................
Selecting Pages .....................................................
Play ................................................................
Thru Channel/Port ...................................................
Send ................................................................
Send Channel ........................................................
Patch Number and Name ...............................................
Updating The Instrument .............................................
Key Commands for Info Line Buttons ..................................


===========================================================================


           The Following Chapters not included in this tutuorial


Editor Controls .....................................................
Numeric Values ......................................................
Text Values .........................................................
Knobs ...............................................................
Sliders .............................................................
Joysticks  ..........................................................
Envelopes ...........................................................
Buttons .............................................................
Resetting a Control Value ...........................................
Linked Controls .....................................................
Parameter Interaction ...............................................


A Mind Of Its Own ...................................................
Distorting ..........................................................
Randomizing .........................................................
Averaging ...........................................................
You Have Some Control Over It .......................................


CHAPTER 6:
CONTROLLING .........................................................

Controlling Basics ..................................................

Using A Controlling Template ........................................
Files Needed For Controlling ........................................
Entering The Editor .................................................
The Editor Info Line ................................................
Exit ................................................................
Undo and Compare ....................................................
Send Channel ........................................................
Send ................................................................
Patch Number and Name ...............................................
Updating The Instrument .............................................
Editor Controls .....................................................

Multi-Program Switching .............................................
HybriSwitch .........................................................
SoftLink ............................................................

CHAPTER 7:
ADDITIONAL FEATURES .................................................

The Built-In Sequencer ..............................................

Template Linking Options ............................................
Linking To Multiple Templates .......................................
Editing The Template Link ...........................................


MIDI Monitor.........................................................
Settings.............................................................
Using The MIDI Monitor...............................................
Exiting The MIDI Monitor.............................................
Macros...............................................................
What Is A MIDI Event.................................................
Hexadecimal vs. Decimal .............................................
What MIDI Events Look Like...........................................
Displaying GenEdit Macros ...........................................
Creating Your Own Macros ............................................
Getting Around The Macro Editor......................................
Display Modes .......................................................
Editing Macros ......................................................
Saving Macros .......................................................
Using MIDI Macros ...................................................

File Management .....................................................
Delete File .........................................................
Copy File ...........................................................
Rename File .........................................................
Create Folder .......................................................
Delete Folder........................................................
Format Disk .........................................................
HybriSwitch .........................................................

User Preferences ....................................................
Paths ...............................................................
Other User Preferences ..............................................
Save Preferences ....................................................
Load Preferences ....................................................

Customizing Your Screen Colors ......................................

AUTOLOAD Files ......................................................


CHAPTER 7A:
SIMPLE CHANGES TO TEMPLATES & CONFIGURATIONS ........................

What You Can Do .....................................................

Modifying A Template's Appearance ...................................

Modifying A Controlling Template's MIDI Output ......................

Modifying A Configuration To
Not Prompt For Send Channel .........................................

Immunity From Automated Editing  ....................................
Immunizing A Parameter ..............................................
Randomize vs Distort / Average.......................................

APPENDIX H:
HYBRISWITCH .........................................................

This Appendix is included with the HybriSwitch Program. HybriSwitch
owners can easily insert Appendix H in the Appendix Section of this manual
or in the manual of any Hybrid Arts program compatible with HybriSwitch
(format allowing).


APPENDIX K:
KEY COMMAND SUMMARY...................................................

Main Screen...........................................................
Editor................................................................

Configuration List Page...............................................

Configuration Edit Page...............................................

Template Page.........................................................

EBDT Page.............................................................

Macro Page............................................................

Monitor Page..........................................................

Text List Dialog (on Template Page)...................................

TextEdit..............................................................

APPENDIX T:
TROUBLESHOOTING.......................................................







                   =====================================

                                 CHAPTER 1
                               INTRODUCTION

                   ======================================



                             In This Chapter:

                             - About This Program
                             - About This Manual
                             - System Requirements
                             - Terminology













------------------
ABOUT THIS PROGRAM
------------------

Welcome to GenEdit, a program that communicates with almost any MIDI
instrument or device. By using GenEdit, you are able to save and load
patches, assemble custom patch banks, and edit patches down to the
individual parameter.

There are several ways to use GenEdit. You can use it to save and load
various types of data (sounds, sequences, microtuning tables, etc) from
different MIDI Instruments.  You can also assemble custom banks of sounds
(for example, group brass patches together, or create a bank for each
song or project), and edit individual patches as well.

GenEdit comes equipped with flies containing Configurations, which can
load and save MIDI information (among other operations). Using the
built-in programming language, known as CNX, you and other GenEdit user
can create Configurations to keep the program compatible with the latest
MIDI gear.

As suggested by its name, GenEdit performs diverse editing operations,
including random patch generation, which Instantly gives you a bank of new
sounds. You can build your own patch editors for MIDI instruments using
Templates  design display screens and assign controls (sliders, buttons,
etc) to different MIDI messages or functions. Templates can also be used
to control MIDI effects devices or mixers.

With GenEdit, you can put together various MIDI SysEx commands. These
Macros can be used for a variety of purposes  for example, for testing
various MIDI parameters of your instruments.

As you can see, GenEdit is a powerful program. This manual will guide you
through each aspect of the program, allowing you to master that power.



-----------------
ABOUT THIS MANUAL
-----------------

How This Manual Is Organized This manual is organized in a way to make
learning the program fun. A basic Tutorial gets you started by
transferring patches from your Instrument.  Then we take you through each
part of the program by discussing concepts in an order which is easy to
follow.

We suggest you first flip through the entire manual to get a general idea
of how the program is laid out. First learn about Configurations (Chapter
3): then. try sending patches to and from your Instrument and organizing
your sounds (Chapter 4); Finally, try editing (Chapter 5). Then flip to
the specific chapters which cover the topics that Interest you.

The Table of Contents lists the appendices that appear at the end of the
manual. These are labeled after a prominent letter of the Appendix name
so you can easily remember their contents: for example.

Appendix K - Key Commands, and T - Troubleshooting (Appendices may be
added or taken out as the software is updated).

Portions of the manual intended solely for Template/Configuration
developers are available separately from Hybrid Arts.

This manual assumes a basic knowledge of  the Atari ST. If you haven't
yet done so, please familiarize yourself with the ST owner's manual.

Suggested Study Habits - To make the learning process easier, read this
manual while in front of your ST with GenEdit loaded. Try the examples as
you go. Feel free to put the manual down and experiment when you learn
something interesting. Instead of rushing through the manual, take some
time to gain a better understanding of the program.



------------------- 
SYSTEM REQUIREMENTS 
-------------------

To get your GenEdit system working effectively, we recommend using I Meg
of RAM.  This amount of memory allows you to receive and send large
amounts of data effectively. It is possible to load the program Into 1/2
Meg (520 ST), but only a small amount of memory remains for editing:
which means larger Template and Configuration Files may not load at all.

Before you begin using the program, make sure you have the following
items:

Required:  
- Any model Atari computer excluding 520ST (see above) 
- A Color or Monochrome Monitor (The program works in either Medium or
  High resolution) 
- One double-sided drive (GenEdit is only available on double-sided disks:
  the program cannot fit on a single-sided disk) 
- At least one MIDI-equipped instrument 
- 2 or more MIDI cables 
- Blank disks

The following are optional items that make your system more effective.

Optional:  
- Additional MIDI-equipped instruments and MIDI cables 
- An audio playback system or set of headphones 
- An additional double-sided drive 
- Hard disk drive (for speed and storage) 
- Additional RAM (internally in the computer. 



----------- 
TERMINOLOGY 
-----------

There are certain words used throughout the program (and manual) you
should become familiar with before you begin.



------------ 
The Menu Bar 
------------

The area across the top of the Main Screen is the Menu Bar  the words
across the bar are the Menu titles.  To access a Menu, move the mouse to
one of the Menu titles to make the menu "drop down". Then select a
Function from the menu. To make the Menu "go away" if you don't want to
select a function right now. Left Click on another area of the screen.



--------- 
Info Line 
---------

Certain operations cause a line of text to replace the Menu Bar at the
top of the screen. This Info Line may simply be informative, such as the
flickering rectangles during MIDI data transfer, or it may request one of
a set of actions  for example, if you type Alternate E on the Main
Screen, the program will request the second half of a key command
sequence. The Menu Bar returns when the process is complete. On certain
pages (the Editor, MIDI Monitor, etc) the Info Line remains until you
exit the page.



----- 
Click 
-----

When the manual says Click on something, It usually means to Left Click.
In many cases. Left Click and Right Click have different effects.

Key Commands - GenEdit also uses key commands. A key combination such as
Control C, means to type C while holding down the Control key. A key
sequence such as Control E C means hold Control, type E, and then type C.
(There is a complete list of Key Commands in Appendix K.)

Combined Mouse Click & Key Commands

Some functions In GenEdit require pressing keys and using the mouse at
the same time. The keys to be held while clicking precede the word Click.
Alternate Shift Click, for example, means hold down the Alternate and
Shift keys while Clicking the mouse.  Great care has been taken throughout
GenEdit's design to maintain consistency. This simplifies learning the
program because you can often guess the result of an action based on the
result of a known similar action. For example. If you Alternate Left Click
on a Configuration on the Configuration List Page, it will initialize that
slot by deleting the Configuration from the list. Therefore, you can
probably guess what will happen when you Alternate Left Click on a
Window's Title Bar on the Main Screen (it will initialize that Window by
deleting all Patch slots).  These GenEdit conventions are listed below.


Left Click on an object to select it or to drag it. For example. Left
Click on the MIDI Icon on the Main Screen to drag it to the Disk Icon or
to either data Window.

Right Click on an object to edit it. For example. Right Click on a data
Window Title to change its Title.  Right Click on a Configuration on the
Configuration List page to go to the Configuration Edit Page, where you
can change the Configuration.

Alternate Click:

Alternate Left Click on an object to initialize or delete it. For
example, on the Template Page,  alternate Left Click on a Control to
remove it from the screen.  On the main page, Alternate Left Click on a
Window Title Bar to clear the Window.

Exiting To exit a page and return to the previous page, press the Esc key,
(However, this is not true for most dialog boxes.)






                        ===========================

                         CHAPTER 2 GETTING STARTED

                        ===========================





                            In This Chapter:


                            - Checking Your Package
                            - Making a Backup
                            - Connecting Your System To MIDI
                            - Loading The  Program
                            - Tutorial
































-------------------- 
THE GENEDIT ARCHIVES 
--------------------


The GenEdit Achives should contain:

- This GenEdit Tutorial
- 1 GenEdit PROGRAM Disk
- 1 GenEdit EXAMPLES Disk
- 1 Cool Studio Disk


Disk Contents:

This package contains three disks: a PROGRAM disk, the EXAMPLES Disk and
COOL_STU disk.


The PROGRAM Disk - contains all information needed to run the program.

The EXAMPLES Disk contains sample Configuration, Template, and Data Files
for a couple MIDI instruments.  The disks should contain the following
files (Not necessarily listed in the order shown):


PROGRAM DISK: 
  GENEDIT .PRG 
  GENEDIT .RSC 
  GENEDIT .CDR 
  GENEDIT .PI2 
  GENEDIT .PI3 
  AUTOLOAD.SQC 
  SYSXPRSS.ACC 
  SYSXPRSS.TXT
  CONTROL .ACC 
  DESKTOP .INF 
  LGSELECT.TXT
  READ_ME .TXT 

AUTO Folder:		
  LGSELECT.PRG 

UTILITY Folder:	
  CNXCHNG.PRG 
  CNXCHNG.DOC 
  D50CONV.PRG 
  D50CONV.DOC


EXAMPLES DISK Macro file:
  FACTORY .MAX
  TUTORIAL.TXT 

Configuration flies:
  E_ENSONQ.CNX 
  F_YAMAHA.CNX 
  UTILITY .CNX 

Template files:
  ESQ    .TEM
  SQ80   .TEM 
  GENFADE.TEM 
  TICTACTO.TEM

Data files:	
  BUNDLDII.ESM 
  BUNDLDII.SQ8
  WNDFLSND.CIO 
  PRTYNICE.CIO
  TIC TAC .TTT


COOL_STU DISK:
  AUTOLOAD.STU (Studio Setup for the Cool Studio) 
  
  CONFIGS folder:
    AUTOLOAD.CNX

  TEMPLATS folder:
    Misc editor templates for Cool Studio instruments

  READ_ME .TXT
  COOL_STU.TXT
  SUPPORT .TXT
  
Important: The READ_ME file contains additional information to this
tutorial, please read it, Double Click on the name READ_ME from the 
Desktop, then click Show.



--------------- 
MAKING A BACKUP 
---------------

GenEdit is not copy protected. If you will be running it from a floppy
disk, it is still a good idea to make a backup copy of your disks.


The EXAMPLES and COOL_STU disks contain data, therefore, it is a good
idea to make copies of all your data files.



---------------- 
Formattinq Disks 
----------------

Both of the GenEdit master disks are double-sided. When making a backup
disk, you must first format 2 disks double-sided.

To Format A Disk Double-Sided from the DESKTOP:  
- Insert a blank disk into drive A 
- Click once on FLOPPY DISK A (it Inverts) 
- Select Format from the File menu 
- Format the disk Double-Sided 
- The number of bytes on a Double-Sided disk is 726016. If this number 
- matches the number on the screen after the formatting is complete, the 
- disk has been properly formatted.  
- Click OK - Click EXIT (to exit from the Format program)



------------------------ 
Double-Sided Drive Users 
------------------------

Most Atari computers come with Double-Sided drives. (These drives can be
purchased separately for any of the Atari ST series computers.) Because
both GenEdit disks are shipped on Double-Sided disks, it is easy to make a
backup copy of each disk.  To Make A Back Up (Using I Disk Drive):  
- Format a disk Double-Sided (726016 bytes on disk) 
- Insert your Master PROGRAM Disk in drive A 
- Click on FLOPPY DISK A once and hold the left mouse button 
- Drag Drive A over to Drive B until Drive B inverts 
- Let go of the mouse button 
- An Alert box appears explaining that doing this will
  erase all of the 
- information on FLOPPY DISK B 
- Click OK 
- This runs an Atari disk copy program 
- When prompted to swap disks:  SOURCE is your Master Disk (Disk A)
  DESTINATION is your newly formatted blank disk (Disk B) 
- Click COPY 
- Disk A will be copied to Disk B 
- When the Disk Copy program returns, Click EXIT

Repeat these steps using your EXAMPLES disk.

MAKE SURE TO LABEL YOUR BACKUP DISK(S).



--------------- 
Hard Disk Users 
---------------

If you have a hard disk drive, you can copy both GenEdit disks to it.
This process will save time when loading. 

Follow these steps to copy GenEdit to a hard disk.


To Copy GenEdit To A Hard Disk:  
- Create a folder called GENEDIT (New Folder, File menu) 
- Open that folder 
- Copy these flies from the PROGRAM Disk into that folder:  
     GENEDIT.PRG 
     GENEDIT.RSC 
     GENEDIT.CDR
     GENEDIT.P12 
     GENEDIT.P13 
     AUTOLOAD  .SQC
- Create these folders (inside the GenEdit folder):  
     TEMPLATS (a place to store Templates) 
     CONFIGS (a place to store Configurations) DATA (a place to store
     data patches, performance data, etc.)
- Copy all the .CNX files from the EXAMPLES disk to the CONFIGS folder 
- Copy all the .TEM files from the EXAMPLES disk to the TEMPLATS folder 
- Copy the .ESQ. .SQ8, .CIO, and .TTT flies from the EXAMPLES disk to the
  DATA folder 
- Copy the FACTORY.MAX file from the EXAMPLES disk to the GENEDIT folder 
- Any time you want to save data, save it in the DATA folder

See User Preferences/Paths (Chapter 7 - Additional Features) for a
description of how GenEdit can help you find flies automatically.



--------------------- 
LGSELECT Installation 
---------------------

For Hard Disk users, you need to follow these steps to install the Little
Green Selector on your Hard Disk.

To Install LGSELECT On A Hard Disk:  
- Insert and Open the GenEdit Program Disk 
- Open the AUTO Folder on the Program Disk 
- Open partition C on your Hard Disk 
- If you have not already done so, create an AUTO Folder on partition C 
- Open the AUTO folder 
- File-Copy LGSELECT.PRG from drive A into drive C's AUTO folder 
- Reboot your computer

The above description assumes your hard disk has Auto-Boot. If it does
not, copy LGSELECT.PRG from the GenEdit PROGRAM Disk to the AUTO Folder on
the floppy disk you boot your computer.

If you want to use a different file selector after installing the Little
Green Selector, remove LGSELECT.PRG from your AUTO folder (or, better yet:
rename it to LGSELECT.PRX) and reboot your system.



------------------------ 
Single-Sided Drive Users 
------------------------

As MIDI programs get more advanced, they grow in size. In the early days
of the ST. when single-sided drives were common and users didn't expect as
many features in programs, it was possible to keep program files smaller
so they would fit on single-sided disks. These days single-sided drives
are rare, and users are demanding more features from programs; thus
support of single-sided drives is no longer possible.

As of v2.0, the GenEdit program (GENEDIT.PRG and its associated .RSC and
.P12/.P13 files) cannot fit on one single-sided disk. You must add a
double-sided drive to your system (if you don't already have one) to run
GenEdit. Double-sided drives are available from your Atari dealer.



------------------------------ 
CONNECTING YOUR SYSTEM TO MIDI
------------------------------

To use GenEdit, you'll need to connect It to a MIDI Device (synthesizer,
sampler, drum machine, effects unit, etc). The basic hookup requires two
MIDI connections: the MIDI Out of your instrument to the MIDI In of the ST
and vice versa.  Sometimes the MIDI Out of the instrument does not have to
be connected to the ST, particularly when GenEdit is being used as a
controller. See your instrument's user manual (and possibly documentation
supplied with an Templates for that instrument) for more information
regarding connections.



------------------- 
LOADING THE PROGRAM 
-------------------

The PROGRAM DISK contains the GenEdit Program.

To Load The PROGRAM DISK: Insert the PROGRAM disk in drive A Turn the
computer ON The disk will spin and open the AUTO folder:  then it will
load the Little Green Selector; then it will load the Desktop information
(DESKTOP.INF).

The screen called the Desktop and a Listing of what is on the disk will
appear. This listing is called the directory of the disk.

Once you see the Desktop, you can load the GenEdit program. Double-click
on the GENEDIT.PRG file.




-------- 
TUTORIAL 
--------

A Fast Introduction to Using GenEdit as a Patch Librarian

Let's perform a simple operation that shows some of the different screens
and features of GenEdit. We'll be doing two things: (1) getting sounds
from our instrument and saving them to disk, and then (2) getting sounds
from the disk and sending them back to our instrument.

First, boot up the program, You should now be looking at the Main Screen.
On the left and right are two data windows, and in the center are two
icons: a disk and a MIDI Jack. Each data window has a title bar, scroll
arrows, and scroll bars.

Note: This tutorial assumes you already have obtained the Configuration
and Template Files for instruments you own. Most Configuration and
Template Files are supplied separately (not included in the GenEdit
package). Contact Hybrid Arts for availability information.



------------------ 
Saving Your Sounds 
------------------

(Think Instrument To Atari or MIDI To Disk)

When you retrieve data from your instrument, you are copying all of the
numbers (parameters) which make up a patch to the GenEdit buffer and then
storing them to disk. Please note this is just a copy. All information
will remain untouched inside your instrument until you replace it.  (See
"Loading Your Sounds" below).

Before doing a Transfer, make sure your instrument is properly connected
to the ST (see "Connecting Your System to MIDI" above),

Also, set up your instrument for System Exclusive (SysEx) communication
and set Transmit ON and Receive ON.  (Check your instrument's user manual
and look for references to SysEx or Bulk MIDI Dump.)

There may be additional settings depending on the instrument (Its user
manual should list these settings).


To Copy Sounds From MIDI To Disk:
- Determine the manufacturer's name for your instrument 
- Insert the Configuration Disk in Drive A 
- Select Load Configurations from the Edit menu 
- The item selector appears listing .CNX Files 
- Select a .CNX File with your instrument manufacturer's name 
- Click OK 
- That Configuration File will load 
- When the disk stops, insert a DATA disk (blank and formatted)

Assuming that the file loaded successfully, you'll be back to the main
screen. Now Left Click on the MIDI jack icon and drag it to the disk icon.
This tells the program that you want to move data from MIDI to DISK.

When you release the button over the disk icon, GenEdit presents a list
of instruments from the manufacturer you chose. Click on the Configuration
for your instrument (see Chapter 3 for details if your instrument has more
than one Configuration listed).

A Configuration for GenEdit could be compared to a printer driver for a
word processor program. More specifically, it handles all the differences
between instruments so that the program can be compatible with all of
them.

Depending on the Configuration you choose, two things could happen:
- The Transfer begins and the Receive indicator flashes: or 
- You may first be prompted for a MIDI channel, a bank, etc. If this
  happens, type in the MIDI Channel number and press Return.

When the transfer is complete, the item selector will appear. You will be
prompted to name your bank of patches to be saved on disk. If you still
have your Configuration disk in drive A, remove it and insert a
blank/formatted data disk to save your bank.  You can use the default
file name (FROMMIDI.xxx), or you can backspace and type in a more
meaningful name.

Note: If the transfer did not work properly, please check connections and
settings, and/or see Chapter 4 - Organizing Your Patches for a detailed
description of a MIDI to DISK transfer.



------------------- 
Loading Your Sounds 
-------------------

(Think Atari to Instrument or Disk to MIDI) Now let's send that bank of
patches back to your instrument.

Note: If it is possible, we strongly recommend you save your patches
elsewhere (RAM card, cartridge, etc) before you start working with
GenEdit. That way, if there is any problem (bad MIDI cable, disk error
etc), you will have a backup somewhere.

Also, even though we have been careful to test the Configurations we
supply for instruments, sometimes manufacturers make changes to an
instrument's SysEx MIDI functions and release new versions of the same
instrument. In such cases, you may need to choose a Configuration that
matches the version of the instrument you are using. You may have to try
several Configurations until one matches your particular unit.

See Chapter 3 - Configurations for details



------------------------------------------- 
To Send a Bank of Patches To an Instrument:  
-------------------------------------------

- Left Click on the disk icon and drag it to the MIDI jack icon (This
  tells GenEdit that you wish to copy data from DISK to MIDI) 
- The item selector prompts for a file 
- Select the file (bank of patches) you just saved 
- Click OK (If prompted, respond to any dialog boxes and press Return) 
- The Transmit indicator flashes


You don't need to select a Configuration going in this direction, because
when GenEdit created the file, it saved a copy of that Configuration with
the data file. When you move the file from DISK to MIDI, GenEdit uses the
Configuration "inside" the data file to drive the MIDI communication.

This Tutorial ignores much of the detail needed to fully understand the
functions within GenEdit.  (Transferring data is only one of the many
features in the program.) For more detailed descriptions, consult the
Table of Contents, or this brief outline:

Chapter 3 	Configurations 
Chapter 3A	Studio Setup 
Chapter 4   Organizing Your Patches 
Chapter 5	Editing 
Chapter 6	Controlling 
Chapter 7   Additional Features 
Chapter 7A	Simple Changes to Templates & Configurations







                      ==================================

                           CHAPTER 3 CONFIGURATIONS

                      ==================================






                         In This Chapter:

                         - Configuration Basics 
                         - Organizing Your Configurations















-------------------- 
CONFIGURATION BASICS 
--------------------

What Are Configurations:

A Configuration contains instructions that tell GenEdit how to
communicate with a specific instrument.

Consider a student taking a trip around the world, visiting dozens of
countries. This tourist may not himself know how to speak every language
he will encounter, but with the help of an interpreter in each country, he
can communicate with people who speak a variety of languages.

Similarly, GenEdit without any Configurations loaded does not know how to
"speak" the language of every MIDI instrument that exists: but with the
help of a Configuration for each instrument, it can communicate in the
instrument's "native tongue".

Configurations are organized Into Configuration Files, which are supplied
on your EXAMPLES disk, or on the TEMPLATE disk for a particular group of
instruments. Each Configuration File contains up to 63 Configurations. For
many popular instruments, GenEdit already has Configurations that allow
for Organizing your sounds and even Editing them: these Configurations are
in files whose names start with 0_ and E_.

For these and many other instruments, there are Configurations that let
you save and load various types of data (banks of patches, banks of
combinations, global settings, etc): files containing these Filing
Configurations have names which start with F_.

All of these Configurations are named after the instrument manufacturer's
name (e.g.  E_YAMAHA.CNX, F_ROLAND.CNX, 0_KORG.CNX, etc). Some additional
configurations are found in files named after the imaginary manufacturer
Miscellaneous (i.e. E_MISC.CNX , etc). There are also a couple
non-manufacturer-specific (Filing) Configurations found in UTILITY.CNX,
which is on your EXAMPLES disk.

Configurations are created using a programming language specifically
designed for use with this program.  If a lot of detail is put into a
Configuration, it is capable of doing more detailed communication work
with your MIDI instrument. In general, GenEdit Configurations can be
classified into three categories:

Filing: These Configurations are used for loading/saving various
types of instrument-specific data.

Organizing: These Configurations are used for: loading/saving Banks of
patches or combinations, displaying and editing Patch names, and moving
Patches around within a Bank or between different Banks.

Editing: These Configurations do everything Organizing Configurations do.
Plus, with a matching Template, you can Edit the Patch information, as
well as Distorting, Randomizing, or Averaging Patches.

Configurations thus allow you to perform a variety of editing, librarian,
and MIDI controlling functions to the instrument of your choice. It is
possible to modify existing Configurations or write new Configurations for
MIDI instruments as they are released into the marketplace.



---------------------- 
Loading Configurations 
----------------------

When you first load GenEdit, it is not ready to "talk" to your
instrument. The GenEdit program is the "shell" which runs tiny little
programs (Configurations) which do all the talking. So the first thing
you have to do is load the appropriate Configuration File which contains a
Configuration that can "talk" to your instrument.

To LOAD A Configuration File:  
- Select Load Configurations from the Edit menu (OR press Alternate L C) 
- Select the desired Configuration File 
- Click OK


What You Can Do With Configurations

Once you load a Configuration File. you can:

- Receive data from the instruments supported in that Configuration File 
- Delete Configurations 
- Move Configurations within one file 
- Move Configurations between different files 
- Edit existing Configurations or create new Configurations 
- Save an edited Configuration File back to disk

Receiving and organizing data from your instruments is covered in Chapter
4  Organizing Your Patches.  If you want. you can jump to that discussion
right now, as you already know all you need to know about Configurations
to be able to receive data dumps and organize patches.  The rest of this
chapter deals with organizing your Configurations, which is something you
will want to do (along with creating a Studio Setup, described in Chapter
3A) to make everyday use of GenEdit easier: but it's something you don't
have to do right away.

Modifying Configurations is an advanced topic. See Chapter 7A -- Simple
Changes to Templates & Configurations  if you're interested in this.



------------------------------ 
ORGANIZING YOUR CONFIGURATIONS
------------------------------

We don't know which instruments you have, so we've supplied
Configurations for all the ones we could think ofl There were way more
than 63, so we couldn't fit them all in one Configuration File. As a
result, you may have to load one Configuration File to use with one of
your instruments, and load another Configuration File to use with another
instrument.

If you find yourself frequently using particular Configurations from
several different Configuration Files, you can combine them into one
Configuration File which will suit your everyday needs.  You can even make
GenEdit automatically load that Configuration File for you every time you
run the program!

Before we explain how to collect Configurations from several files into
one custom Configuration File, we first want to show you how to reorganize
the Configurations within one Configuration File.



--------------------------------- 
Reorganizing A Configuration File
---------------------------------

The F_YAMAHA.CNX file contains Filing Configurations for a lot of
different Yamaha instruments.  (Likewise, E_ENSONQ-CNX has Editing
Configurations for Ensoniq Instruments, and so on.)  If you only have an
FB-O1 and an RX-1 1, you only need to use a few of the Configurations in
the Yamaha file.  To make those Configurations easier to spot when you see
the Configuration List, you could delete the Configurations (Configs) you
don't use and move the remaining ones around so they're nicely organized.
Let's demonstrate how you would do this. We suggest you try this even if
you don't have any Yamaha instruments or the specific ones in our example,
just so you get familiar with using these GenEdit features, which you will
then be able to apply to your particular situation.

Load the F_YAMAHA.CNX Configuration File (as explained above) from the
EXAMPLES disk. Then select Edit Configurations from the Edit menu. You
will enter the Configuration List Page.  The top line shows you the name
of the Configuration File (F_YAMAHA.CNX).  Below the name are 63
Configuration Slots in three columns. The order of Configurations on the
list is not important other than for your convenience.



At the left of the screen Is a Configuration List Toolbox. The only tool
you'll need to use at first is the Trash Can; the others (Printer, Left
Window, Right Window, Clipboard, and ALL) will be described later.

At the bottom of the screen is the Exit button. Clicking Exit (or
pressing Esc on the ST keyboard) will return you to the Main Screen. Each
of the 63 Configuration Slots contains a Configuration Name (the first 17
characters) and a default Extension (the last 3 characters, shown in a
different color) to be used when saving Data Files created using that
Configuration. Empty Configuration Slots are indicated by a row of dashes.

Each Configuration is used for saving a specific type of information from
a particular instrument. When there are several Configurations listed for
one specific instrument, one Configuration may be for saving all patches
(voices), another for saving all performances or combinations (multi's),
another may get everything from the instrument at once, and so on. (The
different types of Configurations commonly available are described in more
detail in Chapter 4  Organizing Your Patches.)

Since, for purposes of this practice example, you only have an FB-O1 and
RX-11, the only Configurations you need are:  
  RX-11 Patterns   RX
  FB-O1 ram banks  FBR 
  FB-O1 allconfigs FBC 
  FB-O1 all        FBA

The first thing you want to do Is to delete all the other Configurations
on the screen. There are two ways to clear a Configuration Slot:

To DELETE A CONFIGURATION From The Configuration List:  
- Left Click on a Configuration and hold the mouse button down 
- You will see an outline around the Configuration (it will also invert) 
- Drag the outline to the Trash Can until the Trash Can color inverts 
- Release the mouse button to "throw the Configuration into the trash" 
    OR 
- Left Click on a Configuration while holding down the Alternate key

Note: If you Right Click on a Confguration. you will find yourself in the
Configuration Edit Page.  You will see two windows containing CNX
Language.  Click Exit to get back to the Configuration List.

Obviously, the second method (Alternate Left Click on Configuration) is
much faster, but the first method (dragging to the trash) is safer, as you
can decide after you start to drag that you didn't want to throw it away,
and cancel the deleting action just by dragging into unused space (for
example, to the unused portion of the screen at the upper left, above the
Trash Can).

The second method (Alternate Clicking) is even faster when you want to
delete several Configurations that are listed in a row, because you can
delete a whole range by Alternate Clicking and dragging. (But don't drag
too fast, as then it might skip over some Configurations.)

To DELETE A RANGE OF CONFIGURATIONS From The Configuration List: 
- Alternate Left Click on the first Configuration you want to delete 
- Keep holding down the Alternate key and the left mouse button 
- Slowly move down the list over all of the Configurations you want to
  delete 
- Each Configuration will be deleted as you move over it 
- Make sure you stop (and then release the mouse button) before you get to 
- a Configuration you want to keep

So, In our example, hold down the Alternate key. Left Click on the first
Configuration Slot (which isn't for the RX-I 1), drag the mouse until you
get to the Config just above the RX-I I Config, and let up on the mouse
button. Then Alternate Click on the first Slot after the RX-I I
Configurations, and drag to delete up to but not including the first FB-OI
Slot. Similarly, you can delete all the other Slots after the last FB-OI
Slot. It's easiest (and safest) to delete Configurations from one column
of Slots at a time.


Note: The Configuration List you're affecting while on this page is in
the computer's  memory only.  No changes arc permanent unless you Save the
new Configuration File to disk (described below). If you make a mistake
and delete a Configuration you didn't intend to, you can Exit the
Configuration List and Load the original Configuration File (F_YAMAHA.CNX
in this example) and start over.

At this point we have a Configuration List with only the four Configs we
want. But they are scattered all over the page. So the the next step is to
move these four Configs to more convenient positions.


To MOVE FROM ONE CONFIGURATION SLOT TO ANOTHER:  
- Press either Shift key and Left Click on a Configuration 
- You will see an outline around the Configuration (it will also invert) 
- Drag the outline to its new Slot 
- The destination Slot will be highlighted (inverse video) 
- Release the mouse button to Move the Configuration to that Slot 
- The destination Slot will be replaced by the new Configuration 
- The source Slot will be deleted (its name will turn to dashes)

If you decide after you start dragging that you didn't want to Move the
Configuration after all, just drag the outline so it's over the original
(source) Slot (make sure that it is the only Slot in inverse video) and
release the mouse button. The Configuration will be "moved to itself,
which has no effect.

Using this procedure, move the "RXI I Patterns" Config to the first Slot
on the screen, the "FB-O1 ram banks" Config to the third Slot. "FB-O1 all
configs" to the fourth Slot, and "FB-OI all" to the fifth Slot.  Leave the
second Slot empty as a "divider line" between instruments). The resulting
screen should look like this:



--------------------- 
Saving Configurations 
---------------------

Once you've Edited a Configuration File, you need to Save it to disk to be
able to use it again later.

To SAVE A Configuration File:  
- If you're on the Configuration List Page, click Exit OR press Esc to 
  return to the Main Screen 
- Select Save Configuration from the Edit menu OR press Alternate S 
  followed by C 
- Give a name to your file (the .CNX extension is automatically added) 
  Click OK

If you make changes to the Configuration List and you try to Quit the
program without having Saved the Configuration File, GenEdit will warn you
that your Configurations have changed, and give you a chance to Cancel the
Quitting process and Save the Configuration File. If you don't need to
save the changes, you can click Quit and exit the program.

To finish this example. Save the Configuration File you just rearranged
as FBO1RX11.CNX.



-------------------------------------------
Combining Configurations From Several Files
-------------------------------------------

In reality,  you  probably have instruments from more than one
manufacturer. Using the techniques described so far, you can simplify the
Configuration Lists for each manufacturer, but you would still have to
load a different Configuration File every time you wanted to save patches
from an instrument made by another company.

A more useful form of Configuration rearrangement is to combine the
Configurations for the instruments you have from several different
Configuration Files into one Configuration File. which will then be the
only one you'll have to load in order to save patches from any of those
instruments.

Let's extend our example by saying that, in addition to a Yamaha FB-O1
and RX-1 1, you also have an Ensoniq ESQ-M, as well as an obscure
instrument for which no specific Configuration is available but which can
be used with the "User Dump I" Config. So you want to combine any Configs
for those instruments with the ones you already put into your FBO1RXII.CNX
file. The Tool you'll need to do this is the Configuration Clipboard.

The Clipboard functions as a "stack", which means that what you put in
first you get out last and vice versa.  If you stack dinner plates in a
kitchen cabinet, you can only easily get at the top plate on the stack at
any given time. When you only have one plate, it is at the top and
bottom, so you can remove it instantly. Once you stack a second plate,
that plate is at the top. and you need to remove it before you can get to
the bottom plate. If you need to give the first dinner guest a red plate,
the second guest a blue plate, and the third guest a green plate (isn't
this a fun dinner!), you have to put the green plate on the stack first,
then the blue plate, and finally the red plate on top (so that you'll be
able to get at it first when the guests arrive).

The Clipboard is not erased when you Load. Save, or Edit Configurations,
so it can be used for gathering Configs from different Configuration Files
and then copying them into another Configuration File.

Back to our example. Load in the UTILITY.CNX Configuration File (on the
EXAMPLES disk) and Edit Configurations. Find the Slot named "User Dump 1
US1" and drag it to the Clipboard ("dragging to copy" is similar to
"dragging to delete", except drag it to the Clipboard instead of the
Trash Can).

Then you release the mouse button over the Clipboard, you will see the
number "01" appear there: this means there is now one item on the
Clipboard.

Exit to the Main Screen.  Load in the E_ENSONQ.CNX file and go to the
Configuration List Page.  Notice the Clipboard still shows "01": the "User
Dump 1" Config is still in there. The Configuration List shows several
different Configs for Ensoniq instruments: the two you're concerned with
are:
  ESQ-M programs     ESM 
  ESQ-M programs LIB ESL

First drag "ESQ-M programs" to the Clipboard; it will show "02". Then
drag "ESQ-M prograrns L!B" to the Clipboard: it will then show "03".

Now re-load your FBO1RX11.CNX file (Saved in the last exercise), and
select Edit Configurations. The Configuration list shows three FB-OI
Configs and one RX-11 Config. The Clipboard indicates your "03" Configs
arc still there. As a reminder, they are:

  ESQ-M programs LIB	  On the top (will come out first) 
  ESQ-M programs		  In the middle (will come out second) 
  User Dump 1             At the bottom	(will come out last)

To bring those Configs from the Clipboard to the Configuration List, drag
the Clipboard to a particular slot. The first time you drag to a Slot the
Clipboard will produce "ESQ-M progrms LIB", so drag to the Slot where you
want to place that. Then drag the Clipboard to the Slot where you want to
place "ESQ-M programs", and lastly drag it to the desired Slot for "User
Dump 1". You now should have a Configuration List with a total of seven
Configs on it, something like this (though, of course, the order you put
these last three Configs in may have been different):

If you don't like the order, you can, of course, now move the
configurations around within the List.

Note: You can interchange two Configuration Slots by dragging the first
Slot to the Clipboard, Moving the second Slot to the first Slot, and
dragging the Clipboard to the second Slot.

At this point, you have all the Configs you need in one Configuration
List (for use in this example studio).  If you wanted to keep this
Configuration File, you'd need to Exit to the Main Screen and Save
Configurations, under some appropriate name like MYSTUDIO.CNX: then every
time you run the program, you could load MYSTUDIO.CNX and be ready to save
data from any of your instruments.

Creating such a custom Configuration File is something you'll undoubtedly
want to do once you've completed this exercise. Just repeat the same steps
using configs for the instruments in your studio.

When creating a custom Configuration File, you may want to start with a
"clean slate" (empty Configuration List) rather than starting with some
particular Configuration File. There are two ways to clear the
Configuration List.

To CLEAR THE CONFIGURATION LIST (From The Main Screen):  
- Select Init Configurations from the Edit menu OR press Alternate I 
  followed by C 
- The Clipboard contents are not affected

To CLEAR THE CONFIGURATION LIST (From The Configuration List Page):  
- Click on ALL 
- You will see an outline around ALL (it will also invert) 
- Drag the outline to the Trash Can until the Trash Can color inverts 
- Release the mouse button to "throw ALL Configurations into the trash" 
- The Clipboard contents are not affected OR 
- Alternate Click on ALL

The following is a summary of Clipboard operations (operations using the
Window icons will be discussed in Chapter 4 -- Organizing Your Patches).


To COPY A CONFIGURATION TO CLIPBOARD:  
- Left. Click on a Configuration and hold the mouse button down 
- You will see an outline around the Configuration (it will also invert) 
- Drag the outline to the Clipboard until the Clipboard color inverts 
- Release the mouse button to copy the Configuration to the Clipboard OR 
- Left Click on a Configuration while holding down the Control key

A number will appear in the Clipboard showing the total count of
Configurations on the stack.  The Clipboard can contain up to 63
Configurations: any attempt to put another Configuration on top of a full
stack will be ignored.

You can also Move a Configuration to the Clipboard by Shift Left Clicking
on the Configuration and dragging. Moving is the same as Copying except
the Configuration is deleted from the slot; i.e. Move is exactly the same
as Copy followed by Delete.


To MOVE FROM THE CLIPBOARD To The Configuration List: 
- Click on the Clipboard 
- You will see an outline around the Clipboard (It will also invert) 
- Drag the outline to the new Slot 
- The destination Slot will be indicated in inverse video 
- Release the mouse button 
- The new Slot will be replaced by the Configuration from the Clipboard 
- The number of Items in the Clipboard will decrease by 1 (If the last Item 
  has been removed, the number inside the Clipboard will disappear) 
     OR 
- Click on the Clipboard while holding down the Control key 
- This moves a Configuration from the Clipboard to the first empty and
  unnamed slot. If there are no empty slots, or if all slots are named, 
  nothing happens.


To COPY ALL CONFIGURATIONS TO THE CLIPBOARD:  
- Click on ALL 
- You will see an outline around ALL (It will also invert) 
- Drag the outline to the Clipboard until the Clipboard color inverts 
- Release the mouse button 
- The number of items In the Clipboard will increase by the number of used
  Slots In the Configuration List (empty Slots are not copied when Copying
  ALL)


To MOVE ALL CONFIGURATIONS FROM THE CLIPBOARD to the Configuration List:
- Click on the Clipboard 
- You will see an outline around the Clipboard (it will also invert) 
- Drag the outline to ALL until ALL inverts 
- Release the mouse button to Move ALL the Configurations on the Clipboard
  to the Configuration List 
- The Configurations will replace empty Slots in the order that they occur
  in the Configuration List: Slots with Configurations will be unchanged


To CLEAR THE CLIPBOARD:  
- Drag the Clipboard to the Trash Can 
- An alert box will ask you to verify that you want to Clear the Clipboard
- Click Clear 
     OR 
- Alternate Click on the Clipboard



------------ 
AUTOLOAD.CNX 
------------

Once you've created a custom studio Configuration File, you can set It up
so that It will load into GenEdlt automatically, saving you the step of
having to Load Configurations each time you run the program, by saving the
Configuration File as AUTOLOAD.CNX.

If using floppy disks:  Place AUTOLOAD.CNX In the same dlrectory (on the
same disk and In the same folder, If any) where GENEDIT.PRG is.

If using a hard disk:  Place AUTOLOAD.CNX in the CONFIGS folder you
created (see Chapter 2 -- Getting Started). You must also set your User
Preferences Paths correctly (see Chapter 7) so that GemEdit will know to
look In the CONFIGS folder.

(Autoload files are discussed In more detail In Chapter 7 -- Additional
Features.)

More Ways To Manioulate The Configuration List

To NAME A Configuration:  
- Left Click on the first character of the name in the Configuration Slot 
- A cursor will appear over the character you clicked on 
- Type the new name (remember: make the last 3 characters the default file 
  extension) 
- You can put comments In a Configuration File by using names of unused 
  Configuration Slots (we suggest you don't use the last 3 characters in 
  this case so that you will be easily able to distinguish comments from 
  names of real Configurations)


To COMPARE Two Configurations:  
- Control Alternate Shift Click on the first Configuration 
- Its checksum and length will appear at the top of the screen 
- Make a note of these two numbers (the checksum may be positive or 
  negative; the length will always be positive) 
- Press either mouse button to continue 
- Repeat the same procedure for the other Configuration 
- The Configurations are the same only if the checksums and
  lengths match exactly

(Advanced note: It's actually a CRC, not a checksum. And there Is a
slight chance two different Configurations will have the same CRC: 1 In
65536!)


To COPY A CONFIGURATION From One Slot To Another: 
- Left Click on the Configuration you want to Copy 
- You will see an outline around the Configuration (it will also invert) 
- Drag the outline to the new Slot 
- The destination Slot will be indicated in inverse video 
- Release the mouse button to Copy the Configuration to that Slot 
- The new Slot will now contain a copy of the source Configuration 
- The source Configuration will remain unchanged

Note: There are no warnings on the Configuration List Page when you drag
Configurations (or empty slots) around. You can drag an empty slot or
Configuration to any other slot. (Copying or moving an empty slot to a
particular Configuration Slot does the same thing as deleting the
Configuration at that Slot.) The program will immediately overwrite any
existing Configuration with the Configuration you dragged. However, any
changes you make on the Configuration List Page are not saved to disk
unless you exit this Page and Save Configurations with the changes. If you
delete or overwrite a Configuration Slot by accident, you can reload the
Configuration File from disk and start again.


To PRINT A LIST OF CONFIGURATIONS:  
- Click on ALL - You will see an outline around ALL (it will also invert) 
- Drag the outline to the Printer icon until the Printer icon Inverts 
- Release the mouse button to print the Configuration List













                    ==================================

                          CHAPTER 3 A STUDIO SETUP

                    ==================================






                            In This Chapter:

                           - Studio Setup Basics 
                           - Global MIDI Options 
                           - Devices


























------------------- 
STUDIO SETUP BASICS 
-------------------

What Is A Studio Setup-

Most likely, you will use GenEdit in a "studio" situation where a number
of different instruments/devices are permanently hooked up. You may even
have a MIDI patch bay to automate the connections between your various
MIDI devices.

Using the Studio Setup capabilities of GenEdit, you tell GenEdit once
everything it needs to know about your studio. From then on, GenEdit can
talk to each device without you having to "re-educate" It every time.
Thus, the Studio Setup is a very valuable shortcut. While you can use
GenEdit without creating a Studio Setup, you'll enjoy the program much
more if you take a few minutes up front to "prepare" it.

The first thing to look at, which is related to (though not specifically
a part oO the Studio Setup, is the Global MIDI Options dialog box.



------------------- 
GLOBAL MIDI OPTIONS 
-------------------

The Global MIDI Options dialog box sets up the parameters for Thru,
MidIPlexer ports, MIDI speed, MIDI patch bay, and filters. You can get to
it in one of three ways:

To Select The Global MIDI Options Dialog Box:  
- Select Global Options from the MIDI menu 
    OR 
- Press Control 0 
    OR 
- Right Click on the MIDI icon

Note: The Port, Transmit Speed, and Filters settings are used as global
defaults, but can be over-ridden in the Studio Setup (see below) for
specific devices. The Thru and Patch Bay settings are global.



---- 
Thru 
----

The word thru means "in one side and out the other". This is true for
MIDI Thru as well; it passes events at the device's MIDI IN on to MIDI
THRU. On the Atari, however, there are only MIDI IN & OUT. To get around
this limitation, the OUT can be programmed in software to act as a Thru.
GenEdit has a switch to do just that.

Thru Enable is the first box you see at the top left of the MIDI Options
box. To turn Thru ON, click once on the Thru On button. It highlights.
(Click again to turn Thru OFF.)

Set channelizing by clicking inside the box below the On button. No
matter what channel comes IN, this channel is the one that the information
goes OUT on. (In the Editor, the Thru Channel is also used as the Play
Channel -- see Chapter 5.)

When using the MidiPlexer, you have a choice of two MIDI input ports
(Aand B) and four MIDI output ports. Click in the IN and OUT boxes to
select which input will be Thru'd to which output.

To Use MIDI Thru:  
- Select the MIDI Options dialog box 
- Turn Thru On (Click on the On Button) 
- Set the desired Channel by clicking inside the little square box 
  (Left Click to decrement. Right Click to increment) When using MIDI Thru,
  be sure you have the proper connections from instrument to instrument:
  MIDI OUT from the source keyboard to Atari MIDI IN: Atari MIDI OUT 
  to other synth or module MIDI IN.

Note: MIDI Thru is active throughout the prograin, except whenever
GenEdit is outputting or inputting MIDI (sending or receiving Banks,
sending parameter changes in the Editor, etc). lf GenEdit disables Thru
while you have a note held down, the note may get stuck". The Macro
assigned to Shift A (in the supplied Macros File) sends an All Notes Off
message on every Channel (not all instruments support All Notes Off,
however). Macros are discussed in detail below.



---- 
Port 
----

When using the MidiPlexer, you have a choice of two MIDI input ports (A
and B) and four MIDI output ports. Click in the IN box to select which
port will be used to receive data: click in the OUT box to select which
port data will be sent out on.

The Thru and Data port settings are independent.



-------------- 
Transmit Speed 
--------------

Some instruments can't respond fast enough to a steady stream of data.
Because of this, some instruments cannot keep up with GenEdit. Therefore,
there is a Transmit Speed feature to decrease the speed at which GenEdit
transfers information.


MIDI Transmit Speed can be set to one of 6 values ranging from normal
(fastest) to very slow.  Some instruments (for example, the DX7) cannot
keep up with the normal MIDI speed. For those (like the DX7) for which we
have Editing or Organizing Configurations, the Transmit Speed is
automatically set within the Configuration.   With certain Filing
Configurations, however, you may need to slow down the Transmit Speed. For
example, the User Dump Configurations can work with a wide variety of
instruments; some will work with the normal Transmit Speed but some may
require a slower one.

To Alter The Speed Of MIDI Transmission:  
- Select the MIDI Options dialog box 
- Click on one of the 6 boxes in the Transmit Speed Window 
- Far Left is FAST; far Right is SLOW



--------- 
Patch Bay 
---------

A MIDI patch bay, in conjunction with the Studio Setup features (see
below), automates the connecting of your instruments/devices to your ST. A
MIDI patch bay contains a number of MIDI inputs and outputs, and can
connect them in a variety of ways (usually selected by patch changes sent
to the MIDI patch bay).

For GenEdit to be able to talk to your MIDI patch bay, you have to tell
it where it is, and how fast it can handle data. In the Patch Bay section
of the Global MIDI Options dialog box, set the channel (between I and 16),
the output port the patch bay "listens to" (if you're using the
MidiPlexer), and the delay (0 to 255 milliseconds).

This delay is inserted between every pair of MIDI events sent to the
patch bay (in the Init or Exit String specified for each Device in the
Studio Setup see below).  Some MIDI patch bays are notoriously sluggish,
and won't respond correctly unless you insert a pause between MIDI
commands you send them. The delay amount may be documented for your MIDI
patch bay. or you may have to determine it by experimentation.




--------------- 
Receive Filters 
---------------

GenEdit can filter out certain MIDI messages during MIDI-to-Window and
MIDI-to-Disk operations.  The types of messages that can be filtered are:

Note Off Note On Polyphonic Key Pressure ("Poly Pressure" in the dialog
box) Control Changes ("Controllers" in the dialog box) Patch Changes
Channel Pressure Pitch Bend Real-Time (including Active Sensing)


To Toggle The Receive Filters:  
- Select the MIDI Options dialog box 
- Click on the box for the message type you want to filter 
- Highlighted means filtered 
- Unhighlighted means enabled

In general, the default settings (Real-Time and Controllers filtered) are
required for most onfigurations, and Configurations which require that the
filters be set differently set them as needed within the Configuration.
We suggest you not alter the Receive Filters unless you encounter a
problem. The Receive Filters do not affect built-in sequencer recording
(see Chapter 7 -- Additional Features).



------- 
DEVICES 
-------

Note:  Before setting up any Devices, you should already have created your
custom AUTOLOAD.CNX file (see Chapter 3 -- Congratulations).


The Studio Setup contains information for up to 60 Devices, which are
selected from a scrollable list in the center of the screen, 10 Device
Slots can be seen at any one time.



----------------- 
Clearing a Device 
-----------------

To clear all Devices, Alternate click on the word "DEVICES" at the top of
the Device List. If you have made any changes to the Studio Setup (ie, to
any Device), a prompt will ask you to verily that you want to Clear all
Devices. You can also clear all Devices by selecting Init Studio Setup
from the MIDI menu.



---------------- 
Editing A Device 
----------------

Note: When it is Cleared, a Device inherits its Port, Transmit Speed, and
Filters from the Global MIDI Options. After you change Global MIDI
Options, it's a good idea to reclear any blank Device before you edit it,
so that it will inherit the new MIDI Options settings.

To edit any of the parameters associated with a Device, Right Click on
the Device Slot. The Device dialog box will appear.

Set the MIDI Channel to your device's basic channel. If the MIDI Channel
for a Device is set to "--", no default channel will be assumed, and most
transfers to and from the Device will prompt you for the channel.  If the
MIDI Channel for a Device is set between I and 16, these prompts will be
skipped.

The data Port, Transmit Speed, and Filters are set just as in the Global
MIDI Options dialog box (see above). As just noted, these settings are
inherited from the Global MIDI Options whenever a Device is Cleared.

The Configuration Name is at the bottom right of the dialog box. When set
to "unknown" (indicated by all dashes), you will be prompted for this
Configuration each time you receive data from the Instrument. This can be
useful if, for example, you want to set up one Device for a particular
Instrument, but use It sometimes to fetch Patch data and sometimes to
fetch Combination data. (There is one drawback to this, however; see
"Using Studio Setups" at the end of this chapter.) If you want to return a
Device Configuration to this "unknown" state. Alternate Click on the
Configuration Name.

To select a Configuration for the Device, click on the Configuration
Name. A list of all Configurations currently in memory (most likely those
from you AUTOLOAD.CNX file) will appear.  To choose a Configuration,
scroll (If necessary) until you see it listed, then Left Click on it and
click OK (or just Right Click on the Configuration).

At the top of the dialog box is the Device Name (the name that appears in
this Device List). If it is blank when you select a Configuration, it gets
set to this Configuration Name (as much as fits). If you want to change
the Device Name, press Esc to clear it (or backspace) and type in the new
name.

Init String and Exit String are for MIDI patch bay users.  Each time data
is about to be transferred to/from a Device, the Init String is sent to
the Patch Bay port specified in the Global MIDI Options.  When the
transfer is completed, the Exit String is sent. The delay specified in the
Global MIDI Options is used before each MIDI Command Byte (in the range
hex 80..FF) as well as at the end of the entire String.

To Assign An Init Or Exit String:  
- Click in the box below "Init String:" or "Exit String:" 
- A block cursor will appear and the mouse buttons will become inactive 
- Type the MIDI String to be sent 
- Each character represents a nibble; each pair of nibbles is a byte 
- The MIDI String must be an even number of nibbles (otherwise a 0 nibble
  will be appended) 
- Use digits 0.. 9 and upper or lower case letters A..F for hex bytes 
- Use lowercase n for a nibble where the MIDI Channel is to be sent 
- For example, "Cn 05" sends a Patch Change on the current Patch Bay 
  Channel 
- When finished entering the MIDI String, press Return: the mouse buttons
  will become active again 
- Click where it says "click here to test" to send the String

Typically you'd use an Init String to connect the Device to the ST's MIDI
In, and an Exit String to connect your keyboard controller back to the
ST's MIDI In.



------------------- 
Rearranging Devices 
-------------------

There are 60 Devices, but only 10 Device Slots are visible at a time.
Scroll the Device List by clicking on the up or down arrow next to the
word "DEVICES". Left click to scroll by I (with mouse auto-repeat):  right
click to scroll by 10 (without autorepeat). To scroll by 10 using the
keyboard, press Control Up Arrow or Control Down Arrow.

Note the Device Slot Numbers, which are always I through 9 plus 0 for the
10th slot on the screen. These are used for key commands, referring to the
10 visible slots. Thus they don't change as you scroll through the Device
List.

To copy a Device, drag it to another slot. You can also copy a Device
using key commands; press the Slot Number you want to copy from, followed
by the Slot Number you want to copy to.

To Insert a blank Device, Control Left Click on a slot; all the Devices
below that will move down one slot (the 60th Device, If any, will be
lost). To delete a Device, Control Right Click on It; all the Devices
below that will move up one slot.




-------------------------------- 
Saving and Loading Studio Setups
--------------------------------

Once you've defined your Devices, you'll want to save your Studio Setup
to disk. Select Save Studio Setup from the MIDI menu. The default file
name Is GENEDIT.STU: use this filename unless you want to save multiple
Studio Setup files. To have GENEDIT.STU auto-load the next time you run
the program, save it to the same directory as GENEDIT.PRG. All 60 Device
Slots are saved In a Studio Setup file.

The MIDI menu also contains Load Studio Setup; you can use this to load
any .STU file, although GENEDIT.STU (or AUTOLOAD.STU) gets loaded
automatically each time you run the program. You get a warning if you try
to load a new Studio Setup file and there are Device changes you haven't
yet saved.



------------------- 
Using Studio Setups 
-------------------

The use of the Studio Setup will be discussed in the applicable contexts
in the next two chapters. In general, anytime you want to do a transfer to
or from MIDI, by telling the program to transfer to or from the specific
Device you will save several steps.

Also, when you load Data Files, the Studio Setup will be scanned to see
if the Data File's Configuration matches any Device's Configuration: if
so, the "context" (MIDI Channel, Port. Transmit Speed, Init and Exit
Strings, and Filters) from that Device will be used for the Data File
(whether it's loaded into a Window or sent directly to MIDI).  Note that
this can't work if the Configuration for a Device is set to "unknown";
GenEdit has no way of determining which Device matches that Data File
except by Configuration.

A bit of confusion can result if you use a Studio Setup, and at different
times have different Configuration Files loaded. If you try to transfer
data from a Device (to a Window or to Disk) and the Configuration for that
Device is not found in the Configuration List Slot where it was before,
you'll get this message:


If you think the Configuration for that Device is in the current
Configuration List, click Find and select the correct Configuration. If
the problem is that you have the wrong Configuration File loaded, Cancel,
Load the correct Configuration File, and start the data transfer again.










                     ===================================

                                 CHAPTER 4 
                           ORGANIZING YOUR PATCHES

                     ===================================




                           In This Chapter:

                           - A Tour Of The Main Screen 
                           - Moving Banks Around 
                           - Backup Files 
                           - Moving Individual Patches 
                           - Auditioning Patches 
                           - Multi-Block Files 
                           - Configurations Within Data Files 
                           - Library Files 
                           - Non-GenEdit/GenPatch Files

























------------------------- 
A TOUR OF THE MAIN SCREEN
-------------------------

Saving, loading, and organizing Patches Is done on the Main Screen, which
consists of a Left Window, Right Window, Device List, and column of icons.
The Left Window and Right Window function identically.  Certain
operations of the Device List (Including setting It up) are covered in
Chapter 3A -- Studio Setup.

Window Title Bar Vertical Scroll Bar Horizontal Scroll Bar Patch Number
Column Patch Name Column Disk Icon MIDI Icon Main Screen Clipboard Icon
Device List

As far as GenEdit Is concerned, a Bank Is the amount of data (number of
patches) that the program fetches from the instrument at one time.

(It is possible, however, for a Window to contain more than one Bank's
worth of data when using the Library function explained later in this
chapter.)

Also, the term "patch" is used in its most general sense a group of
parameters. It could be a single-voice patch, a multi-voice or split
definition, a set of performance parameters, etc.




------------------- 
MOVING BANKS AROUND 
-------------------

By clicking and dragging Main Screen objects (Icons) to each other, you
can transfer between Disk Files, MIDI, and either Window in any direction.
The diagram below shows the possible directions that data can be
transferred:

In general, Left Click on the object you want to transfer FROM, drag It
to the object you want to transfer TO, and let up on the mouse button.

If transferring from MIDI, you will be prompted for a Configuration.
Depending on the particular Configuration (and whether you are using the
Device List), you may be prompted for further Information such as the MIDI
channel.



--------------------------------------------- 
Saving a Bank of Patches From Your Instrument 
---------------------------------------------

The first thing you'll undoubtedly want to do Is save the patches you
already have in each instrument.

To Transfer FROM MIDI TO DISK:  
- Select Load Configurations from the Edit menu 
- Select the Configuration File containing your Instrument's Configuration
  There are 3 types of Configurations: Editing, Organizing, and Filing. If
  an Editing Config for the instrument Is available, use that.  Otherwise,
  if an Organizing Config if available, use that. If neither of these Is
  available, use a Filing Config.  See Chapter 3 -- Configurations -- for
  descriptions of each type of Config.
- Click OK - Left Click & Drag the MIDI Icon to the Disk Icon until the
  Disk Icon Inverts 
- Click once on the Configuration for the instrument you're using  (if it's
  already highlighted, you can press Return to select it) 
- The Main Screen will reappear, with an Info Line appearing at the top 
- If prompted for a MIDI channel, type the channel number then Return
- The Receive Indicator flickers as it shows MIDI data being received 
- When the transfer is done, the gong sounds and the file selector appears 
- The default name FROMMIDI.ext appears, where "ext" Is the 3-character
  extension that appears at the end of the Configuration name 
- Type a l-to-8-character name.  You can choose another extension 
  (signing the type of file you're saving) if you wish, but we recommend 
  you use the default extensions so that you can recognize different 
  Instruments files at a glance. In any case, DON'T USE THE LAST 3 
  CHARACTERS TO MAKE AN 11-CHARACTER NAME!  
- Click OK to save the file to disk


If You Have Created A Device List:  
- Left Click & Drag the Device you want to transfer from, rather than 
  dragging the MIDI Icon 
- If the Device has a Configuration defined, you won't be prompted to 
  select a Configuration now

If the instrument is not responding (perhaps because you don't have the
MIDI cables hooked up properly, or you didn't specify the right MIDI
channel), you won't see the Receive Indicator flashing. 

In that case: 
- Press Control A (for "Abort") on the ST keyboard 
- A dialog box appears: "Key interrupt. What do you want to do?" 
- Click Stop - Another dialog box may appear: "Received data may be 
  incomplete." 
- Click Discard

Check your MIDI cables, channel setting, choice of Configuration, etc,
and try the transfer again.

Some instruments don't have specific Configurations made just for them.
Instead, those instruments generally tend to work with one of the two User
Dump Configurations supplied in the UTILITY. CNX Configuration File. User
Dump I will capture a single SysEx message from the Instrument; User Dump
Many will capture as many SysEx messages as the instrument sends In a
row. You may need to experiment to determine which (if either) of the User
Dump Configurations Is more appropriate for the particular instrument
you're using (User Dump I is easier to use, but User Dump Many, works in
more cases).

Some Filing Configurations (often marked "usend" meaning "you send")
require you to initiate the transfer from the instrument's front panel.
The User Dump I Transfer steps will most likely apply to these
Configurations as well.

The Receive Indicator flickers as MIDI data is received  When the
transfer is done, the gong sounds and the file selector appears  Type a
name for the file  Click OK to save the file to disk

To Transfer MIDI TO DISK USING USER DUMP 1:  
- Select Load Configurations from the Edit menu 
- Load the Configuration File UTILITY.CNX (on the EXAMPLES disk) 
- Left Click & Drag the MIDI Icon to the Disk Icon until the Disk Icon 
  Inverts 
- When prompted for a Configuration, choose "User Dump 1" 
- The Main Screen will reappear, with an Info Line appearing at the top 
- Initiate the transfer from the instrument's front panel (use BULK DUMP or
  some similar function) 
- The Receive Indicator flickers as MIDI data is received 
- When the transfer is done, the gong sounds and the file selector appears 
- Type a name for the file 
- Click OK to save the file to disk

To Transfer MIDI TO DISK USING USER DUMP MANY:  
- Select Load Configurations from the Edit menu 
- Load the Configuration File UTILITY.CNX (on the EXAMPLES disk) 
- Left Click & Drag the MIDI Icon to the Disk Icon until the Disk Icon 
  inverts 
- When prompted for a Configuration, choose "User Dump Many" 
- The Main Screen will reappear, with an Info Line appearing at the top 
- Initiate the transfer from the instrument's front panel 
- When the Receive indicator stops flickering, press Control A 
- A dialog box appears: "Key Interrupt. What do you want to do?" 
- Click Stop - Another dialog box will appear saying: "Received data may 
  be incomplete." 
- Click Keep (you know the received data is in fact complete!) 
- The gong sounds and the file selector appears 
- Type a name for the file 
- Click OK to save the file to disk

Note: Some instruments cannot handle a full-speed data dump of the
maximum possible size. Thus Banks saved with User Dump Many may require
the Transmit Speed (see "Global MIDI Options" in Chapter 3A -- Studio
Setup) to be set to one of the Slower settings when Transferring back to
MIDI. Whether a Slower setting is needed (and which one) will depend on
the particular instrument and/or the size of the Data File.

Some Configurations may prompt you for a MIDI Channel.

Whenever PROMPTED FOR A MIDI CHANNEL:  
- During the course of transferring to or from MIDI, you may get the 
  following prompt:
- To use the pre-selected channel. Left Click OR press Return 
- To choose a different channel, type the channel number, then Left Click 
- To cancel the MIDI transfer. Right Click anywhere OR press Undo

When typing the channel number, if the number is in the 0-to-9 range, you
only need to type the single digit. If the number is in the 10-to-16
range, press Esc first, and then type the two digits.  Sending Patches
Back to the Instrument Once you've saved your patches to disk
successfully, you'll need to know how to send them back to the instrument.


To Transfer FROM DISK TO MIDI:  
- Make sure the ST's MIDI Out is connected to the Instrument's MIDI In 
- Make sure the instrument is ready to receive System Exclusive (SysEx 
  enabled, memory protect off, etc) 
- Drag the Disk Icon to the MIDI Icon (until the MIDI Icon color inverts) 
- Release the mouse button 
- When the file selector appears, choose the File you want to transfer 
- Click OK 
- If it is a proper GenEdit or GenPatch Data File, the Info Line will 
  appear (otherwise an error message will appear) 
- If it asks for a MIDI channel, type the channel number, then press Return
- Within seconds you should see the Transmit Indicator flicker as It shows
  MIDI data being transmitted 
- When the transfer is done, the Info Line will be replaced by the Menu Bar


If You Have Created A Device List:  Drag the Disk Icon to the Device you
 want to transfer to, rather than to the MIDI Icon

Note: Except for a few "Handshaking" exceptions (OUT to IN / IN to OUT),
GenEdit can't tell whether the instrument is receiving the MIDI data
properly, as it doesn't require the instrument's MIDI Out to be hooked up
to the STs MIDI In. This is so that for transfers to MIDI you don't need
to change MIDI cable hookups.

Also, you can abort a transfer to MIDI by pressing Control A then
clicking Stop, but if a transfer to a particular instrument was actually
in progress this may confuse the instrument. Thus we recommend you let the
transfer finish unless you know that the instrument isn't receiving
(perhaps because you chose the wrong channel, or the instrument isn't
turned on, etc).



--------------------------------------------------- 
Transferring Banks Using the Left and Right Windows
---------------------------------------------------

Rather than transferring directly between MIDI and disk, you can transfer
from MIDI to either Window, and between either Window and disk. Below are
lists of advantages to using the Windows as an intermediate step.

When using Organizing Configurations, You Can Use Windows To:  
- View the Patch Names 
- Rename Individual Patches 
- Move Patches around within a Bank 
- Move Patches between Banks 
- Send one Pateh at a time to the instrument

You can also use Windows to:  
- Load non-GenEdit data flies

These functions will be discussed in detail later In this Chapter, but
first let's explain how to get data to/from/between the Windows.  (You
should have already read the more detailed explanations of transferring
FROM MIDI TO DISK and FROM DISK TO MIDI above.)


To Transfer FROM MIDI TO EITHER WINDOW:  
- Connect both IN and OUT MIDI cables 
- Load the appropriate Configuration File 
- Drag the MIDI Icon to either Window Title Bar 
- If there was some data already In the Window, a dialog box will ask you 
  to confirm (by clicking OK) that you want to replace the Window contents
- Click once on the Configuration for the Instrument you're using (if It's 
  already highlighted, you can press Return to select It) 
- An Info Line appears at the top of the Main Screen 
- If prompted for a MIDI channel, type the channel number then Return 
- The Receive Indicator flickers as It shows MIDI data being received 
- The gong will sound and the Window Title shows the file name 
- If you are using an Editing or Organizing Configuration, then a list of
  Patch Names will appear in the Window


If You Have Created A Device List:  
- Left Click & Drag the Device you 
  want to transfer from, rather than dragging the MIDI Icon 
- If the Device has a Configuration defined, you won't be prompted to 
  select a Configuration now


Note: If there is only one Patch in the bank (as far as GenEdit is
concerned), no Patch Number will appear. A few instruments (for example,
the Alesis HR-16 drum machine) which have a variable number or size of
"patches", are treated in GenEdit Windows as having only one Patch, even
though you may be able to access multiple patches/patterns/etc when
Editing (see Chapter 5).

If the instrument is not responding, press Control A, then click Stop
followed by Discard.

If using a User Dump Configuration, use the above procedure, and initiate
the transfer from the instrument's front panel.


To Transfer FROM EITHER WINDOW TO MIDI:  
- Make sure the ST's MIDI Out is connected to the Instrument's MIDI In, 
  and the instrument is ready to receive System Exclusive 
- Drag the Window Title Bar to the MIDI Icon until the MIDI Icon inverts 
- Release the mouse button 
- The Transmit Indicator flickers as it shows MIDI data being transmitted 
- When the transfer is done, the Info Line will be replaced by the Menu Bar


If You Have Created A Device List:  
- Drag the Window Title Bar to the Device you want to transfer to, rather 
  than to the MIDI Icon


To Transfer FROM EITHER WINDOW TO DISK:  
- Drag the Window Title Bar to the Disk Icon until it inverts 
- Release the mouse button - The file selector will appear 
- The default name will be the same name as in the Window Title Bar 
- Press Esc and type a l-to-8-character name 
- Click OK 
- You will get a warning if you are about to replace a file by the same
  name; click Replace to replace it. Backup to back it up, or Cancel to not
  save the file


To Transfer FROM DISK TO EITHER WINDOW:  
- Drag the Disk Icon to either Window Title Bar until it inverts 
- Release the mouse button 
- If there was some data already in the Window that had been transferred 
  from MIDI or otherwise changed, a dialog box will ask you to confirm 
  (by clicking OK) that you want to replace the Window contents 
- The file selector will appear 
- If you dragged the Disk Icon to a Window which already had data in it, 
  the file selector will only show flies with the same extension as
  the Window. For example, if you have BUNDLDII.ESM loaded into a Window,
  and you drag the Disk Icon to that Window, the file selector will default
  to showing only .ESM files. If you want to load a file with a different
  extension, click the "*. *" button near the bottom, of the Little Green
  Selector (supplied with GenEdit), or Cancel and Clear the Window.
- Choose the Data File you want to transfer and click OK 
- If it is a proper GenEdit or GenPatch Data File, the Window Title Bar 
  will show the Data File name (see "Loading Non-GenEdit/GenPatch Files" 
  later in this chapter for what to do in other circumstances) 
- If the file was saved using an Editing or Organizing Configuration, then 
  a list of Patch Names will appear In the Window


To Transfer All Patches FROM ONE WINDOW TO THE OTHER:  
- Drag the Title Bar of the Window you're transferring FROM to the Title 
  Bar of the other Window (the one you're transferring TO) 
- Release the mouse button 
- Click OK to replace If there was some data already In that Window


To CLEAR A WINDOW:  
- Alternate Click on the Title Bar of the Window you want to Clear 
- A dialog box will ask you to confirm that you want to Clear all patches
  In that window; click Clear


To CLEAR BOTH WINDOWS:  
- Select Clear from the Windows menu OR press Control C 
- A separate dialog box will ask you to confirm that you want to Clear all
  patches in each window; click Clear "Dragging" Icons Using the Keyboard

There are key commands for the dragging operations between any two of:
the Left Window, the Right Window, the Disk Icon, the MIDI Icon, and
Devices.


    Icon           Key Equivalent
---------------------------------------
 
Left Window       Left Arrow 
Right Window      Right Arrow 
Disk Icon         Up Arrow 
MIDI Icon         Down Arrow 
Device            1 .. 9, 0 (the number to the left of the Device)


To "drag" using the keyboard, press the key (from the above list)
corresponding to the source, and then press the key corresponding to the
destination. For example, to load a Data File from Disk to the Left
Window, press Up Arrow followed by Left Arrow.



------------ 
BACKUP FILES 
------------

Any time an attempt is made to save a file that already exists, an alert
box appears containing three options: Replace, Backup, and Cancel. Replace
will save the new version over the original, destroying the older version.
Backup changes the extension of the original filename to .BAK, then saves
the new version under the original name.  For example, clicking on the
Backup option while attempting to save a newer version of a file called
MYPATCH.DX7 will first rename MYPATCH.DX7 to MYPATCH.BAK, then save the
updated version as MYPATCH.DX7. Note that If a .BAK file for a given file
already exists, selecting Backup will wipe out the old .BAK file. The
Cancel option aborts the storage process.

Note that if no extension is provided for a file being saved at any time,
the default extension for that file type will be used. For Instance, In
the above example, an attempt to name the file MYPATCH would result In a
file called MYPATCH.DX7.



------------------------- 
MOVING INDIVIDUAL PATCHES
-------------------------

Note: To be able to move individual patches around within a Bank or
between Banks, you must use an Editing or Organizing Configuration to
transfer from MIDI (An exception to this is described later in this
chapter).

Once you have a Window showing the names of patches, you can do much more
than just load/save/transfer the entire Bank.

Scrolling Around a Window

Each window can display up to 19 Patches at a time, and up to 18
characters of each Patch Name.

If the Instrument you're working with uses more than 19 patches per Bank,
you'll need to use the Vertical Scroll Bar to scroll through all the
patches. Click on the arrow at either end of the Scroll Bar to scroll one
patch at a time (if you hold down the mouse button it will repeat).
Click In the shaded area above or below the slider to scroll by 19
patches. Click and drag the slider to move to a particular point within
the Bank (dragging all the way to the top will show you the first 19
patches; dragging all the way to the bottom will show you only the last
patch).

If the instrument you're working with uses more than 18 characters
maximum In each Patch Name (for example, TX802 Performances have
20-character names), the Horizontal Scroll Bar will let you see 18
characters of the Patch Name at a time. At the far left position it will
show you the first 18 characters of the name; at the far right position it
will show you the last character only.



-------------- 
Window Locking 
--------------

When both Windows contain Patches, Shift Clicking on the vertical
sliders, vertical scroll bar, or vertical scroll arrows of either Window
forces the other Window to "lock" to the same vertical position In the
Patch list. Scrolling with the Shift key down will cause both Windows to
scroll in unison. This is a handy time saver when comparing two Banks of
Patches. (When the two Windows contain lists of differing lengths, the
"slave" Window will lock to the closest possible position.)



----------------- 
Selecting Patches 
-----------------

Before you do an operation such as Naming or Moving a Patch, you need to
Select the Patch so that the operation will know which Patch you want to
affect. Some operations work with only one Patch at a time; others can
work with a Patch Region (several Selected Patches In a row); still
others can work with All Selected Patches (whether In a row or not).

You can only have Patches Selected In one Window at a time. If you have
Patches Selected in one Window and Select a Patch In the other Window, all
Patches In the first Window will be Deselected automatically.


Selected Patches are displayed In inverse video (highlighted).


To SELECT A SINGLE PATCH:  
- Left Click on the Patch Name 
- The Patch Name color will invert, indicating the Patch has been Selected 
- All other Patches will be Deselected


To SELECT AN ADDITIONAL PATCH:  
- Shift Left Click on the Patch Name 
- The Patch Name color will invert, indicating the Patch has been Selected 
- Any Patches already Selected (in the same window) will stay Selected


To SELECT A PATCH REGION:  
- Shift Left Click on the first Patch Name you want to Select 
- While continuing to hold the mouse button down, drag the mouse over 
  the other Patches you want to Select 
- Release the mouse button when you've selected all desired patches

If you need to select more Patches than can fit in the Window at once,
you can Scroll Vertically then Shift Left Click on the next unselected
Patch to continue adding to the Patch Region


To SELECT ALL PATCHES III A Bank:  
- Control Click on any Patch Name In the Window


To DESELECT All Patches:  
- Left Click in an unused portion of the screen

Note: If you Right Click on a Patch Name you win enter the Editor
(described in Chapter 5 - Editing). To exit the Editor, press Esc or click
the Exit button.



---------------- 
Renaming Patches 
----------------

Many Instruments use a patch name for each patch. GenEdIt allows you to
change that patch name from the Main Screen.

There are also some instruments which don't use patch names In the
instrument (such as the Caslo CZ series, other than the CZ-I), but for
which GenEdit lets you use Patch Names. In this case, the Patch Name will
start out blank when you transfer from MIDI. You can name each Patch in a
Window using the procedure described below. If you save the Bank (transfer
from Window to Disk), then whenever you reload the Bank (transfer from
Disk to Window) you'll see the Names! Using this feature will make it much
easier to organize patches on these instruments.  


To NAME A PATCH:
- Scroll until the Patch you want to name Is on the screen 
- Left Click on the Patch Name 
- The Patch Name will invert, indicating the Patch has been Selected 
- Select Name from the Patches menu OR press N 
- A dialog box appears with the current Patch Name (and Patch Number) 
- Retype the Patch Name as desired (press Esc to clear the existing name) 
- Click OK 
- The new Patch Name will be displayed in the Window

For some instruments, lower case letters or special characters are not
allowed. In most such cases GenEdit will convert "illegal" characters to
ones the instrument can accept. Many instruments can accept a wide variety
of characters, but the instrument may display special characters
differently than the Atari ST displays them.  For example, what the Yamaha
DX instruments display as the Yen symbol, the Atari ST will display as a
backslash (\).

You can name more than one Patch at a time by either renaming each Patch
separately, or renaming multiple Patches to the same name.


To RENAME MULTIPLE PATCHES:  
- Select more than one Patch as described in "Selecting Patches" above 
- Select Name from the Patches menu OR press N 
- A dialog box appears with the first Patch Name (and Patch Number) 
- Retype the Patch Name as desired (press Esc to clear the existing name) 
- Click OK 
- The dialog box reappears for each successive Patch Name 
- If there's a Patch you selected you don't want to rename after all, click Skip 
- to go on to the next selected Patch 
- When all Selected Patches have been renamed, the Window will be updated 
- with the new Patch Names


To NAME MULTIPLE PATCHES WITH THE SAME NAME:  
- Select more than one Patch
- Select Name from the Patches menu OR press N 
- Type the new Patch Name to be used for all Selected Patches 
- Click All 
- All Selected Patches in the Window will be set to the new Patch Name

When renaming multiple Patches, if you change your mind  and decide you
don't want to rename the rest of the Selected Patches, click Stop in the
dialog box




-------------- 
Moving Patches 
--------------

You can Copy Patches within one Window or between the two Windows. You
can also Copy Patches to and from the Main Screen Clipboard. These
techniques allow you to rearrange the order of Patches within one Bank or
to copy Patches from one Bank to another.


To COPY A PATCH:  
- Left Click on the Patch Name 
- You will see an oufline around the Patch Name (it will also invert) 
- Drag the outline to another Patch until it inverts 
- Release the mouse button 
- The Patch you dragged will replace the Patch you dragged to

You can always Copy Patches within one Window. If both Windows contain
the same type of Bank (created using the same Configuration) you can also
Copy Patches between them. Copying between Windows containing Banks that
were created with different Configurations may be successful if the Banks
are compatible (for example, Casio CZ-1Ol/1000 patches are compatible
with Casio CZ-230S patches, although the Configurations are different
since the instruments have different numbers of patches per Bank).

In cases where the Patches in the two Windows are definitely
incompatible, GenEdit will issue a warning; we suggest you "chicken out"
in all such cases.


Advanced Note:  GenEdlt will Issue the warning If the GetPatch and
PutPatch segments are different between the Conflgs In the two windows.

It's possible that two Configs for completely Incompatible Instruments
with the same number of bytes per patch could have those segments
identical and the warning wouldn't be Issued; It's also possible for two
compatible instruments to have Configs that differ only in comments but
which would be enough to trigger the warning.


You can also Copy a Patch Group by Selecting and dragging a Group of
Patches. Only patches selected in a row can be moved in groups. For
example, if you select patches 3, 4, 5, 7, 8, & 11, then if you click on
either 3, 4, or 5 you will drag 3-5, if on 7 or 8, you will drag only 7
and 8, and if on 11, you will only drag patch 11.


There are two ways to Copy Patches between Patch Locations which are too
far apart to be displayed simultaneously in one Window:


To COPY A PATCH USING THE CLIPBOARD:  
- Drag the Patch Name to the Clipboard until the Clipboard color inverts 
- Release the mouse button 
- The Patch you were dragging will be placed on the Clipboard 
- Scroll until the Patch location you wish to Copy to is visible in the 
  Window 
- Drag the Clipboard to the Patch Name of the Patch you want to replace 
- Release the mouse button 
- The Patch on the Clipboard will replace the Patch you dragged to

You can only place one Patch on the Clipboard at a time, so this
technique may be time-consuming if you have many Patches in a row you want
to move. So you may want to use two Windows to make Patch Copying within a
Bank easier:


To COPY PATCHES USING TWO WINDOWS:  
- Drag the Window Title Bar to the other Title Bar 
- The two Windows now contain the same Bank 
- One Window is the Original Bank and the other Window is temporary 
- You can Scroll each Window to a different position 
- Use the above techniques to Copy individual Patches or Patch Groups from 
  the Original Bank's Window to the temporary Bank's Window

Note: In this case, the two Windows contain two sepanzte copies of the
same Bank. Changing the Bank In one Window will not affect the Bank In the
other Window. (This Is unlike the way the Marl ST Desktop works where you
see two views of the same data If you open two windows to show the same
directory).

You can also use the same procedure to Copy Patches between two different
Banks:


To COPY PATCHES BETWEEN DIFFERENT BANKS:  
- Load one Bank (from Disk or MIDI) into one Window 
- Load the other Bank into the other Window 
- Copy individual Patches or Patch Groups from one Window to the other
  Lastly, you can fill an entire Bank with copies of a single Patch.


To FILL AN ENTIRE BANK WITH ONE PATCH:  
- Drag a single Patch to the Window Title Bar

You can drag a single Patch to the same Windows Title Bar, or to the
other Window's Title Bar. If dragging to the other Window, a compatibility
check is made just as for Copying Patches between Windows.

Note: You cannot fill an empty Wlndow you can only replace all existing
Patches in a Window which already contains a Bank.



------------------
Exchanging Patches
------------------

It's easy to exchange Patches by using the clipboard.

To Exchange Two Patches:  
- Drag patch A to the clipboard 
- Drag patch B to patch A 
- Drag the clipboard to patch B Sorting Patches

All the Patches in a Window can be sorted alphabetically.


To Sort all Patches In A Window:  
- Select Sort from the Windows menu OR press Control S 
- If there are Patches in both Windows, select the Left or Right Window; 
  if only one Window contains patches, there will be no prompt 
- In a few moments, the Patches will be sorted

Sorting is in alphabetical order, with case (upper or lower) ignored.
Non-alphanumeric characters are treated as greater than alphanumeric, so
that weird patch names (for example, the default patch name of all dashes)
are sorted to the end of the Bank).



------------------------- 
Finding Duolicate Patches
-------------------------

GenEdit can find Duplicate Patches within each Window, as well as Patches
which are duplicate in both Windows.


To Find All Duplicate Patches In One Wlndow 
- Make sure there is only one Window with Patches. If you only want to 
  check one Window and there are Patches in the other Window, Clear the 
  other Window first.  
- Select Find Duplicates from the Windows menu OR press Control D 
- Select whether you want to compare Patches on the basis of just the Patch
  Name, just the Patch Data, or Both the name and data.  
- In a few moments, GenEdit will tell you whether duplicate Patches were 
  found 
- If duplicate Patches were found, they can be renamed so that you will be 
  able to spot them easily. Select whether you want to Link the names or 
  Init them.


To Find All Duplicate Patches In Botft Windows:  
- Make sure both Windows contain the same kind of Data. You generally 
  cannot compare Patches from completely different instruments, or 
  different types of data (e.g., Singles and Multi's) from the same 
  instrument. If the Windows can't be compared, you'll get an error message.  
- Proceed as with One Window above


To illustrate the difference between Link and Init Names, assume you have
Patches 3, 7, and 9 in the Left Window all with the name "Good Patch". You
tell GenEdit to Find Duplicates by Patch Name, and it finds them. If you
select mit Names, Patches 7 and 9 will get renamed to the default Patch
Name (usually all dashes: " -------  "). If you select Link Names, Patches
7 and 9 will both get renamed to "L  3", which means they used to have the
same Patch Name as Patch 3 in the Left Window. In either case, Patch 3
won't be renamed.  (The first occurrence of a Patch which has Duplicates
is not changed.)

If you were comparing both Windows, linking would produce names starting
with "L" for a Patch that was a Duplicate of a Patch in the Left Window,
and starting with "R" for a Patch that is a Duplicate of a Patch in the
Right Window.

Windows are compared left first; thus Linking can produce names starting
with "L" in the Right Window, but never a name starting with "R" in the
Left Window. If, for example, you get a file of patches from someone else,
and you want to compare it against your Library, load your Library into
the Left Window, and load the new file into the Righ.t Window.  Any
Duplicates will be shown in the Right Window; your Library in the Left
Window won't be altered.

Duplicate Patches can be determined by comparing Patch Names and/or Patch
Data. Comparing by Names is somewhat faster, but of course it's possible
to have Patches with the same Name that sound different, or Patches with
different Names that sound the same!

If, for example, you just got a lot of public domain patches, and you
want to see if some of them are renamed duplicates of others, you'd
probably want to compare only Patch Data first. (Comparing Both might lead
you to throw away two completely different Patches which different people
happened to name the same!) lint Names in this case. All the Patches you
end up with that have names other than all dashes sound different from one
another.

Once you know the Patch Data is unique, you may want to see if any
Patches (that originally came from different people) have the same name by
coincidence. Find Duplicates again, this type by Patch Name only, and this
time Link Names (if any Duplicates are found). You can then go listen to
the Patches that have Linked Names ("L" or "R" followed by the Patch
Number that had the same name), and make up new names for them.



--------------------- 
Printing a Patch List 
---------------------

If you have a printer, you can print a text list of all the Patches in a
Window.


To PRINT A PATCH LIST:  
- Make sure your printer is online and at the top of a page 
- Select Print from the Windows menu OR press Control P 
- Select which Window to print (Left or Right) 
- The Patch Numbers and Names will be printed in columns on a single page 
- The printer will form feed to a new page

If the printer is not responding (perhaps not turned on or not online)
you will get a chance to Retry (bring the printer online and click Retry)
or Cancel.

Once printing has begun, you can abort the print by clicking either mouse
button. However, the printer may not abort immediately. Most printers have
a buffer in which they store data about to be printed.  GenEdit stops
sending data to the printer's buffer; data already received by the
printer will continue to print.

When you abort a printout, the printer will not form feed to a new page.

Note: When you turn most printers ON, they assume that wherever the paper
Is at that moment Is the top of the page. If you turn the printer OFF when
it's In the middle of the page (for example, after aborting a Window
printout), then you'll have to manually reset the top of page when you
turn it back ON. If you always turn the printer off after a form feed,
and always use form feed (rather than the platen knob) to advance the
printer to a new page, you will never need to readjust the top of form
after set it initially.

Keeping a printed list of Patches for each Bank can be very handy, as you
can refer to it when working with a Bank to see all the Patches at once.

In the Window Options dialog box (select Options from the Windows menu],
if you highlight the box labeled "print window single columns", all
Patches will print in a single column, no matter how many there are in a
Bank. Otherwise, several columns will be used to conserve paper.



------------------ 
Window Information 
------------------

Each Window has associated Data Info (File Name, Data Size,
Configuration, and Template), which is listed in a dialog box which
appears when you Right Click on a Window's Title Bar:

- The Window Data Size should generally not be changed.
- The Window File Name Is automatically set when you transfer a Bank to
  the Window (from Disk, MIDI, or the other Window), but can be changed
  before saving the Bank to Disk.
- The Window Configuration is discussed later in this chapter
  ("Configurations Within Data Files"); when you view the Window Data Info
  dialog you can see the Window Configuration Name for reference, but you
  cannot change it there.
- Editing Configurations are linked to Templates, as discussed in Chapter
  5 -- Editing; when you view the Window Data Info dialog you can see the
  Window Template Name for reference, but you cannot change it there.


To CHANGE THE WINDOW FILE NAME:  
- Right Click on the Window Title Bar 
- The Window Data Info dialog box appears (the cursor is on the File Name
  field) 
- Type the new File Name (press Esc to clear out old name) 
- If you want to retain the previous extension (the 3 characters after the
  dot), you will need to retype it (you can see the old extension displayed 
  in the Window Title Bar while the dialog box is on the screen) 
- Click OK

Each Window also has associated Device Info (MIDI Channel, Port, Transmit
Speed, Filters, and Init and Exit Strings). To see or edit the Window
Device Info, select Info from the Windows menu (or press Control 1). If
there  is  data in both Windows,  select Left or Right Window when
prompted.

The Device Info for a Window is the same as the "context" part of a
Studio Setup Device definition. See Chapter 3A  Studio Setup  for a
description of these parameters and how to edit each.

The Window MIDI Channel is used to determine the default channel when
Editing a Patch, and is also used by certain Configurations to determine
the default channel when Auditioning Patches (described below).  (Some
Configurations remember the Channel if you specified it when you
originally transferred the Bank from MIDI.)

Note: The Window Device Info is reset whenever the Configuration in that
Window is changed. If you load consecutive Data Files created with the
same Configuration, the Window Device Info will remain valid. When you
load a Data File for a different instrument, however, the Window Device
Info is reset.

Be aware that "reset" can have two different meanings depending on the
Studio Setup. If the Window Configuration matches the Configuration for a
Device in your Studio Setup, the Window Device Info will be reset to that
Device's "context"; otherwise, the Window Device Info will be reset to the
Global MIDI Options




------------------- 
AUDITIONING PATCHES 
-------------------

There are times when you may want to try out individual Patches from one
or more Banks without having to load the whole Bank Into the instrument.
With most instruments you can achieve this by Auditioning a Patch:

To Audition A Patch:  
- Drag a single Patch from either Window to the MIDI Icon

	OR

- Point at the Patch 
- Press and hold the left mouse button 
- While holding down the left button, click the right button


If You Have Created A Device List:  
- You can drag the Patch Bar to the Device you want to transfer to, rather
  than dragging to the MIDI Icon 
- In most cases, holding down the left button and clicking the right will
  work just as well, because GenEdit will automatically determine the 
  correct Device to use based on matching Configurations

The way Auditioning affects the instrument will generally be In one of
two ways, depending on whether the Instrument has an edit buffer
accessible via MIDI.

If you are familiar with editing any synthesizer from Its front panel,
you probably already understand the concept of an edit buffer. On most
synths, when you start to edit a patch, you are not altering the main
patch memory but can in fact compare between the "original" (main patch
memory) and "edited" (edit buffer) versions of the patch. If you decide
you like the way the edited patch sounds, you can then decide to save It
to any patch location. If you don't save it, the edits are usually thrown
away when you select a different patch.

Unfortunately, while most instruments have such an edit buffer, on some
Instruments it is not possible to send a patch to the edit buffer via
MIDI. So how Auditioning a Patch in GenEdit will affect the instrument is
not so much dependent on whether the instrument has an edit buffer, but
on whether the instrument's MIDI implementation supports that edit buffer.

On instruments where the edit buffer is accessible via MIDI, all patch
locations in the instrument will remain untouched when you Audition
Patches, unless you take some action on the instrument's front panel to
specifically store the patch.

On instruments where the edit buffer is not accessible via MIDI, the
highest patch location in the instrument is used for auditioning, in place
of an edit buffer.  In this case, sending a single patch to the instrument
will REPLACE the patch in the highest location.

For example, on the Matrix-6/1000, patch number 99 is used in place of an
edit buffer: whatever is in patch 99 in the Matrix before you drag a Patch
from a Window to the MIDI Icon will be replaced by the patch you dragged.
You should make sure you have the patches in the instrument saved to disk
already before you start Auditioning Patches on such an instrument. See
the documentation supplied with a given Template (or Organizing
Configuration) for details on which supported instruments work this way.



------------------------------------------------- 
Window Options - Patch Change Sends Patch to MIDI
-------------------------------------------------

You can control Auditioning via Patch Changes from your MIDI keyboard, if
you wish. Once you set this up, you can go through a Bank of up to 128
Patches, listening to each Patch in the Bank without having to touch the
computer. Send Patch Change messages from your master keyboard to
GenEdit.  When GenEdit receives a Patch Change, it will send the
corresponding Patch to MIDI.

To use this feature, select Options from the Windows menu. At the bottom
of the dialog box is a section labeled "Patch Change sends patch to MIDI".
For each of the two main screen Windows, you can enable Patch Change
Auditioning, as well as determine whether Auditioning will occur in
response to Patch Changes on one channel only, or on any channel.

To enable Patch Change Auditioning for a given Window, click in its On
box so that it highlights. To set which channel that Window will respond
to, click in the box to the right of On and type In the channel number (01
to 16. or for "any channel").



----------------- 
MULTI-BLOCK FILES 
-----------------

Multi-Block Files are most often used to group together Patch Banks for
different Instruments.  These files can be thought of as "project files",
a group of various patches used on a project could be saved together,
then reloaded in one step for another session. Multi-Block Files can
contain as many Data Files as you want (limited only by memory). Each Data
File is first created by saving MIDI to Disk or a Window to Disk.


If the supplied Configuration only saves and loads one Bank at a time,
and the instrument has more than one Bank of patches, a Multi-Block File
could be used to keep multiple Banks together and allow you to send each
Block to a different bank on the Instrument in one operation.  Similarly,
in cases where there is more than one type of information to be saved from
the instrument  such as voices, performances, global parameters, etc.  A
Multi-Block File could be used to combine the different types of Data
Files created separately but which you always want to send back to the
instrument together.

Note to GenPatch ST Users: GenPatch ST (.MLT) Multi-Block files are not
compatible with GenEdit. If you want to use a Multi-Block file you created
in GenPatch, you will need to find the original separate GenPatch Data
Files (which GenEdit can load) and create a new (.MIX) Multi- Block File
within GenEdit.



-------------------------- 
Managing Multi-Block Files
--------------------------

You create a Multi-Block File by Adding to it. Like stacking up building
blocks to make a wall, you put together Multi-Block Files one Block at a
time, repeating the Add step for each Block.


To ADD A BLOCK To A Multi-Block File:
- Select Multi-Block from the File menu OR press Alternate M 
- The Multi-Block File Manager dialog box appears 
- Click Add OR press A 
- A file selector appears: "Select data file containing block to be added:" 
- Select a Data File 
- Another file selector appears: "Add block io which Multi-Block file-" 
- Select a Multi-Block File if you are adding to an existing one 
- If you are CREATING A NEW Multi-Block File:  
- Select the drive / folder where you want to save the Multi-Block File 
- Type the name of the Multi-Block File ("MLX" will be added) 
- Click OK - A dialog will prompt: "This Multi-Block file does not exist. 
  Create it-" 
- Click OK 
- The Multi-Block Manager reappears when the Block has been added 
- Exit the Multi-Block Manager by clicking Exit OR pressing Esc

Note: A Multi-Block File that contains just one Block is no different
from a Data File.

If there is an unnecessary Bank of Patches in a Multi-Block File, you can
Delete that Block from the Multi-Block File without altering any other
Blocks.

To DELETE A BLOCK From A Multi-Block File:  
- Select Multi-Block from the File menu OR press Alternate M 
- Click Delete OR press D 
- A file selector appears: "Delete block from which Multi-Block file?" 
- Select a Multi-Block File containing two or more Blocks

If the Multi-Block File you select contains only one Block, a dialog box
will remind you that the last Block cannot be deleted from a Multi-Block
File (use Delete File firom the File menu to completely delete a
Multi-Block File or any other type of file)


- A dialog box will list all the Blocks within the Multi-Block File,
  prompting: "Select the block to be deleted" 
- Click the Name of the Block you want to delete from the Multi-Block File
  (scroll if necessary) 
- The Multi-Block Manager reappears when the Block has been deleted


You can create a Data File that is a copy of a single Block within a
Multi-Block File by Extracting that Block, The Multi-Block File itself
remains unchanged by the Extract function.


To EXTRACT A BLOCK Fiom A Multi-Block File:  
- Select Multi-Block from the File menu OR press Alternate M 
- Click Extract OR press X 
- A file selector appears: "Extract block from which Multi-Block file-" 
- Select a Multi-Block File 
- If the Multi-Block File contains more than one Block, a dialog box will
  list all the Blocks within the Multi-Block File, prompting:  "Select 
  the block to be extracted" 
- Click the Name of the Block you want to extract from the Multi-Block 
  File (scroll if necessary)
- Another file selector appears: "Save block to what data file-" 
- The file name is the name of the block (it can be changed if desired) 
- Select the drive and folder where you want the Data File to be saved 
- Click OK 
- The Block is written to a separate Data File 
- The Multi-Block File you Extracted from is unchanged 
- The Multi-Block Manager reappears after the Block has been extracted

Other Multi-Block Manager functions let you rename a particular Block
within a Multi-Block File, or Replace a Block in a Multi-Block File with a
Block from another Data or Multi-Block File.  The Replace function
accomplishes the same thing as Delete followed by Add.


To RENAME A BLOCK III A Multi-Block File:  
- Select Multi-Block from the File menu OR press Alternate M 
- Click Rename OR press N - A file selector appears: "Rename block in which
  Multi-Block file?" 
- Select a Multi-Block File 
- If the Multi-Block File contains more than one Block, a dialog box will
  list all the Blocks within the Multi-Block File, prompting:  "Select 
  the block to be renamed" 
- Select the Name of the Block you want to rename
- A dialog box appears with the Block Name 
- Type in the new Block Name 
- Click OK 
- The Multi-Block Manager reappears after the Block has been renamed


To REPLACE A BLOCK In A Multi-Block File:  
- Select Multi-Block from the File menu OR press Alternate M 
- Click Replace OR press R 
- A file selector appears: "Replace with block from which data file-" 
- Select a Data File (or a Multi-Block File, in which case a dialog will
  ask you to select the Block to replace with) 
- Another file selector appears: "Replace block in which Multi-Block file-" 
- Select a Multi-Block File 
- If the Multi-Block File contains more than one Block, a dialog box will
  list all the Blocks within the Multi-Block File, prompting:  "Select the
  block to be replaced" 
- Click the Name of the Block you want to replace 
- The Multi-Block Manager reappears after the Block has been replaced



----------------------- 
Using Multi-Block Files 
-----------------------

If you transfer from Disk to either Main Screen Window and you select a
Multi-Block File, a dialog box will appear asking you to select the Block
to be loaded:

Click on the Name of the Block you want to load (scroll if necessary).
Only one Block can be loaded into each Window.

If you transfer from Disk to MIDI directly, all the Blocks in the
Multi-Block file will be sent in order.  There will be no pause between
Blocks, except for any prompts such as for MIDI channel. And, if you are
using a Studio Setup, many of these prompts may be skipped, because
GenEdit will try to match each Block to a Device on the basis of the
Configuration inside the Block!




-------------------------------- 
CONFIGURATIONS WITHIN DATA FILES
--------------------------------

Normally when you transfer from MIDI (whether directly to Disk, or to a
Window), a Data File is created (in memory, if you transferred to a
Window), containing both the Configuration you used and the Data that was
received. For simple situations, this is convenient: the Configuration is
stored in the Data File so that when you reload the file  to send it to
MIDI, to reorganize Patches, or Edit Patches -- you won't have to find and
load the matching Configuration.

But there are some situations where you need to attach a different
Configuration to a Data File than the one that was used to create it. And
if you are short on disk space, you may find it convenient to not store
the Configuration redundantly in every Data File.

Attaching a Configuration to a Window Let's say you save a Data File using
an Organizing Configuration for the instrument, and later you get an
Editing Configuration for the instrument. As long as the two
Configurations store the Data in the same manner, you can replace the
Organizing Configuration within each Data File with the new Editing
Configuration without having to transfer the Patches to the instrument
and back.


To ATTACH A NEW CONFIGURATION TO A DATA FILE:  
- Load the Configuration File containing the new Configuration 
- Load the Data File into either Window 
- Select Edit Configurations from the Edit menu 
- Left Click on the Slot with the new Configuration 
- You will see an outline around the Configuration (it will also invert) 
- Drag the outline to the Window Icon until it inverts 
- If you loaded Data into the Left Window, drag to the Left Window Icon 
  (above the Clipboard Icon) 
- If you loaded Data into the Right Window, drag to the Right Window Icon
  (above the ALL Icon) 
- Release the mouse button 
- Click Exit or press Esc to return to the Main Screen 
- In a few seconds, the Patch Names in the Window will be displayed again 
- You must save the Data File to disk if you want the new Configuration to
  be permanently attached to the file



--------------------------------------------- 
Window Options - Load/Save Configuration/Data 
---------------------------------------------

Let's say you want to save lots and lots of data flies onto one disk,
especially a floppy disk. Obviously, you'd want these flies to be as small
as possible, right.  Normally a GenEdit Data File contains a complete copy
of the Configuration that was used to create It, which makes It more
convenient for later use, but which may make it take up much more room on
the disk. The problem is that you're saving the same Configuration over
and over again.

By using the Window Options command (in the Windows menu), you can
enable/disable the function which automatically saves the Configuration
within the Data File. These options affect transfers between Disk and
either Window, as well as from MIDI to Disk. The Load options affect
transfers from Disk; the Save options affect transfers to Disk. (However,
when transferring from Disk to MIDI, the Load options are ignored because
transferring Data without a Configuration or vice versa to MIDI would make
no sense.)

Here's one useful application: Save a Data File containing a
Configuration but no Data. Then save as many Data Files as you want
containing Data but no Configuration. Quit the program, and come back two
months later. Load the Data File that has a Configuration but no Data.
Set the Window Options to Load Data but not Load Configuration. You can
now load the Data Files that don't have Configurations, because each time
you load a Data File, the Configuration in the Window will be retained
from the previous file.  But remember to name the Configuration-only Data
File appropriately so that you'll remember two months later which file to
load first! If you load a Data-only file without having a valid
Configuration already loaded, the Data in the Window will be unusable
(unless you attach a Configuration to it, as described above).

Notes: If you save a Data File containing neither Data nor Configuration,
it won't have much use.  Also, if you save a Data File without a
Configuration attached, you will not be able to transfer it directly from
Disk to MIDI. All the Load and Save options default to the enabled state.
If you change some of them to disabled, remember to re-enable them when
you want to load and save "normal" Data Files (with Configuration and Data
both in one file).



------------- 
LIBRARY FILES 
-------------

GenEdit can set up a Library File containing up to 1024 Patches for a
single instrument.  (Patches from different instruments can not be put in
the same Library File.)

A Library File is a Data File with an unusual Configuration. These
Library Configurations are in the same .CNX file as the "normal" Editing
or Organizing Configs for a given instrument.  For example, the Ensonlq
Editing Configs File (E_ENSONQ.CNX on your EXAMPLES disk) contains three
"LIB" Configs in the second column that correspond to the three "normal"
Configs in the first column:

A Library ("LIB") Configuration is the same as an ordinary configuration,
but with no ability to Receive and Transmit Banks (because there is no
instrument that can transmit/receive 1024 patches per bank). The patch
numbering used by a Library File does not necessarily bear any
resemblance to the way the instrument numbers patches.


To SET UP A LIBRARY FILE:  
- Load the Configuration File containing the Library Config you want to use
  (E_ENSONQ.CNX in our example) 
- Drag the MIDI Icon to the Window where you wish to set up the Library 
  Bank 
- If there is already data in that Window, you may be asked if you want to
  Lose the changes made: if not. Cancel and save the Window to Disk first 
- You will be prompted to select a Configuration 
- Right Click on the "LIB" Configuration you want to use ("ESQ-M progrms
  LIB" in our example) 
- The gong will sound momentarily, but it can take a while for the Window 
  to get initialized with 1024 Patches 
- You'll know it's done initializing when the mouse changes from the busy
  bee back to the arrow 
- GenEdit creates an empty Library File (blank Patch Names) 
- You may want to rename all the Patches in this Bank to help you see where
  the Patches are (see "Renaming Patches" earlier in this chapter) 
- Save this file by dragging the Window Title Bar to the Disk Icon 
- The file you saved is a blank Library File


--------------------------
Ways to Use a Library File
--------------------------

You can:  
- drag Patches or Ranges of Patches between a Library File m one Window and
  a "normal" Data File in the other Window (assuming, of course, that the 
  two flies are for the same instrument) 
- drag individual Patches from the Library File Window to MIDI

You cannot:  
- drag an entire Library File from Disk to MIDI or from a Window to MIDI
  (It won't fit in the Instrument!)

Note: Only more recent Library Configs (such as those supplied with, or
sold for use with, GenEdit ST v2.0) can be set up by dragging the MIDI
Icon to a Window. If you have an older Config File where the Library
Configs don't work this way, you may need to look in the GenEdit 2.02
library for an updated CNX file.



-------------------------- 
NON-GENEDIT/GENPATCH FILES
--------------------------

There are, unfortunately, patch file formats out there other than
GenEdit/GenPatch. But in many cases GenEdit can load and save files in
these formats!



------------------------------ 
Loading Files in Other Formats
------------------------------

Transfers from Disk to either Window will accept any file format. Yes,
that means you can perform the useless action of loading your word
processor files into your DX7!  But, more significantly, you can load
flies saved from many other editors/librarians. Here's how it works: If
the file is not in a GenEdit or GenPatch format, a dialog appears.  In
this dialog box you can define the file format in terms of a header length
and a data length. The header length is the number of bytes In the file
before the first byte of actual SysEx data.  The data length is the number
of bytes of SysEx data.

If you do not know the file format and you suspect it may contain a
complete SysEx message, you can enable Find and click OK, which will cause
GenEdit to look for an $FO (hex) byte marking the start of data, and an
$F7 byte marking the end of data. If no $FO is found, there Is an error
message. If no $F7 is found, the data is assumed to be all bytes between
the header and the end of the file. The resulting GenEdit format file has
a simple Configuration called "Unknown Data Format" attached to it, which
causes the entire contents of the file to be transmitted over MIDI, until
the first $F7 is found or the end of the data is encountered (whichever
comes first).

If you think the file format may be in the same format as the Data
portion of a Data File saved with a GenEdit Configuration, disable Find
and click OK. The file will be loaded into the Window without any
Configuration. You can then Attach a Configuration to this Window: if the
Configuration you attached is an Editing or Organizing Configuration, you
can tell if the Configuration matches the file format, by whether the
Patch Names appear correctly in the Window.

The popular intercomputer-standard MIDIEX format (for single or
multi-string raw SysEx message from $FO to $F7) will work with the first
technique.  Several popular editors/librarians create files which work
with the second technique.

Note: GenEdit 2.02 includes a MIDIEX configuration with the .MEX
extension to differentiate RAW sysex files saved by other MIDI dump
utility programs. Once you have loaded a MIDIEX file into one of the
windows, you can attach the MIDEX configuration to it and save the file
to disk.

If you know or suspect that the file format is usable except that there
is a header at the start of the file, you can specify the header length to
be the number of bytes to be discarded, and the data length to be 0. When
you tell GenEdit that the data length is 0, it will automatically compute
the data length as the total length of the file minus the header length.
For example, any file uploaded from a Macintosh with Macbinary enabled
would need to lose 128 bytes of header (assuming that the file format
would have worked as stated above if it had been uploaded with Macbinary
disabled).

The information in the dialog box is remembered between subsequent loads,
making it easier to convert a group of files in the same format. (However,
If you load in a file in a different format, make sure you set the header
length correctly and the data length to 0  for automatic computation
again.) Note that after using the Find function, on the following load,
the header and data lengths will be filled in with the correct values. The
sum of the header and data lengths must be less than or equal to the
total file length.

Note: Once you have converted the file format successfully, you can turn
off the Load Configuration Window Option and repeatedly load additional
files in the same format to the same Window. Remember to turn Load
Configuration back on, however, when you want to load a file in a
different format.



------------------ 
Exporting Raw Data 
------------------

Export Raw Data in the Windows menu is a command which saves the data
from either Main Screen Window, without any GenEdit Information, We can't
make any promises, but in some cases this might produce a file that could
be read into another manufacturer's librarian program, (Of course, we
have no Idea why you might want to do such a thing!) The default file
extension (for a binary file) is .RAW. (You can also export to an ASCII
file, in which case the extension is .TXT.)

If both Windows contain data, GenEdit will prompt for which Window is to
be saved. If only one Window contains data, GenEdit will assume that that
Window Is the one you want to export. If neither Window contains data, the
command has no effect.

A Binary export is most likely to be of use to another librarian program.
The ASCII export may be of use if you want to look at the data yourself.

You can save a file in MIDIEX format by using the User Dump I
Configuration (in the UTILITY.CNX Configuration File) to transfer from
MIDI to the Window, and then Exporting Raw Data from that Window.

The same "other" file formats which can be loaded successfully as
described above using the documented non-MIDlEX technique (no Find, header
length of  0, Attaching an Editing or Organizing Configuration) are the
ones that Export Raw Data is most likely to work with. You can Export Raw
Data from the keyboard via Control X.









                         =============================

                               CHAPTER 5 EDITING

                         =============================







                              In This Chapter:

                              - Editing Basics 
                              - Preparing To Edit 
                              - The Editor 
                              - A Mind Of Its Own











-------------- 
EDITING BASICS 
--------------

The same flexibility for dealing with different Instruments applies to
editing as it does to organizing your patches. GenEdit can be "shown" how
to work as a patch editor for a wide variety of instruments and effects
devices. Just as a Configuration tells GenEdit how to "speak" the
language of the instrument, a Template tells GenEdit how to "look like" a
patch editor for a specific instrument.


As you can see, not only can Templates be adapted for the needs of
different instruments, but they can also take on different styles (text,
graphic, or various combinations of the two).



----------------- 
What Can You Edit 
-----------------

The term Patch, throughout this manual. Is used to describe a general
grouping of parameters that may have different names and different
meanings in different situations.

One very common use of Patches Is to define the way a synthesizer
produces a single sound. Some instruments call this a patch, others a
program, others a voice, others a tone, and so on. When you Edit this type
of Patch, you are changing a sound in the instrument.

But there are other common uses of Patches. For example, a GenEdit Patch
may in fact be something the instrument calls a performance,
configuration, multi, or split: that is, a definition of how to combine
existing individual sounds together (perhaps splitting them across the
range of the keyboard, or layering them, or assigning different sounds to
different MIDI Channels). When you Edit this type of Patch, you are not
changing a single sound, but the way sounds are used together.


Other uses of Patches might be to define "snapshots" of mixes In a MIDI-
controlled mixer, or to define effects device settings that you can store
in the effects unit for later recall.

GenEdit can address any of these applications within Its adaptable
Editing features. Even if you don't have all the supported instruments, we
suggest you experiment with editing Patches for Instruments for which
we've supplied sample Banks. Load in a sample Bank (on the EXAMPLES disk:
BUNDLDII.ESM or BUNDLDII.SQ8) and edit several Patches, looking over the
Editing Pages. Try clicking on numbers and moving sliders if you like
there's nothing you can "break", so experiment away!




-------------------- 
Learning How to Edit 
--------------------

Just as the purpose of a word processor Is to let you easily change what
you write, the purpose of an editor is to let you easily change patches.
But just as a word processor manual cannot teach you grammar or effective
writing style, so a patch editor manual cannot teach you how patches
should be constructed or how a given instrument functions.

This manual assumes that you also have a manual (or third-party book) for
the Instrument you want to edit which describes all the patch parameters
as they would be edited from the front panel. In some cases manuals for
instrument modules that have no front-panel programming capability may
not provide such information. In that case, we suggest you (a) contact the
instrument manufacturer to obtain a manual for the programmable version
(perhaps the keyboard version) of the instrument: and/or (b) obtain a
third- party book (i.e., one published by someone other than the
manufacturer) which describes programming the instrument. MIDI-oriented
periodicals also sometimes publish articles on programming specific
instruments.

Likewise, you may wish to read books or articles about synthesizer
programming in general. Many programming concepts are common to a variety
of instruments, though the terminology (and certain parameters) may change
from instrument to instrument, so manuals or books specifically detailing
the programming of each instrument you use are preferable.

This chapter will describe the general features of GenEdit which are used
in editing any instrument.  Documentation included with each template
covers any differences between the way an instrument front panel works and
the way the corresponding GenEdit Template works, plus possibly other
tips which may be of help to you in editing a particular instrument.  Some
Templates have a "help" Page (see "Selecting Pages" below) where they put
this information.




----------------- 
PREPARING TO EDIT 
-----------------

Files Needed for Editing

Editing involves two kinds of flies: Template Files and Configuration
Files. Configurations (described in Chapter 3) contain instructions that
tell GenEdit how to "converse" with an instrument: Templates define the
layout of the editing screens. Whereas up to 63 Configurations may be
contained within one Configuration File, there is only one Template in
each Template File. Thus, the terms Template and Template File are used
Interchangeably.


In general, the Template and the Configuration have to match for you to
be able to edit.  In some cases, there Is one Editing Configuration for
one Template, In other cases, closely-related instruments may be able to
use the same Template File even though you may need a different
Configuration for each of those instruments (perhaps because the
difference between the instruments is in how many patches they hold).  The
documentation supplied with each group of Templates should describe which
Template / Configuration combinations you need for each supported
instrument.

The graphic aspects of a Template (what the controls look like, how
they're arranged on the screen, etc) are independent of the Configuration,
so that you can make changes to the way the Template looks without having
to learn the CNX Language. (See Chapter 7A  Simple Changes to Templates &
Configurations.) Theoretically, different people could develop multiple
Template flies (differing in visual aspects) which would all be compatible
with the same Editing Configuration.

In addition to a Configuration and a Template, you also need a starting
Patch.  You can start either by fetching a Bank from the Instrument (as
described in Chapter 4) or by loading In a Bank of Patches from disk.


To PREPARE TO EDIT:  
- Load a Bank of Patches into Either Window (this Bank must have been 
  created with an Editing Configuration)

Data files created with GenEdit vl.l or later should already contain
Editing Configurations which are correctly linked to Templates.  (Linking
Is the mechanism by which GenEdit figures out which Template to
automatically load when using a Bank created with a given Configuration.)

However, if you just upgraded from GenEdit vl.0, and you have Banks you
created in vl.0, you must first convert these flies to use the current
Editing Configurations. This can be done easily by running CNXCHNG.PRG in
the UTILITY folder on the PROGRAM disk. Please read the CNXCHNG.DOC file
(also in the UTILITY folder) for further Instructions.

If you try to Edit using a Bank created with a v1.0 "Editing"
Configuration (or with an Organizing Configuration), you will get an error
message:



------------------- 
Entering the Editor 
-------------------

While you can load the Template ahead of time if you wish (described
below), you don't have to. As long as the Bank of Patches was created
using an Editing Configuration, GenEdit will automatically load the
correct Template when you Edit a Patch,


To EDIT A PATCH:  
- Right Click on the Patch Name 
    OR 
- Select a single Patch (by Left Clicking on the Patch Name) 
- Select Edit from the Patches menu OR press E

If the Template needed is already in memory, the Editor screen will draw.
In addition, the Patch will be sent to the instrument (just as if you had
dragged that individual Patch to the MIDI Icon on the Main Screen).

If the Template needed is not in memory, GenEdit will try to load it from
disk. If it finds it, the first Editor Page will appear In a moment. If it
doesn't find it, GenEdit will put up a file selector asking you to find
the Template File. This usually happens if the Template Is on another
disk (if you're using a floppy) or in a different folder (if you're using
a hard disk).

If the Template is on another floppy disk, insert that disk and (if using
the supplied Little Green Selector) click on the drive letter (A or B) to
display the contents of that disk. The file selector will only show you
the flies which match the Template File it's looking for; if you see no
files, that doesn't mean the disk is empty, it just means the Template
File needed Isn't on it.

If the Template is in another folder (or hard disk partition), select the
folder containing the Template.

Once you've found the Template File, select it and click OK (with the
Little Green Selector, you can just right click on the file name to select
and OK in one step). GenEdit will load the Template and display the first
Editor Page.

If you briefly see a message at the top of the screen which says "Scaling
template...", it simply means the Template is being converted to your
current screen resolution. See "About Template Scaling" below.

If you get an error message which says:

it means the Template you have loaded does not match the Configuration in
the Window containing the Patch you're trying to Edit.


If you get an error message which looks something like this:

it may mean the Template doesn't match, or it may mean there is an
Invalid value in a Patch, If you try several Patches from the same Window
and they all cause similar messages to appear, a mismatch is the likely
reason; in this case we recommend you click Cancel.

If only one Patch causes messages like this to appear, you can select
Skip to force each parameter to a valid value. (Clicking OK will force alt
parameters to valid values; this is equivalent to clicking Skip at every
such dialog.) Invalid values sometimes exist (even in factory patches)
because other patch editors may have created them, and the Instrument may
accept and store such invalid values in a patch (although it can't really
make use of them). You will also get an error message if there is not
enough memory to Edit.

Note: Editing within GenEdit is "destructive" in the sense that you have
to save the result of your editing back to the same Patch (in the Window)
which you Edited. If you plan to (or think you might create a new Patch
based on the one you Edit (but want to keep the unedited version also),
you should copy the Patch first, then Edit the copy.

Manually Loading Template Files While most of the time it's easiest to
just let GenEdit load the Templates for you automatically when you Edit a
Patch, you can load a Template manually.


To LOAD A TEMPLATE Manually:  
- Select Load Template from the Edit menu 
- A file selector will appear, showing you files with the .TEM extension
  (actually, TE followed by any third character) 
- Select the Template File you want to load and click OK


About Template Scaling

If you manually load a Template that was last saved on a monitor with a
resolution different from yours (color medium vs monochrome high), you
will see the following alert box:

If the Template is being loaded automatically,  the  message  "Scaling
template..." will briefly appear at the top of the screen during loading.

Scaling can take a few seconds, so if you always use a Template at the
same screen resolution, you can save time in the long run by saving the
scaled Template, using Save Template from the File menu. (If you wish to
make any changes to the Template's appearance, see Chapter 7A  Simple
Changes to Templates & Configurations.) As long as you don't switch
resolutions, the Template will not need to be scaled again.



---------- 
THE EDITOR 
----------


The Editor Info Line

At the top of the screen is the Edit Info Line. Here you can see, and in
many cases control, various aspects of the Editor.

The Exit button returns you to the Main Screen. If you made any changes
within the Editor, it asks if you want to Keep or Discard those changes.
If you Keep the changes, the Patch you edited will be replaced by the
changed Patch. If you Discard the changes, the Patch in the Main Screen
Window will be unchanged, but you will lose all the changes you made while
in the Editor. If you Cancel, you will remain in the Editor.

The Undo and Orig buttons are grey if you haven't made any changes, and
black if you have changed one or more parameters (since entering the
Editor, or since Undoing). You can only click on them when they're black.

The Undo button restores the Patch to the way it was before you started
Editing, but leaves you Inside the Editor. It asks you to verify whether
you really want to lose all the changes you've made.

The Edited button is highlighted when the Editor is showing you the
Edited Patch.  If you then click on it, the Original (before editing)
settings of all parameters will be displayed, and the Orig button will
highlight. You cannot Undo or Exit (or edit) while viewing the Original
Patch. Click on Edited to see the Edited Patch and resume editing.  There
are eight Pages in the Editor. Some Templates only use one Page, some use
several, and some may use all eight. The pages which are empty are greyed
out on the Editor Info Line. For example, in the picture above, only Pages
I and 3 are available.

Most Templates are organized in the following way:

Page 1 = entire Patch at a glance (in text form) 
Page 2 = certain parameters in graphic form (knobs, sliders, etc.) 
Page 3 = envelopes and filters displayed graphically 
Page 4 =	 "      "     "        "         "
Page 7 = envelopes and filters displayed graphically 
Page 8 = help screen

Most commonly, if there is an entire-patch-at-a-glance display, it is on
page 1: an envelope display, if present, is on page 3 ("E" backwards is
"3"!); and if a help screen exists it is on page 8. Not all templates fit
this pattern, however, and it's less practical to standardize other
displays.  The information supplied with a Template should document how
the Pages are used (if it's not obvious by looking at them).

To go to a particular Editing Page, simply click on the appropriate Page
number (between 1 and 8) in the Info Line. Numbers for empty pages are
grey, and clicking on them has no effect.

Note: If you exit the Editor on some page other than Page I, you will be
viewing that same Page when you later re-enter the Editor, unless a
different Template has been loaded in the meantime.  The Editor always
shows Page I the first time you enter it after a Template has been loaded.

Any screen can be printed using the built-in Atari function Alternate
Help. By pressing these keys, the current screen will print. With this in
mind, it is possible to create a patch sheet by printing the Editor Page
containing all patch parameters.

The Play button lets you play the sequencer from within the Editor. Right
Clicking on Play will always play the GenEdit Sequence (see Chapter 7
Additional Features -- for a description of the GenEdit Sequencer). If you
are running GenEdit under HybriSwItch and you also have MidiTrack ST
(SmpteTrack or EditTrack, v5.0 or later) loaded in memory. Left Clicking
on Play will play the MidiTrack ST sequence (just as if you had clicked on
Play within  MidiTrack ST). If MidiTrack ST is not co-resident under
HybriSwitch, either Left or Right Clicking on Play will play the GenEdit
Sequence.

As either sequencer is playing, the mouse turns into an eighth note. You
can abort sequencer playback by clicking either mouse button or by
pressing any key.

The Thru Channel determines what Channel the GenEdit Sequence plays on
(while you are in the Editor), This setting Is the same as the Thru
Channel in the Global MIDI Options, if Thru is enabled (see Chapter 3A
-Studio Setup). If Thru is disabled, the Thru Channel shows as dashes
(""").

To change the Thru Channel, Right Click on it to increment. Left Click to
decrement. Set it to dashes to turn Thru off.

If you are using the MidiPlexer, a miniature letter (A, B.C. or D)
appears next to the Thru Channel; this is the Thru Port (for output). This
is the same setting as the Thru Out Port in the Global MIDI Options.

Changing the Thru Channel or Port in the Editor changes it in the Global
MIDI Options and vice versa.


The Send button is discussed in "Updating the Instrument" below.

The Send Channel should be set to the Basic MIDI Channel used by the
instrument you are editing. This Channel setting determines where your
patch is sent as you are editing it.

The Send Channel is inherited from the Window MIDI Channel (if it was
set: see "Window Information" in Chapter 4). If it is Undefined ("--")
then most Configurations will prompt you for the MIDI Channel when you
enter the Editor and will set the Editor MIDI Channel accordingly.

If you need to change the Editor MIDI Channel,  Right Click on it to
increment, Left Click to decrement.

When you exit the Editor, the Window MIDI Channel is inherited from the
Editor MIDI Channel.

The Send Port cannot be set in the Editor Info Line. Instead, it is
inherited from the Window Out Port.  If you are using a MidiPlexer, we
strongly suggest you use the Studio Setup features (see Chapter 3A): this
way, you can set each Device once for the appropriate Out (Send) Port,
and not have to worry about it again.

The Patch Number and Patch Name are shown for reference only; they cannot
be changed on the Editing Page. If you entered the Editor without a Patch
selected. "(No Edit Buffer)" will be displayed instead of the Patch

Number and Name: in that case, you won't be able to save any changes you
make back to a Patch in either Window. If you accidentally selected Edit
from the Patches menu without a Patch selected and you get this display,
click the Exit button to return to the Main Screen, and select a Patch to
be Edited.

Some Templates are designed for Controlling rather than Editing purposes
and are expected to be used with no Patch selected: these are discussed in
Chapter 6 -- Controlling.



----------------------- 
Updating the Instrument 
-----------------------

It is possible, of course, to edit a Patch In the Editor without having
an Instrument hooked up, and then save the Patch back to a Bank in a
Window, on the assumption that the whole Bank will be later sent to the
Instrument.  But in most cases, you want to hear the changes you're
making to the Patch as you make them.

The Editor has two basic methods of updating the instrument as you change
parameters: either by Sending the entire Patch, or by transmitting a MIDI
parameter change for the individual parameter you've altered.  At certain
times, it's clear the entire Patch needs to be Sent (for example, when
you first enter the Editor, when you Undo, or when you switch between the
Edited and Original Patch). But as you're modifying individual parameters,
one method or the other may be preferable, depending on the instrument.
(Indeed, many instruments will only work with one or the other method.)

The method used by each Template Is designed into the Template. However,
if the Template depends on Sending the entire Patch, you can control how
often the Patch gets Sent. And if the Template updates each parameter via
a MIDI parameter change as you change a Control, you still have a way to
cause the entire Patch to be Sent.

If the Template uses Patch Sending to update the instrument, the Send
button will be highlighted in inverse video when you enter the Editor. In
that case:
 
- Auto-Send is on 
- The entire Patch will be sent when you:  
- Enter the Editor 
- Undo 
- View
- Original 
- View Edited 
- Finish interacting with any Control (described below) 
- Right Click the Send button


If you turn off the Send button (by Left Clicking on it):
 
- Auto-Send will be off 
- The entire Patch will only be sent when you:  
- Undo 
- View Original 
- View Edited 
- Right Click the Send button 
- Left Click the Send button to turn Auto-Send back on In general, it's
  most convenient to leave the Auto-Send on at all times, but if you are
  entering parameters from a patch sheet, for example, you may prefer the
  quicker response of turning Auto-Send off temporarily (turn it back on
  once you've entered all parameters).

If the Template uses MIDI Parameter Changing to update the instrument,
the Send button will be unhighlighted when you enter the Editor. In that
case:
 
- Auto-Send is off 
- The entire Patch will only be sent when you:  
- Enter the Editor 
- Undo 
- View Original 
- View Edited 
- Right Click the Send button 
- The parameter you change will be sent:  
- When you finish interacting with the parameter; 
    OR 
- Continually as you're interacting with the parameter 
- Which of these two methods is used depends on the Template, and may even
  vary from one Control to another

Note: You should not turn on Auto-Send in this case. Mixing MIDI
Parameter Monitoring with Patch Send Monitoring will only slow down the
operation of the Editor and possibly confuse the instrument.

To "finish interacting with a parameter" means to let up on the mouse
button, either in the case of mouse auto-repeat or in the case of clicking
and dragging.

In summary. Left Clicking the Send button toggles Auto-Send on or off,
while Right Clicking the Send button Sends the entire Patch once.

A very few Templates use yet another scheme:  They bypass GenEdit's
normal Send mechanism altogether, and instead provide custom Buttons on
Template Pages to send to the instrument. Very often this Is because they
want to give you the option to send part of the edited data at a time.

If the Template uses custom Buttons to update the instrument, the Send
button will be greyed out when you enter the Editor. In that case, you
can't turn on Auto-Send, and you can't Send using any of GenEdit's normal
features (Right Clicking on the Send button, pressing S, etc).



----------------------------------
Key Commands for Info Line Buttons
----------------------------------

Most of the Editor Info Line actions described above have key command
equivalents, which are as follows:


Button				Key Command
_____________________________________________
                   
 
Exit                    Esc Undo				      
Undo Orig vs Edited     Tab
1                       1
2                       2
3                       3
4                       4
5                       5
6                       6
7                       7
8                       8
Left on Play            Space Bar 
Right on Play           Alternate Space Bar 
Left on Thru Channel    Numeric - 
Right on Thru Channel   Numeric +
Right on Send           S 
Left on Send            Control S















                        =============================

                                  ADDENDUM

                        =============================







                           - User Preferences 
                           - Customizing Screen Colors 
                           - Autoload Files 
                           - Editing a Configuration










----------------
USER PREFERENCES
----------------

A number of user-adjustable settings can be saved by GenEdit. Some of
these (Global MIDI Options) have to do with your MIDI setup, others
(Paths) with how your files are organized on disk, and still others
(Window Options and User Preferences) with the way you like to work.


-----
Paths
-----

By saving Paths in the Preferences file. each time you load GenEdit, you
save time by not having to search for different files. Files can be found
either on a floppy disk or a Hard Drive. When you choose Set Paths from
the File menu, a display appears presenting a list of the different file
types:



To edit, click on the File Type button to the left of a path. You will be presented with a file selector and 
asked to find the relevant type of file.

To Set Paths:
- Select Set Paths from the File menu
    OR Right Click on the Disk Icon
    OR press Alternate P
- Choose the type of file to find
- Click on the drive designator or folder that holds these files
- Open folders until you get to where you want to save that type of data
- Click OK

The Set Paths screen returns, with your path setting listed. Repeat the
process for other file types. Once all the paths are set. Click OK to
return to the Main Screen.

Make sure you save Preferences (see below) if you want your Paths
settings to be permanent.


----------------------
Other User Preferences
----------------------

If you select User Preferences from the File menu. the following dialog
box will appear:

The Mouse Delay setting determines how long you have to hold down the mouse button after you click it 
before it starts repeating. The Mouse Repeat setting determines how often it repeats. Drag the slider to 
adjust.

The Default Data File name will be used every time you transfer from MIDI
(or from a Device).  If you want this to be something other than FROMMIDI
you can type in a different name. (The extension is always obtained from
the Configuration you use to transfer with.)

You can also toggle whether:
 
- A "gong" will sound after each MIDI transfer completes
- A "chaser effect" animates the outline of anything you're dragging
- You get the following extra warning when you Quit:
  (This is in addition, to the warning you will get if you have changed
  Window Data, Configurations, etc -- see picture under "Saving
  Configurations" in Chapter 3.)
- The mouse buttons invert (Left Button increments, Right Button
  decrements) within the Editor. (Note that this does not affect the
  Editor Info Line or any dialog boxes -- only Numeric, Text, and Knob
  Controls.)


----------------
Save Preferences
----------------

Once you have all of your Preferences set, you'll want to save them to
disk.

To Save Preferences:
- Select User Preferences from the File menu
- Click Save
- Name the file
- Click OK
- Click Exit to return to the Main Screen

If you want the Preferences to be loaded automatically each time GenEdit
runs, name the file GENEDIT.INF and store it in the same directory where
GENEDIT.PRG is run from.

Settings in the following dialog boxes are saved in the Preferences file:
Global MIDI Options (MIDI menu) Window Options (Windows menu) Set Paths
(File menu) User Preferences (File menu)


----------------
Load Preferences
----------------

Preferences (including Paths) are initially loaded automatically from the
GENEDIT.INF file. If GENEDIT.INF cannot be found, all Paths default to the
same path as the program (GENEDIT.PRG).  You can manually load a different
.INF file if you want.

To Load Preferences:
- Select User Preferences from the File menu
- Click Load
- Click on the preference file
- Click OK
- Click Exit to return to the Main Screen


------------------------------
CUSTOMIZING YOUR SCREEN COLORS
------------------------------

(Color Monitor)

The factory color settings are:
Black   Text
White   Background
Blue    Blotter
Red     Alternate

The supplied Templates have been designed with these colors in mind. You
can customize your colors, but you should be aware that many color
combinations will make some Templates harder to read. For example, some
Templates have Red text on a White background. If you change the Red color
to a light yellow, while leaving the background White, those Templates
will become less legible.  The screen colors are saved in the GENEDIT.P12
picture file. You can change the screen colors in any paint program that
can edit Degas-format files.


(Monochrome Monitor)
The factory color settings are:
White   Background
Black   everything else

The screen colors are saved in the GENEDIT.P13 picture file. You can
change the screen colors in any paint program that can edit Degas-format
files.


--------------
AUTOLOAD FILES
--------------

With so many different file types, working with GenEdit could become
tedious if it were not for a feature called file "Auto-Loading":

When you run GenEdit, it checks the disk for the following files, and if
it finds them, it loads them along with the program.

GENEDIT  .INF   (Preferences) contains your preferred working environment.

AUTOLOAD .CNX   (Configurations) contains Configurations for all the
                equipment you normally work with.

GENEDIT  .STU   (Studio Setup)  Contains your Device definitions.
AUTOLOAD .MAX   (Macros)        Contains your favorite Macros.
AUTOLOAD .TEM   (Template)      Contains your favorite Template.

AUTOLOAD .SQC   (Sequence)      Contains a Sequence for use while Editing
                                or Controlling.

If any of these files exist, they will be loaded. The GenEdit Program
Disk includes an AUTOLOAD.SQC with the opening notes from "Also Sprach
Zarathustra" (the theme from "2001").  If you do not wish this file to
load automatically, rename it to any name other than AUTOLOAD.

To Create An AUTOLOAD file:
- Save the file with the correct name
- Make sure it is in the same directory as GENEDIT.PRG (unless instructed
  otherwise elsewhere in the manual where that specific autoload file is
  discussed).

Note: If you hold down the Alternate key while the program is loading,
the AUTOLOAD files are not loaded and GenEdit uses default settings.



-----------------------
EDITING A CONFIGURATION
-----------------------

Configuration Segments
----------------------

Each Configuration is made of a number of Segments. A Segment is a separately-edited portion of CNX 
Code within a Configuration.  Different Segments have different purposes within GenEdit, and are 
executed at different times. The Segments and their basic functions are:

Segment                      Function                                                                                           .

Initialize      To set up overall pararneters of a Configuration
Receive         To receive a Bank of Patches to the Instrument          
Transmit        To transmit a Bank of Patches to the Instrument
GetPatch        To get a single Patch out of a Bank:
                (1) for displaying a  Patch  Name  In  the  Main  Screen
                    Window 
                (2) for copying a Patch (followed by the PutPatch Segment)
    
PutPatch        To put a single Patch Into a Bank:
                (1) for renaming a Patch In the Main Screen Window
                (2) for copying a Patch (following the GetPatch Segment)

MakeEdit        To turn a single Patch from a Bank into an Edit Buffer for:
                (1) Editing
                (2) moving to/from the Main Screen Clipboard
                (3) sending a single Patch over MIDI
                (4) Distorting/Randomizing/Averaging

UnmakeEdIt      To turn an Edit Buffer (created by MakeEdIt) into a single
                Patch that can be put Into a Bank

SendEdit        To send an Edit Buffer (created by MakeEdit) to the
Instrument:     (1) when a single Patch Is dragged to the MIDI Icon 
                (2) when a single Patch Is Distorted or Averaged 
                (3) when thatches are Averaged 
                (4) when the Patch needs to be Sent from the Editor

Validate        To execute CNX code when any EBDT Parameter is changed
                from the Editor

Common          To allow Tables needed by multiple Segments to be defined
                in just one place:  this  Segment is allvays  executed
                immediately before any of the other segments listed above
                (except Initialize)


The following table shows, for each GenEdit operation, which Segments are
executed (the Common Segment Is not specified explicitly; it always
executes right before any other Segment):


     Operation                  Segments executed                                                         .
-------------------------------------------------------------------------

Transfer MIDI to Disk               Receive

Transfer Disk to MIDI               Transmit

Transfer MIDI to Window             Receive

Display Patch Names
  in Main Screen Window             Initialize, then GetPatch once per 
                                    Patch In Bank

Transfer Window to MIDI             Transmit
Drag Patch from Window to Window    GetPateh. PutPatch

Drag Patch to MIDI                  MakeEdit, SendEdit

Drag Patch from Window 
  to Clipboard                      MakeEdIt

Drag Patch from Clipboard
  to Window                         UnmakeEdit

Edit a Patch                        MakeEdit

Send a Patch from within Editor     SendEdit

Changing an Active Control          Validate (and then SendEdit if Send
                                    is on)

Exit Editor, Keeping                UnmakeEdit

Distort                             MakeEdit. UnmakeEdit (also SundEdIt
                                    (If a single Patch is selected)

Randomize                           MakeEdit, UnmakeEdit (also SendEdit
                                    (If a single Patch Is selected)

Average                             MakeEdit per Patch, UnmakeEdit, 
                                    SendEdit 


Note: If the Instrument uses handshaking, the SysEx specs may seems to
indicate you need to use Receive commands within the Transmit and SendEdit
Segments. You should, however, use Wait commands Instead. See the
description of the Wait command in Appendix C for details



------------------------
The Configuration Editor
------------------------


Printing All Segments of the Configuration
------------------------------------------

Before you start editing a Configuration, you may find it useful to make
a printout of all the Segments that make up that Configuration.  On the
Configuration List Page, drag the Configuration slot to the Printer Icon.
The printer will form feed between Segments, and will skip page
perforations automatically.  The Configuration Name will be printed at the
start, and the Segment name will be printed at the start of each Segment.


Entering and Exiting
--------------------

When you Right Click on a slot In the Configuration List, you enter the
Configuration Editor. Here you can edit any Segment, and even move CNX
code between Segments.

The Configuration Editor is exited by clicking on the Exit button or by
pressing Esc.


The Segment Windows
-------------------

The Configuration Editor has two Segment Windows.  Any two Segments can
be displayed at one time, except that you cannot display the same Segment
in both Segment Windows at once.

Only one Segment Window is active at a time. The active Segment Window
displays its Segment name in black, while the Inactive Segment Window's
Segment name is shown in gray. To make the other Segment Window active,
click inside it (not on window border parts). To change which Segment the
active Window is displaying, click on the Segment name; a Segment menu
will drop down, allowing you to choose any Segment other than the one
displayed in the other Segment Window. (To make the Segment menu go away
without choosing another Segment, you must click on the current Segment
name at the top of the menu.)

Each Segment Window is scrollable both horizontally and vertically. If
you only need to look at one Segment at a time, and want to avoid having
to scroll horizontally to see long lines, you can Full the Window, by
clicking on its Full Box (the Inverse diamond to the right of the Undo
button).  If the Segment Window is already Fulled, you can return to a
two-window display by clicking on the Full Box again; in this case, the
active Window will become the left Window, even if it was the right
Window before you Fulled It.

You can print the Segment shown in the active Window by clicking on the
Print button at the left of the screen.

To clear the active Segment Window, click on the Clear button at the top
of the Window or press CIr/Home: a prompt will ask you to verify that you
want to clear the Window.


Compiling
---------

If you've made any changes Inside the active Segment Window, you can make
GenEdit "compile" those changes (checking for syntax errors In each line)
by selecting the other Segment Window, by clicking on the Segment name in
the current Window (to choose another Segment), or by exiting the
Configuration Editor (clicking Exit or pressing Esc). If an error is
found, the line containing the error will be highlighted, and the program
will prompt:


Press any key to acknowledge the prompt. You must correct the  error (or
Undo) before you can exit the current Segment. If you cannot fix the line
until later (perhaps after you look at another Segment or even another
Segment in a different Configuration), you can temporarily turn the line
into a comment by adding a semicolon (:) at the start of it.

If you want to Undo all the current changes to the active Segment Window,
click on the Undo button at the top of the Window or press Undo. You will
be prompted to verify that you want to Undo all changes.

Note: You can only Undo changes you've made since the last time the
Segment was complied.  Therefore we strongly recommend that you Copy the
Configuration to an empty Slot before editing the Configuration, so that
you can return to the original version of the Configuration if you spot
an error after compiling.


Typing CNX Code
---------------

To type CNX code into a Segment, display that Segment In the active
Segment Window, and Left Click at the position you want to start typing.
Then type away!

You can use a variety of key commands to move around and edit within the
Segment Window. The Arrow keys move the Text Cursor, Shift Arrow keys
scroll, and Control Left/Right Arrow keys take you to the beginning/end of
the current line.  Insert and Delete insert and delete a character:
Control Insert and Control Delete insert and delete a line.  Backspace
deletes a character to the left. See Appendix K -- Key Commands -- for a
full list.

The Configuration Editor Clipboard
----------------------------------

To cut-and-paste or copy-and-paste. Right Click on the frst line you want
to cut/copy, and drag the mouse down to the last line you want to cut/copy
(you cannot select lines outside the window). You can also Control Right
Click on a line to cut/copy from that line to the end of the Segment
(even if some of the lines are beyond (he bottom edge of the window). To
cut, press X: the lines you selected will be erased from the window and
put Into the Configuration Editor Clipboard. To copy, press C; the lines
you selected will be put Into the Clipboard, but will also remain in the
window. If you want to append to lines you've already put Into the
Clipboard, press Shift X for appcnd-ciil or Shift C for append-copy.

Once you have something in the Clipboard, the Paste and Clear Clip
buttons at the left of the screen turn black (they are gray when there is
nothing in the Clipboard). To paste the contents of the Clipboard before
the line the Text Cursor is on, click the Paste button or press Control
P. to clear the Clipboard, click the Clear Clip button or press Control C.
you will be asked to verify that you want to clear it.

The Configuration Editor Clipboard remains intact until you clear it,
even if you exit the Configuration Editor, Load or Initialize
Configurations, etc. Thus you can use the Clipboard to move portions of
CNX code between Segments, between Configurations, and even between
Configuration Files.


What to Do With It
------------------

Refer to Appendix C -- CNX language Guide -- for a description of all the
commands available in the CNX Language. Also, study the supplied
Configurations to learn how the CNX language can be used.

You can use the Configuration Editor both to make modifications to
Configurations we've supplied, and to create your own Configurations. The
next Chapter (9 -- How We Did It) explains, by example, how you would
create a Configuration and a Template for an Instrument which GenEdit
does not yet support.


MODIFYING A "BIG" CONFIGURATION'S BANK NAMES

Load the "Big" Configuration File.   Go to the Configuration List Page.
and Right Click the slot for the Instrument you are interested in. If the
active window in the Configuration Editor does not show the Initialize
Segment, Click the Segment name at the top of the window, and Click
Initialize on the menu (that drops down. There should be a series of lines
of CNX code something like tills:

FormatBank  'A'   64   1
FormatBank  'B'   64   1
FormatBank  'C'   64   1
FormatBank  'D'   64   1

These lines set up banks (four banks, In this example) with Patch Numbers
A1..A64. B1..B64, C1..C64, and D1..D64. For many applications, this maybe
quite acceptable, but there is an additional level of organization
available in a Library File. We didn't know what kind of patches you have
in your Library so we gave the banks generic names like A, B, C, and D.
but you could replace these names with more meaningful ones. For example;

FormatBank  'strg'   64   1
FormatBank  'orgn'   64   1
FormatBank  'perc'   64   1
FormatBank  'fx  '   64   1

Now you will have a bank with 64 positions available for string patches,
64 for organ patches, 64 for percussion patches, and 64 for sound effects.
Remember: Bank names are limited to four characters. But even with four
characters it's usually possible to create a meaningful bank name.

Let's say you don't plan to store many sound effects in your Library, but you do plan to store a lot of 
string patches. You could further modify the CNX code to read like this:

FormatBank  'strg'   128   1
FormatBank  'orgn'   64    1
FormatBank  'perc'   32    1
FormatBank  'fx  '   32    1

When you use this Configuration to generate a Library File, you'll have
128 positions available for string patches, 64 for organ patches, 64 for
percussion patches, and only 32 for sound effects.

At this point, probably the best thing to do (If you really want this
Library File), Is to go ahead and create the Library File by following the
instructions In Chapter 4 -- Organizing Your Patches.




----------------------------------------------------------------------------
                              END OF TUTORIAL
----------------------------------------------------------------------------



It is hoped that this tutorial provides enough information for the average
user to load, save, and  send  sysex files to your instruments and to
create a library of patches for your instrument, as well as edit them in
GenEdit.  

The Desk Accessory SysXpress included with GenEdit, allows you
to send sysex data files to your MIDI instrument from your desk top or
from within your  favorite sequencer program. SysXpress runs on all Atari
computers in all resolutions.


Final Note: 
GenEdit is a comprehensive program with many additional features not
documented here. This tutorial constitutes about one third of the complete
manual which was scanned from the first four and one half chapters of the
GenEdit version 2 manual. It lacks many screen shots of the original
manual that may  be helpful to some users of the program.

A complete manual will be available in PDF format, included on a GenEdit
2.02 CD. The CD will be available sometime in 2004. The manual contains
all screen shots and instructions on how to create your Templates
and Configurations using GenEdit's own CNX language. 

If you are interested in purchasing this CD, please contact Joe Hlifka
via e-mail at:

jhlifka@yahoo.com


I hope you Enjoy GenEdit 2.02

Joe Hlifka
Albuquerque, New Mexico
USA

