In Noteworthy 2.1, when I selected a chord that solved in the next chord and clicked 'tie' (or pressed '/'), only the notes that did not change between the chords would actually tie. But now, in version 2.5, ALL the notes are trying to tie. So I get stuck with (mostly) 2 notes that are not able to tie, but show a tie anyway... Correcting this takes a lot of time. Building a chord 1 by 1 also takes more time (I use a midi keyboard now)...Anyone know how to handle this?In the attachments you will see the bad situation (knipsel1) and what I want it to be (knipsel 2).
There's an easy way to toggle the tie on and off for each note of a chord. If you position your cursor over the notehead in question and right-click, a context menu appears, in which "Tie" is a choice. Clicking that will toggle the tie on or off for that note in the chord.
The trick is to enter the "/" before doing Enter or Cntl/Enter to add the note.Note how the nwctxt looks:!NoteWorthyComposerClip(2.51,Single)|Chord|Dur:4th,Dotted,Slur|Pos:-3,b-1^,b2|Chord|Dur:16th,Slur|Pos:b-4^,-1^,1|Chord|Dur:16th,Slur|Pos:-4^,-1^,0^|Chord|Dur:4th|Pos:-4,-1,0!NoteWorthyComposerClip-EndThe carat "^" indicates a tie. As a last resort you can cut a note to the clipboard, fix it with editor, select all to the clipboard, go back to NWC and paste it back.HTH
Now that NWC 2.5+ has a notehead interface, it makes sense that the 'Note Tie' Toolbar Button would affect all notes in the user selection. NWC 2.5+ behavior makes arpeggiating much easier.
then it 'saw' which notes were also present in the next chord and only tied those notes instead of all the notes in the chord...
I remember the days where, for instance, I could change the instrument of a staff with the keyboard only.
The same happened with the selector buttons. Beautiful and elegant, but, instead of one click, you now need at least two clicks (and again position the mouse).
Page created in 0.043 seconds with 24 queries.