playback tempo changes without doing anything
I have the newest 4.0 and when using playback the tempo will change without me doing anything. In my piece I have playback set to 96, but after the 2nd ending it changes to 76. Any clue why this is happening?
Comments
Not without the score
I am having this problem too! Have you found any solutions? I'm going to have to go back to 3.0 if I can't fix it, which would be sad because I like a lot of the other new features. Mine is switching back and forth between tempos nearly every measure, it's terrible.
In reply to I am having this problem too… by Beth Marmorstein
Why 3.0 rather than 3.6(.2)?
Anyway: those fermatas stretch each note to 200% their duration
In reply to Why 3.0 rather than 3.6(.2)?… by Jojo-Schmitz
Sorry, it was 3.6.2 My mistake. I just mean the previous version and wasn't really thinking about exactly which it was.
In reply to Why 3.0 rather than 3.6(.2)?… by Jojo-Schmitz
Yes, the fermatas are definitely the problem. If I remove all the fermatas it plays correctly. I've been playing around with this and it's basically the more fermatas, the worse the tempo issues are.
I don't think the fermatas work correctly at all. As far as I can tell, the fermata causes the tempo to change to 1/2 what it was, which might be fine for very simple compositions, but if you have multiple parts with the fermata falling on different duration notes, it results in strange behavior. I'm attaching a simple test case. The fermatas in the second measure are meant to lengthen the last beat of the measure. But because the note in the baseline is a whole note, it apparently gets applied to the first beat of the measure and messes up the rhythm of the upper line, which ought to be steady quarter notes until the last beat.
In reply to Yes, the fermatas are… by Beth Marmorstein
You can change that stretch in the Properties of the Fermatas
In 3.x the default stretch was 100%, no stretch
In reply to You can change that stretch… by Jojo-Schmitz
The problem is that the tempo doesn't return to its previous setting after fermatas but remains at whatever stretch the fermata is set at. So unless you go in and change them all to 100%, playback tempo gets slower and slower.
In reply to The problem is that the… by Daryl Yoder
The fermata only affects the one chord it is attached to, by stretching it, directly afterward the original tempo is continuing
In reply to The fermata only affects the… by Jojo-Schmitz
That is not how it is currently functioning in MuseScore 4 for me. The original tempo is not continuing afterwards.
In reply to That is not how it is… by Daryl Yoder
Then this might be a new bug
In reply to That is not how it is… by Daryl Yoder
It works for me, but there might be something unique about your score triggering a problem.. Please attach it and describe where the issue occurs.
In reply to It works for me, but there… by Marc Sabatella
Looking closer, it seems a slightly different from simply not returning to the original tempo. Though all fermatas are set at 200% stretch, they actually play at 1/3 the original tempo, then it doubles tempo at the end of the fermata, meaning it's slower than before. E.g. if original tempo is 75 bpm, the fermata plays at 25 bpm, and then continues at 50 bpm afterwards. I created a new score with a couple of bars and a fermata and it behaved normally so I'm at a loss as to what is different with this one.
In reply to Looking closer, it seems a… by Daryl Yoder
Are you talking about bar 29? I'm not hearing anything unusual there, the tempo resumes normally. Perhaps a temporary glitch that fixes itself on save/reload?
In reply to Are you talking about bar 29… by Marc Sabatella
It was happening at all 4 or 5 fermatas in the score, but a quit and restart seems to have fixed it--thanks. I'll keep an eye if anything seems to trigger it again.
I tested by turning on the metronome. The metronome click is so erratic as to sound more like a clave. Doesn't make a difference if tempo markings are left as is, or removed. Borders on bizarre.
I had the same problem after rewriting some notes form voice 2 to voice 1, making some fermatas disappear by deleting the attached note (not the fermata), and then changing the stretch of the visible fermatas.
Apparently the fermatas that disappeared by the attached note in voice 2 does not truly disappear. I noticed this when I removed all notes from voice 2 in a measure. The fermata would then reappear in approximately the same spot. The measure that changed the tempo of the piece had such a "hidden fermata". Removing this fermata fixed the issue for me.
In reply to I had the same problem after… by Martentje
Thanks to you folks for your thoughts on this tempo changing problem. I don't know how to make a suggestion to Musescore developers, but if I could I would say sacrifice the "Tempo's response to Fermatas and such" for now. Offer a way to keep Tempo locked in at one speed for now. Once a bug has been worked out, try adding less important but hugely destructive features that make "playback" unusable for the masses. Best Wishes all. I can't use it as is.
In reply to Thanks to you folks for your… by frontdrumpogo
Hmm, sounds liek you are experiencing some sort of problem, but it isn't at all clear what it is and whether it's a bug or just something you need help with. Please attach your score and describe the problem you are perceiving in more detail so we can try to reproduce it for ourselves. Then we can either help you correct the notation if that's what's causing the issue, or help you submit a bug report if appropriate.
Meanwhile, if you prefer not to have your score change tempo, the obvious solution is, don't add tempo markings. Their whole point is to change the tempo, after all.
Unless I close and reopen my projects, the same thing happens to me. When I add a fermata, the playback tempo drops at the fermata but doesn't revert to the original tempo. Instead, it goes to a slower tempo. This doesn't go away unless I close and reopen the project. However, when I do this to fix the issue, it just comes back once I edit any previous fermatas or add new ones. It's like a never-ending cycle of closing and reopening just to hear my projects play correctly.
Same problem here w/version 4.2.1-240230937 on macOS 14.2, Arch.: x86_64.
After restarting musescore, the tempo appears to be honored when going into the second ending. Has nothing to do with the score itself. Bug.