Re: Timing or Mathmatical Problem
Reply #72 –
I took 'obscure trickery' as a compliment, but David, you are correct: it was probably intended to be snide.
No, it does not. It concerns where the next note/chord/rest should be placed after a RestChord or Chord with differing durations (IOW, |Dur: <> |Dur2:). The solution for the original poster was to either use layering or to use a tie. He chose a tie.
Before layering (c. 1998), NoteWorthy tried to handle 2 voices on one staff without forcing the User to expressly mark each note/rest/chord as to its voice. This was all in the spirit of NWC being easy to get a song done without mastering the entire program. It was found to be inherently unworkable. One reason was this very problem. There were others. It was a painful realization that was reached only after much discussion.
RestChords and split stem Chords are legacy objects. There is nothing that can be done with them on one staff that cannot be done without them on 2 layered staves. This has been true for about 7 years. AFAIK, there has never been an official announcement, but NoteWorthy stopped all enhancement of them somewhere around v1.70. They are supported in about the same sense that Micro$oft supports Outlook Express 6 in XP. It runs, but don't look for new features.
Some examples: NWC2 adds 'Use stems for articulations' to every RestChord even if it has no articulation. This might make some sense if an articulation could be added later, but this is not possible except by editing the ClipText. Modifing the 'Vertical Offset' runs into the same wall. RestChords cannot be beamed and split stem Chords do not beam properly. Split stem chords lack independent adjustment of stem lengths making them generally worthless in a song with Lyrics.
These problems have existed for years. IMO, they don't get fixed because you can always put each voice in its own layer.
(to slurs!)
This topic was dormant for 2 months until I posted <this>. I now regret doing it.