list of improvement (by Marc) to may be documented
I was wondering, could we make all pages about New Musescore 2.0 Feature as the list by Marc about the Beta 1 ... what do other think of it
Here it is
Here are some of the major changes you will find in MuseScore 2.0 Beta 1:
Linked parts - changes in score automatically reflect in parts and vice versa
Have been partially integrated in Exporting parts, not to be confused with linked tablature
http://musescore.org/en/node/36156#saving
Continuous view - scroll horizontally through your score with no line or page breaks
Done : here http://musescore.org/en/node/38436
Tablature - variety of tab notation styles for guitar, bass, lute, and more
http://musescore.org/en/node/7845
Fret diagrams - easily create diagrams and set up your own palette of commonly used chords
http://musescore.org/en/node/38086 Page created as Advanced topic , but not done
Flexible chord symbols - enter chord symbols using any common spellings, including support for German and solfege note naming and lower case minor chords
(in Layout and formatting, not done , and may be wrong placed)
http://musescore.org/en/node/35896
Dynamic text styles - changes automatically apply to all elements with that style
unprecised but here http://musescore.org/en/node/35951
More supported notations - support for Steinberg's new open source Bravura music font, more flexible time signatures, pedal change markings, grace notes after (trill endings), falls/doits/scoops/plops/bends, bagpipe embellishments, figured bass, ambitus, early music notations, and a huge set of additional music symbols from Bravura
Musical font have been named in http://musescore.org/en/node/35896#style-edit-general-style-score but unprecised are the possibilities ... (should a new page be done)
and some other specific pages http://musescore.org/en/node/37461(early music) http://musescore.org/en/node/15183 (figured bass) http://musescore.org/en/node/36016 (grace note after )...
Layout improvements - automatic correct positioning and spacing for multi-voice chords and rests, dots, accidentals, ties, articulations, hairpins, pedal markings, voltas, etc.
????
Score management facilities - create scores of multiple movements, combine scores into albums, define and apply custom score styles, select default styles for scores and for parts
Album , Layer, and Break and Spacer pages
Playback improvements - new and more realistic soundfont, mid-score instrument changes, playback of more score markings, flexible swing style, improved JACK support for interoperability with other MIDI and audio programs
soundfont, ....
MIDI import improvements - automatic simplification of rhythms, handling of multiple voices
Midi import (new feature)
MusicXML import/export improvements - greater compatibility with other applications, ability to control degree of layout preserved
???
Guitar Pro import - supports GP3, GP4, GP5, and GPX formats
Waiting to be done
Usability improvements - repitch mode, on-screen piano keyboard for note entry, element inspector window, more precise manual adjustments, easier selection of instruments, simpler and more powerful page layout, copy/paste improvements, split and join measures, screenshot mode for creating graphical excerpts, customizable palettes and workspaces, expanded availability of keyboard shortcuts
Inspector, Copy paste improvement , and other may have been integrated other I don't know ...
And lots more!
Comments
FWIW, what I always envisioned is a version of that list with more detai, but not exactly in a "Handbook" type format (showing how to do it). Instead, I was picturing somethiung like the "Tour" I put together a while bsck for the main page of musescore.org that basically just shows off the features with illustrations. More "marketing" than "documentation", I guess.
But clearly, all those new features need to be documented, and having a Handbook heading called "New Features" that lists the features and takes you right to the respective Handbook pages for each makes sense (in addition to having those features listed under whatever other headings it makes sense to list them under).
In reply to FWIW, what I always by Marc Sabatella
I think that it was what I meant
so this list could be usefull to know new things to be documented ;)
In reply to I think that it was what I by Zynette
Go ahead with the documentation Lamardelmy. Doing good!
In reply to Go ahead with the by Thomas
Thank you Thomas,
I don't think that is perfect but i'm doing my best ;)
In reply to Thank you Thomas, I don't by Zynette
It's doesn't need to be perfect. Any start is a good start, as it will inspire others to step up and improve your work.
In reply to It's doesn't need to be by Thomas
page about mid staff instruemnt change done
[node:39041]