FUTURE PLANS
------------

        I still can't say how soon I'll have the new JVEDIT ready, but
here is a synopsis (as of sep, 2 - 1998).

        1) I've implemented dialog boxes like those in other MIDI sequencing
           programs that let you choose the input and output drivers for
           JVEDIT to use.  The original version uses the MIDI Mapper for
           an output driver, and opens every input driver that the system
           tells it is there.  So the new version won't depend on the MIDI
           Mapper, and will only open the drivers that have been specified.
           Your choices can be saved in the configuration file to be used
           each time you run JVEDIT if you so desire.

        2) I've added the ability to run the editor on patches that are
           in the Temporary Performance Patch buffers, in addition to the
           original ability to edit the patch in the Temporary Patch Buffer.

        3) The original version's blank initial window has been replaced
           with a Patch Selection area and a display of which patches you
           have loaded into the 8 possible Temporary patches (the Temporary
           Patch buffer and the 7 Temporary Performance Patch buffers).
           The Patch Selection area lets you load patches from any .SYX
           format file (and perhaps .MID files - if I put that enhancement
           in before release) that contains JV patches.  All patches found
           in the files are added to a list of patches that are displayed
           in a list box (new patches are always added to the end of the
           list when read from a file, but you can push a "Sort" button to
           alphabetize the list whenever you want to).  A few key parameters
           about the "Current" patch (the one that is selected in the list
           box) are displayed, such as the source of each wave (INT, EXP,
           PCM), which tones are active, what Reverb and Chorus algorithms
           are used, and perhaps some other details.  You can select any
           of the 8 JV Temporary Patches and transfer the "Current" patch
           into the JV at that location.  Selecting the Temporary Patch, or
           one of the 7 Temporary Performance Patches causes JVEDIT to
           switch your JV into Patch or Performance mode as necessary.  You
           can then press an EDIT button to edit the patch at that location,
           if so desired.

        4) Fixed a bug in the MIDI loopback code (actually in the MIDI input
           routines, but it only was apparent when loopback mode was enabled)
           that closed a small timing window where the program could get
           confused about the number of messages in its input buffer
           (essentially forgetting about one received message each time the
           bug occurred).  This was resulting in behavior such as the most
           recent note played would not sound until its key was released, or
           until another key was pressed, (if only one message got forgotten).

        And, thats about it for the next release.  I've got some plans
beyond that, but they could be a long time in the future (if I ever do
get to them).  This seems like enough of an enhancement to be worth
distributing, and something that I'll be able to get finished up soon.


Greg Youngdahl
Lucent Technologies  Naperville, IL
youngdahl@lucent.com


--- end of txt file ---