Pedal symbols also should work, but they only work on the staff they are placed on;
Pedal symbols affect the MIDI channel of the staff they are placed on.
I placed a D# (cursor on D, press #, press enter), then pressed ctl-enter on the same staff line. The note moved over slightly (why?)
I also tried entering a Dnat with a D# and saw one two-stemmed note with both a sharp and a natural.
In real music would this need to be shown as a D chorded with an Eb instead of D#?
While I was fooling around with chords, attempting to answer the question about d and d#, I was confused by Noteworthy's behavior, and curious about how it SHOULD be displayed. I placed a D# (cursor on D, press #, press enter), then pressed ctl-enter on the same staff line. The note moved over slightly (why?) and the note now had a sharp and two stems -- up and down. When I tried entering the natural note first, it looked the same. When I played it, it seemed to play both notes, but looking at it, it looked like two D#s chorded together. I also tried entering a Dnat with a D# and saw one two-stemmed note with both a sharp and a natural. In real music would this need to be shown as a D chorded with an Eb instead of D#? Is there any way to show a chord of D# and Dnat in the same octave?
Hi Susanna,any accidental in a bar (measure) will affect all the subsequent notes of the same pitch (on the same line or space) for the rest of the bar (measure) unless there is a negating accidental (natural, flat, double sharp etc.). This is standard notation practice.However, when the parts are "divisi" but on the same staff then an accidental on a stem up note should not be interpreted as affecting a following stem down note on the same line or space. NWC does not perform this differentiation thus it is necessary to place a negating accidental on the subsequent note of the other part.This is not a problem if the parts are on layered staves, it only occurs if both parts are written as chords (they may be split stem or not) on a single staff.Another shortcoming of NWC is that if there is an accidental on one note, then, contrary to standard practice, it will affect the same note in all octaves. This also requires a negating natural that wouldn't normally be seen in a score (unless some nice arranger/notator decided to put in a courtesy accidental as a reminder).Hopefully this will help.
I'm wondering if perhaps I have to delete both notes, re-add one, and then make a layer with the other. Will that work, or will all the rests I put in the staff with the single note show up somewhere on the staff?
Warren - I don't see that they don't line up.
They don't. Male and female voices should be singing the same rhythm at the start of the refrain. You can see the problem at the bottom of
One more question, Rick - how do I find the information on how to convert the code you posted?
I'm a fairly new - and rather timid - user of Noteworthy 2
Why in the world are there no plans to fix it? Is the solution that complex? I used to work for a software company, and that sort of thing would have been completely unacceptable to our customers. Or perhaps noteworthy is the only - or best - player in the game, and doesn't feel that it's necessary to fix everything?
This is an architectural quirk of NWC. Note accidentals apply in all octaves within the bar. The way to avoid the problem at present is to always use the correct accidental in all other octaves of that same named note after you use an accidental in one octave of the named note.
This find method has a set of predefined find algorithms which can be used to search for objects in the staff. The Unassigned Octave Accidental algorithms can be useful when trying to resolve octave intervals in a staff that do not sound as expected. Unassigned Octave Accidental: When an accidental is assigned to a note in one octave, notes of the same pitch in that bar that appear in different octaves should have an accidental assigned to them as well, in order to avoid confusion. This find category helps to quickly locate notes in different octaves that do not have an accidental assignment, but probably should have one.
Page created in 0.053 seconds with 23 queries.