Mike,
my commentary comes little bit later... And I will mention only negative
points :-)
> Here they are so far:
>
> 1) flash EEPROM software upgrade capability (as I develop new software
> you will all be able to download it and continue upgrading your Poly
> and EX800's as long as we keep developing new features).
> 2) Sysex single patch dump send and receive.
Will you use some temporary edit buffer for this function? It would be great
just for quick going thru the patches from some librarian without necessity
to write them into the memory. Only if I will decide to use some patch, I
can write it into the selected memory location.
> 3) All notes off panic button.
> 4) Omni On, Off or Auto on power up.
> 5) Keyboard MIDI TX channel selection (1-16 or no MIDI TX).
Not for EX800...
> 6) Joystick MIDI TX channel selection (1-16 or no MIDI TX).
Not for EX800...
> 7) Local keyboard control on/off.
Not for EX800...
> 8) Local joystick control on/off.
Not for EX800...
> 9) Extended playing range on/off (increases the playing range by two
> octaves while ignoring the parameters 11 and 21).
That means one octave more up and one octave more down?
> 10) Cascade mode (for when you have two Poly's or a Poly and an EX800.
> One unit plays odd notes and the other plays evens).
> 11) Cascade sync mode (the master unit sends sysex patch dumps to the
> slave as well as setting the Poly mode and program changes. This
> ensures that your slave unit plays exactly the same sounds as the master).
I suppose this function can be switched On or Off, sometimes it could have
sense to play the same music with different sounds, just for the effect or
fun (of course lot of such combinations have no use).
> 12) Portamento mono mode with slide rate parameter stored per patch
> (accessed by pressing the poly key twice).
There's no Poly key on EX800, how you will implement this?
> 13) MIDI controllers for setting Poly, Hold, Chord and Portamento.
Poly can be implemented rather as a Poly/Unison selector, so I would call it
Unison - in Poly the instrument will work normally, in Unison it will play
in unison (monophonically with all oscillators detuned if possible, detune
depth should be changeable).
> 14) a second LFO is now used to control the VCF MG.
I don't understand this. You mean one LFO will modulate another LFO? Here
you write "VCF MG" but below under 17 you use a term "LFO2 for VCF", I'm
confused what you mean.
> 15) Both LFO1 and LFO2 now have triangle wave, reverse triangle and
> square wave parameters.
> 16) Both LFO1 and LFO2 now have free running modes (so that they don't
> reset on note down events. They just keep cycling).
> 17) LFO2 for VCF has random mode.
So LFO1 is for DCO, LFO2 for VCF?
> 18) Poly mode is stored and recalled with patches.
That means Poly/Unison status?
> 19) MIDI controllers implemented for LFO1 rate, VCF cutoff and
> resonance depth.
Will you use for this Non registered parameters as implemented in the other
instruments (Yamaha, Roland...)? Standard setting is:
- LFO rate: CC 99 = 1, CC 98 = 8
- VCF Cutoff: CC 99 = 1, CC 98 = 32
- VCF Resonance: CC 99 = 1, CC 98 = 33
For last two you can use more simple way:
- VCF Cutoff: CC 74
- VCF Resonance: CC 71
I would prefer this.
> 20) Bend depth stored per patch.
>
> That's it so far.
>
> Mike.
>
Great work you are doing, compliments!
All the best.
Daniel Forro