Playback faster than it should be
Does anyone know why the guitar note plays quicker (approximately the tempo of a quaver) than the rest of the score?
Is it correctable for 2.0?
I think I added the anacrusis later and messed with tempo texts, which could be part of the cause.
| Attachment | Size |
|---|---|
| Playback faster than it should be.mscz | 2.19 KB |
Comments
There are two tempo changes in the
tempolistinside the file.However, there are no tempo texts. Probably by inserting tempo texts at the proper ticks the tempo changes can be overwritten.
Here are the lines in the tick.mscx file inside the mscz archive.
{syntaxhighlighter brush:xml;first-line:45;}
2.33333
1.16667
{/syntaxhighlighter}
In reply to There are two tempo changes by ABL
Like what normally happens in 2.0 for tempo markings deleted in 1.3 scores, it could appear invisible.
Any disagreement?
In reply to Like what normally happens in by chen lung
Please elaborate...
In reply to Please elaborate... by [DELETED] 5
I thought this was fixed, but maybe not: #11603: Inputting empty Tempo Text name should list BPM
Anyway, in the attached example, you may see that in 1.3, one tempo marking is visible, but in 2.0, there are two - one is visible and the other, invisible.
![Invisible tempo.png]( "Invisible tempo.png")
However, if you delete it in 1.3, save, and open it in 2.0, no tempo marking appears.
Using MuseScore 2.0 Nightly Build 28b5daf - Mac 10.7.5.
In reply to I thought this was fixed, but by chen lung
You expected it to appear after deleting and saving it? I'm confused.
In reply to You expected it to appear by Marc Sabatella
No, he's saying if you delete the visible one in 1.3 (leaving the invisible one alone because you can't see it), the invisible one also disappears when loading into 2.0
In reply to No, he's saying if you delete by schepers
As far as I can tell, the only reason the invisible one appears in 2. was that it "borrowed" the text of the visible one. Now that there is no visible one to borrowed from, there is nothing to display. But I am not sure under what circumstances any of this would normally occur, so it's hard to say what I expect.
In reply to As far as I can tell, the by Marc Sabatella
That's what I was thinking as well. Why is it an exact copy, almost like a shadow?
In reply to I thought this was fixed, but by chen lung
In this sample there are _3_ tempos defined on measure 1. One 1.2 (d=72), one 2.4 (d=144) and one 1.2 (d=72) in that order. The d=72's are invisible. There's also an entry higher up in the xml called
tempolist fix="2"
tempo tick="0" 2.4
/tempolist
When the visible d=144 is removed (and the file saved and reloaded), the tempolist fix is empty and the two invisible d=72 remain, and are still showing in grey.