This is a control layout for any E-mu Systems sampler running eos 4.xx. It should work with version 3.01 and above actually, but there were extra options added in 4.xx such as more LFO waveforms etc, these extra parameters will have no effect on versions below 4.xx. testers and feedback will be great. I have tried it out and it seems to be working fine. Please remember that due to MD2 not being able to "receive" sysex in dumps (the only way Emu transmits values), its not possible to display the current values, I didn't find this a problem though, as I like to just "design" sounds. You'll always need the sampler front panel to edit the samples and create the presets anyways, as there is no sysex for this functionality. Please note, I dont consider this a limitation of MD2, as it goes well outside its designed scope of use, but newer users may not understand why it doesnt "track" changes via Sysex.
Points to note.
- Sysex on e-mu eos was done in a buffer "seperate" to the screen/front panel buffer. This means that you can easily edit a preset/voice/group/sample via sysex and the screen on the e-mu will not show the results of change until you go to that preset on the front panel.
- I have set the front preset control to change the E-mu presets with 3 actions. These are - change the preset on the E-mu front panel with a standard midi program change, select the preset in the sysex buffer, and also select the first voice "group" (group1) so that when you change voice parameters it applies to everything in that group.
- Remember to be careful with the Amplifier Envelope Release 2 Level. Any value greater than zero can at times cause the sample to infinitely loop. This is actually normal behaviour. The Amp envelope in the E-Mus was directly coupled to the VCA (no cord) so any modulation "virtual" voltage on the final release stage will essentially hold it open.
- The the whole setup is set to the default Sysex ID (System ID) of the Emu (00) so you can technically only edit one unit at a time. But, if you so desired you could setup a "hack" and use the Channel variable in the Sysex as a substitute for Sysex ID in each Sysex command, I may do this at a later stage. Im pretty sure the Emus receive all Sysex in Omni (edit : all sysex is "channeless", sorry, I've only recently fully read the midi spec docs). I only ever use one Sampler at a time so, I never needed that functionality.
Its confusing but heres how the selections work, this is E-mus spec, not my fault sorry. Straight from the E-mu document :-
These Selection Parameters are independant of what is selected from the front
pannel of the E4. Once you select something remotely, the only way to change
the selection is remotely, with a couple of exceptions. Any regular front pannel
editing can be done without affecting what was selected for remote editing.
A Preset Selection will always remain until you change it.
A Link Selection will remain until you select another Link, or if you select
another Preset, in which case no Links are selected.
Similar with a Voice, and Group Selection.
A Sample Zone selection will get reset if you select a new Voice or a new Preset.
So the selection goes in levels
- Level 0 Preset Selection
- Level 1 Group Selection
- Level 2 Sample Selection
- Level 3 Voice Selection
So if you select say a Voice, then all editing of Filters, Amps etc is applied just to tat voice, if you then select Group 1 then all editing is applied to any voice/sample in that group. Then a preset selection clears all and the preset becomes the selected sysex buffer. This is still beta but ill version it more as time goes on, although, Ive implemented nearly all the Sysex available in this version (except for some global midi parameters etc)
Usage tips ;-
- Make sure you move at least up and down once on the preset to make it select everything initially.
- When loading presets from Emu, if some things dont work correctly, unplug all the cords. Some presets have obscure cords hooked up that can modulate to full and prevent any movement.
- Although you can use it as a "playable" controller using the sysex, its still probably more stable/efficient in regards to midi data, to use the Midi controllers and cords hooked up to modulation points to play with values while jamming. This is now easy to do using the Midi Controller setup on the "Other" tab.
Happy sampling. Im working on an Akai S5000/6000 panel next, not sure how that will go.
Brett the dood