MusicXML export news

4 messages

MusicXML export news

Reply Threaded

Hi Lasconic, All...
Sorry for the long time passed since my last post...
Let's do a little summary about my past work in the musescore
project... I was integrating the MusicXML export code in order to add
some missing features. In particular I was developing the code able to
export the layout position of some elements such as notes, staves,
systems and measures accordingly to MXML definitions.
If you remember in our last chat I posted a patch that was causing a
bad MusicXML import in Finale for some unknown reasons... But we were
also discussing about a possible bug in the page-width and page-height
export calculation.

I've worked on the exportxml.cpp code to fix the problem of the bad
page width and height and I figured out that this problem was causing
the system stretch in Finale as well.

Here is how I changed the code to fix the problem:

In the past version of Musescore the page-height and page-width of a
musicxml exported document was calculated with the following instructions:

double t = 2 * PPI * 10 / 9;
xml.tag("page-height", height() * t);

I don't fully understand this formula but I'm quite sure (as you
suggested in your last mail) that the result is wrong...
In my version the code is changed in:

xml.tag("page-height", height() * (INCH / millimeters * tenths));

and the result looks perfect now.
I've also tried the exported xml in Finale and everything seems to be
correct there too. For coherence I've changed the import MusicXML
algorithm too. It seems to work smoothly...

I attach the last patch... Let me know what do you think.

Hear you soon,
Raffaele

------------------------------------------------------------------------------

_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer

layout-tags-MXML.patch (35K) Download Attachment

lasconic

Re: MusicXML export news

Reply Threaded

No problem. I'm busy with the mac version for now. But I will free
some time to review your patch.
It looks like a step forward for layout support in musicXML.
I will let you know when it's done.

Lasconic

2009/7/2 Raf <[hidden email]>:

> Hi Lasconic, All...
> Sorry for the long time passed since my last post...
> Let's do a little summary about my past work in the musescore
> project... I was integrating the MusicXML export code in order to add
> some missing features. In particular I was developing the code able to
> export the layout position of some elements such as notes, staves,
> systems and measures accordingly to MXML definitions.
> If you remember in our last chat I posted a patch that was causing a
> bad MusicXML import in Finale for some unknown reasons... But we were
> also discussing about a possible bug in the page-width and page-height
> export calculation.
>
> I've worked on the exportxml.cpp code to fix the problem of the bad
> page width and height and I figured out that this problem was causing
> the system stretch in Finale as well.
>
> Here is how I changed the code to fix the problem:
>
> In the past version of Musescore the page-height and page-width of a
> musicxml exported document was calculated with the following instructions:
>
> double t = 2 * PPI * 10 / 9;
> xml.tag("page-height", height() * t);
>
> I don't fully understand this formula but I'm quite sure (as you
> suggested in your last mail) that the result is wrong...
> In my version the code is changed in:
>
> xml.tag("page-height", height() * (INCH / millimeters * tenths));
>
> and the result looks perfect now.
> I've also tried the exported xml in Finale and everything seems to be
> correct there too. For coherence I've changed the import MusicXML
> algorithm too. It seems to work smoothly...
>
> I attach the last patch... Let me know what do you think.
>
> Hear you soon,
> Raffaele
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Mscore-developer mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
>

------------------------------------------------------------------------------
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer

lasconic

Re: MusicXML export news

Reply Threaded

I commited your patch in SVN r1915.
Lasconic

2009/7/3 Lasconic <[hidden email]>:

> No problem. I'm busy with the mac version for now. But I will free
> some time to review your patch.
> It looks like a step forward for layout support in musicXML.
> I will let you know when it's done.
>
> Lasconic
>
> 2009/7/2 Raf <[hidden email]>:
>> Hi Lasconic, All...
>> Sorry for the long time passed since my last post...
>> Let's do a little summary about my past work in the musescore
>> project... I was integrating the MusicXML export code in order to add
>> some missing features. In particular I was developing the code able to
>> export the layout position of some elements such as notes, staves,
>> systems and measures accordingly to MXML definitions.
>> If you remember in our last chat I posted a patch that was causing a
>> bad MusicXML import in Finale for some unknown reasons... But we were
>> also discussing about a possible bug in the page-width and page-height
>> export calculation.
>>
>> I've worked on the exportxml.cpp code to fix the problem of the bad
>> page width and height and I figured out that this problem was causing
>> the system stretch in Finale as well.
>>
>> Here is how I changed the code to fix the problem:
>>
>> In the past version of Musescore the page-height and page-width of a
>> musicxml exported document was calculated with the following instructions:
>>
>> double t = 2 * PPI * 10 / 9;
>> xml.tag("page-height", height() * t);
>>
>> I don't fully understand this formula but I'm quite sure (as you
>> suggested in your last mail) that the result is wrong...
>> In my version the code is changed in:
>>
>> xml.tag("page-height", height() * (INCH / millimeters * tenths));
>>
>> and the result looks perfect now.
>> I've also tried the exported xml in Finale and everything seems to be
>> correct there too. For coherence I've changed the import MusicXML
>> algorithm too. It seems to work smoothly...
>>
>> I attach the last patch... Let me know what do you think.
>>
>> Hear you soon,
>> Raffaele
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Mscore-developer mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>>
>>
>

Raffaele-3

Re: MusicXML export news

Reply Threaded

Perfect...

Thank you...
Raffaele

On Mon, Jul 6, 2009 at 1:06 PM, Lasconic<[hidden email]> wrote:

> I commited your patch in SVN r1915.
> Lasconic
>
> 2009/7/3 Lasconic <[hidden email]>:
>> No problem. I'm busy with the mac version for now. But I will free
>> some time to review your patch.
>> It looks like a step forward for layout support in musicXML.
>> I will let you know when it's done.
>>
>> Lasconic
>>
>> 2009/7/2 Raf <[hidden email]>:
>>> Hi Lasconic, All...
>>> Sorry for the long time passed since my last post...
>>> Let's do a little summary about my past work in the musescore
>>> project... I was integrating the MusicXML export code in order to add
>>> some missing features. In particular I was developing the code able to
>>> export the layout position of some elements such as notes, staves,
>>> systems and measures accordingly to MXML definitions.
>>> If you remember in our last chat I posted a patch that was causing a
>>> bad MusicXML import in Finale for some unknown reasons... But we were
>>> also discussing about a possible bug in the page-width and page-height
>>> export calculation.
>>>
>>> I've worked on the exportxml.cpp code to fix the problem of the bad
>>> page width and height and I figured out that this problem was causing
>>> the system stretch in Finale as well.
>>>
>>> Here is how I changed the code to fix the problem:
>>>
>>> In the past version of Musescore the page-height and page-width of a
>>> musicxml exported document was calculated with the following instructions:
>>>
>>> double t = 2 * PPI * 10 / 9;
>>> xml.tag("page-height", height() * t);
>>>
>>> I don't fully understand this formula but I'm quite sure (as you
>>> suggested in your last mail) that the result is wrong...
>>> In my version the code is changed in:
>>>
>>> xml.tag("page-height", height() * (INCH / millimeters * tenths));
>>>
>>> and the result looks perfect now.
>>> I've also tried the exported xml in Finale and everything seems to be
>>> correct there too. For coherence I've changed the import MusicXML
>>> algorithm too. It seems to work smoothly...
>>>
>>> I attach the last patch... Let me know what do you think.
>>>
>>> Hear you soon,
>>> Raffaele
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Mscore-developer mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>>>
>>>
>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Mscore-developer mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>