I just uploaded another release with fixes for all bugs reported
recently...
0.1.18-alpha
* libfomus: fixed erroneous measure integrity check
* libfomus: improvements in module scheduling
* untie: new module that removes ties from notes, resulting in
unconventional but easier-to-read notation
* libfomus: added main library support needed for `untie' module
(module still needs to be written)
* markgrps: fixed bug causing mark groups (e.g., `pizz' and
`arco') to appear incorrectly in tied notes across measure
boundaries
* grslurs: fixed bug causing mysterious slurs to appear over notes
when FOMUS determines note durations
* libfomus: fixed bug causing rests in invisible voices (created
by mark events, for example) to be notated incorrectly when
there are tuplets in other voices (and causing LilyPond output
to crash with an error)
* lilyout: actual accidentals are output when `lily-autoaccs' is
set to a non-empty value (letting LilyPond decide how to notate
them)
* libfomus: fixed a bug that caused inconsistencies in octave
change signs (and other potential problems)
* fomus.el: fixed a few annoying warnings that pop up in new
version of emacs
* cm/grace: fixed measures not receiving proper time values (fix
is in cm/grace package)
The cm/grace fix at the bottom hasn't appeared in the cm repository yet.
The `untie' algorithm is pretty basic and a bit experimental at the
moment--I've already noticed a few enhancements that could be made
(probably in the next release). The code for this and future modules
will appear in the docs to show how to write modules (to replace or add
to FOMUS's functionality), although the module API isn't quite stable
yet (function names are still shifting around quite a bit).
Also, it's worthwhile at this point to set `n-threads' to something
greater than 0 (in your `.fomus' file) if you have multiple cores or
CPUs... (For example, if you have 4 cores set this to 4.) This will
schedule FOMUS's algorithms to run in parallel in many situations, and
seems to be fairly stable now... If you experience a problem (like a
segfault) just remove the `n-threads' setting.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
fomus-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fomus-user
