Tom,

As discussed, here are my initial thoughts on feature updates for
EZScore Plus.


I use a LOT of MIDI control information, as you know.  Especially
MIDI  VOLUME;  but  others  as  well  (Breath  Controller,   Foot
Controller, etc, etc).

It  seems  to  me  that you might be able to  have  some  way  of
allowing the user to 'map' the controllers to specific functions.
A  great  example  might  be the use of  MIDI  VOLUME  to  equate
CRESCENDOS  and DECRESCENDOS.  Similar to the way you  allow  the
user  to  map which keyboard controllers  affect  'inputting,'  I
would  like  to see a way to do likewise  with  other  controller
information.   Since  there _are_ some  repetitive  circumstances
(like crescendos), if one could choose which control data effects
which symbol, it would save great amounts of time.   Here's  some
possibilities I can think of right away:

 CRESC/DeCresc  can equate with MIDI VOLUME (a skew amount  might
be  helpful, ie, the lowest 'value' that will start a  crescendo,
and the highest value the will start a decrescendo).

 The above could also be BREATH CONTROL or FOOT CONTROL.  (ie, if
it was 'mappable' it would be best).

 ACCENTS (^ or >) could be equal to a velocity value GREATER THAN
X  (where X is set by the user, or defaults and is changeable  by
the  user).   I guess setting a "mid level" would  also  work  to
establish   what velocities would equate accent marks.   I  don't
have the slightest thought on how to handle staccato marks (".")
though! (grin).

  PITCH  BENDS  in  the sequences can  equate  EITHER  'falloffs'
or  'glisses'  (lines drawn up to or down from the note) if  they
are  so  'mapped' (ie, if the user "maps" the pitch  bend  during
auto-score,  it  will  put the 'lines' in for  the  user  in  the
appropriate   direction).   This  might  also   'disregard'   the
quantizing factor while auto-scoring ONLY in terms of the  PITCH-
BEND  use  (also assuming MIDI INPUT is not being used  and  only
auto-scoring will apply here).


 There  are other possibilities for handling  controller  data...
I'm sure YOUR imagination could run away with this... mine has.

And, you might even want a "don't use control data" option just
in case the user doesn't want to, or shouldn't...

On to other thoughts:   multi-part staves.  For instance, I  have
a 4 part trumpet section on ONE track of the sequencer, but would
like  it  auto-scored as 2 sections (so to speak).  It  would  be
nice  to have the program either ask or  automatically  determine
(probably not easy or accurate) how many parts to split, and then
take,  as an example, the UPPER 2 parts scored with UP STEMS  and
the LOWER 2 parts scored with DOWN STEMS on ONE STAFF.  Or, to be
able  to  use MORE than ONE staff to do the auto-score  but  with
source  from  only  ONE  sequencer  track.   (Same  principal  as
splitting the 4 parts into 2 but using 2 staves instead of  one).
As it is now, the user can "suggest" a low/high note, but  that's
not  the same as saying take the upper 2 parts, etc.    The  only
problem  I see here (other than programming!) is what to do  when
parts 'merge' into less parts (ie, 4 to 3 for xx bars, then  back
to  4),  or when all parts are unison (or  octave).   My  initial
thoughts  are to ask the user how to handle each  case  (unisons,
less parts, etc).


Lastly  (for  now  - grin), it would be nice to  have  a  "master
score," ie, the ability to mark (bracket off) groups like:
  Staff 1 & 2 are bracketed on the left margin/bar as VIOLINS I &
II,  for  example), or to at least be able to 'title'  the  staff
(TRUMPETS, BONES, etc).  While I can do that now using  free-form
TEXT symbols, I must place them IN the bar, as opposed to outside
the left of the first bar on each Staff.


Welp,  I  hope I've at least given you food for  thought.   These
suggestions  are  based on MANY hours of using  the  program  and
discovering 'needs,' or 'wants.'

I  still  think  it's  incredibly easy  to  use,  and  hope  keep
enthusiasm  (ie, I hope it sells like MAD) and that you  continue
to update this great program!


Thanks for the 'ear' !
                