NoteWorthy Composer Forum

I found it too. I'm using it right now with NWC and it works fine, but I don't know if it will solve the problems between Windows 10 and SoundFonts... In the site it says that the software is only for WinXP (SP3), Vista (SP1), 7 (SP1) and 8.x

This could be a good time for someone to test it in W10 

lloyd.

... it could be better if the MIDI command can send values between -8192 and 8191, like in MPC

nwcplay.midi(#offsetSPP,'Command',#midiData1,[#midiData2])

I think the end result of the clip should be as below.
Two points:
Notes on a single stem should only have one slur, but in this instance the slur ending needs to be extended by one unit – in other words: where you would expect it to be with or without the extra notes. (But this is not the case for an upward stem )
In the second pair, obviously the slur shouldn't cross the stem.

FWIW I'd make the changes 

Since most musicians are by far more familiar with the score note duration than with the MIDI details, I'll suggest the very complicated formula: 4*PPQ/Speed. 
In this case 4 means 1/4, 8 means 1/8 and so on. What's clearer for a musician? 
Furthermore, as you said, no restriction to use only integer values.
Default value? 32 (i.e. 1/32) like NWC grace notes.

Another question: since the arpeggio rate is proportional to the score's tempo, I expected "playback speed" related to the usual note duration, so e.g., 32 meaning 1/32.
The value seems instead completely arbitrary and 32 as a default is by far too fast.
As Rich suggested, a value of 10..16 seems far better.

There's a problem if you stop the play and then restart it.
Try to start playing from bar 3 in the following snippet.

Code: (nwc) [Select · Download]

!NoteWorthyComposerClip(2.75,Single)
|Clef|Type:Treble
|TimeSig|Signature:4/4
|User|Arpeggio.ms|Pos:0|Speed:4
|Chord|Dur:Whole|Pos:-9^,-7^,-4^|Opts:Stem=Down,Muted
|Bar
|Chord|Dur:Whole|Pos:-9,-7,-4|Opts:Stem=Down,Muted
|Bar
|Rest|Dur:Whole
|Bar
!NoteWorthyComposerClip-End

Note that the chord which follows the arpeggio marking 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.

Check the attached: two staves, one with one note having one sharp accidental; the other with two notes, one having one sharp accidental.  Now layer the staves.  From whence the extra sharp??
Thank you.

You are. Who knows?

Hi,

maybe I'm wrong (sorry if it's the case ) but I would say that acciaccatura line might be in other direction when stem down...
I mean,  / <--- this direction for stem up (as it does) but  \ <--- this direction for stem down.

What do you think Mike?

There is no MIDI file equivalent to a fermata ...

I am looking into this.

Going back to a question I posted a couple of years ago, using this example:

Quote

[a piece in] D major that has two accidentalized notes marked to trill sharp.
The note progression is A tr  A#tr#  B tr    B#tr#    C#      D        D#        E

Since the composer's wishes for the trilled A# and B# are ambiguous (read, "confusing to many musicians"), a solution is to show the upper note of the trill as a bracketed target note over the beginning of the trill squiggly. I think the script or LUA (I'm easily confused) should allow for such a ghost-note as well as an accidental.

N.B. I didn't try v. 2.75 there... yet. Shoud I expect problems?

Or, possibly like this:

Code: (nwc) [Select · Download]

!NoteWorthyComposer(2.75)
|PgSetup|StaffSize:18|DurationPadding:N
|StaffProperties|EndingBar:Open (hidden)
|Clef|Type:Treble
|TimeSig|Signature:4/4
|RestChord|Dur:Half|Opts:Stem=Down,HideRest|Dur2:Whole|Pos2:0^
|Spacer|Width:200
|User|Trill.test|Pos:8.5|Span:2|AuxiliaryOffset:1|LineType:Jagged
|Note|Dur:Half|Pos:x-1|Opts:Stem=Down|Visibility:Never
|Spacer|Width:200
|Bar
|Note|Dur:Whole|Pos:0|Opts:Muted
|Spacer|Width:400
|Bar
!NoteWorthyComposer-End

The is one occurrence I've seen that doesn't seem to have been discussed.

Unfortunately I don't have an example to show, but imagine a semibreve with the trill symbol appearing later in the bar than the note, OR a pair of tied notes with the trill appearing over the second note OR partway along the tie.

It seems to me they all mean to hold the note steady for a while (half the duration?) indicated by the location of the trill symbol and then start trilling.

Thanks, Mike. Looks good. I haven't tested it extensively yet, but it seems trouble-free so far. I appreciate the offset ability for the end of the slur. Not so sure about the wavy line (I'd prefer thicker and a bit more angular), but I'll probably get used to it.

Well, you can probably ignore the downward trill. However, the choice of whether to start the trill on the upper note (the trill note) or the lower note (the principal note: the note that is written in the score) does need to be handleable. If the playback recognizes a grace note or acciaccatura before the trilled note, it can probably be handled that way. Better would be if the object had an option for which note to begin the trill on, and would draw the grace note or acciaccatura itself.

I am interested in playback, and I have a somewhat different set of suggestions from Rick's.

I agree with his observation that a trill over notes with a shared stem requires all notes on that stem to be trilled, but I would observe that trilling more than two notes at a time on just about any instrument is impossible, and most can only trill one note at a time (keyboards are the principal exception, although a really good string player can pull it off). I think if users want more than one note trilled simultaneously, though, they should write them on separate staves, layering if they really want the finished music to be on only one staff. If the object encounters a chord, I would lean toward having it trill just the top note and sound the others normally. Others may have a different opinion, and it might be necessary to allow a choice between top and bottom notes.

On speed, I like your idea better than Rick's. However, two questions remain: (1) whether to start the trill on the written note or the trill note, and (2) whether to trill up or down. I think these should be handled as options. Default should be to start on the written note and trill up. The method I'm familiar with to indicate starting on the trill note is to place it before the principal note as a grace note or acciaccatura. Trilling to the note below is uncommon, and I know of no standard way to indicate it, although I don't do enough performing to be sure there isn't one.