Product Direction

Don't be fooled, ZoeOS is a functioning product as it stands - but to give you an idea of where we are going with the product in the short term, immediate plans for ZoeOS include:


Window position snapshots	[implemented]
Nested tab panel workspace	[implemented]
Previous session restore	[implemented]
Local disk sample auditioning	[implemented]
Toolbar for quick access to most common functions	[implemented]
Online help system	[implemented]
Auditioning remote samples and presets	[implemented]
Auto-mapping of samples	[implemented]
Implemention of keyboard short-cuts.	[pending]
Interactive graphical editors for building Realtime, Keyboard and Velocity Windows	[implemented]
Dockable palettes	[implemented]
Snapshots for individual sections such as the envelopes, cords, etc..	[pending]
More ZCommands (plug-ins or macros) and house-keeping functions	[implemented]
Peptalk functionality (ala EOSLink) with front panel <--> ZoeOS synchronization	[pending]
Undo capabilities for presets and parameters	[pending]
Further refinement of drag & drop capabilities	[implemented]

And sometime thereafter...

MacOS X and Linux versions.
Graphical and syncable multi-track midi sequencer tightly coupled with the Emulator multimode.
Sample editing inside ZoeOS.
Support for reading and writing REX2 and Recycle formatted files.
Midi sample dump (for non-SCSI connected PCs).
Virtual Emulators for offline editing.
External midi control of parameters.
The ability to toggle between the present tabular format and a graphical rotary/slider bank format.
Investigation into integrating ZoeOS with other music products.
EOS user-level scripting.
Integration with a LISP based algorithmic processor.
Other algorithmic tools.

^ top

Product Philosophy

ZoeOS was born from the production experience of Paul, the developer of ZoeOS, and came into being for a number of reasons:

To deliver what was for many years an absent industry first - a PC based editor that was fully designed for and focused on EOS.
To give the EOS user community the best hardware editing features on the market.
To fully leverage the remoting capabilities of EOS via tight integration between SysEx and SMDI.
To provide a stable and easily expandable EOS editor via state-of-the-art Java technology.
To drastically reduce the effort in cleaning up and organizing the EOS memory bank
via excellent house-keeping and drag & drop functions.
To enable the implementation of interfaces that encapsulate "macros" or "methodologies" for EOS.
To enable the implementation of a fully-functional non-midi dependent audio-sequencer inside an E4.