Play Panel Tempo persists despite tempo marking
The score is marked 120 to the quarter. I temporarily changed
that to 80 to hear some parts more clearly.
Now, every time I open the score, it has remained at 80. I deleted the
tempo text, and re-entered it. No effect. I can change the tempo to
120 with the play panel, but as soon as I close the score and reopen it
it is back to 80.
Can't find anything more explanatory in the manual...help?
Thanks,
Comments
What version are you using. I seem to remember a bug like this being fixed some time ago.
If you attach your score, we can do better just guess, but if I had to guess, based on the specific numbers you mention, my money is on confusion between quarter and dotted quarter as the tempo unit. That and/or the properties set on that tempo marking in the Inspector.
Marc and Mike,
Thanks so much for the quick replies. Great support!
Version is 2.2 running on Linux,
The piece is in 4/4, and the tempo mark reads quarter note = 120.
(double-checked).
When I opened the score this morning, it had mysteriously cured
itself. Ouch. Very embarrassing, sorry.
I couldn't get it to behave when I posted, though, despite anything.
I write software, so I know ( presumably) how to test an app,,
One odd thing: I had pinned the tempo marking to a rest right after the
first note ( not the first note ). The piece started in the right tempo, then abruptly
went to 80 to the quarter. I re-pinned it to the first note, saved, closed, and reopened.
And it worked. But I opened another ( earlier ) version with the tempo
pinned to the same rest, and it played at the right tempo. So...go figure.
Anyway, really happy with the new version. It's one of the most intuitively-
written apps I've used... I usually find it challenging to learn someone else's
software. I'm currently reading Marc's book.
Thanks again ,
msp
In reply to Marc and Mike,… by msphild
There are many bugs in the tempo marks. You have apparently found one. See #272381: [EPIC] Tempotext issues. Perhaps you could shed light on the issue you have discovered.
In reply to Marc and Mike,… by msphild
Glad it's working! There are a couple of known bugs (listed in the above link) that are close to what you describe, but the ones I can think of fix themselves after reloading the score, and you said you saw the problem each time you opened the score, so the descriptions didn't fit. Indeed though, if you ever do figure out how to reproduce the problem, post again and describe the steps - or check the link above to see if it's already reported.