Skip to main content
Recent Posts
General Discussion / Re: Question for musicxml experts: representation of flow directions
Last post by Opagust -
Well, it seems I did kwew it back in 2021 :o .
Here's what I found in the coding I wrote for the musicxml to Noteworthy  convertor:

Code: [Select · Download]
def convert_tag_direction_end(element):
    object_line = {
        'dynamic': '|Dynamic|Style:mp|Pos:7',
        'dynamic_variance-sfz': '|DynamicVariance|Style:Sforzando|Pos:7',
        'dynamic_variance-rfz': '|DynamicVariance|Style:Rinforzando|Pos:7',
        'dynamic_variance_text': '|Text|Text:sfp|Pos:7',
        'segno': '|Flow|Style:Segno|Pos:8',
        'coda': '|Flow|Style:Coda|Pos:8',
        'D.C. al Fine': '|Flow|Style:DCalFine|Pos:8|Justify:Right',
        'D.S. al Fine': '|Flow|Style:DSalFine|Pos:8|Justify:Right',
        'D.C. al Coda': '|Flow|Style:DCalCoda|Pos:8|Justify:Right',
        'D.S. al Coda': '|Flow|Style:DSalCoda|Pos:8|Justify:Right',
        'To Coda': '|Flow|Style:ToCoda|Pos:8|Justify:Right',
        'D.C.': '|Flow|Style:DaCapo|Pos:8|Justify:Right',
        'fine': '|Flow|Style:Fine|Pos:8',
        'pedal': '|SustainPedal|Pos:-11|Wide:Y'

General Discussion / Re: Question for musicxml experts: representation of flow directions
Last post by Bart -
Dear opagust,

When you open Musescore, add some "Repeats and Jumps" and export it as a musicxml file, the following code can be found in the file. It seems that the more exotic directions are just a combination of <words> and <sound> tags:

Code: [Select · Download]
      <direction placement="above">
          <segno default-x="-8.00" relative-y="20.00"/>
        <sound segno="segno"/>
Code: [Select · Download]
      <direction placement="above">
          <words relative-y="20.00">D.S. al Fine</words>
        <sound dalsegno="segno"/>
Code: [Select · Download]
      <direction placement="above">
          <words relative-y="20.00">Fine</words>
        <sound fine="yes"/>

Hope this helps.
Object Plugins / Re: PrintConfiguration (0.3)
Last post by hmmueller -
V.0.3 added in root posting, replaced examples in second posting:
- Corrected access to bool properties
- PrintVariation.hmm modifies previous items (so that it is useful for spacers). Because of this, PrintVariation 0.3 is not compatible with previous versions. Also, its properties as well as the internal storage for complete measure replacements have changed.

The object is still buggy with text properties of user objects - strange things happen there, as NWC sometimes (or always?) adds quotes. I do have an idea how to repair this, but it's more work than I hoped.
General Discussion / Re: Import troubles
Last post by Flurmy -
I think I got it.

The import wizard says: "The options below control how each track will be mapped into staves".
Also "Separate MIDI channels", in Options->Import->Track splitting options (in the help it's called "Map each MIDI channel to new staff") makes it clear: different track, different staff.
But, unless you're dealing with a MIDI type 0 file, who has only one track, usually (always...) each track has only one channel.

I was hoping I can still manually force all che channels in a single staff by editing the "list of import instructions" in the import wizard but it's impossible.

It seems the only way is the one I did: convert the MIDI file to type 0 and then import it with "Map each Midi Channel to a new staff" unchecked.
General Discussion / Re: Import troubles
Last post by Flurmy -
No, Rich, I didn't, but that's not my problem.
The problem is strictly connected with channels and tracks.
And, even using a MIDI file type 0, I get a "tempo" hidden staff too.
General Discussion / Import troubles
Last post by Flurmy -
I tried to import a MIDI file putting all the channels in a single staff.
Of course I unchecked the relevant option and... one staff per channel, no matter.

To have all in a single staff I had to save the MIDI file in format type 0. This way it works.
But I saw nowhere the indication of "not for MIDI type 1".
Did I miss it?