![Profile picture for user sj1](/sites/default/files/styles/avatar/public/avatars/picture-3263-1546274390.jpg?itok=SXtU0WpN)
Posted
Hi,
Exporting MusicXML from a file that starts like this:
is giving results like this (as imported into Band-in-a-Box):
As can be seen, the chord qualities ("m7", "7") are not arriving in the destination.
For reference, I've attached the Synfire-exported .musicxml file, and another file 'Desafinado.musicxml' which imports fine into BIAB with all the chord qualities intact.
The difference appears to be in the kind tag inside of the harmony tag.
Insufficient: <kind>minor-seventh</kind>
Working: <kind text="m7" use-symbols="no">minor-seventh</kind>
Of course the goal of using MusicXML is interoperability, so a fix for this is much-to-be-desired. Thanks.
Tue, 2024-06-25 - 18:51 Permalink
BTW, my hope for MusicXML export of chords would be for the chords as expressed in Synfire's governing Harmony parameters to be expressed exactly as such in the exported MusicXML <harmony> tags.
IOW, don't (or at least optionally don't) render to MIDI and then back-analyze to specify/name the chords. Rather, take the specified/named chords as they exist in the Harmony parameters and keep that specification/naming (as originally provided by the user!) in force for the MusicXML output.
To put it another way: Preserve the composer's explicitly written intent as to the harmony at any given measure. (as that explicitly written intent has been provided in order to guide musicians, programs, or any other entity's subsequent realization)
Wed, 2024-06-26 - 18:19 Permalink
You need to reset your Catalog with File / New / Extended.
(https://docs.cognitone.com/synfire/EN/interface/AppCatalog.html?hl=cata…)