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.

3302
General Discussion / Re: Bizare behaviour
I think it counts only the first note value entered in each chord. 

Noteworthy uses the the shorter duration. Order does not matter. The clip may look funny for two voices, but what if there are 3 or more? One might need this seemingly "bizarre" behaviour.  One of NoteWorthy's more user friendly features is that it does not constantly check the user's work.

If you want the program to look over your shoulder, just put 1 voice on each staff.
3304
General Discussion / Re: Creating a chord composed of regular notes and grace notes
You don't. Grace notes and regular notes will not align vertically will any consistency. This is why grace notes make poor "cue" notes.  Best workaround I know of is to use regular notes, make the noteheads blank and put smaller noteheads in as text.  The beams are still too fat, but it is close. Sometimes, it helps to make the stems shorter.
3305
General Discussion / Re: measures per printed line: aka, page set-up?
If you are referring to the Tenor Staff, perhaps it is because that bar is:

|Bar|Style:Single|SysBreak:N|Color:0|Visibility:Never

(Color added)
After enabling measure #'s and assuming a zero base (which is what is set in the file) and changing Staff Bold to a font on my sytem, I make it to be measure 34
3306
General Discussion / Re: Bug: Note Spacing (Beta 1 Version 2)
Rich:
If you replace all the double bar lines lines in your clip with single lines it looks fine. If you put enough stuff in a line or set the margins large enough, eventually NWC will get around to formatting it correctly.

Thanks for taking a look at it even though I do not appear to have the fluency to describe it.
3307
General Discussion / Re: Bug: Note Spacing (Beta 1 Version 2)
Rich,
I can't see what you are describing. Repeat barlines are, by their nature, different, but all the other bar lines cause the same alignment.
Please elaborate.
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Note|Dur:Half|Pos:0
|Note|Dur:Half|Pos:0
|Bar
|Note|Dur:Half|Pos:0
|Note|Dur:Half|Pos:0
|Bar|SysBreak:Y
|Note|Dur:Half|Pos:0
|Note|Dur:Half|Pos:0
|Bar|Style:Double
|Note|Dur:Half|Pos:0
|Note|Dur:Half|Pos:0
|Bar|Style:Double|SysBreak:Y
|Note|Dur:Half|Pos:0
|Note|Dur:Half|Pos:0
|Bar|Style:SectionClose
|Note|Dur:Half|Pos:0
|Note|Dur:Half|Pos:0
|Bar|Style:SectionClose|SysBreak:Y
|Note|Dur:Half|Pos:0
|Note|Dur:Half|Pos:0
|Bar|Style:SectionClose
|Note|Dur:Half|Pos:0
|Note|Dur:Half|Pos:0
|Bar|Style:SectionClose|SysBreak:Y
!NoteWorthyComposerClip-End
3308
General Discussion / Re: Bug: Note Spacing (Beta 1 Version 2)
David,
Quote
... rules for the maximum distance from the bar line to the first note in the bar, taking into account stem direction, accidentals and clustered chords ...
I think you are making this more complex than it is. NWC (both versions) add space to notes to get them to justify a line. It already handles the first note in the line. Programatically, it cannot be difficult to determine if a note is the first in a measure. It is even easier to know if a note is invisible.

Prior to NWC, I used a DOS/UNIX program: MusicEZ.  It wasn't (easy), but it didn't have this bug.

Perhaps the following clip shows it better.  It also shows another annoyance.  Notice how the presence of text in lines 2-4 causes less space between the KeySig and the first note.

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Clef|Type:Treble
|Key|Signature:F#
|TimeSig|Signature:4/4
|Rest|Dur:Whole
|Bar|SysBreak:Y
|Text|Text:"no gap"|Font:StaffItalic|Pos:8|Justify:Center|Placement:AtNextNote
|Note|Dur:Half|Pos:0
|Note|Dur:Half|Pos:0
|Bar
|Text|Text:"\|--- gap ---\|   "|Font:StaffItalic|Pos:8|Justify:Right|Placement:AtNextNote
|Note|Dur:Half|Pos:0
|Note|Dur:Half|Pos:0
|Bar|SysBreak:Y
|Text|Text:"no gap"|Font:StaffItalic|Pos:8|Justify:Center|Placement:AtNextNote
|Chord|Dur:Half|Pos:-1,0
|Note|Dur:Half|Pos:0
|Bar
|Chord|Dur:Half|Pos:-1,0
|Note|Dur:Half|Pos:0
|Bar|SysBreak:Y
|Text|Text:"no gap"|Font:StaffItalic|Pos:8|Justify:Center|Placement:AtNextNote
|Chord|Dur:Half|Pos:b-1,b0
|Note|Dur:Half|Pos:0
|Bar
|Chord|Dur:Half|Pos:b-1,b0
|Note|Dur:Half|Pos:0
|Bar|SysBreak:Y
|Note|Dur:Half|Pos:0
|Note|Dur:Half|Pos:0
|Bar
|Note|Dur:Half|Pos:0
|Note|Dur:Half|Pos:0
|Bar|SysBreak:Y
|Chord|Dur:Half|Pos:-1,0
|Note|Dur:Half|Pos:0
|Bar
|Chord|Dur:Half|Pos:-1,0
|Note|Dur:Half|Pos:0
|Bar|SysBreak:Y
|Chord|Dur:Half|Pos:b-1,b0
|Note|Dur:Half|Pos:0
|Bar
|Chord|Dur:Half|Pos:b-1,b0
|Note|Dur:Half|Pos:0
|Bar|SysBreak:Y
!NoteWorthyComposerClip-End

3309
General Discussion / Re: Bug: Note Spacing (Beta 1 Version 2)
You've got a forced system break that stretches the first line in the print preview.
Gee ... no kidding? ... I'd have never guessed.
Quote
If you remove the forced system break and copy/paste the same few bars onto the end of your staff, so you end up with enough to wrap a few times without a forced system break, when you print preview I think you'll see the spacing is normal.
No, all I'll see is a workaround for the bug.  I need the SysBreak where it is.  I have workarounds for this.  I have gotten tired of using them.  I'd rather see a fix.
Quote
When you view it in Typeset with a forced system break, where does Typeset put the extra spacing needed to stretch out the bars?
Evidently you use some program called "Typeset".  By "typeset music", I meant the kind printers have been doing for the last 400 years or so.  Sorry for the confusion.





3310
General Discussion / Bug: Note Spacing (Beta 1 Version 2)
Look at this clip in Print Preview.  NWC2 (correctly) does not add extra space the front of the first note in each line.  But this should also true for the first note in all other measures.  This is an unsightly bug (that also exists in NWC 1.75b). Typeset music handles this correctly; NWC2 should as well.

I won't call this a bug, but IMO, NWC2 should not add extra space to invisible notes/rests either.

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Clef|Type:Treble
|Key|Signature:C|Visibility:Never
|TimeSig|Signature:4/4
|Note|Dur:16th|Pos:3|Opts:Stem=Down,Beam=First
|Note|Dur:8th,Dotted|Pos:5|Opts:Stem=Down,Beam=End
|Bar
|Chord|Dur:Half|Pos:1,3,6
|Chord|Dur:Half|Pos:0,2,5
|Bar
|Chord|Dur:Half,Dotted|Pos:-2,1,3
|Note|Dur:16th|Pos:3|Opts:Stem=Down,Beam=First
|Note|Dur:8th,Dotted|Pos:5|Opts:Stem=Down,Beam=End
|Bar
|Chord|Dur:4th,Dotted|Pos:6|Opts:Stem=Up|Dur2:Half|Pos2:1,3
|Note|Dur:16th|Pos:7|Opts:Stem=Up,Beam=First
|Note|Dur:16th|Pos:6|Opts:Stem=Up,Beam=End
|Chord|Dur:Half|Pos:0,2,5
|Bar|SysBreak:Y
|Chord|Dur:Half,Dotted|Pos:-2,1,3
|Note|Dur:16th|Pos:1|Opts:Stem=Down,Beam=First
|Note|Dur:8th,Dotted|Pos:2|Opts:Stem=Down,Beam=End
|Bar|Style:Double
|Chord|Dur:8th|Pos:2|Opts:Stem=Up,Beam=First|Dur2:4th,Dotted|Pos2:-4,-2
|Note|Dur:16th|Pos:1|Opts:Stem=Up,Beam
|Note|Dur:16th|Pos:1^|Opts:Stem=Up,Beam=End
|Note|Dur:8th|Pos:1|Opts:Stem=Up,Beam=First
|Chord|Dur:8th|Pos:2|Opts:Stem=Up,Beam=End|Dur2:8th|Pos2:-3
|Chord|Dur:4th|Pos:-3,2
|Chord|Dur:16th|Pos:-4,1|Opts:Stem=Up,Beam=First
|Note|Dur:8th,Dotted|Pos:3|Opts:Stem=Up,Beam=End
|Bar
!NoteWorthyComposerClip-End
3313
General Discussion / Slur visibilty problem (Beta 1 Ver 2)
It seems right that slurs inhert their visibilty from their starting note/rest, but why should they also inherit visibility from the first note after a system break? This causes a different result depending on page flow. IMHO, this should be corrected.
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Rest|Dur:Whole
|Bar
|Rest|Dur:Whole
|Bar
|Rest|Dur:Whole
|Bar
|Note|Dur:Whole,Slur|Pos:0
|Bar|SysBreak:Y
|Note|Dur:Whole,Slur|Pos:0|Visibility:Never
|Bar
|Note|Dur:Whole,Slur|Pos:0
|Bar
|Note|Dur:Whole|Pos:0
!NoteWorthyComposerClip-End
The slur is invisible on the second line but, if you change the SysBreak to the next Bar, the slur appears.
3315
General Discussion / Re: Beam direction bug (Beta 1 Update 2)
This would appear to be incorrect as well:
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Note|Dur:8th,Dotted|Pos:1|Opts:Stem=Up,Beam=First
|Note|Dur:16th,Grace,Slur|Pos:0|Opts:Stem=Up,Beam=First
|Note|Dur:16th,Grace,Slur|Pos:1|Opts:Stem=Up,Beam=End
|Note|Dur:16th|Pos:0|Opts:Stem=Up,Beam
|Note|Dur:8th|Pos:-1|Opts:Stem=Up,Beam
|Note|Dur:8th|Pos:-2|Opts:Stem=Up,Beam=End
!NoteWorthyComposerClip-End
Interestingly, NWC 1.75b handles this correctly, but mishandles my original example.
3316
General Discussion / Re: Beam direction bug (Beta 1 Update 2)
Rick, it's correct.  Only on the last note of the beam will show the flag left.
Being consistent doesn't make it right. Consider this:
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|TimeSig|Signature:AllaBreve
|Note|Dur:8th|Pos:0|Opts:Stem=Up,Beam=First
|Rest|Dur:16th
|Note|Dur:16th|Pos:-1|Opts:Stem=Up,Beam
|Note|Dur:8th|Pos:-2|Opts:Stem=Up,Beam
|Note|Dur:8th|Pos:-4|Opts:Stem=Up,Beam=End
|Note|Dur:8th,Dotted|Pos:0|Opts:Stem=Up,Beam=First
|Note|Dur:16th|Pos:-1|Opts:Stem=Up,Beam
|Note|Dur:8th|Pos:-2|Opts:Stem=Up,Beam
|Note|Dur:8th|Pos:-4|Opts:Stem=Up,Beam=End
!NoteWorthyComposerClip-End
The rythym is the same. The 16th note's position in the rythym is the same.
How can it possibly be right for the 16th beam (flag) to change direction?
3317
General Discussion / Re: Timing or Mathmatical Problem
If I recall correctly, it was RickG who introduced me to the idea of "digital white-out"... 

Guilty. But I use it only as a last resort. Even though it is "white", my printer still counts it as a color and goes into "half-speed" mode. Also, since it must be used after what you want to obliterate, it is tricky to fix the position if you can't attach it to something. In the above example, I would use a layer.

Best uses for digital white-out I've found are:
  • wipe out staves to the end of the line for special endings
  • change triplet 3 to a 6
3318
General Discussion / Beam direction bug (Beta 1 Update 2)
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|TimeSig|Signature:AllaBreve
|Note|Dur:8th|Pos:0|Opts:Stem=Up,Beam=First
|Rest|Dur:16th
|Note|Dur:16th|Pos:-1|Opts:Stem=Up,Beam
|Note|Dur:8th|Pos:-2|Opts:Stem=Up,Beam
|Note|Dur:8th|Pos:-4|Opts:Stem=Up,Beam=End
|Rest|Dur:Half
!NoteWorthyComposerClip-End
Clearly, the 16th note beam should point to the left.
See Could this be a bug? in the beta newsgroup for more details.
3320
General Discussion / Re: Comfotable Notation Size?
Anything over 20pt seems to insult my flute players.
16pt is my minimum except for one important exception:

A piece with not many accidentals and lots of 32nd notes is sometimes best done in 14pt. The situation to avoid at all costs is where you only get 1 measure on a line, e.g. Pachebel's Canon.
Accidentals and strange rythyms make me favor a larger size more than the range of notes.

For piano music, (my instrument), I have found that the presence of 3 or 4 accidentals on a single chord usually means 18pt.  Anything less and I can't read on the fly. Otherwise, 16pt works well. I used 14pt on my piano reduction of Pachebel's Canon.

You didn't ask, but one deviation I make for piano music is in the margins. I set left and right to 1/4 inch, top to 0, Title font to 20.  It seems to me that the reason for margins is for adding memos and that the paper wears out around the edges. With NWC, I don't need memos, I can build them into the piece. When the paper wears, I just pitch it and print another. This gets me the functionality of 9x12 with 8½x11 paper. I keep the bottom margin at ½" minimum, since I never know when I'll have a piano with a deep lip.
3323
General Discussion / Re: Glitch in nwc2upd_v2p1z_beta1x00 Update
I just installed the nwc2upd_v2p1z_beta1x00.exe update and opened a choral piece I was working on and found that all the triplets over unbeamed eight notes were gone. 

Setting a stem direction for each note solves the problem. It also solves the crochet problem. A quick workaround would appear to be:

  • Load the song.
  • Select the entire staff and set all stems either up or down.
  • Redo the triplets. (If you remember where they are :( )
  • Audit note stems.

Another problem:
Audit Note Stems removes all the |RestChord| Vertical Offsets!  Not nice.

This:
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|RestChord|Dur:Whole|Opts:Stem=Down,VertOffset=-2|Dur2:Whole|Pos2:4
!NoteWorthyComposerClip-End

Becomes this (after Audit Note Stems):
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|RestChord|Dur:Whole|Opts:Stem=Down|Dur2:Whole|Pos2:4
!NoteWorthyComposerClip-End
3325
General Discussion / Re: Mezzo-staccato
Is there any way to notate mezzo-staccato (portato) without resorting to text?
No.  You can simulate the sound with slurred staccato notes. Make sure that the slur extends past the last staccato note.

Quote
Do we need to put on the wish-list to be able to have both together.
This has been wished for, several times.
3328
General Discussion / Re: Stuck notes again
Another source of stuck notes:
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Instrument|Name:"Recorder"|Patch:74|Trans:0|DynVel:10,30,45,60,75,92,108,127|Pos:8
|Note|Dur:4th|Pos:0^
|Note|Dur:4th|Pos:0|Opts:Muted
|Rest|Dur:Whole
|Rest|Dur:Whole
|Note|Dur:4th|Pos:b0
!NoteWorthyComposerClip-End
Tieing a note into a muted note supresses the midi note off

It might seem logical that a muted note produces no output, but perhaps it should act as a note with no initial note on.
3329
General Discussion / Re: Preview and print problem
Inconsistent bar lines, TimeSigs, and staves of varing lengths create all kinds of "special" effects.

It is too bad that Audit Bar Lines is not interactive. Folks would use it more often and it would fix problems like this.

A score audit that would check TimeSigs, Bars, and Flow on the visible staves would be a welcome addition.
3330
General Discussion / Re: octave transpositions ("8va")
I'd also like to request the ability to shift two octaves, though there's slightly less conventon fo rthat. 16va, 15va - I suspect it ought to be 15ma, really - as well as clefs with little 15s above and below 'em.

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Note|Dur:4th|Pos:0
|Instrument|Name:"8va"|Trans:12|Pos:6|Justify:Center|Placement:AtNextNote
|Note|Dur:4th|Pos:0
|Instrument|Name:"15ma"|Trans:24|Pos:6|Justify:Center|Placement:AtNextNote
|Note|Dur:4th|Pos:0
|Instrument|Name:"loco"|Trans:0|Pos:6|Justify:Center|Placement:AtNextNote
|Note|Dur:4th|Pos:0
!NoteWorthyComposerClip-End
3332
General Discussion / Re: icons
You can do a long extension and redo all your associations, but it is not really worth it.
Easier by far to put your 1.75b in a separate folder.
3334
General Discussion / Re: Space and Invisible rests
You are not missing anything. Visibility:Never generally means no ink and no width.
Think of it as: doesn't exisit in Print Preview or Print

There are cases where it would be useful to have width but no ink. Alas, this is not a feature.

The best you can do is change the object's Color to Highlight n and define Highlight n to the background color (usually white) .  You may have to move the object so as not to occlude a prior object. It would be useful to be able to set a Highlight color to none.
3335
General Discussion / Re: position of fermata
Quote
Using toolbar customization, I have a fermata on my 1.75b toolbar

I stand corrected. It has been so long ago that I forgot when toolbars got configurable.
I expected to find it under Tools->Options rather than View. (Not that this has changed)

It has been improved it NWC2. Staff Position is at the cursor rather than fixed at 9

I'll defer to your knowledge of Italian plurals.
3336
General Discussion / Re: position of fermata
Quote
I always use the toolbar button for fermata(s?)

Yeah, but this is the General Discussion Forum.
There seems to more NWC2 content here since the forum format changed.
I suspect that it is quite confusing to folks that only use ver 1.75b

BTW, it is probably fermati
3337
General Discussion / Re: position of fermata
Justification: Center
Alignment/Placement: at next note/bar
Preserve Width should not be checked.

This should be the default for a fermata, but it is not. :(
3338
General Discussion / User Tool Bug in 1z
This applies to any User Tool that writes to StdOut.
If your selection includes a Beam=First and does not include a Beam=End, the beamed note group will become unbeamed. This also applies to a selection of Beam=End without Beam=First

This also happens if you simply select the first or last beamed note and press ctrl+c followed by ctrl+v

For testing, here is possibly the world's shortest VBScript User Tool:
Code: [Select · Download]
Do Until WScript.StdIn.AtEndOfStream
WScript.StdOut.WriteLine WScript.StdIn.ReadLine
Loop

Another problem with beamed notes:
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Note|Dur:8th|Pos:-1|Opts:Beam=First
|Note|Dur:8th|Pos:1|Opts:Beam=End
|Note|Dur:8th|Pos:1|Opts:Beam=First
|Note|Dur:8th|Pos:-1|Opts:Beam=End
!NoteWorthyComposerClip-End
In order to paste a beamed group and keep it beamed, all the stems should have the same direction.  The paste parser will usually detect this and unbeam them, but it evidently misses the case where notes have different default directions and none of the notes have a stem direction specified.

I was trying to write an enhanced Audit Note Stems, that would ignore RestChords and work with a selection. It works fine until it gets to beamed notes ...

3339
General Discussion / Minor RestChord Problem with ver 1z
You cannot remove an articulation from a RestChord
You cannot add an articulation to a RestChord

In order to have an articulation on a RestChord, you must have the appropriate button(s) down when you add the note. I can see no technical reason for this and it is not user friendly.

Frankly, I see no necessary distinction between a rest and a note with a special notehead that, when encountered, does not play.
3340
General Discussion / Re: staccato notes
If you do want to export, then import back, it will be more readable if you put a playing style legato at the beginning of each staff.
3341
General Discussion / Re: Feature Request: Note variation
For a smaller clef, Set User 1 to NWC2STDA, size=staff size and use something like this:
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Rest|Dur:Whole
|Bar
|Text|Text:"a  "|Font:User1|Pos:-1|Justify:Right|Placement:AtNextNote
|Clef|Type:Treble|Visibility:Never
|Note|Dur:4th|Pos:0
!NoteWorthyComposerClip-End

a=Treble, b=Bass, ]=Percussion
3342
General Discussion / Re: Feature Request: Note variation
All of this can currently be done with a blank space notehead and a user font text entry.

That said, more noteheads would expand the flexibilty of NWC2, but what is needed first is the ability to specify what font to use as the system font. Having it hard coded to NWC2STDA is becoming a PITA.
3343
General Discussion / Re: Numbering Lyric Lines
With either version you can tie a grace note to the first note. Set both notes to "Lyric Always". Set Visibility on the grace note to "Never".  This will keep playback and midi export intact. Be careful "auditing accidentals".
3344
General Discussion / Re: Converting score to jpg?
Obtain the free program "Irfan View." This program can open a metafile and export it as a graphic image of your choice, including JPG. But I think you will like GIF or TIF better."
_______________________________________________
. . . but when I do this from NWC 1.75b I have a very poor quality TIFF file when viewed with Photoshop, no matter what resolution I set on the printer (is there somewhere else to set res?)
Try reducing the color depth of your monitor. For some reason, IrfanView (and some other apps) produce a higher resoulution jpeg (or tif) when in 16bit or 256 color mode (as opposed to TrueColor)
3346
General Discussion / Re: Stuck notes again
So one will be able to write a section in A and then revisit it in Ab as long a there is not a tied note at the flow redirection that is affected by the key change. Sounds good, but ...

I suspect that it will only be a few weeks before you get another stuck note report.  Knowing that it can only be caused by a tie across a key change will help find it, but it would be nice to finally end this problem.

Something you might consider is an "all notes off" for the channel at each key change.  I can't say that I have ever seen a tie across a key change.  Someone will probably prove me wrong.
3347
General Discussion / Stuck notes again
Mostly fixed in ver 1y, but this cropped up in the newsgroup:

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Clef|Type:Treble
|Instrument|Name:"Flute"|Patch:73|Trans:0|DynVel:10,30,45,60,75,92,108,127|Pos:10
|TimeSig|Signature:4/4
|Bar|Style:MasterRepeatOpen
|Note|Dur:Half|Pos:-4^
|Note|Dur:Half|Pos:-4
|Bar
|Note|Dur:Half|Pos:-2^
|Note|Dur:Half|Pos:-2
|Bar
|Note|Dur:Half|Pos:0^
|Note|Dur:Half|Pos:0
|Key|Signature:Bb,Eb,Ab
|Bar
|Note|Dur:Whole|Pos:-2
|Bar|Style:MasterRepeatClose
!NoteWorthyComposerClip-End

By changing the KeySig, you can get all, some, or none or the notes to stick.
99.99% of the time you will want to repeat in the original key so you should restore the KeySig, but it should be fixed.  This is a problem with D.S. flows as well.
3348
General Discussion / Re: beams across barlines
Well, wonder of wonders, Lawrie, I was about to make the same point about the beta group when this new fangled forum told me a reply had been posted while I was replying and that I might want to check it before hitting Post.

I would also add that it is not uncommon to have the first and last staff be unusually large to get the right # of systems on the page. I would not like to have the layers be that large.
3349
General Discussion / Re: beams across barlines
This comes up frequently. It always seems to be a case of a standard staff that is larger than the orchestral or grand staff that it layers. 

It might help to have the staff sizes (and possibly types) added to Score Review.

An option to show all or just visible staves might be useful as well.