Swing not consistant

• Sep 3, 2020 - 22:10

Hey,
so I wrote a score for a boogie woogie song with a common blues pattern in C, but unfortunately, only the C lick and not the F and G lick in the bass line are played back in Swing. I double checked, I even exported this to a midi file and after some investigation, I can clearly confirm that the pattern is only swung in C. It works perfectly fine for C, but somehow doesn't apply to the measures in F and G (yes, I activated Swing globally, and when I figured it didn't work, I turned it off globally and seperately tried with the text "Swing", both tries were at 60% intensity)

I attached a screenshot of the program 'Piano From Above' in order to display the exported MIDI file, as you can see, the lick played in F should be played the same as in C (please consider the length of the green marked tiles which displays the duration of the note played, and they should be the same when they are not). Score is written in 204bpm, maybe there is a bug but I sense that I must be missing out on something.

I also attached the score. Reducing the bpm just makes the not swung parts stand out more.

Additionally, I attached the exported .ogg File from that very score. Can you hear how in F and G the notes are played without a swing rhythm when they should be?

Please help!
Leonard


Comments

In reply to by afx_piano

I don't know what the picture is supposed to be showing. I'm sure it from a DAW or something similar. I could be a smart @$$ and tell you I agree that the F's don't swing because there are none after m8 but I'm sure that's a typo on your part. I listened to the entire thing at 104 BPM and the swing was unmistakable throughout. At 204 BPM, it was so fast that I had trouble hearing any swing on any note. Face it 60% swing isn't very much. When I set the swing to 67 (which is common) the swing becomes apparent to me even at 204 BPM and it stays steady throughout.

In reply to by afx_piano

The ogg file made it easier for me to see where you were hearing the difference. It's in mm3-4. You message is at m8 so I wasn't concentrating on mm3-4. I deleted the measures then reentered them exactly has you had them and they worked fine.

I looked through the music file (.mscx) to see if there was anything affecting the playback in there. I found the problem and I suspect you edited it with the Piano Roll Editor (PRE) because I see this in the file

     <Measure>
        <voice>
          <Beam>
            <StemDirection>up</StemDirection>
            </Beam>
          <Chord>
            <durationType>eighth</durationType>
            <Note>
              <Events>
                <Event>
                  </Event>
                </Events>
              <pitch>53</pitch>
              <tpc>13</tpc>
              </Note>
            </Chord>
          <Chord>
            <durationType>eighth</durationType>
            <Note>
              <Events>
                <Event>
                  </Event>
                </Events>
              <pitch>53</pitch>
              <tpc>13</tpc>
              </Note>
            </Chord>

Those <Event> entries are made by the PRE.

When I deleted the notes then reentered them from scratch it played correctly.

In reply to by afx_piano

Obviously: If there is a change made within the PRE, priority is given to the PRE. (which makes sense).
Even though it looks like nothing has been done in the "events" tags (empty), because there are those "Events" tags there, the software gets the message "attention: there is an operation with PRE here" and the Swing operation is canceling for these measures.

Possible solution: If the "Events" tags are empty, this unnecessary information should not be there.

In reply to by afx_piano

Go to https://musescore.org/en/project/issues/musescore and click on the "Add new issue" button.

Set the priority to "medium" and the severity to "major"
In the text area list clear steps to reproduce the issue. Perhaps provide a starting point score as attachment.
Something like:

1. Open the attached score
2. Open the Piano Roll Editor
3. Select notes ...
4. Do some more stuff

Expected result: Swing is preserved
Actual result: Swing is overridden

Likely cause: There are empty "event" tags inserted, see attached resulting file

Someone will then cross link the issue with this forum thread so the developers will have all background information available.

Do you still have an unanswered question? Please log in first to post your question.