Hi Gilberto!
Let me know if I can help with anything else.
Which operating system do you use? 32-bit or 64-bit?
I suspect that you did not compile Lilypond yourself but used one of the
installers. Am I right?
If I'm right: Don't use the python interpreter distributed with lilypond, use
pyt
Hi Knut,
Thanks a lot for your reply. I use Linux Mint 18.3, 64-bit, and my
LilyPond is version 2.19.82. The default python interpreter in my
installation is 2.7.12, which I think is what came with my Linux Mint
18.3 (I believe I've never bothered trying to update it since I do all
my Python
Hi Gilberto!
I use Linux Mint 18.3, 64-bit, and my LilyPond is version 2.19.82. The default python interpreter in my installation is 2.7.12, which I think is what came with my Linux Mint 18.3 (I believe I've never bothered trying to update it since I do all my Python coding with Python 3). Do yo
Hi Knut,
You did not answer the question if you used one of the installers from
lilypond.org or if you compiled lilypond.
My apologies, forgot about that bit. I am not compiling myself, I am
using the installers from lilypond.org.
Try if replacing
musicxml ...
with
python2 $(grep
Am 10.07.19 um 10:09 schrieb lilyp...@maltemeyn.de:
Am 2019-07-10 10:02, schrieb Simon Albrecht:
On 09.07.19 22:14, Malte Meyn wrote:
The bug is that when the Staff starts with an \ottava setting this
affects the AmbitusNoteHeads. A later setting of \ottava doesn’t
change that behaviour:
Hi Gilberto!
Try if replacing
musicxml ...
with
python2 $(grep -o '"[^$^"]*$me"' `which musicxml2ly` | sed -e 's/"//g' -e
's/$me/musicxml2ly/') ...
Yes, that does seem to fix the issue! The .ly file created by musicxml2ly does not have the encoding and strange character issues and co
Hi Knut,
Thank you so much for your help and for the explanation, I really
appreciate it. This solves the main issue I was having.
Concerning the other two feature requests I made in my original in
relation to supporting slur positioning and al niente hairpins in
musicxml2ly (see
http://lil
