Tempoangaben (Paletten->Tempo) beim Playback unwirksam in einigen Fällen
Hallo,
ich habe eine Partitur, die mit einem Auftakt beginnt, und habe eine bestimmte Tempoangabe über Paletten->Tempo eingestellt.
Nun habe ich festgestellt, dass beim PLayback die Tempoangabe nur für den ersten Takt der Partitur wirksam ist, aber nicht für den Rest der Partitur. Es liegt offenbar daran, der erste Partitur-Takt ein Auftakt ist, den ich über die Takteigenschaften (nominell und effektiv) konfiguriert habe. Erst wenn ich die gleichen Tempoangaben auch für den 2. Takt eingestellt habe, ist das Playback korrekt und für die gesamte Partitur wirksam.
Die Partitur ist attached.
Plattform: Fedora 23, mscore-2.0.2-1
| Attachment | Size |
|---|---|
| 2. Satz.mscz | 45.6 KB |
Comments
Well, this score was last saved with 2.1, a nightly or self-build version from the master branch, not with 2.0.2 as claimed.
It changes to 96 BPM in measure 1 (not counting the anacrusis) and very briefly to 107 BPM in measure 13 and 16, and some other valies in some other places.
Has this been imported from midi? In that case sometimes (truely!) infisble tempo markings creep in.
(This it the Englisch forum, hence a reply in Englisch)
Actually there are 3 tempo texts at the beginning, 2 dragged off sight and contradiciting one another ("II. Andante", 75BPM in the anacrusis and "II. Andante", 96BPM in the 1st measure)
Then an "Adagio Tutti", 72BPM in measure 58, which seems to be attended and not dragged out of sight.
The brief changes are probably tie to trills being played, maybe a plain display bug.
Actualy the time stretch on (some of) the trills seem to cause a significant speed up?
Anyway, attach the score with just one tempo marking and 80PBM all the way through
In reply to Well, this score was last by Jojo-Schmitz
A) The mscz score file was not imported from a midi file.
B) The described effect appears with mscore-2.0.2, self compiled mscrore-2.0.3 and self compiled msccore-2.1
C) How do you see all mentioned tempo texts in the score? I see only one (in the first measure).
In reply to A) The mscz score file was by Joachim Backes
A) yes, meanwhile I guessed that too, thre were no realy invisble tempo markings, see C)
B) Well, it has ben saved last with 2.1, and guves a corresponding warning when opened in 2.0.3...
C) select the visile tempo marking, right-click. select all similar, then reset x- and y-offset in Inspector to the defaults, then you can see and delete them. Similar for trills, select one, right-click, select all similar, then reset time stretch to default.
I actually first looked at the mscx file with a plain text editor ('vim' actually)
In reply to A) yes, meanwhile I guessed by Jojo-Schmitz
C) Thanks for the hints, it helped! Now, my score has been cleaned and plays as desired!