Bug: grace note followed by ritard., a tempo

2009-12-18 07:21 pm

When NWC 1.75 encounters a ritard. following a grace note, it starts the ritard. before the grace note.
NWC2 starts it after. A reasonable change which causes few problems unless there is an a tempo. Then, NWC2 sometimes gets confused and adds extra tempo(s) after the a tempo.

This clip distills and exagerates the problem:

Quote

!NoteWorthyComposerClip(2.0,Single)
|Tempo|Tempo:120|Pos:11
|Rest|Dur:Whole
|Bar
|Rest|Dur:4th,Grace
|TempoVariance|Style:Ritardando|Pos:8
|Rest|Dur:Half
|Tempo|Tempo:90|Pos:-9|Visibility:Never
|Tempo|Tempo:120|Pos:-6|Visibility:Never
|Text|Text:"a tempo"|Font:StaffItalic|Pos:8
|Rest|Dur:Half
|Bar|Style:LocalRepeatOpen
|Rest|Dur:Whole
|Bar|Style:LocalRepeatClose|Repeat:250
!NoteWorthyComposerClip-End

If you press F5, you will see a running time of: 11:04
If you remove the grace rest, the running time changes to: 8:24

This mf2t output shows the problem. The erroneous tempo generated is in red.

Quote

MFile 1 2 192
MTrk
0:0:0 Meta Text "Generated by NoteWorthy Composer"
0:0:0 Tempo 500000
1:0:36 Tempo 504201
1:0:49 Tempo 508474
1:0:62 Tempo 512820
1:0:75 Tempo 517241
1:0:88 Tempo 521739
. . .
1:1:152 Tempo 631578
1:1:164 Tempo 638297
1:1:177 Tempo 645161
1:1:190 Tempo 652173
1:2:0 Tempo 666666
1:2:0 Tempo 500000
1:2:11 Tempo 659340
1:2:11 Meta TrkEnd
TrkEnd
MTrk

Bug applies to: NWC2.exe, Version 2.0

Re: Bug: grace note followed by ritard., a tempo

Reply #1 – 2009-12-18 09:06 pm

Confirmed. Good catch...