View Single Post
Old 02-15-2016, 07:42 PM   #263
Human being with feelings
Join Date: Mar 2007
Posts: 328

pcartwright, I'd previously collected up the FRs in the past notation thread but it was overtaken by the release, so here's some things people had to say in that previous thread. Some of them are redundant, some are already implemented; I'll leave their relevance to your own (much better organized) feature list to your judgement.


Collected and organized from different threads - all essential core features for any score editor.


Key signatures: correct display of enharmonics, e.g. note number 48 A# correctly displayed as A# when in the key of F#, but displayed as Bb when in the key of F. In minor keys, the “leading tone” is preferred (e.g. in the key of Am (no sharps or flats), G# will be preferred by default over Ab)
Correct keys for transposing instruments - allow two views: transposing score/non-transposing score
Visual quantize (to help keep the score easy to read -
this is actually the same as: “interpretation mode” (aka “quantize view”): loosely played MIDI is “interpreted” by the score editor and displayed, i.e. notes that are a bit shorter or longer than a quarter note are displayed as a quarter note (instead of notated as say a triple dotted eighth followed by a 64th rest)
and: Played notes interpretation
and very close to: minimum rest duration setting... for having not too many rests popping up whilst editing, and for interpreting notes of imperfect length correctly. Ideally it needs to be variable too.
Option for continuous view (staves continue to move from left to right with no system break)
multiple staves/systems for editing and viewing
multiple midi channels in same item in the same staff (“voices” feature from Logic/Sibelius etc)
selection tool to draw a frame around an area which will then be insertable as graphic in an office-software like in logic audio 5.5win (copy & paste graphic export)
Printing (of course :-))
in piano notation (two stave), allow RH and LH to be on separate “voices” so the voices can freely cross the staves
note heads - for the moment, regular, X, slash with stem, slash without stem. Will post in more detail as time goes by.
decent complement of bar lines: regular; double; final; right repeat; left repeat; invisible
multiple endings for repeated sections (1st, 2nd, etc, but also user definable)
Tuplets (e.g defining if triplet 1/8 or 1/16 note)


Text in score assignable as midi event (text “arco” assignable to, say, a C0 for use as a keyswitch). Save-able *per instruments* (different instruments might require entirely different notes as a keyswitch to e.g. “arco”- say C0 for violin but C5 for double bass - it will make no sense to make these global). Maybe a save-able “instrument profile” that can be assigned to a track - bonus points for providing us with a way to export banks of these templates and share them with others (e.g. a Kontakt VSL Strings Template).
Formatting options to arrange bars (e.g. Sibelius - “keep bars together” i.e. they don’t break at line returns, and “line break” so you can impose them on bars
“cue notes” - ability to paste in a bit of notation from another track that will display in small “cue-size” for musicians to, say, follow along during rests.
Rehearsal letters (including “insert rehearsal letters at all double bars”. Dynamically recalculating would be great (insert A, B and C - now delete B, and rehearsal letter C should change to B).
page view with selectable page size
fields for inserting instrument names, Texts, hints, (images would be cool also :-))... this could be really spartan, like a notepad... nothing has to look shiny, but it would be cool to use the notation as a dirty sketchbook area...
settings for graphical representation (borders, sizes, spaces...)
When editing needing off-grid notes for midi, on grid for score (this may be the same as “played note interpretation”)
"MIDI does not contain the data such as note length (quaver, crotchet, etc) and placement in the bar in terms of musical notation. So when imported into a notation editor such as Musescore, the editor has to interpret this and place notes on the stave, and some of them do this incorrectly. However, this notation information will have already been established in the notation view of Reaper by means of 'visual quantisation'. So at this point, is it possible to take the note information not from MIDI, but from the notation editor "visual quantisation", and export this in XML format?”
more concise: MusicXML export is done from the alread-tidied notation view, NOT the raw MIDI. This may be self-evident.
kerryg is offline   Reply With Quote