Skip to main content ↑ ↓

Messages

This section allows you to view all Messages made by this member. Note that you can only see Messages made in areas you currently have access to.

Messages - Mike Shawaluk

901
General Discussion / Re: How do you call this rhythm indication in some music scores?
Quote from: Bart –
I have a music score with a rhythm indication on top which states that 2 eight notes should be sung/played as triplets (see Capture.png in attachement).
What is the correct name for this indicator?
Is there a way to add this indicator in NWC songs with the current 2.51 version?
Could the future user object facility be used to create these kind of objects?
I don't know what that is called, but it's present as a character in one of the custom fonts that can be used with NWC. I'm surprised that Rich or Lawrie hasn't already posted a response on how to install/use it. (I don't have that font installed at the moment so I can't give you any more details.)

It should also be possible to create that type of mark via a user object. There are a number of possible variations, that you'll see once you install the font. Since I've been dabbling with user objects, I should give this a try.

Mike
902
General Discussion / Re: My 3 wishes: 1) small staffs 2) fine-scale note-width 3) copyright on each page
Hello Harald,
Quote from: hmmueller –
... I'm not very concerned about the perfect beauty of the result - for example, I had no great complaints about those slurs which curve "in interesting ways".
If you haven't been part of the beta testing for 2.75, you'll be interested to know that there are several changes to the slurs, including a new "marker" that can be used to change the endpoint positions and shape.

Quote from: hmmueller –
But there are three things I'd dearly need, in descending order of importance:
...
2. Finer-scaled "Extra Note Spacing" that takes tenths instead of only integral values; and negative values up to maybe minus 1. Sometimes, in a little more complex chords assembled on 2 layered staffs, just shifting over a note "a little bit" would make the chord really readable. And, sometimes, I'd like to push notes together a little bit, usually in a scale or a repetitive acc. pattern: This might save that unncessary fourth page where just 2 measures spill over, and still keep the score perfectly readable.
I can't help with your first point (maybe someone else will have a suggestion on that.

But for your second point, one thing that many people (including myself originally) have missed is that the Spacer object can actually be used to reduce the space between notes. But to make this work, you must insert a small-width spacer on each staff where you want the space to be removed. I can post a sample if you want to see this in action.
Quote from: hmmueller –
3. Printing fixed text on each page would also be great - for copyright purposes, but more for title and instrument remarks. I usually prepare all the different printouts (instruments, singers, conductor's score) by creating PDFs on my laptop during my (train) commute. Then I print all of the PDFs together - so inserting different paper is no option. But maybe I have to look into some batch tooling that adds footers into PDFs easily.
One of the new features being introduced in version 2.75 is the idea of "user object" plugins. Without going into too much detail on it here, I have been working on a plugin that will allow repeating headers/footers, as well as more complex composer/lyricist information (e.g. multiple lines of text).

Thanks very much for posting examples of your work.

Mike
904
General Discussion / Re: Lyrics for chorded notes within special endings
After reading Lawrie's reply, I went back and tried using Extra Note Spacing on the first note/chord in the special ending. And lo and behold, it behaves exactly as John described for "Start of note/accidental" lyrics. It hadn't occurred to me that he used extra note spacing to do this.

As you can see, I did use a Spacer element in my example, as Lawrie has suggested, and it doesn't have this problem.
905
General Discussion / Re: Lyrics for chorded notes within special endings
Quote from: John Ford –
I can do so this evening, but I'm not at my music machine right now.  Just wanted to post it while it was on my mind.
I am looking forward to your example. I tried to recreate what you were describing, and I am not seeing the problem you describe. But maybe my example is too simple a case.

Just out of curiosity, what version of NWC are you using? (I tried this in both 2.51a and in the current beta version of 2.75, with identical results.)
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.51)
|Locale|ACP:1252
|Editor|ActiveStaff:2|CaretIndex:9|CaretPos:-2
|SongInfo|Title:""|Author:"<Name>"|Lyricist:""|Copyright1:"Copyright © 2015 <Name>"|Copyright2:"All Rights Reserved"
|PgSetup|StaffSize:16|Zoom:4|TitlePage:Y|JustifyVertically:Y|PrintSystemSepMark:N|ExtendLastSystem:N|DurationPadding:Y|PageNumbers:0|StaffLabels:None|BarNumbers:None|StartingBar:1
|Font|Style:StaffItalic|Typeface:"Times New Roman"|Size:10|Bold:Y|Italic:Y|CharSet:0
|Font|Style:StaffBold|Typeface:"Times New Roman"|Size:8|Bold:Y|Italic:N|CharSet:0
|Font|Style:StaffLyric|Typeface:"Times New Roman"|Size:7|Bold:N|Italic:N|CharSet:0
|Font|Style:PageTitleText|Typeface:"Times New Roman"|Size:24|Bold:Y|Italic:N|CharSet:0
|Font|Style:PageText|Typeface:"Times New Roman"|Size:12|Bold:N|Italic:N|CharSet:0
|Font|Style:PageSmallText|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User1|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User2|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User3|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User4|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User5|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User6|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|PgMargins|Left:1.27|Top:1.27|Right:1.27|Bottom:1.27|Mirror:N
|AddStaff|Name:"Staff"|Group:"Standard"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:12|BoundaryBottom:16|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Lyrics|Placement:Bottom|Align:Standard Rules|Offset:0
|Lyric1|Text:"These are lyr-ics\r\nand so are these.\r\n"
|Clef|Type:Treble
|TimeSig|Signature:4/4
|Note|Dur:4th|Pos:1
|Note|Dur:4th|Pos:0
|Note|Dur:4th|Pos:-1
|Note|Dur:4th|Pos:-2
|Bar
|Ending|Endings:1
|Spacer|Width:600
|Text|Text:"C"|Font:StaffBold|Pos:8|Placement:AtNextNote
|Note|Dur:4th|Pos:-2
|Note|Dur:4th|Pos:-1
|Note|Dur:4th|Pos:0
|Note|Dur:4th|Pos:1
|AddStaff|Name:"Staff-1"|Group:"Standard"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:10|BoundaryBottom:14|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:2
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Lyrics|Placement:Bottom|Align:Start of Accidental/Note|Offset:0
|Lyric1|Text:"These are lyr-ics\r\nand so are these.\r\n"
|Clef|Type:Treble
|TimeSig|Signature:4/4
|Note|Dur:4th|Pos:1
|Note|Dur:4th|Pos:0
|Note|Dur:4th|Pos:-1
|Note|Dur:4th|Pos:-2
|Bar
|Ending|Endings:1|Visibility:Always
|Spacer|Width:600
|Text|Text:"C"|Font:StaffBold|Pos:8|Placement:AtNextNote
|Note|Dur:4th|Pos:-2
|Note|Dur:4th|Pos:-1
|Note|Dur:4th|Pos:0
|Note|Dur:4th|Pos:1
!NoteWorthyComposer-End
Mike
907
General Discussion / Re: Encoding notes of different lengths
Quote from: MusicJohn –
Hi, Rick.

Wrong again?  Not the way I'm looking at it.  I am unable to get two same-value notes one above the other with tails in opposite directions without forcing them.

So ... what aren't I doing right?

MusicJohn, 9/Jun/15
I think I see what you are saying. For example, if you want a split stem chord where both notes are quavers (quarter notes), and the upper note is a C and the lower note is an A (with a treble clef in effect), you will generally have to force the stem directions for each note, otherwise you'll get a normal chord.

(Edit: All this controversy on my signature has convinced me it's time to change it. Let's see who can recognise where this one is from. No fair googling.)
908
General Discussion / Re: Encoding notes of different lengths
Quote from: MusicJohn –
Incidentally, if you want two same-value notes - two crotchets, say - to sit one above the other but with the tails in opposite directions, then you must force each tail.
That has not been my experience. If you haven't explicitly set the stem direction (or, if you press Shift-Up or Shift-Down until neither of the stem direction buttons are lit), you can just press Enter followed by Ctrl-Enter to set the same note with stems in both directions.
910
General Discussion / Re: Encoding notes of different lengths
Quote from: lew.myrick –
Thanks MIke, your example is precisely what I was trying to achieve.  However the clip you attached is complicated to to decipher.  I;m referring to the bit that starts out "Code: (nwc) [Select] and so forth. How do I include this in my NWC file?
The Code section is actually just the NWC clipboard. When you Copy (Ctrl-C) a series of notes or items in NWC, it puts them in the clipboard in a sort of text format, that is called "nwctxt". You can paste this into a text editor, or in the forum, or anywhere that text can be entered. To paste this "code" back into NWC, do this:
  • Click the "Select" link. This will highlight the contents of the Code window.
  • Press Ctrl-C to copy it to your clipboard.
  • With NWC running, either paste it into a score you have open, or alternately do Edit -> Paste as New File. This will create a new score with the copied clip.
Quote from: lew.myrick –
I encode notes and chords by moving the cursor to the keyboard at the bottom of the NWC screen, then depress the mouse key to enter the note, and depress the left mouse and hold it while I move the cursor to the next note and add it to the chord with the right click of the mouse. I can enter the notes and chords quite quickly.  Does NWC store as codes similar to your clip example? 

To do it my way, I have to set the length of the note(s) by first clicking on the duration icon in the tool bar.  I generally enter a string of notes/chords of the shortest or most prevalent duration, then go back and edit the durations that differ from the ones I first entered. There is no easy way I can find to do splitstemchords.  My methods produces the correct notes when played back, but the score looks messy as hell.  Still tying the notes together works for me and it's a fast way to transcribe a piece of music into an NWC file.

Is there a macro language that goes along with NWC?  Is that what you are describing in your example?
As I mentioned above, this isn't really a "macro language"; it's just copy and paste, a way to easily share snippets of a score here in the forum. I notice you are using the piano keyboard to enter your notes. I don't use that for note entry, so I'm not sure if it can be used to create a split stem chord.  Following is how I created the sequence in my previous message:
  • Press 2 (to select half note duration), then use the arrow keys to position the cursor on middle C, and press Enter. This adds the half note.
  • Press 3 (to select quarter note duration), then move the cursor up 2 positions (to E). Then press Ctrl-Enter. This adds the E and makes the split stem chord. Notice that when you do this, the stem on the C will flip downward.
  • Press 4 (to select eighth note duration), and move up one position (to F), press Enter, move up again (to G) and press Enter. Highlight the two eighth notes and beam them so they look pretty :)
One you get used to entering notes via the keyboard, I think it's a lot quicker for score entry than using the mouse and piano keyboard. This is just my opinion.

Mike
911
General Discussion / Re: Encoding notes of different lengths
Quote from: lew.myrick –
I see a lot of NWC files that appear as they do in published form. How does one encode two or more notes together when they are different length?  I can make them all the shortest length and tie them the together to accomplish this, but I would prefer the alternative more traditional notation. 

For example say I have a measure with a half note C and a quarter note E and two eight notes F and G all to be played with two beats (the quarter and eighth notes are on the stop of the half note.  The files I see are not different staves layered together, but encoded that way in a single staff. 

There is a discussion of chords in the user manual, but this are not really chords, but multiple notes of different lengths played together. This method is prevalent, but I don’t how to duplicate it.
Is this what you were describing?
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.51,Single)
|Clef|Type:Treble
|TimeSig|Signature:4/4
|Chord|Dur:4th|Pos:-4|Opts:Stem=Up|Dur2:Half|Pos2:-6
|Note|Dur:8th|Pos:-3|Opts:Stem=Up,Beam=First
|Note|Dur:8th|Pos:-2|Opts:Stem=Up,Beam=End
!NoteWorthyComposerClip-End
(I've also attached a screen shot image.)

NWC calls these "split-stem chords".  They are discussed in the help file under Chord Member Command. However, this might be what you described seeing in the help file. If you are talking about something different that what I created, can you paste an example?

Thanks,
Mike
912
General Discussion / Re: Undo
While we were talking about this, it reminded me of another minor peeve I've had with the lyric editor window. Sometimes I want to "select all" so I can copy lyrics to a different verse or staff. I've noticed that Ctrl-C, Ctrl-X and Ctrl-V all do what one would expect (Copy, Cut, Paste) but Ctrl-A (Select All) doesn't do anything here. However, there is a Select All choice available if I right click in the text box. I wonder whether it would also be possible to have Ctrl-A work here for Select All (another place where this would be nice is the User Object properties window).

Side note: I find myself doing Ctrl-A at times to "select all the notes on the current staff", and I instantly realize I've just added a new staff to my score (which of course Ctrl-Z will undo). So I do know that this isn't something that is going to work anywhere except inside a text dialog.
913
General Discussion / Re: Undo
Quote from: Flurmy –
Hint: why not add the undo function (at least one level) to the edit boxes?
I'm thinking in special mode to the lyrics one, but also the others.
For a blunderer like me...

Does Ctrl-Z not work for you in the lyrics editor? It seems to work for me. (But just a single level, hence it will "toggle" the most recent change.)

Mike
914
General Discussion / Re: Chant clefs?
I would echo @Rick G.'s comment about version 2.75. Specifically, it allow custom "staff signature" items to be created, which can be automatically inserted in a staff for each system.

While I'm not very familiar with chant notation, I did a little searching around, and found a font called Caeciliae which appears to have the necessary characters for the do and fa clefs. Here's a document that describes the font: http://marello.org/files/Caeciliae%20Tutorial.pdf

I am curious what you use for the notes shapes for your Gregorian chant scores. The above font also has the various note shapes, but I'm not sure how easy it would be to make it work with NWC for the actual notation.

Mike
916
General Discussion / Re: Dedication information
I agree that the approach @Rick G. used is quite novel. He has shared a similar sample before, but I don't think I've seen a description of his approach, so I thought I would try to describe how it works:
  • Make sure that the score suppresses the normal title / author / lyricist display.
  • Add an extra staff, layered with the top staff of the system, with the number of staff lines set to 0. We'll call this the "title staff"
  • Insert an extra measure for all staves, and insert boundary change collapse/uncollapse commands before/after this measure for all staves except the title staff.
  • In the first measure of each staff, insert a whole rest and add a system break after that measure. This gives a single measure for the first system.
  • Insert text items in the first measure of the title staff that you want to be displayed at the top of the score, choosing an appropriate font. For items that you want to be on the left, insert them to the left of the rest, and choose Left alignment, Best Fit. For items that you want to be centered, insert them to the left of the rest, and choose Center alignment, At Next Note/Bar. For items that you want to be right aligned, insert them to the right of the rest, and choose Right alignment, Best Fit Forward or At Next Note/Bar.  Adjust each text item's vertical position as needed.
  • Collapse the title staff after the system break, and insert boundary change margin adjustments if needed to preserve the required space.
  • On Page Setup > Options, set the starting measure to 0, to offset for the dummy measure that was inserted. This will maintain the correct measure count in the remainder of the score.

I also notice that Rick has inserted large spacers to the left & right of the whole rest in the first system. This allows the title text to be previewed while in Edit mode, but does not appear to affect the print preview.

All in all, I like this tip/trick. If I have described anything incorrectly or left out an important step, please let me know.

Mike
917
Object Plugins / Slur.ms (2.1)
This object can be used to draw slurs of various types and shapes. Here are its properties:

Note Span: Number of notes to span. Default = 2
Line Type: Type of line (solid, dash, dot). Default = solid
Direction: Direction of slur (Default, Upward, Downward). Default = 'Default', which uses the starting note's Slur Direction property.
Start Offset X:
Start Offset Y: Used to adjust the starting point of the slur. Each coordinate is between -100 and 100. Default = 0, 0
End Offset X:
End Offset Y: Same as above, except for the ending point of the slur.
Strength: Strength of the curve; a positive value between 0 and 100. Default = 1
Balance: Left/right balance of the curve's shape; a value between -0.5 and 0.5. Default = 0 (center)

To add a slur to your score, position the cursor immediately before the note where you want the slur to start, and insert the object.

The following keys can be used to interactively adjust various parameters, while the Slur object marker is selected:
  • + and - increment/decrement the Note Span parameter.
  • The 5 key actives "edit" mode and toggles the current parameter pair between the left, middle and right ends of the slur. Square "edit" boxes will appear on the slur when edit mode is active, and the current parameter pair will be indicated by a filled in box.
  • The 2, 4, 6 and 8 keys will move the selected point in the specified direction. For the slur's left and right end points, the keys increment/decrement the slur's Start Offset X & Y and End Offset X & Y, respectively. For the middle point, the slur's Strength and Balance are adjusted. For keyboards with a numeric pad, these keys are generally labeled with arrow symbols in the specified direction.
  • The 3 and 9 keys (labeled as PgDn and PgUp on the numeric pad) will move the entire slur downward or upward, by simultaneously adjusting both endpoints.
  • The 0 key will reset the selected parameter to its default values (0, 0 for start or end offset, 1, 0 for Strength/Balance)
  • Pressing Shift-Z will reset all of the offset, strength and balance parameters to their default values.

Please note that the slur object is ornamental only, and has no effect on note playback or lyric placement.

Following are a few notes on its usage:
  • The Note Span property indicates the number of notes you want the slur to cover. By default, it will be the first two notes that follow the object.
  • The default end point positions for the slur are calculated based on the starting note's stem direction and Slur Direction property, and the slur object's Direction property. The above start and end offsets adjust these positions relative to their default locations.
  • The Strength property adjusts the amount of curvature of the slur. A value of 0 will result in a straight line.
  • When the Line Type property is set to 'solid', the slur will be drawn as a shaped Bézier curve, similar in appearance to regular NWC slurs. When a value of 'dot' or 'dash' is used, the line will be of uniform thickness.
918
General Discussion / Re: Difficulty trying to tie certain chords.
One other thing to remember is that when you want to tie two chords or notes, you don't want to highlight both of them; just select the leftmost one and press "/". It will create ties to the next matching note or chord that it finds. However, for your example of C-E-G and C-Eb-G chords, it would create a tie from the E, past the Eb to the next E that it finds (or the end of the staff if it can't find one). So you would want to right-click on the E in the first chord (as Rich described above) and uncheck "Tie" to remove that tie, leaving just the ties on the C and G.

Mike
Edit - I should mention that highlighting both notes/chords and pressing "/" will work when the two notes or chords have identical pitches. However, doing a tie by highlighting only the first chord will work for either case, except that it will create "hanging ties" for any unmatched notes, as I described above.
919
General Discussion / Re: determining version
Quote from: guidovanharten –
Accidentally I overwrite my NWC2.51-file with the NWC1.75. There is a .BAK-file, but I do not know if the .BAK is the original 2.51-file.
On which way can I determine if the .BAK-file (in the meantime renamed to another name and extension .NWC) is my original 2.51 file?
You could try running NWC 1.75 and attempt to load the file. If it is a 2.51 format file, it should give you an error.

Mike
921
General Discussion / Re: The awkwardness of polyphony
I've been following this discussion (with a few comments) and have found the examples interesting and useful. I don't notate a lot of piano parts (which seem to have the highest occurrence of cross-staff beams) but I've thought about the issue a bit. As some might know, a number of us have been involved in the creation of user plugins for the upcoming release of NWC 2.75 (currently in beta). Some of these plugins are attempts to make certain types of notation simpler or more flexible. (If you haven't already seen them, you can check them out in the User Plugins forum.) One thing that occurs to me is that it should be possible to create a plugin that could ease the creation of cross-staff beams. It also occurs to me that another plugin creator might already be working on such an object, in which case it would make sense to "reach out" to avoid duplication of effort.

Or, perhaps this type of discussion doesn't belong in the General Discussion forum?

Mike
923
General Discussion / Re: The awkwardness of polyphony
Quote from: Roger Carpenter –
When the layers are collapsed, the redundant rests and superimposed clefs are simply unacceptable.  I will have a go with the specialist tools mentioned ...
One additional item to consider when layering is the Boundary Change command, specifically the "Start a collapsible section" and "Cancel/forbid collapse" options. This can be used as an alternative to marking rests/clefs as hidden, so that they won't show through the layers.

One last comment: if you are changing clefs in layered parts, you pretty much need to do the same clef changes in each staff that is layered, if you want the merged notes to make any sense. Unless I'm not understanding how you are using the layers in your score.

Mike
924
General Discussion / Re: The awkwardness of polyphony
Quote from: William Ashworth –
I don't consider layering clumsy. Giving each voice its own staff gives it maximum freedom to be notated properly. If each voice has its own staff, no voice is subordinate to any other. Layering is actually perfectly suited to polyphonic writing - the advantages far outweigh the disadvantages. Perhaps you simply need to reconsider what you are trying to do with the score.
I am a proponent of layering, and use it for choral scores for our church choir. One advantage of having each voice on its own staff is that it is easy to mute or alter the volume for specific parts for practice purposes. But that said, there are a few things about layered staves that can require additional tweaking during score entry. For example, the logic that automatically offsets vertically adjacent noteheads in a chord doesn't work across layered staves; you need to edit notes/chords manually when this happens (or, run a user tool that automates the process). Also, stem lengths on layered notes in the same chord may require adjustment so they are compatible lengths, when the notes are beamed. I would not quite call this "clumsy", but the process can be tedious, especially if one is trying to create a score that both looks/prints nice and plays back correctly.

Overall, I think that layers are a very powerful feature that take a bit of learning to use effectively. And, of course, with great power comes great responsibility.

Mike
925
General Discussion / Re: The awkwardness of polyphony
Quote from: Roger Carpenter –
There are many aspects of NWC I love, but trying to enter more than one part to a stave is not one of them.  I realize this CAN be done - clumsily - with layering, or even more clumsily by pretending it's a lot of chords.  Is there really a fundamental technical reason why NWC could not cope with entering multiple lines on a single stave?  Could a note not be tagged as belonging to one part rather than another?  E.g. by temporary colour-coding?

There is probably no 'fundamental technical reason' why this might not be accomplished in NWC - if that were the way the author wanted it to do it. He has chosen the approach of layered staves, which might not be the easiest or most convenient to enter/edit, but layers have a number of other uses, such as more complex lyrics and annotations. @Opagust and @Warren Porter have mentioned several tools or techniques that might make the layering process a bit less clumsy.

Mike
926
Object Plugins / Acciaccatura.ms (version 1.4)
This object adds a slash ornament to a grace note (appoggiatura), turning it into an acciaccatura. Playback is optionally available, which will be before the beat.

Paste the following snippet into NWC 2.75, then go to Tools > Manage Objects to install the object.

Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|User|Acciaccatura.ms|Pos:-2
|Note|Dur:8th,Grace|Pos:0
|User|Acciaccatura.ms|Pos:-2|Style:Downward
|Chord|Dur:8th,Grace|Pos:0,1
|User|Acciaccatura.ms|Pos:-2
|Note|Dur:8th,Grace|Pos:0|Opts:Stem=Down
|User|Acciaccatura.ms|Pos:-2|Style:Downward
|Chord|Dur:8th,Grace|Pos:-1,0|Opts:Stem=Down
|Bar
!NoteWorthyComposerClip-End

Once the plugin is installed, insert the object to the left of the eighth grace note or chord you wish to ornament. The slash will be automatically added at the correct location on the note's flag. If Class = Standard, only a single grace note will receive the ornament; if Class = StaffSig, all subsequent eligible grace notes, up to the next Acciaccatura.ms object, will be affected. To discontinue automatic acciaccatura marks, insert another object with Class = Standard, or Visibility set to Never. (The first option will ornament a single following grace note; the second option will end ornamentation.)

Also note that for Class = StaffSig, playback will only occur for grace notes within a SPP offset of 32 quarter notes from the location of the user object. Insert additional StaffSig objects in your score if you have grace notes that are too far from the user object, or for the most accurate playback, use Class = Standard objects at each grace note location.

The object has the following parameters:

Rate: Specifies the playback rate for the acciaccatura, expressed as the number of notes per whole note duration. For example, 64 would correspond to a 1/64 note. A value of 0 disables playback, which is the default. Also note that the grace note must be muted for playback to occur.
Down-stem Style: Determines the style for the slash ornament on down-stem notes. Selecting "Upward" will render the slash from lower left to upper right (the same as for up-stem notes), while selecting "Downward" will render the slash from upper left to lower right.  The default is "Upward".

The current object will only affect an unbeamed eighth (quaver) grace note.

Note that playback will currently work correctly only for a single acciaccatura preceding a note. Multiple note playback, as well as beamed notes, are under future consideration.
927
Object Plugins / Arpeggio.ms (2.3)
This object draws an arpeggio for a chord. It uses no special fonts. It will draw the arpeggio marking and optionally play the chord in arpeggio style.

To add an arpeggio to a chord, insert the object immediately before the chord which you wish to ornament. The arpeggio will automatically cover the range of notes in the chord, and will update automatically if the chord is moved or modified.

The following parameters control the appearance and operation of the arpeggio:

Side of Chord: Side of the chord (left, right) on which the arpeggio marking will be drawn. Default value is left.
Direction: Determines the direction of the arpeggio (up, down). When the direction is down, adds an arrowhead to the bottom of the arpeggio. This option also controls the arpeggio's playback (see below). Default value is 'up'.
Horizontal Offset: Used to increase or decrease the distance between the arpeggio and its chord. Value is between -5 and 5 notehead widths; default value is 0.
Extend Arpeggio with Marker: Controls whether the user object marker vertical position extends the arpeggio above or below the notes of the chord. This can be used to 'stretch' the arpeggio to extend to an adjacent staff. Note that this does not affect the arpeggio's playback. Default value is unchecked.
Force Arrowhead for Up Arpeggio: Used to force the appearance of an arrowhead for up arpeggios. (Down arpeggios always have an arrowhead.) Default value is unchecked.

The following options only pertain to playback:

Play Notes: Determines whether arpeggio playback is enabled. Default value is true. Note that the chord following the arpeggio mark should be muted for proper playback. When this chord is tied to subsequent chords, those chords should not be muted. This will allow the arpeggiated chord to play through the tie.
Arpeggio Rate: Controls the rate at which the arpeggio is played, as a number of notes per whole note duration. Range of values is 1 (very slow) to 128 (very fast), with a default value of 32. The playback speed is also relative to the score's tempo.
Anticipated Playback: When checked, specifies that the arpeggio should anticipate (precede) the chord, so that the final arpeggiated note occurs on the chord's beat position. When unchecked, a 'normal' arpeggio will occur, in which the first note of the arpeggiated chord is on the beat. Default is unchecked.

The following sample clip will get you started, and demonstrates arpeggios of various types. Note that the speed is intentionally slowed so that the up/down and normal/anticipated playback can be discerned.

Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.75)
|AddStaff|Name:"Staff-1"|Group:"Standard"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:10|BoundaryBottom:10|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:2
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Clef|Type:Treble
|TimeSig|Signature:4/4
|User|Arpeggio.ms|Pos:0|Rate:16
|Chord|Dur:Whole|Pos:-9,-7,-4|Opts:Stem=Down,Muted
|Bar
|User|Arpeggio.ms|Pos:0|Dir:down|Rate:16
|Chord|Dur:Whole|Pos:b-8,b-5,-3|Opts:Muted
|Bar
|User|Arpeggio.ms|Pos:0|Dir:up|Anticipated:Y|Rate:16|ForceArrow:Y
|Chord|Dur:Whole|Pos:n-8,-6,-3|Opts:Muted
|Bar
|User|Arpeggio.ms|Pos:0|Side:right|Anticipated:Y|Rate:16
|Chord|Dur:Whole|Pos:b-7,b-4,-2|Opts:Muted
|AddStaff|Name:"Staff-2"|Group:"Standard"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:10|BoundaryBottom:10|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:3
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Clef|Type:Bass
|TimeSig|Signature:4/4
|Note|Dur:Whole|Pos:-8
|Bar
|Note|Dur:4th,Dotted|Pos:b-7
|Note|Dur:8th|Pos:b0^
|Note|Dur:8th|Pos:0|Opts:Stem=Down,Beam=First
|Note|Dur:8th|Pos:0|Opts:Stem=Down,Beam=End
|Note|Dur:4th|Pos:-7
|Bar
|Note|Dur:4th,Dotted|Pos:n-7
|Note|Dur:8th|Pos:n0^
|Note|Dur:8th|Pos:0|Opts:Stem=Up,Beam=First
|Note|Dur:8th|Pos:-7|Opts:Stem=Up,Beam=End
|Note|Dur:4th|Pos:0
|Bar
|Note|Dur:4th,Dotted|Pos:b-6
|Note|Dur:8th|Pos:b1^
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam=First
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam=End
|Note|Dur:4th|Pos:-6
!NoteWorthyComposer-End
928
Object Plugins / TremoloSingle.ms (2.1)
This object implements a single note tremolo, as described in various texts. It draws the tremolo markings, and will optionally play the notes in tremolo style.

To create the tremolo, insert the object immediately before the note to receive the tremolo, and the marking will be drawn on the note's stem, or above/below a whole (semibreve) note. The note can be any chord or RestChord.

The following parameters control the appearance and playback of the tremolo:

Number of Beams: Specifies the number of beams to be drawn, between 1 and 4. The default value is 3. The number of beams for a tremolo can also be modified by highlighting the object and pressing the + or - keys.
Vertical Offset: Specifies an optional offset distance for the location of the beam(s). For stemmed notes, positive values move the beams away from the stem tip and toward the note head. For unstemmed (whole) notes, positive values move the beams away from the note head. The default value is 0.
Play Notes: Enables playback of the tremolo. Default value is checked. Note that the notes/chords should be muted for proper playback.
Triplet Playback: Specifies that the playback notes should be in triplet rhythm. This will generally be used when the tremolo notes are dotted. Default value is unchecked.
Split Chord Member: Specifies which split chord member (top or bottom) should receive the tremolo marking and be played. This parameter is ignored for non-split chords and rest chords. The default value is "top".

For eighth through 64th notes, the tremolo beams will be auto-positioned to avoid collision with the note's beam or flag.  If additional space is needed to accommodate a larger number of beams, increase the note's stem length, and/or specify an Offset value if desired.

The following sample clip will get you started. The screen shot demonstrates various types of tremolos, with the bottom staff indicating the actual notes that are played.

Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.75)
|AddStaff|Name:"Staff"|Group:"Standard"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:12|BoundaryBottom:12|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Clef|Type:Treble
|TimeSig|Signature:4/4
|User|TremoloSingle.ms|Pos:0|Beams:3|Offset:0|Play:Y
|Note|Dur:4th|Pos:0|Opts:Stem=Down,Muted
|User|TremoloSingle.ms|Pos:0|Beams:2|Offset:0|Play:Y
|Note|Dur:8th|Pos:1|Opts:Stem=Down,StemLength=8,Beam=First,Muted
|User|TremoloSingle.ms|Pos:0|Beams:2|Offset:0|Play:Y
|Note|Dur:8th|Pos:3|Opts:Stem=Down,StemLength=8,Beam=End,Muted
|User|TremoloSingle.ms|Pos:0|Beams:2|Offset:0|Play:Y
|Note|Dur:Half|Pos:-2|Opts:Stem=Up,Muted
|Bar
|User|TremoloSingle.ms|Pos:0|Offset:0|Beams:2|Play:Y
|Chord|Dur:Whole|Pos:1,2|Opts:Stem=Down,StemLength=6,Muted
|AddStaff|Name:"Staff-1"|Group:"Standard"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:10|BoundaryBottom:10|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:2
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Clef|Type:Treble
|TimeSig|Signature:4/4
|Note|Dur:32nd|Pos:2|Opts:Stem=Down,Beam=First
|Note|Dur:32nd|Pos:2|Opts:Stem=Down,Beam
|Note|Dur:32nd|Pos:2|Opts:Stem=Down,Beam
|Note|Dur:32nd|Pos:2|Opts:Stem=Down,Beam
|Note|Dur:32nd|Pos:2|Opts:Stem=Down,Beam
|Note|Dur:32nd|Pos:2|Opts:Stem=Down,Beam
|Note|Dur:32nd|Pos:2|Opts:Stem=Down,Beam
|Note|Dur:32nd|Pos:2|Opts:Stem=Down,Beam=End
|Note|Dur:16th|Pos:1|Opts:Stem=Down,Beam=First
|Note|Dur:16th|Pos:1|Opts:Stem=Down,Beam
|Note|Dur:16th|Pos:3|Opts:Stem=Down,Beam
|Note|Dur:16th|Pos:3|Opts:Stem=Down,Beam=End
|Note|Dur:16th|Pos:-2|Opts:Stem=Up,Beam=First
|Note|Dur:16th|Pos:-2|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-2|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-2|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-2|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-2|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-2|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-2|Opts:Stem=Up,Beam=End
|Bar
|Chord|Dur:16th|Pos:1,2|Opts:Stem=Down,Beam=First
|Chord|Dur:16th|Pos:1,2|Opts:Stem=Down,Beam
|Chord|Dur:16th|Pos:1,2|Opts:Stem=Down,Beam
|Chord|Dur:16th|Pos:1,2|Opts:Stem=Down,Beam
|Chord|Dur:16th|Pos:1,2|Opts:Stem=Down,Beam
|Chord|Dur:16th|Pos:1,2|Opts:Stem=Down,Beam
|Chord|Dur:16th|Pos:1,2|Opts:Stem=Down,Beam
|Chord|Dur:16th|Pos:1,2|Opts:Stem=Down,Beam
|Chord|Dur:16th|Pos:1,2|Opts:Stem=Down,Beam
|Chord|Dur:16th|Pos:1,2|Opts:Stem=Down,Beam
|Chord|Dur:16th|Pos:1,2|Opts:Stem=Down,Beam
|Chord|Dur:16th|Pos:1,2|Opts:Stem=Down,Beam
|Chord|Dur:16th|Pos:1,2|Opts:Stem=Down,Beam
|Chord|Dur:16th|Pos:1,2|Opts:Stem=Down,Beam
|Chord|Dur:16th|Pos:1,2|Opts:Stem=Down,Beam
|Chord|Dur:16th|Pos:1,2|Opts:Stem=Down,Beam=End
!NoteWorthyComposer-End
929
Object Plugins / Tremolo.ms (2.1)
This object implements a two-note tremolo, as described in various texts. It draws the tremolo markings, and will optionally play the notes in tremolo style.

To create a tremolo, you must first create two RestChords of the desired duration. For whole, half and quarter note tremolos, the rest duration should be half of the note's duration. For eighth tremolos, the note duration should be quarter and the rest duration sixteenth. Also, the rest portion of each RestChord should be marked as hidden. Once the notes are present, insert the object between the notes, and the marking will be drawn between the stems. If additional space is needed to accommodate a larger number of beams, increase the stem length of the notes.

The following parameters control the appearance and type of tremolo:

Number of Beams: Specifies the number of beams to be drawn between the notes, between 1 and 4. Default value is 3. The number of beams for a tremolo can also be modified by highlighting the object and pressing the + or - keys.
Half Note Beam Style: Specifies one of three styles for half-note tremolos, and is an integer with values of 1 to 3. It is ignored for other tremolo durations. Default value is 1.
Play Notes: Enables playback of the tremolo. Default value is checked. Note that the RestChords should be muted for proper playback.
Triplet Playback: Specifies that the playback notes should be in triplet rhythm. This will generally be used when the tremolo notes are dotted. Default value is unchecked.
Variance (%): Specifies a dynamic variance between the first and second chord. The specified value is a multiplier for the volume of the second note. This allows more realistic playback. The range of values is 50% to 200%, and the default setting is 100% (no variance).
Beam Angle Offset: Specifies a vertical (staff position) offset to the right side of the beams, for whole note tremolos only. The range of values is -10 to 10, and the default setting is 0. This allows the beam angle to be adjusted; by default, the angle will be that of the lowest noteheads.

For whole note tremolos, the vertical position of the beams may be altered by moving the object marker up and down on the staff. The beam angle can also be adjusted using the Beam Angle Offset parameter.

If the notes on either side of the object are not both RestChords, or if their stem directions are not the same, then the tremolo will not be drawn. If the two notes are of differing durations, the tremolo will be drawn in the style of the right-hand note.

The following sample clip will get you started. The screen shot demonstrates various types of tremolos, with the bottom staff indicating the actual notes that are played.

Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.749741)
|AddStaff|Name:"Staff"|Group:"Standard"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:12|BoundaryBottom:12|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Clef|Type:Treble
|TimeSig|Signature:4/4
|RestChord|Dur:8th|Opts:Stem=Down,ArticulationsOnStem,Muted,HideRest|Dur2:4th|Pos2:-2
|User|Tremolo.ms|Pos:-1|Beams:3|Style:1|Play:Y
|RestChord|Dur:8th|Opts:Stem=Down,ArticulationsOnStem,Muted,HideRest|Dur2:4th|Pos2:1
|RestChord|Dur:16th|Opts:Stem=Down,ArticulationsOnStem,Muted,HideRest|Dur2:4th|Pos2:1
|User|Tremolo.ms|Pos:-1|Beams:3|Style:1|Play:Y
|RestChord|Dur:16th|Opts:Stem=Down,ArticulationsOnStem,Muted,HideRest|Dur2:4th|Pos2:0
|RestChord|Dur:16th|Opts:Stem=Down,ArticulationsOnStem,Muted,HideRest|Dur2:4th|Pos2:-1
|User|Tremolo.ms|Pos:-1|Beams:3|Style:1|Play:Y
|RestChord|Dur:16th|Opts:Stem=Down,ArticulationsOnStem,Muted,HideRest|Dur2:4th|Pos2:-2
|Bar
|RestChord|Dur:4th|Opts:Stem=Up,Muted,HideRest|Dur2:Half|Pos2:5
|User|Tremolo.ms|Pos:-1|Beams:2|Style:2|Play:Y
|RestChord|Dur:4th|Opts:Stem=Up,Muted,HideRest|Dur2:Half|Pos2:3
|Bar
|RestChord|Dur:Half|Opts:Stem=Down,Muted,HideRest|Dur2:Whole|Pos2:-5
|User|Tremolo.ms|Pos:4.5|Beams:2|Style:1|Play:Y
|RestChord|Dur:Half|Opts:Stem=Down,Muted,HideRest|Dur2:Whole|Pos2:-3
|AddStaff|Name:"Staff-1"|Group:"Standard"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:12|BoundaryBottom:12|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Clef|Type:Treble
|TimeSig|Signature:4/4
|Note|Dur:32nd|Pos:-2|Opts:Stem=Up,Beam=First
|Note|Dur:32nd|Pos:1|Opts:Stem=Up,Beam
|Note|Dur:32nd|Pos:-2|Opts:Stem=Up,Beam
|Note|Dur:32nd|Pos:1|Opts:Stem=Up,Beam
|Note|Dur:32nd|Pos:-2|Opts:Stem=Up,Beam
|Note|Dur:32nd|Pos:1|Opts:Stem=Up,Beam
|Note|Dur:32nd|Pos:-2|Opts:Stem=Up,Beam
|Note|Dur:32nd|Pos:1|Opts:Stem=Up,Beam=End
|Note|Dur:32nd|Pos:1|Opts:Stem=Up,Beam=First
|Note|Dur:32nd|Pos:0|Opts:Stem=Up,Beam
|Note|Dur:32nd|Pos:1|Opts:Stem=Up,Beam
|Note|Dur:32nd|Pos:0|Opts:Stem=Up,Beam=End
|Note|Dur:32nd|Pos:-1|Opts:Stem=Up,Beam=First
|Note|Dur:32nd|Pos:-2|Opts:Stem=Up,Beam
|Note|Dur:32nd|Pos:-1|Opts:Stem=Up,Beam
|Note|Dur:32nd|Pos:-2|Opts:Stem=Up,Beam=End
|Bar
|Note|Dur:16th|Pos:5|Opts:Stem=Down,Beam=First
|Note|Dur:16th|Pos:3|Opts:Stem=Down,Beam
|Note|Dur:16th|Pos:5|Opts:Stem=Down,Beam
|Note|Dur:16th|Pos:3|Opts:Stem=Down,Beam
|Note|Dur:16th|Pos:5|Opts:Stem=Down,Beam
|Note|Dur:16th|Pos:3|Opts:Stem=Down,Beam
|Note|Dur:16th|Pos:5|Opts:Stem=Down,Beam
|Note|Dur:16th|Pos:3|Opts:Stem=Down,Beam=End
|Bar
|Note|Dur:16th|Pos:-5|Opts:Stem=Up,Beam=First
|Note|Dur:16th|Pos:-3|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-5|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-3|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-5|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-3|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-5|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-3|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-5|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-3|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-5|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-3|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-5|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-3|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-5|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:-3|Opts:Stem=Up,Beam=End
!NoteWorthyComposer-End
930
Object Plugins / GuitarChord.ms (2.2)
This object can be used to draw guitar chord charts above a note or chord, and optionally "strum" the notes.

When adding a new chord, the user can choose one of 132 predefined chords, or can choose "(Custom)" to create a chord chart from scratch. When a chord is added to a staff, if there is another GuitarChord object earlier in the staff, it will inherit the style and properties of that object.

Following are the parameters used to configure the chart:

Chord Name: Name of the chord, drawn above the chart. Default value is blank.
Font Style: The font style to be used for the chord name and label text. The possible values are Serif (MusikChordSerif, Times New Roman), Sans (MusikChordSans, Arial) and Swing (SwingChord, SwingText). The default setting is Serif.
Fingerings: Contains the fret position (and optional finger number, separated by ':') for each string. o = open, x = don't play. Default value is blank.
Barres: Contains start:end string numbers for a set of strings to be held down by a particular finger. An arc is drawn over the string pair. Note that the strings are numbered from low pitch to high pitch. Default value is blank.
Chart Size: Size of the chord chart. This value can be thought of as a scale factor. Default value is 1
Frets to Show: Number of frets to show in the chart. Default value is 4.
Top Fret: Top fret displayed in the chart. When the value is 2 or more, "# fr." is displayed to the right of the chart. Default value is 1.
Fret Text Location: Determines whether the fret text (for Top Fret > 1) is displayed next to the top or bottom row of finger dots. Default value is 'top'.
Top Barre Offset: - this allows a barre at the top of the chord chart to be moved upward a specified distance, to avoid collision with "x" or "o" string labels. Default value is 0, which specifies no movement.

The Fingerings parameter above determines the notes which will be played back by the object, based on standard guitar tuning (E A D G B E). The following additional parameters are for playback only:

Capo Position: Indicates whether the chord should be transposed upward the specified number of steps. Default value is 0.
Note Span: Determines how many notes/rests the chord playback should span. A value of 0 will disable playback. Pressing the + or - keys while the object is selected will increase/decrease the span value. Default value is 0.
Strum Direction: Determines the direction in which the chord is strummed. This direction is the physical direction that the strings would be strummed on a guitar, so 'down' is from low- to high-pitched strings, and 'up' is the opposite. Default value is 'down'.
Anticipated Playback: Specifies that the strum should anticipate (precede) the chord, so that the final played note occurs on the chord's beat position. When unchecked, the first played note of the strummed chord is at the chord's beat position. Default value is on (checked).

The code for the object is attached to the post. A sample clip follows, which will sound best with the staff instrument set to one of the acoustic guitars.

Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.75,Single)
|Clef|Type:Treble
|TimeSig|Signature:4/4
|User|GuitarChord.ms|Pos:6|Name:A/E|Frets:5|Size:1.5|Finger:"o o 2:1 2:1 2:1 o"|Barre:3:5|Span:2
|Rest|Dur:Half
|Note|Dur:Half|Pos:-8
|Bar
|User|GuitarChord.ms|Pos:6|Name:Ebsus/Bb|Frets:5|Size:1.5|Finger:"2:1 2:1 4:2 4:2 5:3 x"|Barre:"1:2 3:4"|Span:2|Style:Sans
|Rest|Dur:Half
|Note|Dur:Half|Pos:b-4
|Bar
|User|GuitarChord.ms|Pos:6|Name:Db|Frets:5|Size:1.5|Finger:"x 4 6 6 6 x"|TopFret:3|Barre:3:5|Span:2|Style:Swing
|Rest|Dur:Half
|Note|Dur:Half|Pos:b-5
|Bar
|User|GuitarChord.ms|Pos:6|Size:1.5|Frets:5|Name:Gb|Finger:"2:T 4:2 4:3 3:4 2:1 2:1"|Barre:5:6|Span:2
|Rest|Dur:Half
|Note|Dur:Half|Pos:b-9
|Bar
|User|GuitarChord.ms|Pos:6|Size:1.5|Frets:5|Name:Ab/Gb|Finger:"2 x 1 1 1 x"|Barre:3:5|Span:2
|Rest|Dur:Half
|Note|Dur:Half|Pos:b-8
|Bar
|User|GuitarChord.ms|Pos:6|Size:1.5|Frets:5|Name:(open)|Finger:"o o o o o o"|Span:3
|Rest|Dur:Half
|Note|Dur:Half|Pos:-4^
|Bar
|Note|Dur:Whole|Pos:-4
!NoteWorthyComposerClip-End

As always, feedback and suggestions are welcome.

Mike
931
Object Plugins / VerseNumbers.ms (version 1.0)
This object will add verse numbers to lyrics on a staff. The numbers will be drawn using the current "StaffLyric" font, to match the size and style of the lyrics.

The following parameters control the sequence and placement of the numbers:

Start Verse Number: The starting point for numbering the verses. Default is 1.
Starting Verse: The number of the first lyric line to receive a number. Default is 1.
Maximum Verses: The number of the last lyric line to receive a number. Default is 'All'.
Separator Position: Inserts a short horizontal separator line between the verse numbers every 'n' lyric lines. Default is 'Off', which disables this function.
Special Text: Allows a user specified series of verse labels to be used instead of ascending numbers. It is either a series of values separated by spaces, or an empty string to disable this feature. Default is an empty string.
Punctuation: Text to append to each verse number. Default is ". " (a period followed by a single space)

Each verse number will be positioned right-justified before the first lyric-bearing note or rest that follows the object. The verse numbers are vertically aligned based on the widest syllable.

Known issue: When a syllable is hyphenated at the end of a line, NWC normally draws a "courtesy" hyphen at the beginning of the next system, and this may be obscured by the verse numbers. This courtesy hyphen can be suppressed by inserting a line break in the lyric editor for that syllable, after the hyphen.

Attached is a copy of the NWC sample song "God Save the Queen" with verse numbers added via this object.
932
Object Plugins / Ottavamatic.ms (2.0)
This object is used to create 8va (ottava) marks in your score. A single copy of the object can be added to the beginning of each staff which will contain 8va/15ma/22ma sections, and it will create the marks automatically where they are needed.

The object takes the following parameters:

+1 Octave Text:Label text to use for transposing up one octave. Default is 8va.
-1 Octave Text:Label text to use for transposing down one octave. Default is 8va bassa.
+2 Octave Text:Label text to use for transposing up two octaves. Default is 15ma.
-2 Octave Text:Label text to use for transposing down two octaves. Default is 15ma bassa.
+3 Octave Text:Label text to use for transposing up three octaves. Default is 22ma.
-3 Octave Text:Label text to use for transposing down three octaves. Default is 22ma bassa.
Add Courtesy Marks:Determines whether "( )" should be added around the label when a section extends from the previous system. Default is checked.
Include Rests:Determines whether beginning and ending rests should be included within a section. Default is unchecked.
Suppress Line for Short Sections:Determines whether the dashed line should be suppressed for sections which are shorter than the label text (e.g. single notes). Default is unchecked.
Staff Transpose:Staff transposition value, to allow for non-C instrument parts. Default value is 0.
Start Offset:Horizontal offset for the position of the label text, relative to the first note or rest of the 8va section. Default value is 0.
End Offset:Horizontal offset for the position of the ending tail, relative to the last note or rest of the 8va section. Default value is 0.
To use the object, insert Instrument Change commands at the start and end of each section that you wish to mark, with the starting instrument change having an effective transpose[1] of 12, -12, 24, -24, 36 or -36, and the ending instrument change having an effective transpose of 0.  If you want to discontinue 8va marks in your score, insert another Ottavamatic object and set its visibility to Never. To re-enable the marks, add another visible one later in the score.

Each 8va mark can be positioned vertically by moving the starting instrument change up and down in the staff. The vertical position of the Ottavamatic object has no effect on the positions of any marks.

Setting Include Rests to true will allow an 8va region to include beginning or trailing rests. Normally, the marks will only bracket the first and last notes between the instrument changes (which is standard engraving practice).

Performing a staff transpose (Tools > Staff transpose...) will automatically update the object's Staff Transpose parameter, so that it will remain in the correct relationship with existing instrument changes in the staff.

Following is a sample clip that demonstrates the object, along with a screen shot.

Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.75,Single)
|User|Ottavamatic.ms|Pos:0|Class:StaffSig
|Clef|Type:Treble
|TimeSig|Signature:4/4
|Note|Dur:4th|Pos:-4
|Note|Dur:4th|Pos:-5
|Note|Dur:4th|Pos:-6
|Note|Dur:4th|Pos:-5
|Bar
|Note|Dur:4th|Pos:-4
|Note|Dur:4th|Pos:-4
|Note|Dur:Half|Pos:-4
|Bar
|Instrument|Trans:12|DynVel:10,30,45,60,75,92,108,127|Pos:7.5|Wide:Y
|Note|Dur:4th|Pos:-5
|Note|Dur:4th|Pos:-5
|Note|Dur:Half|Pos:-5
|Bar
|Note|Dur:4th|Pos:-4
|Note|Dur:4th|Pos:-2
|Note|Dur:Half|Pos:-2
|Instrument|Trans:0|DynVel:10,30,45,60,75,92,108,127|Pos:-4|Wide:Y
!NoteWorthyComposerClip-End
1 'Effective transpose' is the difference in transposition from the staff's default instrument transpose value. For example, a Bb clarinet staff would have a staff instrument transpose of -2. Therefore, an 8va section for this instrument would have starting and ending transpose values of 10 and -2.↵
933
General Discussion / Re: song title of 2 lines
Quote from: guidovanharten –
I want to set a song title (head and sub head).
How do I do that?
NWC will only allow a single line of text for the song title. If you want a sub-title, you can add a text item to the top staff of the first system and position it below the title. You will need to do a Print Preview and adjust the horizontal and vertical position of the text to get it to align with your title.
Hope this helps,
Mike
935
General Discussion / Re: Read-only Tracks and Step-Play
Quote from: Bruce Miles –
Can I set individual tracks in NWC to read-only ? This is so that I can download a simple say 3 track file as a pattern and build a more complex say 10 track file from it by extracting and editing bits and pieces of the pattern. It is much easier to do if all the tracks are together and aligned bar-by-bar but it is all too easy to start editing a pattern track by mistake when chaos soon ensues.

This might not be exactly what you're looking for, but you can mark a staff as hidden, and it will still play. (Go to Page Setup to do this.) That would prevent accidental edits.

Mike
936
General Discussion / Re: MPC help needed
Quote from: Rick G. –
Are you sure about that? I would generally expect no difference for a pipe organ. Bruce says that he is trying to emulate a theatre organ. Theatre organs are beasts. For many stops, you don't know what you get until you try them.

I was thinking of the case of someone trying to "emulate" a pipe organ on a velocity sensitive keyboard. I'd imagine if one plays an actual pipe organ (which I have never done) and presses a key slowly, there might be a softer beginning to the note because the air pressure changing as the key valve opens, versus pressing the key down quickly. But this was more of a musing on my part.

I don't know much about theater organs either, but Wikipedia says that they tend to be pipe organs.

Mike
937
General Discussion / Re: MPC help needed
Quote from: Bruce Miles –
I am staying clear of the midi velocity minefield - it is just not relevant to organ music. It only concerns instruments whose tonality can change as they are played. (There - I've really stuck my neck out on that one)
This disagrees with most of what Flurmy has said - sorry about that but it's how things seem to me.
Bruce Miles

I don't think you're disagreeing with Flurmy - he was just commenting in general, for instruments which have a "velocity", such as a piano. Pressing a piano key quickly vs. slowly gives a different tone, but you're correct about organ music. Other than a little extra "air" noise as you are pressing the key (on a pipe organ) there won't be any difference in a fast vs. slow key press.
Edit: I re-read Flurmy's message, and now I think I see what you are disagreeing with. In NWC properties, dynamics (p, pp, mf, etc.) have a velocity associated with them, but they can also have an optional volume change expression. However, inserting a dynamic will also change the volume for instruments that don't have velocity, such as an organ, so they must be specifying both the velocity and volume during playback.

Mike
938
General Discussion / Re: Why no keyboard shortcut for Print Preview?
This won't solve the issue of their not being a shortcut, but there are a few things that might save you time:

If your cursor is inserted at the point of your most recent edit, when you Print Preview, it will show you that page initially (so you shouldn't need to navigate to it)

Also, you can press Esc to close the Print Preview window.

Finally, if you have a keyboard that lets you remap its special keys, you could program one of them to send Alt-F, V (which will open the Print Preview).

Mike
939
General Discussion / Re: Data Security
Quote from: NoteWorthy Online –
Our metrics, and general industry trends, indicate that many people have moved to cloud based e-mail. Although this sacrifices privacy, it does tend to protect against catastrophic hacks. In this scenario, your provider wants to be the sole source of data tracking, so they tend to protect you from external attacks. Good news, bad news...

I currently do both - a Gmail account that screens most of the spam, and where I initially read and screen the ones that made it through. Then I pull down the surviving messages to my PC via Outlook, so I have an offline copy.
940
User Tools / Re: Lua as user tool script
Quote from: Opagust –
I realise now I didn't show the output of my coding. Here are both the code and the output
Code: [Select · Download]
local function ShowVar(name, var)
	if Testing then
		nwcut.warn(name.." ==> ", var, "\n")
	end -- if
end -- ShowVar
 
local line = item:__tostring()
ShowVar("line", line)
local durs = item.Opts.Dur
ShowVar("#durs",#durs)
for i = 1 , #durs do
	ShowVar("dur"..i , durs[i])
end -- for
Output:
I had setlevel(2). That's why I included to _tostring line, to show the contents of item.
The result shows that the item.Opts.Dur is nil. Why isn't it = "Half"?

Now that I've thought about it a bit more, I think the problem is #durs. I think you would be better off iterating through the table using pairs(..) rather than a counting loop.

This article describes the issue a bit better:

http://stackoverflow.com/questions/2705793/how-to-get-number-of-entries-in-a-lua-table

Mike
941
User Tools / Re: Lua as user tool script
Quote from: Opagust –
Two other problems:
1)
Code: (lua) [Select · Download]
local NoteLengths = { "16th" = 48, "32th" = 24, "4th" = 192, "64th" = 12, "8th" = 96, "Half" = 384, "Whole" = 768 }
gives this error:
Code: [Select · Download]
 '}' expected near '='

That code looks correct to me too, but you might want to look at the preceding or following statement. Sometimes Lua will "complain" about the wrong line.

I think you need to put [ ] around the keys in your assignment (i.e. around the "16th", etc.). Also, you probably want to change 32th to 32nd :)

Quote from: Opagust –
2)
Code: (lua) [Select · Download]
local function ShowVar(name, var)
	if Testing then
		nwcut.warn(name.." ==> ", var, "\n")
	end -- if
end -- ShowVar

local line = item:__tostring()
ShowVar("line", line)
local durs = item.Opts.Dur
ShowVar("#durs",#durs)
for i = 1 , #durs do
	ShowVar("dur"..i , durs[i])
end -- for

I expected 'durs' to be a string = "Half", but when I treated it as a string I got an error stating that it was a table. So I included the ShowVar() calls, with following result:
What did I do wrong?

Mind you, I have not done much with nwcut, but I think your problem is that Dur is not part of the Opts segment of the nwctext. (Opts only contains the Stem=Down part.) Try changing "item.Opts.Dur" to "item.Dur".

Mike
942
General Discussion / Re: How do I print out tremolos?
Quote from: John H White –
Many thanks Warren, Richard and William. I'll do what you say and try my luck. I had been experimenting with multiple dashes and equals signs from my keyboard but I could not find away of moving them laterally so that they all stacked up one above the other.
 On advice from this forum, I downloaded version 2.51a a few days ago and now I can't find the usual notes in the notes tool bar. All there seems to be is a red note symbol which gives alternative fancy note heads that I don't need and a black note symbol which produces a sub menu of different sized notes. I like to be able to click on a particular sized note before inserting it at the appropriate place on the stave, as I have been doing for the last 18 or so years.

Hi John,

As part of the newer version, there are new "selector" buttons which allow for more compact toolbars, and the default toolbars are now using these in place of the previous individual duration buttons. However, the previous note buttons (one per duration) are still available, and can be added back to the toolbar. You only need to do this once, and they will be present when you rerun the program. Here is how to add them:

1. Go to View > Toolbars..., and on the window that opens, click the Customize... button. This will open the Customize Toolbars window.
2. We'll assume you want to add the buttons to the bottom of the Notes toolbar. So, first choose the "Notes" toolbar at the top, and scroll the "Active tools" slider to the bottom and click on the "Insert Chord Member" row.
3. Scroll the "Available tools" slider down until you see "Note1: Whole", "Note2: Half" and so forth up to "Note7: 64th". Highlight each of the Note* rows and click the "-->" button, which will move each to the "Active tools" section.
4. When you are finished, click the "Close" button. You should now have the old note duration buttons back.

There are more details on the Customize Toolbars function in the program's help file, but hopefully this will get things back on track for you.

Cheers,
Mike
943
General Discussion / Re: Why does my Noteworthy keep crashing?
Quote from: John H White –
Once again, many thanks everyone for all your helpful suggestions. I've now deleted Malware Bytes and enjoyed two one a half hour  crash free sessions on Noteworthy.
   I'm still puzzled  about the version number. Every time I go to "Help, About" it still comes up with version 2.5.5, copyright 2012.
     Cheers,
          John.

John,

Eric is saying that you're running an old version of NWC, and should update to the latest version, which is 2.51a. If you go to "Help > Access Noteworthy Software.com" it will tell you if you are running the latest version, and give you the opportunity to upgrade.

Mike
944
General Discussion / Re: Why does my Noteworthy keep crashing?
I think that part of the problem might be that 2.5.5 is being seen by some users as being newer than 2.51a (which would be expected if the second '.' is omitted). Some of that confusion might have been eliminated with a different version number.

I guess it is easy to see these things in hindsight. I once worked for a company whose most popular software version was 2.04g
945
General Discussion / Re: Why does my Noteworthy keep crashing?
Quote from: Lawrie Pardy –
Ahh, I stand corrected, thanks Francis.

Nevertheless, multiple anti-malware is usually a speed problem, not often a crash creator (well, not THAT often :)  )

I'd still look at CPU temps...  Or just possibly video card temps.

If you are looking for "hardware" reasons for apps to lock up or crash, another item to consider is the "bad capacitor" issue that has plagued various motherboards. See http://en.wikipedia.org/wiki/Capacitor_plague for background information. I've had one system that I decided to replace because of this (repairing motherboards is something I don't have the tools to do).  You may be able to inspect the capacitors for bulging or ruptures to see if this is happening on your system.

Mike
946
General Discussion / Re: from 6/8 to C (C in brackets)
It is possible to put in two text objects: the "C" symbol, and a pair of brackets with the appropriate number of spaces between them. Each text object should have its alignment set to Center, and would be positioned vertically so that they align as desired.

Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.51,Single)
|Note|Dur:4th|Pos:-3
|Text|Text:"D"|Font:StaffSymbols|Pos:-2|Justify:Center
|Text|Text:"(  )"|Font:StaffSymbols|Pos:0|Justify:Center
|Spacer|Width:175
!NoteWorthyComposerClip-End
947
General Discussion / Re: Making Ritarando Work
Quote from: MotS –
Me again. In bar 2, I set the Tempo base to half note and the tempo to 96; in bar 8, I insert a Tempo Variance of Ritarando; in bar 9, I insert a Fermata (6) on the 3rd beat (4/4 time); in bar 10, I insert Tempo with base half note and tempo of 96. When I play this back, there is no gradual slowing at the Ritarando - there is a pauses on the Fermata but otherwise playback proceeds with the original Tempo. What am I missing?

In order to see the effect of the Ritardando, you need to insert a Tempo, sometime after the Ritarando, at a slower tempo. (This is separate from a Fermata, which only affects the note it is placed over). The tempo will change gradually from the point of the Ritardando until it reaches the slower Tempo mark.

If you want the tempo to speed back up again, you can insert an Accelerando, and another Tempo at a faster beat. The tempo will likewise increase gradually until the song reaches that next Tempo marker.

Does this make sense? Perhaps if you were able to share your score, or a segment of it, one of us could more easily show you what commands are needed.

Thanks,
Mike
948
General Discussion / Re: Renaissance proportional tempo marking
Quote from: LPeterP –
I'm looking for advice on choosing a font file. I need to add a tempo change indication to a renaissance viol fantasia. The time signature changes from 4/2 to 3/2. At the point where the time signature changes, above the staff I want to add text consisting of a whole note, an equal sign, and a dotted whole note. Can you recommend a suitable font file for this?

The built-in StaffSymbols font (and StaffCueSymbols, which is basically StaffSymbols scaled down in size) has characters for a whole note and an augmentation dot. However, I don't think it has the "=" character. So you would need to concatenate or overlay multiple Staff Text objects to get these together.

There may be other notation fonts that have all of these characters available; I'll let someone else comment on that.

Mike
949
General Discussion / Re: Fetching preview...
Quote from: Flurmy –
Brand new computer and brand new Firefox.
Again: Fetching preview...

I've been reading these posts and scratching my head a bit... all I can think of are the obvious that have already been stated: are you blocking some "important" Javascript? There's a ton of JS going on, a lot of it relevant to Preview. Are you comfortable/familiar with the F12 key? It might show you what's going awry when you click Preview.

AND.... I just followed my own advice. I fired up Firefox (which I normally do not use), and lo and behold, IT DOESN'T PREVIEW FOR ME EITHER!!!!!

When I hit F12 and try to preview, I get this error:

TypeError: XMLDoc.getElementsByTagName(...)[0] is undefined

This is the exact statement that is throwing the error:

var i, preview = XMLDoc.getElementsByTagName("smf")[0].getElementsByTagName("preview")[0];

Now, I don't consider myself a skilled Javascript debugger, but perhaps there is someone else here who can take this and run with it. Note that when I do a Preview in Chrome or IE11 with the F12 window open, they both work fine.

Mike
950
General Discussion / Re: Did Firefox cause this?
Susanna,

To avoid confusion, can you confirm a couple things?

1. When you say "Viewer Mode", do you mean running NWC with the "glasses" clicked, or do you mean the separate Noteworthy Viewer program? I suspect you mean the former, since the icon tooltip says "Viewer Mode".
2. Which version of NWC (or the Viewer) are you running? The release version, or one of the beta previews?

Thanks,
Mike