Introduction
|
- Release 3.2 has been a long work, with a lot of
new features. It exhibits a special focus on the
integration of the Tesseract public OCR to handle
all textual informations, and a significant
redesign of key processing steps
|
Distribution Changes
|
-
Examples: Included 2 PDF examples
(BrahWiMeSample.pdf and Dichterliebe01.pdf) by
curtesy of
Recordare. They demonstrate rather complex
measures in terms of voices.
-
Application: We have switched to the
Swing Application Framework, in order to use a
standard approach for such tasks as:
application lifecycle, resources, actions,
session persistency,... all in an
OS-independent way. This framework is bypassed
when Audiveris runs in batch mode.
-
EventBus: This event bus from Michael
Bushe has been added for notification of user
selections, using specific user event types.
-
PDFRenderer: The PDFRenderer tool has
been added to allow the reading of PDF images.
-
Tesseract: The opensource Tessaract OCR
is the engine for text recognition.
-
Tesjeract: Access to Tesseract C++
software from Java via a JNI bridge.
|
New Features
|
-
Barlines: Systems building and Measure
building have been redesigned, to allow easy
assignment or deassignment of a measure barline
by user interaction. The former BARS step is
now split into SYSTEMS and MEASURES steps.
-
Drag'n Drop: Audiveris now supports
drag'n drop features, dragging a image file to
the Audiveris main window loads the sheet and
perform a (customizable) default step.
-
Files: Files for Script, Score export,
Midi can be specified via "Save / Save As".
-
Image: PDF format has been added to the
collection of image formats that Audiveris can
load, thanks to the PDFRenderer companion tool.
-
Midi: The user now has the ability to
select and playback just a sequence of
measures, besides the whole score.
-
Notations: All raticulations such as
legato, staccato, accent, etc are recognized
and translated.
-
Patterns: After automatic glyph
recognition, a series of tests are gathered in
various glyph patterns to handle specific cases
(slurs, beams hooks, sharps, naturals, broken
clefs, imposed time signatures, etc). Thus the
PATTERNS step replaces the former CLEANUP step.
-
Parameters: All major score parameters
are gather in a single dialog box for quick
update.
-
Parts: Systems can now have different
numbers of parts from one system to the other.
-
Score Layout: The user can dynamically
change the layout of the score display, and
switch between a vertical layout (like the
original sheet) and a horizontal layout (more
like a timeline).
-
Score Rebuild: The user has the ability
to rebuild the score entities at any time. When
dealing with very large systems, one can also
disable the automatic score rebuild and perform
the rebuild manually later when the
modifications are completed.
-
Section Selection: Besides glyph
selection, the user can now select one or
several sections, thus building a glyph by
hand. This allows the splitting of glyphs at
section borders.
-
Copy/Paste metaphor: The user can copy a
shape from an existing glyph and paste it to
another glyph.
-
Similar Glyphs: The user can now browse
through a sequence of glyphs "similar" to a
selected glyph. This is helpful when dealing
with similar cases all around a music sheet.
The "similarity" is handled by a specific
Linear Evaluator since a Neural Network is not
linear at all.
-
Slots: Slots with insufficient margins
are looked for, because they may indicate a
too small slot margin value.
-
Steps: Some steps, the ones that follow
the SCORE step, are flagged as not mandatory
and can be re-performed at will. The user has
bow the ability to reperform (almost) any step.
-
System Boundaries: The boundaries of any
system area are now defined by broken lines,
that the user can modify by mouse movements.
This allows a more flexible definition of which
glyphs belong to a system.
-
Text: A whole hierarchy of text items is
now defined to precisely handle Lyrics as well
as Titles, Directions and the like. The actual
text content can be entered manually via the
glyph board and automatically via the OCR
mechanism.
|
Bug Fixes
|
-
Active Glyphs: Use of a reliable test for
detecting which glyphs are active in a system.
-
Beams: They do not divide the duration of
embraced notes when these ones are rests.
-
Message Log: The Log window now displays
all messages, including the ones that were
logged before the GUI was launched.
-
Local Browsing: The user is now able to
navigate to the Audiveris documentation stored
locally in the installation folder.
-
MusicXML Export: Fixed wrong order in
elements for lyrics item, which triggered error
messages in Finale. Also removed an xmlns:ns2
namespace which was legal but not accepted by
Finale.
-
Vertex removal: The removal of a vertex
sometimes led to a double removal attempt.
|
Known Issues
|
-
Injection: The user needs the ability to
directly enter score entities of his own. To be
addressed in the next release.
-
Parameters: Besides the generic
constants mechanism (accessed via Tools |
Options menu), we need a more user-oriented way
to deal with global parameters. The current
ScoreBoard is the first step in this direction.
|
Other Changes
|
-
Bus: Introduced the EventBus companion
tool, to replace the proprietary Selection
mechanism for handling the notifications of
user selections.
-
MusicXML: Upgraded the export step to
comply with the new JAXB binding of ProxyMusic.
-
Options: This huge tree / Table has been
revamped for better usability.
-
Script: All user actions that may impact
the resulting score are continuously recorded
in a script in memory, and any such action is
in fact implemented as an immediate execution
of the ScriptTask instance.
-
Threading: Multi-threading is given much
attention, using Brian Goetz JCIP annotations.
-
UML: Used the basic UMLet tool, which is
very convenient for simple UML drawings found
here and there in Audiveris doc.
-
Statistics: Added on Audiveris home page
a link to the Ohloh statistics about this
software. Cost is estimated a bit above 1
million $, just for the code ...
|