NoteWorthy Composer Forum

Forums => General Discussion => Topic started by: cfflorendo on 2017-10-02 04:41 am

Title: Double Bar Line should not affect flow (serious bug)
Post by: cfflorendo on 2017-10-02 04:41 am
Dear all,

This is related to this report:
https://forum.noteworthycomposer.com/?topic=9365.msg66905#msg66905

I use the 2.75.

I made a piece:

intro
master repeat open
some measures with DOUBLE BARS
first ending
master repeat close
second ending

When the DOUBLE BARS are replaced with single bars, the software follows the flow direction.  If I retain the double bars, the repeat is done many times and jumps to an unintended measure.

DOUBLE BARS should have no effect on playback as it is merely a cosmetic indicator of some sectional change in a piece. 
https://en.wikipedia.org/wiki/Bar_(music)

I hope this bug can be fixed...

Thank you!

Best Regards,

Carlo


 



Title: Re: Double Bar Line should not affect flow (serious bug)
Post by: hmmueller on 2017-10-02 06:57 am
Yes - this is one of the two NWC surprises with playback (the other is that accidentals shift also notes an octave higher and lower).

My solution is that I now don't use double bars, but two single bars with a spacer of length 0.25 in between:

Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|Note|Dur:4th|Pos:0|Opts:Stem=Down
|Note|Dur:4th|Pos:0|Opts:Stem=Down
|Note|Dur:4th|Pos:0|Opts:Stem=Down
|Note|Dur:4th|Pos:0|Opts:Stem=Down
|Bar
|Spacer|Width:25
|Bar
|Note|Dur:4th|Pos:0|Opts:Stem=Down
|Note|Dur:4th|Pos:0|Opts:Stem=Down
|Note|Dur:4th|Pos:0|Opts:Stem=Down
|Note|Dur:4th|Pos:0|Opts:Stem=Down
|Bar
!NoteWorthyComposerClip-End

The attachment shows that measure numbers are still correct with this trick; and that line breaks work as expected (i.e., both single bars end up in the upper line).

H.M.
Title: Re: Double Bar Line should not affect flow (serious bug)
Post by: cfflorendo on 2017-10-09 09:08 am
Dear hmmueller,

Wow!!! Thank was a good work around :)  It worked for me.  Thank you!!! I wish though that this bug gets fixed in the next versions.

Best Regards,

Carlo