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 - Rick G.

151
General Discussion / Re: Melismatic Object and Rest Chord
You might try putting a header and footer on that clip.
The problem is not the RestChord. It is the Rest(s). Melismatic does not seem to allow them.
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.751)
|AddStaff|Name:"Staff"
|StaffProperties|BoundaryBottom:13
|Lyrics|Align:Standard Rules|Offset:-1
|Lyric1|Text:"Ah, ah, ah!\n"
|User|Melismatic.nw|Pos:-4|Class:StaffSig
|Clef|Type:Treble
|Key|Signature:F#|Tonic:G
|TimeSig|Signature:3/8
|Marker|Pos:10.5
|User|Trill.ms|Pos:9.5|Span:2
|RestChord|Dur:8th,Dotted,Slur|Opts:Stem=Up,ArticulationsOnStem,HideRest|Dur2:4th,Dotted,Slur|Pos2:3
|Note|Dur:8th,Slur|Pos:0|Opts:Muted|Visibility:Never
|Note|Dur:16th,Grace|Pos:#3|Opts:Stem=Up,Beam=First
|Note|Dur:16th,Grace|Pos:4|Opts:Stem=Up,Beam=End
|Note|Dur:16th,Slur|Pos:0|Opts:Muted|Visibility:Never
|Bar
|Note|Dur:8th,Dotted,Slur,Accent|Pos:6|Opts:Stem=Down,Lyric=Never,Beam=First
|Note|Dur:16th,Slur|Pos:5|Opts:Stem=Down,Lyric=Never,Beam
|Note|Dur:16th,Slur|Pos:4|Opts:Stem=Down,Lyric=Never,Beam
|Note|Dur:16th|Pos:3|Opts:Stem=Down,Lyric=Never,Beam=End
!NoteWorthyComposer-End
154
General Discussion / Re: incorrect layout
Quote from: guidovanharten –
What can I do to fix this problem?
It would help if you would re-state the problem. So far, I can get this much from the image:
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.751)
|PgSetup|StaffSize:18
|Font|Style:StaffItalic|Size:11.25
|Font|Style:StaffBold|Size:9
|Font|Style:StaffLyric|Typeface:"Verdana"|Size:8.1|CharSet:1
|AddStaff|Name:"Staff"
|StaffProperties|EndingBar:Open (hidden)|BoundaryBottom:16
|Lyrics|Align:Standard Rules
|Lyric1|Text:"de duxxxi yyyyyel al-le\n"
|Note|Dur:4th|Pos:-1
|Note|Dur:Half|Pos:0
|Spacer|Width:50
|Note|Dur:4th|Pos:-1
|Note|Dur:Half|Pos:-2
|Note|Dur:4th|Pos:-3
!NoteWorthyComposer-End
At a minimum, the correct lyric would help.

157
Object Plugins / Re: Slur.ms (2.1)
Quote from: SEBC –
when I removed the nwc slur then the lyrics got messed up.
One solution is to keep the slur and hide it with a Marker.
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.751)
|AddStaff|Name:"Staff"
|StaffProperties|EndingBar:Open (hidden)|BoundaryBottom:16
|Lyrics|Align:Standard Rules
|Lyric1|Text:"a b\n"
|Marker|Pos:0|Visibility:Never
|Note|Dur:4th,Slur|Pos:0
|Note|Dur:4th|Pos:1
|Note|Dur:4th|Pos:2
!NoteWorthyComposer-End
158
General Discussion / Re: chord notes of differing value
Quote from: David Palmquist –
Layering is designed to be a workaround for things that can't be notated any other way.
I disagree. When multiple voice share the same staff, putting each voice on its own layered staff makes for a clearer presentation.
Layering takes longer to get to the "first draft," but by the final edit you get the time and effort back.
Quote from: David Palmquist –
I don't play piano, so I must ask, how is a pianist going to get two shorter notes of such a chord to end before the two longer notes?
You take your foot off the damper pedal and lift your fingers off the short notes.
166
General Discussion / Re: Collapsing stave /lyrics
Start with a SATB template. Enter the notes.
Set the staff boundaries to cover the notes/stems/beams.

Add a zero line Verses staff below the Alto Staff. Set Lyric Alignment to Top.
Add a zero line Chorus staff below the Verses Staff. Set Lyric Alignment to Top.
These do not get layered!

Use muted, headless, stemless note to hang the Lyrics on. Non-visible notes lack the flexibility needed to horizontally align the lyrics.

Add the Lyrics.
Set the top staff boundary on the Verses Staff to cover the lyrics. Set the bottom to one.
Set the top staff boundary on the Chorus Staff to one. Set the bottom to cover the Verse lyrics.
Set the Lyric Offset on the Chorus Staff to -3. This will center the Chorus against the Verses.

This should look good in the Viewer, play back properly, and highlight the Lyrics properly.
Adjust where needed, but do not change the staff boundaries on the Lyric staves.

Now comes the tricky part. The adjustments from here on apply to Print Preview.
Just before the double barline that starts the Chorus:

Add to the Verses staff:
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|Boundary|Style:NewSize|Upper:2|Color:6
!NoteWorthyComposerClip-End
Adjust 'Upper' so that the chorus lyrics do not collide with any Alto note stems/beams.

Add to the Verses staff:
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|Boundary|Style:NewSize|Lower:1|Color:6
!NoteWorthyComposerClip-End

Add to the Tenor staff:
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|Boundary|Style:NewSize|Upper:4|Color:6
!NoteWorthyComposerClip-End
Adjust 'Upper' so that the chorus lyrics do not collide with any Tenor note stems/beams.

The attachment aligns properly no matter where the system breaks (or a SysBreak is placed.)
167
Object Plugins / Re: Glissando.ms (2.11)
Quote from: Jorge D. Fuentes –
The Glissando notes, however, aren't following the Crescendo.  They are ignoring it and using the velocity (dynamic marking) that is before the < marking.
Can you make the Glissando notes adhere to Crescendos and Decrescendo/Graphic Crescendo and Decrescendo rules?
You need to use volume, not note velocity.
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|Clef|Type:Treble
|Key|Signature:C|Tonic:C
|TimeSig|Signature:4/4
|Rest|Dur:4th
|Dynamic|Style:f|Opts:Velocity=127,Volume=92|Pos:-8
|Note|Dur:4th|Pos:#1
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam=First
|Note|Dur:8th|Pos:1^|Opts:Stem=Down,Beam=End
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam=First
|Note|Dur:8th|Pos:1^|Opts:Stem=Down,Beam=End
|Bar
|Note|Dur:8th,Grace|Pos:1|Opts:Diminuendo|Visibility:Never
|Note|Dur:Half|Pos:1|Opts:Diminuendo,Muted
|User|Glissando.ms|Pos:1|Playback:Chromatic|Pen:wavy
|Note|Dur:8th,Grace|Pos:-7|Opts:Stem=Up,Muted|Visibility:Never
|Dynamic|Style:p|Opts:Velocity=127,Volume=45|Pos:-8
|Rest|Dur:Half
|Bar
!NoteWorthyComposerClip-End
169
Tips & Tricks / Re: Change dynamics font size
Quote from: SimonJShaw –
I guess it would only take 15 mins to do but seems unnecessary :-/ 
You must be doing it wrong. Use 'Filtered Properties...' to set all the Dynamics to Visibility:Never.
Use 'Find...' and Find Next to add Text items.
Quote from: SimonJShaw –
And I'd like a solution for the future as the relative sizing thing is pants.
The solution for the future is to hide them as you go along and use Text items. Text items are much more flexible for positioning and if the piece is at all complex, you will need that flexibility.
175
General Discussion / Re: Acciaccatura
Quote from: Flurmy –
When the tempo is slow the acciaccatura made with a grace note is too long.
In some extreme cases, even 1/64 in a hidden staff is too slow.
You might try something like this:
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|MPC|Controller:tempo|Style:Absolute|TimeRes:Quarter|SweepRes:1|Pt1:0,10|Pos:12
|Note|Dur:8th,Grace,Slur|Pos:4
|Note|Dur:4th|Pos:3
|MPC|Controller:tempo|Style:Absolute|TimeRes:Thirtysecond|SweepRes:1|Pt1:0,120|Pt2:1,10|Pos:9
|Note|Dur:8th,Grace,Slur|Pos:4
|Note|Dur:4th|Pos:3
!NoteWorthyComposerClip-End
176
General Discussion / Re: Slow grace notes
Quote from: Flurmy –
How convoluted!
I agree.
Quote from: Flurmy –
There is something in the NWC handling of grace notes that's out of my logic.
I won't comment on your logic, but NWC 2.75a.2 generates bad MIDI for grace notes that are a final tie destination, if they are not visible.
Quote from: Flurmy –
N.B. It seems that the tenuto has very little effect, if any.
Very little, but some. In the example, the notes stay on for 24 PPQN's instead of 22
177
General Discussion / Re: Slow grace notes
Quote from: Flurmy –
Does exist a trick for this?
This will get you close:
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|RestChord|Dur:8th,Grace|Opts:Stem=Down,Muted|Dur2:Whole,Grace|Pos2:-6z^|Visibility:Never
|Note|Dur:8th,Grace,Tenuto|Pos:3|Opts:Stem=Up,Slur=Upward,Beam=First|Visibility:Never
|RestChord|Dur:8th,Grace|Opts:Stem=Down|Dur2:Whole,Grace|Pos2:-6z^|Visibility:Never
|Note|Dur:8th,Grace,Tenuto|Pos:2|Opts:Stem=Up,Slur=Upward,Beam|Visibility:Never
|RestChord|Dur:8th,Grace|Opts:Stem=Down|Dur2:Whole,Grace|Pos2:-6z^|Visibility:Never
|Note|Dur:8th,Grace,Tenuto|Pos:3|Opts:Stem=Up,Slur=Upward,Beam=End|Visibility:Never
|RestChord|Dur:8th,Grace|Opts:Stem=Down|Dur2:Whole,Grace|Pos2:-6z^|Visibility:Never
|RestChord|Dur:8th,Grace|Opts:Stem=Down,Muted|Dur2:Whole,Grace|Pos2:-6z|Visibility:Never
|Note|Dur:Half|Pos:2
!NoteWorthyComposerClip-End
Seems OK with piano and harp. May be a bit choppy for winds:
Code: (miditxt) [Select · Download]
0 On ch=1 n=76 v=116
24 On ch=1 n=76 v=0
48 On ch=1 n=74 v=116
72 On ch=1 n=74 v=0
96 On ch=1 n=76 v=116
120 On ch=1 n=76 v=0
144 On ch=1 n=74 v=110
352 On ch=1 n=74 v=0
180
General Discussion / Re: Slow grace notes
Quote from: Lawrie Pardy –
Flurmy's example and the first part of Rick's example playback identically on my PC.
Are you sure? On my system, Flurmy's example plays this:
Code: (miditxt) [Select · Download]
0 On ch=1 n=76 v=110
1 On ch=1 n=76 v=0
1 On ch=1 n=74 v=0
1 On ch=1 n=76 v=0
48 On ch=1 n=74 v=110
96 On ch=1 n=76 v=110
144 On ch=1 n=74 v=110
352 On ch=1 n=74 v=0
while my example plays this:
Code: (miditxt) [Select · Download]
0 On ch=1 n=76 v=110
46 On ch=1 n=76 v=0
48 On ch=1 n=74 v=110
94 On ch=1 n=74 v=0
96 On ch=1 n=76 v=110
142 On ch=1 n=76 v=0
144 On ch=1 n=74 v=110
352 On ch=1 n=74 v=0
182
General Discussion / Re: Slow grace notes
Works for me. Compare and contrast:
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|Note|Dur:8th,Grace|Pos:3^|Opts:Stem=Up,Slur=Upward,Beam=First
|Note|Dur:8th,Grace|Pos:3|Opts:Stem=Up,Slur=Upward,Beam
|Note|Dur:8th,Grace|Pos:2^|Opts:Stem=Up,Slur=Upward,Beam
|Note|Dur:8th,Grace|Pos:2|Opts:Stem=Up,Slur=Upward,Beam
|Note|Dur:8th,Grace|Pos:3^|Opts:Stem=Up,Slur=Upward,Beam
|Note|Dur:8th,Grace|Pos:3|Opts:Stem=Up,Slur=Upward,Beam=End
|Note|Dur:Half|Pos:2
|Note|Dur:8th,Grace|Pos:3|Opts:Stem=Up,Slur=Upward,Beam=First
|Note|Dur:8th,Grace|Pos:2|Opts:Stem=Up,Slur=Upward,Beam
|Note|Dur:8th,Grace|Pos:3|Opts:Stem=Up,Slur=Upward,Beam=End
|Note|Dur:Half|Pos:2
!NoteWorthyComposerClip-End
188
General Discussion / Re: Hidden Articulation Marks and Slurs
This also works:
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.751)
|AddStaff|Name:"Staff"
|StaffProperties|EndingBar:Open (hidden)
|Marker|Pos:6.5|Target:Articulation
|Note|Dur:4th,Slur,Accent|Pos:3|Opts:ArticulationsOnStem
|Note|Dur:4th|Pos:4
!NoteWorthyComposer-End
Check 'Use stem for articulations.' This auto-positions the slur and the articulation Marker puts the accent back on the head.
193
General Discussion / Re: Chord Problem
Quote from: William Ashworth –
doing that or simply shrinking the space requires layers in NWC (unless Rick can come up with something).
I cannot. IMO, with two voices, layers should be used. Something like this:
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.751)
|Editor|ActiveStaff:2|CaretIndex:1|CaretPos:0
|AddStaff|Name:"Staff"
|StaffProperties|EndingBar:Open (hidden)|Visible:N
|Clef|Type:Treble
|Key|Signature:C|Tonic:C
|TimeSig|Signature:6/8
|Chord|Dur:8th|Pos:1|Opts:Stem=Down,Beam=First|Dur2:4th,Dotted|Pos2:2
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam=End
|Chord|Dur:8th|Pos:1|Opts:Stem=Down,Beam=First|Dur2:4th,Dotted|Pos2:2
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam=End
|Bar
|AddStaff|Name:"Staff-2"
|StaffProperties|EndingBar:Open (hidden)|WithNextStaff:Layer
|Clef|Type:Treble
|Key|Signature:C|Tonic:C
|TimeSig|Signature:6/8
|Note|Dur:4th,Dotted|Pos:2|Opts:Stem=Up,XNoteSpace=1
|Note|Dur:4th,Dotted|Pos:2|Opts:Stem=Up,XNoteSpace=1
|Bar
|RestMultiBar|NumBars:14|PrintOnce:N|WhenHidden:ShowBars,ShowRests
|Bar
|Boundary|Style:NewSystem|NewPage:N
|AddStaff|Name:"Staff-2-2"
|StaffProperties|EndingBar:Open (hidden)
|Clef|Type:Treble
|Key|Signature:C|Tonic:C
|TimeSig|Signature:6/8
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam=First
|Spacer|Width:175
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam
|Spacer|Width:175
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam=End
|Spacer|Width:175
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam=First
|Spacer|Width:175
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam
|Spacer|Width:175
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam=End
|Bar
!NoteWorthyComposer-End
195
General Discussion / Re: Hidden Articulation Marks and Slurs
Quote from: Mike Shawaluk –
You are trying to move the articulation above the slur. When you use the marker to move it, the slur gap is still present. And if you check both the Slur and Articulation box on the marker, then they overlap.
Then use two markers:
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.751)
|AddStaff|Name:"Staff"
|StaffProperties|EndingBar:Open (hidden)
|Marker|Pos:5
|Marker|Pos:6.5|Target:Articulation
|Note|Dur:4th,Slur,Accent|Pos:3
|Note|Dur:4th|Pos:4
!NoteWorthyComposer-End
197
General Discussion / Re: Performance Notes
Quote from: SEBC –
I had a foreign word in my text and included a footnote of how to pronounce it. I tried to put it on the bottom of the page in which it first appeared, but it kept moving around as I edited the score and so I ended up moving it multiple times.
I agree that a footnote object would be useful. While it would not be difficult to position text relative to the bottom of the page of where a footnote object might exist, AFAIK there is no way to prevent it from colliding with the bottom staff. It would be non-trivial to avoid collisions where more than one footnote might occur on a page.