The « bug » seems to have been introduced since MuseScore 2.2.x: 2.1.0 behaves as expected.
JM > Le 6 mai 2018 à 11:51, Martin Tarenskeen <m.tarensk...@zonnet.nl> a écrit : > > > > On Sun, 6 May 2018, Urs Liska wrote: > >> Attached you'll find a simple nobeam.ly and the file nobeam.xml, which is >> the result from exporting with the current master of python-ly. This will be >> opened without beams in MuseScore 2. > > I am getting beams in MuseScore 2.2.1, Linux Fedora 28. > >> nobeam-withbeams.xml is the result of exporting from the branch >> xml-handle-beams (my current pull request). > > Looks the same to me in MuseScore. I am getting four 1/8 notes in a 4/4 time > bar. BTW: Does anyone know how to insert more notes in that bar in MuseScore? > If I try, it jumps to the next bar, thus creating an anacrusis? > > When using musicxml2ly to convert back to lilypond, I can see the difference > between the two files though. > > -- > > MT _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
