metadata vs printed text in musicxml

3 messages Options
Embed this post
Permalink
Leon Vinken

metadata vs printed text in musicxml

Reply Threaded More More options
Print post
Permalink
All,

in order to properly distinguish metadata and printed text, I intend to
make the following changes:

Map all entries in the metadata dialog to their corresponding MusicXML
metadata elements:
work title <-> score-partwise/work/work-title
work number <-> score-partwise/work/work-number
movement title <-> score-partwise/movement-title
movement number <-> score-partwise/movement-number
source <-> score-partwise/identification/source
Add missing metadata fields to the metadata dialog (creator, rights)

Text (to be) printed in the header (title, composer, etc.) are MusicXML
credit elements. Note that these can contain formatting and layout
information.

Older files typically don't include MusicXML credit elements, which were
introduced with MusicXML 1.1. If no credit elements are present,
metadata also has to be copied to corresponding MuseScore texts.

As always, all suggestions are welcome.

Regards, Leon.


------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
lasconic

Re: metadata vs printed text in musicxml

Reply Threaded More More options
Print post
Permalink
Very good! That is for import right?
For export, I guess : if metadata fields are empty, take the musescore text ones to fill musicXML metadata elements. Musescore texts will be saved in credit.

Looking forward to test this.

2009/2/26 Leon Vinken <[hidden email]>
All,

in order to properly distinguish metadata and printed text, I intend to
make the following changes:

Map all entries in the metadata dialog to their corresponding MusicXML
metadata elements:
work title <-> score-partwise/work/work-title
work number <-> score-partwise/work/work-number
movement title <-> score-partwise/movement-title
movement number <-> score-partwise/movement-number
source <-> score-partwise/identification/source
Add missing metadata fields to the metadata dialog (creator, rights)

Text (to be) printed in the header (title, composer, etc.) are MusicXML
credit elements. Note that these can contain formatting and layout
information.

Older files typically don't include MusicXML credit elements, which were
introduced with MusicXML 1.1. If no credit elements are present,
metadata also has to be copied to corresponding MuseScore texts.

As always, all suggestions are welcome.

Regards, Leon.


------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer


------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Leon Vinken

Re: metadata vs printed text in musicxml

Reply Threaded More More options
Print post
Permalink
Importing/exporting meta-data and handling of credits is in as of r1720, please test, especially compatibility with other applications.

Notes:
- complicated things like multiple credit-word elements of font changes in texts are not supported yet, e.g. Recordare's BeetAnGeSample.xml is not imported correctly
- I don't have access to Finale, would like to know if Finale compatibility is OK

Regards, Leon.

lasconic wrote:
Very good! That is for import right?
For export, I guess : if metadata fields are empty, take the musescore text
ones to fill musicXML metadata elements. Musescore texts will be saved in
credit.

Looking forward to test this.

2009/2/26 Leon Vinken <leon.vinken@xs4all.nl>

> All,
>
> in order to properly distinguish metadata and printed text, I intend to
> make the following changes:
>
> Map all entries in the metadata dialog to their corresponding MusicXML
> metadata elements:
> work title <-> score-partwise/work/work-title
> work number <-> score-partwise/work/work-number
> movement title <-> score-partwise/movement-title
> movement number <-> score-partwise/movement-number
> source <-> score-partwise/identification/source
> Add missing metadata fields to the metadata dialog (creator, rights)
>
> Text (to be) printed in the header (title, composer, etc.) are MusicXML
> credit elements. Note that these can contain formatting and layout
> information.
>
> Older files typically don't include MusicXML credit elements, which were
> introduced with MusicXML 1.1. If no credit elements are present,
> metadata also has to be copied to corresponding MuseScore texts.
>
> As always, all suggestions are welcome.
>
> Regards, Leon.
>
>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco,
> CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the
> Enterprise
> -Strategies to boost innovation and cut costs with open source
> participation
> -Receive a $600 discount off the registration fee with the source code:
> SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Mscore-developer mailing list
> Mscore-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Mscore-developer mailing list
Mscore-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mscore-developer