Thank you, Carl, for all your research!
Normally I'm a searcher and not a questioner, but I hadn't researched
StemUp/Down syndrome extensively yet, so I simply added it as a
postscript to my more problematic concern, since I also saw it as an XML
import error and not as a feature.
I tried the command line options --nsd/--no-stem-directions and they
worked perfectly. It wouldn't be bad to add the new options to the
official documentation, or is it just for the stable version?
Andreas
Am 15.01.2019 um 05:36 schrieb Carl Sorensen:
On 1/14/19, 9:32 PM, "Carl Sorensen" <c_soren...@byu.edu> wrote:
On 1/14/19, 11:11 AM, "samaru...@aim.com" <samaru...@aim.com> wrote:
PS Windows+Mac: StemUp/Downs appear everywhere after the import, this
was not the case with older LilyPond versions, e.g. 2.19.31, which I
still use on my Windows system because of the errors listed above (I
know that would probably be another separate issue).
Further searching for philomelos (which was a fork of musicxml2ly that was apparently reintegrated into lilypond in the commit I referenced earlier) led to the following:
https://github.com/Philomelos/lilypond-musicxml2ly-dev
which contains the following in its release notes:
v0.1.13:
added the command line options --nsd / --no-stem-directions to ignore stem direction indications given in MusicXML, and use lilypond's automatic stemming instead.
You might try using the command option --no-stem-directions or --nsd and see if that eliminates the spurious stem direction commands.
HTH,
Carl
And LilyPond issue #4751 (https://sourceforge.net/p/testlilyissues/issues/4751/?page=1) confirms that the stem directions and the new command-line option were added as part of 2.19.44
HTH,
Carl
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
