Musescore 4.4 changing tempo rewinds or fast forwards
During playback of a score, if use the tempo slider to slow the tempo, it also rewinds the score a certain amount. If I use the tempo slider to speedup the tempo, it fast forwards the score a certain amount. How much it rewinds or fast forwards seems related to % of tempo change.
Is it suppose to work that way? I prefer it continue playback from where I made the tempo change, instead of rewind or fast forward.
Attached pic of tempo slider.
| Attachment | Size |
|---|---|
| Screenshot 2025-02-27 at 10.43.47 AM.png | 144.67 KB |
Comments
I didn't even know there WAS a tempo slider...the more you know! ^^'
Are you trying to change the overall tempo of the song, or is it for navigational purposes? Personally, I prefer manually inputting my tempos lol. (I just looked over some of my own scores, and I don't even HAVE a slider! How do you access that feature?)
For the score playback, couldn't you just use the accel. and rit. palettes? Place specific tempos at two separate measures, then place the accel. or rit. in the space between them. From there, you can choose the specific percentage at which the song speeds up or slows down! Also, having a manually-inputted tempo negates the need for a slider, you just type in a new tempo number if you don't like the current one lol
In reply to I didn't even know there WAS… by SpartanChief17
To get the Tempo Slider, drag the 6 dots down (see screenshot). To get rid of it, drag the 6 dots up. It'd be nice if when you hover over the 6 dots it tells you what you can do with it. I learned about it coming across a post on it by chance.
To be clear:
In reply to To be clear: Tempo marks… by DanielR
I know and agree. I use the tempo slider to temporarily change the tempo when I am learning a piece.
I don't think either of you has addressed the point that firepiston is trying to make. I have noticed the exact same problem. I get round this by assigning a fictitious tempo to the bit that I am trying to playback (eg for the purposes of analysing the section ) and then, when I am happy, scrubbing that tempo.
This is certainly a bug.
In reply to I don't think either of you… by Ali Wood
@Ali Wood, thanks for noticing the bug. The tempo slider is a useful tool to quickly and temporarily slow down or speed up a score that I am learning to play. The accompanying rewind / fast forward messes up the spot I was working on and have to spend time to find where I left off. I did search for posts reporting this problem, didn't find any, so started this one.
In reply to @Ali Wood, thanks for… by firepiston
Thanks - It is quite a significant bug, isn't it?
I guess folks within the development team notice these posts, but who knows - if you find a good way of escalating this let everyone know.
In reply to Thanks - It is quite a… by Ali Wood
Most don't, so you'd better report this on GitHub, https://github.com/musescore/MuseScore/issues/new/choose
In reply to Most don't, so you'd better… by Jojo-Schmitz
I do not have a github account and do not want to create one. This is the support forum for musescore! There's no way to report bugs here?
In reply to I do not have a github… by firepiston
You don't need to report it.
Known issue https://github.com/musescore/MuseScore/issues/16084
I'm not so sure this is a bug. Consider the three sets of numbers in the top right of the panel. The first shows the time the score has been playing at the given tempo. The second is cursor location. The third is the given tempo. Personally, I don't care for the percentage method of changing the tempo. But when you change the slider, look at the lapse time number. It doesn't change. Look at the cursor location number. It shows where the cursor would be if the score had been playing at the new tempo all along. That's why playback starts at a different place.
It's working the way it has been programed. But it isn't what we expect. That doesn't make it a bug. I don't use this method because, as I said, the whole percentage idea doesn't make sense to me. In general, it seems quicker to just add a new tempo, and then delete it when I'm done.
In reply to I'm not so sure this is a… by bobjp
We can guess whether something was designed to do what it does or not, but ha! - surely the effect of jumping to a different place in the score can not have been intentional ;)
I do get your point, bobjp, about it not being a "bug". However it is a poor design, if nothing else, as you have acknowledged. How are 'bad designs' reported? As enhancements?
As to your workaround using changed tempo markings - yes, we are obliged to use this, but it is quite clumsy and time-consuming if experimenting with different speeds..
In reply to We can guess whether… by Ali Wood
Sure. It's just that on my list of things that I believe need to be worked on, this is very, very low. I'm used to the "workaround" because it is what I've always used.
In reply to I'm not so sure this is a… by bobjp
Regarding the three sets of numbers in the top right of the panel, the first 2 can be changed but not the last (tempo). Why? If tempo numbers can be changed (w/o rewind/ fast forward), that would work for me, then the tempo slider is no longer needed. You can then also get rid of the 6 dots. Result is a simpler and cleaner interface.