After repeat/jump chord symbol playback doesn't stop at Fine if there's no chord symbol at the start of the next measure
Reported version
3.5
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
please check joint file; I had the same problem with similar files, sometimes play continues 5 measures in the first repeat section (normally forbidden) and than hangs.
| Attachment | Size |
|---|---|
| Salut_Reine_du_Rosaire_RC.mscz | 28.34 KB |
Fix version
3.6.0
Comments
It repeats the entire piece 3 times and on a 4th round until the Fine, that's what the repeat barline, the play count property of its measure and the D. C. al Fine and the Fine ask for.
What do you expect to happen, or what happens for your?
In reply to It repeats the entire piece… by Jojo-Schmitz
Dear Jojo Schmitz,
Thank you for your quick reply!
The last silence duration must be 1/4th and silent. If you listen to it, an unwanted "E" slowly fades away and this lasts during at least 6/4. Only after approximately 15 seconds the play function is disabled.
That is the problem! I have changed the duration of the last measure back to 4/4, initially programmed for 3/4 to cope with the pick-up measure, but the problem remains.
Can you please give me a hint to play this last measure as written in the partition?
Many thanks on beforehand,
Gérard Kieft (my first name was changed to gerrd when I subscribed)
So this is not about the repeats and jump at all?
In reply to So this is not about the… by Jojo-Schmitz
No, I managed after a lot of trying to make most repeats and jumps working. The handbook is not extremely clear on doing these things!
No, the main problem is the final duration and the persisting note fading away ofter a while.
The song should last 2:39" but the record lasts 3:02". You can check if you take the file and export as mp3 and than listen: after the normal timing the "E" sound fades away from 2:39 to 2:47 , followed by a silence from 2:47 to 3:02.
In reply to No, I managed after a lot of… by gerrd kieft
The Eb chord in the "Fine" measure causes this.
Click on the "Eb" chord and change its duration from the Inspector: "Chord / Rest duration".
By default, "Until next chord symbol" is set. However, the chord continues for a while as there is no chord symbol in the next beat/measure.
This is THE simple SOLUTION! Marvellous! After hours of restarting to write the score for no result.
Now I can continue rewriting this marvellous song and prepare it for our choir as soon as COVID allows us to sing together again!
Merci beaucoup! ;-))
Gérard
Seems to be the same basic issue as an example reported in the forum recently - in both cases, a chord symbol before a jump but no corresponding chord symbol in the next measure, which confuses the playback algorithm. See https://musescore.org/en/node/311854
Workaround: change the last 'desired' chord symbol's duration via the Inspector to "Chord / Rest duration" or " Measure End)
Relates to #310930: [EPIC] Issues with Chord Symbols playback and #299323: [EPIC] Issues with repeats and jumps
Other workaround - finish entering the chord symbols :-). The problem isn't with the chord symbol itself but the fact that the next measure lacks one, but in both cases, that appears to have just been an oversight.
In reply to Relates to #310930: [EPIC]… by Jojo-Schmitz
Thank you so much for your answers!
I can now progress again with Musescore
Gérard
https://github.com/musescore/MuseScore/pull/6857
In reply to https://github.com/musescore… by jeetee
I had a good answer on Nov 2th. The problem is resolved. Why do you want me to subcribe to github.com?
Gérard
In reply to I had a good answer on Nov… by gerrd kieft
I don't want you to do so.
What you have been given is a workaround for the mentioned issue.
What I have linked to is a code change that will make this work more as intended by default; so future users don't need to look up workarounds and use them.
This is how our issue tracker works; When that linked code will be accepted into MuseScore, this will also update this issue to mark it as fixed.
The issue tracker is not just like a forum post. Issues here remain open until we abandon them officially or they get fixed for real.
In reply to I don't want you to do so… by jeetee
Thank you for this kind reply. After having worked on machine language for APPLE more than 40 year ago and swithched to Pascal I have abandoned any code working except a bit of HTML for my poor website. I prefer putting notes on lines to make/change songs and combine sounds! But I'll try to integrate solution this weekend!
Again though.. there is nothing for you to do unless you desire building an unstable development version yourself.
What you're witnessing is just the normal process of how a patch is added to MuseScore. It requires no further action from your end.
The code maintainers will include this patch into the codebase for the upcoming 3.6 release.
In reply to Again though.. there is… by jeetee
Thank you again for this reply! I indeed am very hesitant to tinker with a stable working program. I'll leave it to the professionals!
Fixed in branch 3.x, commit 60741ad2b5
Fix #312489 Harmony duration interpretation
Fixed in branch 3.x, commit acd66afa49
_Merge pull request #6857 from jeetee/312489-Harmony-duration-interpretation
Fix #312489 Harmony duration interpretation_
Fixed in branch master, commit c19d1b4c24
Fix #312489 Harmony duration interpretation
Automatically closed -- issue fixed for 2 weeks with no activity.