Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Jan-Peter Voigt]

Hi Urs,

I was just curious what the lilypond-export OLL-module 
(https://github.com/jpvoigt/lilypond-export/) is doing with this 
pattern. It seems the final beam closing is not fetched correctly. At 
least in MuseScore the last note with automatic beams is not beamed.


Best
Jan-Peter


Am 05.05.2018 um 08:25 schrieb Urs Liska:

Hi,

I'm trying to add support to python-ly for exporting manual beams to 
MusicXML.


I managed to export the commands to start and end a beam, but that's not 
sufficient. In theory 
(https://usermanuals.musicxml.com/MusicXML/Content/EL-MusicXML-beam.htm) 
the beaming pattern is described in detail in MusicXML, and when I 
export something from MuseScore this is also what I get.


I don't see it as reasonable to properly implement this in the python-ly 
exporter (at least for now) because that would essentially mean 
re-implementing the whole beaming-pattern code from LilyPond (which even 
isn't fully correct either).


However, I realized that when I have the beam start and end encoded by 
python-ly and then (so far manually) add


     continue

to each note, regardless of the actual beaming pattern situation, 
MuseScore will correctly import the XML file (and add the correct 
encoding when re-exporting to XML).


While I know this is not a correct export I think it would be a good 
start and in any case better than nothing. But I would like to know what 
the other programs will do with the code.


So I'd be happy if people could import the attached .xml file to Finale, 
Sibelius and (if possible) Dorico, and tell me about the results. Also 
attached is the reference image of what it should look like.

(Note that the .xml is manually tweaked at this point).

TIA
Urs



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user





export-example2.pdf
Description: Adobe PDF document

http://www.musicxml.org/dtds/partwise.dtd;>



Part 1


Part 2





1024



A
4

512
1
eighth
begin



B
4

256
1
16th
continue



A
4

256
1
16th
end



G
4

512
1
eighth
begin



A
4

128
1
32nd
continue



B
4

128
1
32nd
continue



C
5

256
1
16th
end



B
4

448
1
16th


begin



A
4

64
1
64th
continue



G
4

256
1
16th
continue



A
4

128
1
32nd
end



G
4

128
1
32nd






1024



A
4

512
1
eighth
begin



B
4

256
1
16th
continue



A
4

256
1
16th
end



G
4

512
1
eighth
begin



A
4

128
1
32nd
continue



B
4

128
1
32nd
continue



C
5

256
1
16th
end



B
4

448
1
16th


begin



A
4

64
1
64th
continue



G
4

256
1
16th
continue



A
4

128
1
32nd
continue



G
4

128
1
32nd
end




\version "2.19.80"
%%%
% %
% This file is part of openLilyLib,   %
%  ===%
% the community library project for GNU LilyPond  %
% (https://github.com/openlilylib)%
%  ---%
% %
% Library: lilypond-export%
%  ===%
% %
% export foreign file formats with LilyPond   %
% %
% lilypond-export is free software: you can redistribute it and/or modify %
% it under the terms of the GNU General Public License as published by%
% the Free Software Foundation, either version 3 of the License, or   %
% (at your option) any later version. %
% %
% lilypond-export is distributed in the hope that it will be useful,  %
% but WITHOUT ANY WARRANTY; without even the implied warranty of  %
% MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the   %
% GNU General Public License for more details.%
% %
% You should have received a copy of the GNU General Public License   %
% along with openLilyLib. If not, see . %
% %
% openLilyLib is maintained by Urs Liska, u...@openlilylib.org  %
% lilypond-export is maintained by Jan-Peter Voigt, jp.vo...@gmx.de   %
% %
%   

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Patrick Hubers]

Dorico imports these as intended



Op 5-5-2018 om 08:25 schreef Urs Liska:

...


So I'd be happy if people could import the attached .xml file to 
Finale, Sibelius and (if possible) Dorico, and tell me about the 
results. Also attached is the reference image of what it should look 
like.
(Note that the .xml is manually tweaked at this point). 


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Jacques Menu Muzhic]

Thanks Simon, I’ll have something quite interesting to read in the forthcoming 
time!

JM

> Le 7 mai 2018 à 20:08, Simon Albrecht  a écrit :
> 
> On 07.05.2018 18:51, Jacques Menu Muzhic wrote:
>> Would it be a reasonable approach to have LilyPond first produce data in 
>> memory, i.e. Scheme data representing the whole score, and then either to 
>> produce the score or a MIDI file or supply this data to other applications, 
>> such as a MusicXML exporter?
> 
> That’s exactly the approach which Erik Sandberg described in his Master’s 
> thesis  for which 
> apparently he at one point had a code branch, which IIUC never got merged 
> into LilyPond proper.
> 
> Best, Simon


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Simon Albrecht]

On 07.05.2018 18:51, Jacques Menu Muzhic wrote:

Would it be a reasonable approach to have LilyPond first produce data in 
memory, i.e. Scheme data representing the whole score, and then either to 
produce the score or a MIDI file or supply this data to other applications, 
such as a MusicXML exporter?


That’s exactly the approach which Erik Sandberg described in his 
Master’s thesis  
for which apparently he at one point had a code branch, which IIUC never 
got merged into LilyPond proper.


Best, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[lists]

7. Mai 2018 18:51, "Jacques Menu Muzhic"  schrieb:

> Would it be a reasonable approach to have LilyPond first produce data in 
> memory, i.e. Scheme data
> representing the whole score, and then either to produce the score or a MIDI 
> file or supply this
> data to other applications, such as a MusicXML exporter?

Yes, that's the idea.
We had talked about the idea of providing something like an API where 
"consumers" could take that data either from some serialization on disk or 
(better) from some memory representation. Ideally such a converter should be 
writable in different languages.

> 
> Of course this would mean a lot of work.

Oh well, yes. That's why this doesn't exist yet ;-)

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Jacques Menu Muzhic]

Would it be a reasonable approach to have LilyPond first produce data in 
memory, i.e. Scheme data representing the whole score, and then either to 
produce the score or a MIDI file or supply this data to other applications, 
such as a MusicXML exporter?

Of course this would mean a lot of work.

> Le 7 mai 2018 à 18:18, Urs Liska  a écrit :
> 
> 
> 
> Am 07.05.2018 um 18:13 schrieb Jacques Menu Muzhic:
>> Hello Urs,
>> 
>> With the LP code:
>> 
>> {
>>   c'8 [ d' e' f' ]
>> }
>> 
>> what is the difficulty for producing  markups in the MusicXML output?
> 
> None. This works now (although the Pull Request hasn't been merged.
> 
> What does *not* work is producing beams in MusicXML from *that*:
> 
> {
>  c'8 d' e' f
> }
> 
> Since the implicit beams are not explicit in the input file python-ly doesn't 
> know about them.
> 
> Similarly:
> 
> {
>  c'8 [ d'16 e'16 ]
> }
> 
> Can't *correctly* be exported because MusicXML expects detailed information 
> about the beaming pattern (how many beams at each note), which again isn't 
> explicitly available in the LilyPond input.
> 
> To overcome this limitation python-ly would either have to reimplement all 
> the stuff the LilyPond parser does (think about what happens when we come to 
> Scheme functions :-O ) - or we find a way to have LilyPond parse the score 
> and pass the parsed expressions to some exporter module (which is the 
> approach Jan-Peter is exploring).
> 
> Urs
> 
>> 
>> JM
>> 
>>> Le 6 mai 2018 à 12:20, Urs Liska  a écrit :
>>> 
>>> 
>>> 
>>> Am 6. Mai 2018 12:08:39 MESZ schrieb Jacques Menu Muzhic 
>>> :
 I’m not familiar with python.ly ’s internals: does
 it use LP’s internal description, shown below by \displayMusic?
>>> No, it parses the input file(s) - which points to the single most 
>>> significant limitation of python-ly's/Frescobaldi's approach.
>>> 
 Starting lilypond 2.19.80 [nobeam.ly]...
 Processing
 `/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T/frescobaldi-nx6e_mso/tmp2kwa263p/nobeam.ly'
 Parsing...
 Interpreting music...
 Preprocessing graphical objects...
 Finding the ideal number of pages...
 Fitting music on 1 page...
 Drawing systems...
 Layout output to
 `/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T//lilypond-pwPv1B'...
 Converting to `nobeam.pdf'...
 Deleting
 `/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T//lilypond-pwPv1B'...
 
 (make-music
 'SequentialMusic
 'elements
 (list (make-music
 'NoteEvent
 'articulations
 (list (make-music
 'BeamEvent
 'span-direction
 -1))
 'duration
 (ly:make-duration 3)
 'pitch
 (ly:make-pitch 0 0))
 (make-music
 'NoteEvent
 'pitch
 (ly:make-pitch 0 1)
 'duration
 (ly:make-duration 3))
 (make-music
 'NoteEvent
 'pitch
 (ly:make-pitch 0 2)
 'duration
 (ly:make-duration 3))
 (make-music
 'NoteEvent
 'articulations
 (list (make-music
 'BeamEvent
 'span-direction
 1))
 'duration
 (ly:make-duration 3)
 'pitch
 (ly:make-pitch 0 3
 
 Success: compilation successfully completed
 Completed successfully in 0.8".
 
> Le 6 mai 2018 à 11:58, Urs Liska  a écrit :
> 
> 
> 
> Am 06.05.2018 um 11:43 schrieb Jacques Menu Muzhic:
>> Hello Urs,
>> 
>> musicsml2ly and Finale 2014 behave as expected, but MuseScore 2.2.1
 produces beams in both cases, i.e. even when there are no beams in the
 MusicXML data.
> OK, that seems that between 2.1.0 and 2.2.1 MuseScore has added that
 feature.
> Still it's of course inacceptable not to export beams at all.
> 
> Unfortunately we can so far only deal with explicit beams, there's no
 way (without substantial work to redo LilyPond's autobeaming (and
 beaming pattern) in Python).
> Thanks for testing
> Urs
> 
>> Strange…
>> 
>> JM
>> 
>>> Le 6 mai 2018 à 11:09, Urs Liska  a écrit :
>>> 
>>> Hello Jacques,
>>> 
>>> 
>>> Am 06.05.2018 um 10:11 schrieb Jacques Menu Muzhic:
 Hello Urs,
 
 I’m doing tests with MusicXML, could you send me an example where
 MuseScore doesn’t show any beams after exporting from LilyPond?
>>> 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.
>>> nobeam-withbeams.xml is the result of exporting from the branch
 xml-handle-beams (my current pull request). The XML file I originally
 sent was also created from that branch.
>>> Thanks for helping to look into it.
>>> Urs
>>> 
 Thanks!
 
 JM
 
> Le 5 mai 2018 à 11:50, 

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Urs Liska]

Am 07.05.2018 um 18:13 schrieb Jacques Menu Muzhic:

Hello Urs,

With the LP code:

{
   c'8 [ d' e' f' ]
}

what is the difficulty for producing  markups in the MusicXML output?


None. This works now (although the Pull Request hasn't been merged.

What does *not* work is producing beams in MusicXML from *that*:

{
  c'8 d' e' f
}

Since the implicit beams are not explicit in the input file python-ly 
doesn't know about them.


Similarly:

{
  c'8 [ d'16 e'16 ]
}

Can't *correctly* be exported because MusicXML expects detailed 
information about the beaming pattern (how many beams at each note), 
which again isn't explicitly available in the LilyPond input.


To overcome this limitation python-ly would either have to reimplement 
all the stuff the LilyPond parser does (think about what happens when we 
come to Scheme functions :-O ) - or we find a way to have LilyPond parse 
the score and pass the parsed expressions to some exporter module (which 
is the approach Jan-Peter is exploring).


Urs



JM


Le 6 mai 2018 à 12:20, Urs Liska  a écrit :



Am 6. Mai 2018 12:08:39 MESZ schrieb Jacques Menu Muzhic 
:

I’m not familiar with python.ly ’s internals: does
it use LP’s internal description, shown below by \displayMusic?

No, it parses the input file(s) - which points to the single most significant 
limitation of python-ly's/Frescobaldi's approach.


Starting lilypond 2.19.80 [nobeam.ly]...
Processing
`/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T/frescobaldi-nx6e_mso/tmp2kwa263p/nobeam.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to
`/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T//lilypond-pwPv1B'...
Converting to `nobeam.pdf'...
Deleting
`/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T//lilypond-pwPv1B'...

(make-music
'SequentialMusic
'elements
(list (make-music
'NoteEvent
'articulations
(list (make-music
'BeamEvent
'span-direction
-1))
'duration
(ly:make-duration 3)
'pitch
(ly:make-pitch 0 0))
(make-music
'NoteEvent
'pitch
(ly:make-pitch 0 1)
'duration
(ly:make-duration 3))
(make-music
'NoteEvent
'pitch
(ly:make-pitch 0 2)
'duration
(ly:make-duration 3))
(make-music
'NoteEvent
'articulations
(list (make-music
'BeamEvent
'span-direction
1))
'duration
(ly:make-duration 3)
'pitch
(ly:make-pitch 0 3

Success: compilation successfully completed
Completed successfully in 0.8".


Le 6 mai 2018 à 11:58, Urs Liska  a écrit :



Am 06.05.2018 um 11:43 schrieb Jacques Menu Muzhic:

Hello Urs,

musicsml2ly and Finale 2014 behave as expected, but MuseScore 2.2.1

produces beams in both cases, i.e. even when there are no beams in the
MusicXML data.

OK, that seems that between 2.1.0 and 2.2.1 MuseScore has added that

feature.

Still it's of course inacceptable not to export beams at all.

Unfortunately we can so far only deal with explicit beams, there's no

way (without substantial work to redo LilyPond's autobeaming (and
beaming pattern) in Python).

Thanks for testing
Urs


Strange…

JM


Le 6 mai 2018 à 11:09, Urs Liska  a écrit :

Hello Jacques,


Am 06.05.2018 um 10:11 schrieb Jacques Menu Muzhic:

Hello Urs,

I’m doing tests with MusicXML, could you send me an example where

MuseScore doesn’t show any beams after exporting from LilyPond?

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.

nobeam-withbeams.xml is the result of exporting from the branch

xml-handle-beams (my current pull request). The XML file I originally
sent was also created from that branch.

Thanks for helping to look into it.
Urs


Thanks!

JM


Le 5 mai 2018 à 11:50, li...@openlilylib.org a écrit :

Hi Torsten,

5. Mai 2018 11:44, "Torsten Hämmerle" 

schrieb:

Hi Urs,

Sibelius works fine:





Thanks.


As my Dorico evaluation period has expired, I can't even start

it.

All the others allow testing w/o save/export functionality, but

Steinberg is

much more restrictive in that respect.


On the Facebook group I got a screenshot of Dorico, so (not

unexpectedly) this works too.

So my conclusion is: we can export faulty XML, and Finale,

Sibelius, Dorico, MuseScore and Verovio will still properly handle it.

I find that somewhat embarrassing, but I think it's much better

than nothing (I was pretty surprised to see that MusesScore didn't show
*any* beams after exporting a small example from LilyPond ...)

Thanks to all who responded.
Urs


All the best,
Torsten

--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Jacques Menu Muzhic]

Hello Urs,

With the LP code:

{
  c'8 [ d' e' f' ]
}

what is the difficulty for producing  markups in the MusicXML output?

JM

> Le 6 mai 2018 à 12:20, Urs Liska  a écrit :
> 
> 
> 
> Am 6. Mai 2018 12:08:39 MESZ schrieb Jacques Menu Muzhic 
> :
>> I’m not familiar with python.ly ’s internals: does
>> it use LP’s internal description, shown below by \displayMusic?
> 
> No, it parses the input file(s) - which points to the single most significant 
> limitation of python-ly's/Frescobaldi's approach.
> 
>> 
>> Starting lilypond 2.19.80 [nobeam.ly]...
>> Processing
>> `/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T/frescobaldi-nx6e_mso/tmp2kwa263p/nobeam.ly'
>> Parsing...
>> Interpreting music...
>> Preprocessing graphical objects...
>> Finding the ideal number of pages...
>> Fitting music on 1 page...
>> Drawing systems...
>> Layout output to
>> `/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T//lilypond-pwPv1B'...
>> Converting to `nobeam.pdf'...
>> Deleting
>> `/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T//lilypond-pwPv1B'...
>> 
>> (make-music
>> 'SequentialMusic
>> 'elements
>> (list (make-music
>> 'NoteEvent
>> 'articulations
>> (list (make-music
>> 'BeamEvent
>> 'span-direction
>> -1))
>> 'duration
>> (ly:make-duration 3)
>> 'pitch
>> (ly:make-pitch 0 0))
>> (make-music
>> 'NoteEvent
>> 'pitch
>> (ly:make-pitch 0 1)
>> 'duration
>> (ly:make-duration 3))
>> (make-music
>> 'NoteEvent
>> 'pitch
>> (ly:make-pitch 0 2)
>> 'duration
>> (ly:make-duration 3))
>> (make-music
>> 'NoteEvent
>> 'articulations
>> (list (make-music
>> 'BeamEvent
>> 'span-direction
>> 1))
>> 'duration
>> (ly:make-duration 3)
>> 'pitch
>> (ly:make-pitch 0 3
>> 
>> Success: compilation successfully completed
>> Completed successfully in 0.8".
>> 
>>> Le 6 mai 2018 à 11:58, Urs Liska  a écrit :
>>> 
>>> 
>>> 
>>> Am 06.05.2018 um 11:43 schrieb Jacques Menu Muzhic:
 Hello Urs,
 
 musicsml2ly and Finale 2014 behave as expected, but MuseScore 2.2.1
>> produces beams in both cases, i.e. even when there are no beams in the
>> MusicXML data.
>>> 
>>> OK, that seems that between 2.1.0 and 2.2.1 MuseScore has added that
>> feature.
>>> Still it's of course inacceptable not to export beams at all.
>>> 
>>> Unfortunately we can so far only deal with explicit beams, there's no
>> way (without substantial work to redo LilyPond's autobeaming (and
>> beaming pattern) in Python).
>>> 
>>> Thanks for testing
>>> Urs
>>> 
 
 Strange…
 
 JM
 
> Le 6 mai 2018 à 11:09, Urs Liska  a écrit :
> 
> Hello Jacques,
> 
> 
> Am 06.05.2018 um 10:11 schrieb Jacques Menu Muzhic:
>> Hello Urs,
>> 
>> I’m doing tests with MusicXML, could you send me an example where
>> MuseScore doesn’t show any beams after exporting from LilyPond?
> 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.
> nobeam-withbeams.xml is the result of exporting from the branch
>> xml-handle-beams (my current pull request). The XML file I originally
>> sent was also created from that branch.
> 
> Thanks for helping to look into it.
> Urs
> 
>> Thanks!
>> 
>> JM
>> 
>>> Le 5 mai 2018 à 11:50, li...@openlilylib.org a écrit :
>>> 
>>> Hi Torsten,
>>> 
>>> 5. Mai 2018 11:44, "Torsten Hämmerle" 
>> schrieb:
>>> 
 Hi Urs,
 
 Sibelius works fine:
 
 
>> 
 
>>> Thanks.
>>> 
 As my Dorico evaluation period has expired, I can't even start
>> it.
 All the others allow testing w/o save/export functionality, but
>> Steinberg is
 much more restrictive in that respect.
 
>>> On the Facebook group I got a screenshot of Dorico, so (not
>> unexpectedly) this works too.
>>> 
>>> So my conclusion is: we can export faulty XML, and Finale,
>> Sibelius, Dorico, MuseScore and Verovio will still properly handle it.
>>> I find that somewhat embarrassing, but I think it's much better
>> than nothing (I was pretty surprised to see that MusesScore didn't show
>> *any* beams after exporting a small example from LilyPond ...)
>>> 
>>> Thanks to all who responded.
>>> Urs
>>> 
 All the best,
 Torsten
 
 --
 Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
 
 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-user
>>> ___
>>> lilypond-user mailing list
>>> lilypond-user@gnu.org
>>> 

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Urs Liska]

Am 6. Mai 2018 12:08:39 MESZ schrieb Jacques Menu Muzhic 
:
>I’m not familiar with python.ly ’s internals: does
>it use LP’s internal description, shown below by \displayMusic?

No, it parses the input file(s) - which points to the single most significant 
limitation of python-ly's/Frescobaldi's approach.

>
>Starting lilypond 2.19.80 [nobeam.ly]...
>Processing
>`/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T/frescobaldi-nx6e_mso/tmp2kwa263p/nobeam.ly'
>Parsing...
>Interpreting music...
>Preprocessing graphical objects...
>Finding the ideal number of pages...
>Fitting music on 1 page...
>Drawing systems...
>Layout output to
>`/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T//lilypond-pwPv1B'...
>Converting to `nobeam.pdf'...
>Deleting
>`/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T//lilypond-pwPv1B'...
>
>(make-music
>'SequentialMusic
>'elements
>(list (make-music
>'NoteEvent
>'articulations
>(list (make-music
>'BeamEvent
>'span-direction
>-1))
>'duration
>(ly:make-duration 3)
>'pitch
>(ly:make-pitch 0 0))
>(make-music
>'NoteEvent
>'pitch
>(ly:make-pitch 0 1)
>'duration
>(ly:make-duration 3))
>(make-music
>'NoteEvent
>'pitch
>(ly:make-pitch 0 2)
>'duration
>(ly:make-duration 3))
>(make-music
>'NoteEvent
>'articulations
>(list (make-music
>'BeamEvent
>'span-direction
>1))
>'duration
>(ly:make-duration 3)
>'pitch
>(ly:make-pitch 0 3
>
>Success: compilation successfully completed
>Completed successfully in 0.8".
>
>> Le 6 mai 2018 à 11:58, Urs Liska  a écrit :
>> 
>> 
>> 
>> Am 06.05.2018 um 11:43 schrieb Jacques Menu Muzhic:
>>> Hello Urs,
>>> 
>>> musicsml2ly and Finale 2014 behave as expected, but MuseScore 2.2.1
>produces beams in both cases, i.e. even when there are no beams in the
>MusicXML data.
>> 
>> OK, that seems that between 2.1.0 and 2.2.1 MuseScore has added that
>feature.
>> Still it's of course inacceptable not to export beams at all.
>> 
>> Unfortunately we can so far only deal with explicit beams, there's no
>way (without substantial work to redo LilyPond's autobeaming (and
>beaming pattern) in Python).
>> 
>> Thanks for testing
>> Urs
>> 
>>> 
>>> Strange…
>>> 
>>> JM
>>> 
 Le 6 mai 2018 à 11:09, Urs Liska  a écrit :
 
 Hello Jacques,
 
 
 Am 06.05.2018 um 10:11 schrieb Jacques Menu Muzhic:
> Hello Urs,
> 
> I’m doing tests with MusicXML, could you send me an example where
>MuseScore doesn’t show any beams after exporting from LilyPond?
 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.
 nobeam-withbeams.xml is the result of exporting from the branch
>xml-handle-beams (my current pull request). The XML file I originally
>sent was also created from that branch.
 
 Thanks for helping to look into it.
 Urs
 
> Thanks!
> 
> JM
> 
>> Le 5 mai 2018 à 11:50, li...@openlilylib.org a écrit :
>> 
>> Hi Torsten,
>> 
>> 5. Mai 2018 11:44, "Torsten Hämmerle" 
>schrieb:
>> 
>>> Hi Urs,
>>> 
>>> Sibelius works fine:
>>> 
>>>
>
>>> 
>> Thanks.
>> 
>>> As my Dorico evaluation period has expired, I can't even start
>it.
>>> All the others allow testing w/o save/export functionality, but
>Steinberg is
>>> much more restrictive in that respect.
>>> 
>> On the Facebook group I got a screenshot of Dorico, so (not
>unexpectedly) this works too.
>> 
>> So my conclusion is: we can export faulty XML, and Finale,
>Sibelius, Dorico, MuseScore and Verovio will still properly handle it.
>> I find that somewhat embarrassing, but I think it's much better
>than nothing (I was pretty surprised to see that MusesScore didn't show
>*any* beams after exporting a small example from LilyPond ...)
>> 
>> Thanks to all who responded.
>> Urs
>> 
>>> All the best,
>>> Torsten
>>> 
>>> --
>>> Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
>>> 
>>> ___
>>> lilypond-user mailing list
>>> lilypond-user@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
 
>> 

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Jacques Menu Muzhic]

I’m not familiar with python.ly ’s internals: does it use 
LP’s internal description, shown below by \displayMusic?

Starting lilypond 2.19.80 [nobeam.ly]...
Processing 
`/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T/frescobaldi-nx6e_mso/tmp2kwa263p/nobeam.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to 
`/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T//lilypond-pwPv1B'...
Converting to `nobeam.pdf'...
Deleting `/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T//lilypond-pwPv1B'...

(make-music
'SequentialMusic
'elements
(list (make-music
'NoteEvent
'articulations
(list (make-music
'BeamEvent
'span-direction
-1))
'duration
(ly:make-duration 3)
'pitch
(ly:make-pitch 0 0))
(make-music
'NoteEvent
'pitch
(ly:make-pitch 0 1)
'duration
(ly:make-duration 3))
(make-music
'NoteEvent
'pitch
(ly:make-pitch 0 2)
'duration
(ly:make-duration 3))
(make-music
'NoteEvent
'articulations
(list (make-music
'BeamEvent
'span-direction
1))
'duration
(ly:make-duration 3)
'pitch
(ly:make-pitch 0 3

Success: compilation successfully completed
Completed successfully in 0.8".

> Le 6 mai 2018 à 11:58, Urs Liska  a écrit :
> 
> 
> 
> Am 06.05.2018 um 11:43 schrieb Jacques Menu Muzhic:
>> Hello Urs,
>> 
>> musicsml2ly and Finale 2014 behave as expected, but MuseScore 2.2.1 produces 
>> beams in both cases, i.e. even when there are no beams in the MusicXML data.
> 
> OK, that seems that between 2.1.0 and 2.2.1 MuseScore has added that feature.
> Still it's of course inacceptable not to export beams at all.
> 
> Unfortunately we can so far only deal with explicit beams, there's no way 
> (without substantial work to redo LilyPond's autobeaming (and beaming 
> pattern) in Python).
> 
> Thanks for testing
> Urs
> 
>> 
>> Strange…
>> 
>> JM
>> 
>>> Le 6 mai 2018 à 11:09, Urs Liska  a écrit :
>>> 
>>> Hello Jacques,
>>> 
>>> 
>>> Am 06.05.2018 um 10:11 schrieb Jacques Menu Muzhic:
 Hello Urs,
 
 I’m doing tests with MusicXML, could you send me an example where 
 MuseScore doesn’t show any beams after exporting from LilyPond?
>>> 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.
>>> nobeam-withbeams.xml is the result of exporting from the branch 
>>> xml-handle-beams (my current pull request). The XML file I originally sent 
>>> was also created from that branch.
>>> 
>>> Thanks for helping to look into it.
>>> Urs
>>> 
 Thanks!
 
 JM
 
> Le 5 mai 2018 à 11:50, li...@openlilylib.org a écrit :
> 
> Hi Torsten,
> 
> 5. Mai 2018 11:44, "Torsten Hämmerle"  schrieb:
> 
>> Hi Urs,
>> 
>> Sibelius works fine:
>> 
>> 
>> 
> Thanks.
> 
>> As my Dorico evaluation period has expired, I can't even start it.
>> All the others allow testing w/o save/export functionality, but 
>> Steinberg is
>> much more restrictive in that respect.
>> 
> On the Facebook group I got a screenshot of Dorico, so (not unexpectedly) 
> this works too.
> 
> So my conclusion is: we can export faulty XML, and Finale, Sibelius, 
> Dorico, MuseScore and Verovio will still properly handle it.
> I find that somewhat embarrassing, but I think it's much better than 
> nothing (I was pretty surprised to see that MusesScore didn't show *any* 
> beams after exporting a small example from LilyPond ...)
> 
> Thanks to all who responded.
> Urs
> 
>> All the best,
>> Torsten
>> 
>> --
>> Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
>> 
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>> 
> 

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Urs Liska]

Am 06.05.2018 um 11:43 schrieb Jacques Menu Muzhic:

Hello Urs,

musicsml2ly and Finale 2014 behave as expected, but MuseScore 2.2.1 produces 
beams in both cases, i.e. even when there are no beams in the MusicXML data.


OK, that seems that between 2.1.0 and 2.2.1 MuseScore has added that 
feature.

Still it's of course inacceptable not to export beams at all.

Unfortunately we can so far only deal with explicit beams, there's no 
way (without substantial work to redo LilyPond's autobeaming (and 
beaming pattern) in Python).


Thanks for testing
Urs



Strange…

JM


Le 6 mai 2018 à 11:09, Urs Liska  a écrit :

Hello Jacques,


Am 06.05.2018 um 10:11 schrieb Jacques Menu Muzhic:

Hello Urs,

I’m doing tests with MusicXML, could you send me an example where MuseScore 
doesn’t show any beams after exporting from LilyPond?

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.
nobeam-withbeams.xml is the result of exporting from the branch 
xml-handle-beams (my current pull request). The XML file I originally sent was 
also created from that branch.

Thanks for helping to look into it.
Urs


Thanks!

JM


Le 5 mai 2018 à 11:50, li...@openlilylib.org a écrit :

Hi Torsten,

5. Mai 2018 11:44, "Torsten Hämmerle"  schrieb:


Hi Urs,

Sibelius works fine:




Thanks.


As my Dorico evaluation period has expired, I can't even start it.
All the others allow testing w/o save/export functionality, but Steinberg is
much more restrictive in that respect.


On the Facebook group I got a screenshot of Dorico, so (not unexpectedly) this 
works too.

So my conclusion is: we can export faulty XML, and Finale, Sibelius, Dorico, 
MuseScore and Verovio will still properly handle it.
I find that somewhat embarrassing, but I think it's much better than nothing (I 
was pretty surprised to see that MusesScore didn't show *any* beams after 
exporting a small example from LilyPond ...)

Thanks to all who responded.
Urs


All the best,
Torsten

--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user





___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Jacques Menu Muzhic]

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  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

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Martin Tarenskeen]

On Sun, 6 May 2018, Jacques Menu Muzhic wrote:

musicsml2ly and Finale 2014 behave as expected, but MuseScore 2.2.1 
produces beams in both cases, i.e. even when there are no beams in the 
MusicXML data.


Strange…


My guess is that MuseScore does things it isn't supposed to do. Which can 
sometimes be pleasant but still incorrect.


--

MT
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Martin Tarenskeen]

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

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Jacques Menu Muzhic]

Hello Urs,

musicsml2ly and Finale 2014 behave as expected, but MuseScore 2.2.1 produces 
beams in both cases, i.e. even when there are no beams in the MusicXML data.

Strange…

JM

> Le 6 mai 2018 à 11:09, Urs Liska  a écrit :
> 
> Hello Jacques,
> 
> 
> Am 06.05.2018 um 10:11 schrieb Jacques Menu Muzhic:
>> Hello Urs,
>> 
>> I’m doing tests with MusicXML, could you send me an example where MuseScore 
>> doesn’t show any beams after exporting from LilyPond?
> 
> 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.
> nobeam-withbeams.xml is the result of exporting from the branch 
> xml-handle-beams (my current pull request). The XML file I originally sent 
> was also created from that branch.
> 
> Thanks for helping to look into it.
> Urs
> 
>> Thanks!
>> 
>> JM
>> 
>>> Le 5 mai 2018 à 11:50, li...@openlilylib.org a écrit :
>>> 
>>> Hi Torsten,
>>> 
>>> 5. Mai 2018 11:44, "Torsten Hämmerle"  schrieb:
>>> 
 Hi Urs,
 
 Sibelius works fine:
 
 
 
>>> Thanks.
>>> 
 As my Dorico evaluation period has expired, I can't even start it.
 All the others allow testing w/o save/export functionality, but Steinberg 
 is
 much more restrictive in that respect.
 
>>> On the Facebook group I got a screenshot of Dorico, so (not unexpectedly) 
>>> this works too.
>>> 
>>> So my conclusion is: we can export faulty XML, and Finale, Sibelius, 
>>> Dorico, MuseScore and Verovio will still properly handle it.
>>> I find that somewhat embarrassing, but I think it's much better than 
>>> nothing (I was pretty surprised to see that MusesScore didn't show *any* 
>>> beams after exporting a small example from LilyPond ...)
>>> 
>>> Thanks to all who responded.
>>> Urs
>>> 
 All the best,
 Torsten
 
 --
 Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
 
 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-user
>>> ___
>>> lilypond-user mailing list
>>> lilypond-user@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Urs Liska]

Hello Jacques,


Am 06.05.2018 um 10:11 schrieb Jacques Menu Muzhic:

Hello Urs,

I’m doing tests with MusicXML, could you send me an example where MuseScore 
doesn’t show any beams after exporting from LilyPond?


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.
nobeam-withbeams.xml is the result of exporting from the branch 
xml-handle-beams (my current pull request). The XML file I originally 
sent was also created from that branch.


Thanks for helping to look into it.
Urs


Thanks!

JM


Le 5 mai 2018 à 11:50, li...@openlilylib.org a écrit :

Hi Torsten,

5. Mai 2018 11:44, "Torsten Hämmerle"  schrieb:


Hi Urs,

Sibelius works fine:




Thanks.


As my Dorico evaluation period has expired, I can't even start it.
All the others allow testing w/o save/export functionality, but Steinberg is
much more restrictive in that respect.


On the Facebook group I got a screenshot of Dorico, so (not unexpectedly) this 
works too.

So my conclusion is: we can export faulty XML, and Finale, Sibelius, Dorico, 
MuseScore and Verovio will still properly handle it.
I find that somewhat embarrassing, but I think it's much better than nothing (I 
was pretty surprised to see that MusesScore didn't show *any* beams after 
exporting a small example from LilyPond ...)

Thanks to all who responded.
Urs


All the best,
Torsten

--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


\version "2.19.80"

{
  c'8 [ d' e' f' ]
}
http://www.musicxml.org/dtds/partwise.dtd;>

  

  python-ly 0.9.5
  2018-05-06

  
  

  

  
  

  
2

  4
  4


  G
  2

  
  

  C
  4

1
1
eighth
  
  

  D
  4

1
1
eighth
  
  

  E
  4

1
1
eighth
  
  

  F
  4

1
1
eighth
  

  


http://www.musicxml.org/dtds/partwise.dtd;>

  

  python-ly 0.9.5
  2018-05-06

  
  

  

  
  

  
2

  4
  4


  G
  2

  
  

  C
  4

1
1
eighth
begin
  
  

  D
  4

1
1
eighth
continue
  
  

  E
  4

1
1
eighth
continue
  
  

  F
  4

1
1
eighth
end
  

  

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Jacques Menu Muzhic]

Hello Urs,

I’m doing tests with MusicXML, could you send me an example where MuseScore 
doesn’t show any beams after exporting from LilyPond?

Thanks!

JM

> Le 5 mai 2018 à 11:50, li...@openlilylib.org a écrit :
> 
> Hi Torsten,
> 
> 5. Mai 2018 11:44, "Torsten Hämmerle"  schrieb:
> 
>> Hi Urs,
>> 
>> Sibelius works fine:
>> 
>>  
>> 
> 
> Thanks.
> 
>> 
>> As my Dorico evaluation period has expired, I can't even start it.
>> All the others allow testing w/o save/export functionality, but Steinberg is
>> much more restrictive in that respect.
>> 
> 
> On the Facebook group I got a screenshot of Dorico, so (not unexpectedly) 
> this works too.
> 
> So my conclusion is: we can export faulty XML, and Finale, Sibelius, Dorico, 
> MuseScore and Verovio will still properly handle it.
> I find that somewhat embarrassing, but I think it's much better than nothing 
> (I was pretty surprised to see that MusesScore didn't show *any* beams after 
> exporting a small example from LilyPond ...)
> 
> Thanks to all who responded.
> Urs
> 
>> All the best,
>> Torsten
>> 
>> --
>> Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
>> 
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Jacques Menu Muzhic]

Hello,

Not sure whether this helps:

removing:

continue

from the file, MuseScore 2.2.1 produces:



Finale 2014 produces:




and musicxml2ly produces:


musicxml2ly: Reading MusicXML from 
O5beamWithoutBeamNumberContinue.xml_inter.xml ...
musicxml2ly: Converting to LilyPond expressions...
musicxml2ly: Output to `O5beamWithoutBeamNumberContinue.xml_inter.ly'
musicxml2ly: Converting to current version (2.19.58) notations ...




JM

> Le 5 mai 2018 à 11:50, li...@openlilylib.org a écrit :
> 
> Hi Torsten,
> 
> 5. Mai 2018 11:44, "Torsten Hämmerle"  schrieb:
> 
>> Hi Urs,
>> 
>> Sibelius works fine:
>> 
>>  
>> 
> 
> Thanks.
> 
>> 
>> As my Dorico evaluation period has expired, I can't even start it.
>> All the others allow testing w/o save/export functionality, but Steinberg is
>> much more restrictive in that respect.
>> 
> 
> On the Facebook group I got a screenshot of Dorico, so (not unexpectedly) 
> this works too.
> 
> So my conclusion is: we can export faulty XML, and Finale, Sibelius, Dorico, 
> MuseScore and Verovio will still properly handle it.
> I find that somewhat embarrassing, but I think it's much better than nothing 
> (I was pretty surprised to see that MusesScore didn't show *any* beams after 
> exporting a small example from LilyPond ...)
> 
> Thanks to all who responded.
> Urs
> 
>> All the best,
>> Torsten
>> 
>> --
>> Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
>> 
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[lists]

Hi Torsten,

5. Mai 2018 11:44, "Torsten Hämmerle"  schrieb:

> Hi Urs,
> 
> Sibelius works fine:
> 
>  
> 

Thanks.

>
> As my Dorico evaluation period has expired, I can't even start it.
> All the others allow testing w/o save/export functionality, but Steinberg is
> much more restrictive in that respect.
> 

On the Facebook group I got a screenshot of Dorico, so (not unexpectedly) this 
works too.

So my conclusion is: we can export faulty XML, and Finale, Sibelius, Dorico, 
MuseScore and Verovio will still properly handle it.
I find that somewhat embarrassing, but I think it's much better than nothing (I 
was pretty surprised to see that MusesScore didn't show *any* beams after 
exporting a small example from LilyPond ...)

Thanks to all who responded.
Urs

> All the best,
> Torsten
> 
> --
> Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Torsten Hämmerle]

Hi Urs,

Sibelius works fine:

 

As my Dorico evaluation period has expired, I can't even start it.
All the others allow testing w/o save/export functionality, but Steinberg is
much more restrictive in that respect.

All the best,
Torsten



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Thomas Weber]

  
  
Sibelius 8.1.1 creates exactly the same beaming.


Am 05.05.2018 um 09:38 schrieb Robert Blackstone:
> Hi Urs,
> 
> This is what your file produces with Finale 2024.5, on a MacBook with
> OSX 10.9.5.
> 
> 
> 
> (I should have compressed it a bit.)
> 
> Best regards,
> 
> Robert Blackstone
> 
>> Hi,
>> 
>> I'm trying to add support to python-ly for exporting manual beams
>> to MusicXML.
>> 
>> I managed to export the commands to start and end a beam, but
>> that's not sufficient. In theory
>> (https://usermanuals.musicxml.com/MusicXML/Content/EL-MusicXML-beam.htm)
>> the beaming pattern is described in detail in MusicXML, and when I
>> export something from MuseScore this is also what I get.
>> 
>> I don't see it as reasonable to properly implement this in the
>> python-ly exporter (at least for now) because that would
>> essentially mean re-implementing the whole beaming-pattern code
>> from LilyPond (which even isn't fully correct either).
>> 
>> However, I realized that when I have the beam start and end encoded
>> by python-ly and then (so far manually) add
>> 
>> continue
>> 
>> to each note, regardless of the actual beaming pattern situation,
>> MuseScore will correctly import the XML file (and add the correct
>> encoding when re-exporting to XML).
>> 
>> While I know this is not a correct export I think it would be a
>> good start and in any case better than nothing. But I would like to
>> know what the other programs will do with the code.
>> 
>> So I'd be happy if people could import the attached .xml file to
>> Finale, Sibelius and (if possible) Dorico, and tell me about the
>> results. Also attached is the reference image of what it should
>> look like. (Note that the .xml is manually tweaked at this point).
>> 
>> TIA Urs
>> 
>> <05-beam.xml><05-beam.png>___
>>
>> 
lilypond-user mailing list
>> lilypond-user@gnu.org 
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 
> 
> ___ lilypond-user mailing
> list lilypond-user@gnu.org 
> https://lists.gnu.org/mailman/listinfo/lilypond-user



  



05-beam - Full Score.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Urs Liska]

Hi Robert,

thanks for testing. Given that I'm not interested in the *looks* of it 
this is what I hoped to get :-)


Thanks
Urs


Am 05.05.2018 um 09:38 schrieb Robert Blackstone:

Hi Urs,

This is what your file produces with Finale 2024.5, on a MacBook with OSX 
10.9.5.


(I should have compressed it a bit.)

Best regards,

Robert Blackstone


Hi,

I'm trying to add support to python-ly for exporting manual beams to MusicXML.

I managed to export the commands to start and end a beam, but that's not 
sufficient. In theory 
(https://usermanuals.musicxml.com/MusicXML/Content/EL-MusicXML-beam.htm) the 
beaming pattern is described in detail in MusicXML, and when I export something 
from MuseScore this is also what I get.

I don't see it as reasonable to properly implement this in the python-ly 
exporter (at least for now) because that would essentially mean re-implementing 
the whole beaming-pattern code from LilyPond (which even isn't fully correct 
either).

However, I realized that when I have the beam start and end encoded by 
python-ly and then (so far manually) add

 continue

to each note, regardless of the actual beaming pattern situation, MuseScore 
will correctly import the XML file (and add the correct encoding when 
re-exporting to XML).

While I know this is not a correct export I think it would be a good start and 
in any case better than nothing. But I would like to know what the other 
programs will do with the code.

So I'd be happy if people could import the attached .xml file to Finale, 
Sibelius and (if possible) Dorico, and tell me about the results. Also attached 
is the reference image of what it should look like.
(Note that the .xml is manually tweaked at this point).

TIA
Urs

<05-beam.xml><05-beam.png>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Need someone testing XML file in Finale and Sibelius (and Dorico)

[Robert Blackstone]

Hi Urs,

This is what your file produces with Finale 2024.5, on a MacBook with OSX 
10.9.5.

05-beam_Finale_2014_5.pdf
Description: Adobe PDF document

(I should have compressed it a bit.)

Best regards,

Robert Blackstone

> Hi,
> 
> I'm trying to add support to python-ly for exporting manual beams to MusicXML.
> 
> I managed to export the commands to start and end a beam, but that's not 
> sufficient. In theory 
> (https://usermanuals.musicxml.com/MusicXML/Content/EL-MusicXML-beam.htm) the 
> beaming pattern is described in detail in MusicXML, and when I export 
> something from MuseScore this is also what I get.
> 
> I don't see it as reasonable to properly implement this in the python-ly 
> exporter (at least for now) because that would essentially mean 
> re-implementing the whole beaming-pattern code from LilyPond (which even 
> isn't fully correct either).
> 
> However, I realized that when I have the beam start and end encoded by 
> python-ly and then (so far manually) add
> 
> continue
> 
> to each note, regardless of the actual beaming pattern situation, MuseScore 
> will correctly import the XML file (and add the correct encoding when 
> re-exporting to XML).
> 
> While I know this is not a correct export I think it would be a good start 
> and in any case better than nothing. But I would like to know what the other 
> programs will do with the code.
> 
> So I'd be happy if people could import the attached .xml file to Finale, 
> Sibelius and (if possible) Dorico, and tell me about the results. Also 
> attached is the reference image of what it should look like.
> (Note that the .xml is manually tweaked at this point).
> 
> TIA
> Urs
> 
> <05-beam.xml><05-beam.png>___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Need someone testing XML file in Finale and Sibelius (and Dorico)

[Urs Liska]

Hi,

I'm trying to add support to python-ly for exporting manual beams to 
MusicXML.


I managed to export the commands to start and end a beam, but that's not 
sufficient. In theory 
(https://usermanuals.musicxml.com/MusicXML/Content/EL-MusicXML-beam.htm) 
the beaming pattern is described in detail in MusicXML, and when I 
export something from MuseScore this is also what I get.


I don't see it as reasonable to properly implement this in the python-ly 
exporter (at least for now) because that would essentially mean 
re-implementing the whole beaming-pattern code from LilyPond (which even 
isn't fully correct either).


However, I realized that when I have the beam start and end encoded by 
python-ly and then (so far manually) add


    continue

to each note, regardless of the actual beaming pattern situation, 
MuseScore will correctly import the XML file (and add the correct 
encoding when re-exporting to XML).


While I know this is not a correct export I think it would be a good 
start and in any case better than nothing. But I would like to know what 
the other programs will do with the code.


So I'd be happy if people could import the attached .xml file to Finale, 
Sibelius and (if possible) Dorico, and tell me about the results. Also 
attached is the reference image of what it should look like.

(Note that the .xml is manually tweaked at this point).

TIA
Urs


http://www.musicxml.org/dtds/partwise.dtd;>

  

  python-ly 0.9.5
  2018-05-05

  
  

  

  
  

  
128

  4
  4


  G
  2

  
  

  A
  4

64
1
eighth
begin
  
  

  B
  4

32
1
16th
continue
  
  

  A
  4

32
1
16th
end
  
  

  G
  4

64
1
eighth
begin
  
  

  A
  4

16
1
32nd
continue
  
  

  B
  4

16
1
32nd
continue
  
  

  C
  5

32
1
16th
end
  
  

  B
  4

56
1
16th


begin
  
  

  A
  4

8
1
64th
continue
  
  

  G
  4

32
1
16th
continue
  
  

  F
  4

16
1
32nd
continue
  
  

  E
  4

16
1
32nd
end
  

  

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user