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.

3351
General Discussion / Re: NWC2 Clip Text in the new forum
Using IE on Win98SE:
Triple click selects all unless there is a scroll bar. Then it just selects a word.

A problem:
The mouse wheel lets me scroll the page until the pointer is over a code area with a scoll bar.
Then it scrolls the code area. IMHO, it would be better to require a click in the code area to use the wheel to scroll there.
3352
General Discussion / Re: Text buglet in Rev 1y
Peter, I think your analysis is correct.

Robin, alt + 160 is great when NWC2 decides to trim strings and you don't want it to, but it adds nothing here.

Lawrie: If you save the file, it loads back as <Text Expression>, yet another bug.

I'm just reporting a bug, not looking for a workaround.
A small one, but NWC2 shouldn't allow you to create something that can't be copied or saved.

How or if NoteWorthy decides to fix this is their concern.
One fix would be to have the OK button disabled until the expression is valid.
3353
General Discussion / Re: Text buglet in Rev 1y
original text was something like this:
|Text|Text:" "|Font:PageText|Pos:6|Wide:N|Justify:Left|Placement:BestFit|Color:0|Visibility:Default

Then I essentially made the text "" by editing the &Expression
3354
General Discussion / Text buglet in Rev 1y
If you enter some text, select its Properties and delete everything in the &Expression box,
you get some thing like this:
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Text|Text:""|Font:PageSmallText|Pos:7|Wide:Y|Justify:Center|Placement:AtNextNote
!NoteWorthyComposerClip-End
If you copy and paste it, you get this:
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Text|Text:"<Text Expression>"|Font:StaffItalic|Pos:8|Wide:Y|Justify:Center|Placement:AtNextNote|Visibility:Never
!NoteWorthyComposerClip-End
Curiously, the position changes and the font gets zapped.
3357
General Discussion / Re: Different number of staffs to be printed in one song
Not so straightforward. The top staff (or one of its layers) usually has the top margin for the system break.  If it is empty, NWC will still have to account for its Vertical Size: Upper. Ditto for the bottom staff and Vertical Size: Lower

  • Then there is the problem of a Grand System... (and some of those have 3-4 visible staves)
  • Organists probably won't want their Pedal Staff going away just because it is empty.
  • Then there's the score where 2 instruments are doing a "back and forth" every 2 measures, but because its a score, you're only getting 2 measures on a page...
I think a more elaborate approach would be needed, probably bar by bar control.
3358
General Discussion / Re: Sharps and flats
I've saved a lot of time with this:
>  use mf2t on the midi
>  insert a KeySig in the txt file (usually you need to use WordPad)
>  use t2mf on the text file.
3360
General Discussion / Re: Thoughts on NWC - importing MIDI, MIDI playback, NIFF/MusicXML
I've been using NWC since '96.  Import was never meant to be more that a starting point to get some notes into the program.  At that time (and still unresolved) there were legal issues about programs facilitating copyright abuse.

Programatically, intelligent import can be done, but if done too well (at least here in the US), one is likely to get sued.

There is a simple reason why midi export is good. The song has to be converted to realtime midi to play it.  It is not very difficult to add a timestamp to each midi command and buffer it for export.

I have long suspected that fermatas and breathmarks were never realtime midi commands, just delays in the stream, and that that is why they are not exported.

Gee, breathmarks and fermatas aren't even in the spellchecker.
Not much chance of them being added to midi export any time soon ...

My 2 cents
3362
General Discussion / Re: Accidental positioning anomaly in 1y
Thanks Lawrie. I'm going to look Alfred up the next time I'm at a used book store.  I wonder if the rules are the same for dbl#.  Seems one could start packing closer than a sixth. G. Schirmer (probably the biggest US publisher) also "half tucks" flats for a nice effect. They also start closer, clipping half the leger line if needed. 'Spose that's too much to ask of NoteWorthy.
3363
General Discussion / Re: Accidental positioning anomaly in 1y
Thanks for the thoughtful reply. A jazz standard is an oxymoron isn't it? I wish I could find some standards. University of Colorado and LilyPond try, but are woefully incomplete.

My normal reference is G. Schirmers' 54 Piano Pieces from the modern repertoire, which has some of the hardest to reproduce bits imaginable.

This is like the Scotch snap problem. Easy to workaround, but hard to spot ...
Until you screw up in front of 100 people ...

Yeah, I know, I should catch these things in practice.  But when I've finished notating a piece, I've spent so much time with it that I know how to play most of it, but 6 months later when I pull it out to do a request, the errors hit me.
3364
General Discussion / Re: Cadenzas - How to get small notes?
David, Why would anyone want to use grace notes for playback?
IMO, enhancing playback is not its forte.

80% of the time I have a grace note in a finished work it is muted.

Exceptions that come to mind are:
A one staff only cadenza where I am modifing the tempo. (See Scriabin's Poem that I put in the newsgroup).

These uses (all hidden);
Simulating trills, tremolos, and staccatissimo.
Suppressing accidentals and articulations.

Grace notes make possible a number of very nice visual effects.

Note: tremolos and trills need to be added to the spell checker.
3365
General Discussion / Accidental positioning anomaly in 1y
NoteWorthy is usually very good at this, but ...

My source, Warner Bros. Publications Inc. uses the positioning in the second note and I agree with them.
Layer these 2 staves:

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
# Layer with next staff
|Chord|Dur:4th|Pos:b-4,n-2,0,b3
|Chord|Dur:4th|Pos:-4,n-2,0,3|Opts:XAccSpace=1
!NoteWorthyComposerClip-End
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Rest|Dur:4th|Visibility:Never
|Chord|Dur:4th|Pos:b-4z,0z,b3z|Opts:StemLength=0,NoLegerLines,Muted
!NoteWorthyComposerClip-End
3366
General Discussion / Re: Saving as MIDI by using File/Export
Sue, I cannot reproduce your problem on my Win98SE box.
Perhaps you should enable "show file extensions" in Explorer and report back the extension that is being used.

Even if I "force" an "nwc" extension, I get a  prompt giving me the name (with extension) asking me if I want to overwrite it.
3367
General Discussion / Re: Bug with ties
Try hitting {F9} after you set the tie.

BTW, if you paste this, the editor corrects itself immediately:

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Chord|Dur:4th|Pos:-5^,1^
|Bar|Style:Double
|TimeSig|Signature:2/4
|Chord|Dur:4th|Pos:-5,1
!NoteWorthyComposerClip-End

Edit: This has been fixed for a long time.
3368
General Discussion / Re: Cadenzas - How to get small notes?
Using grace notes as cue notes sounds simple enough for a User Tool.

The problem is that you cannot align a grace note directly over a normal note. Unless this is changed, grace notes as cue notes will never have a general workaround. Sometimes they will work, but mostly they will not.
3369
General Discussion / Re: Scotch snap workaround
Another example, from https://forum.noteworthycomposer.com/?topic=5366. To fix it, hide the notes with the offending flags and layer with:

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Bar|Style:Double
|Key|Signature:C|Visibility:Never
|TimeSig|Signature:2/4
|Chord|Dur:8th,Dotted,Accent|Pos:-3,b0,2|Opts:Stem=Down,Beam=First,Muted|Visibility:Never
|Note|Dur:16th,Slur|Pos:2|Opts:Stem=Down,Beam,Muted
|Note|Dur:8th|Pos:4|Opts:Stem=Down,Beam,Muted
|Rest|Dur:16th
|Note|Dur:16th,Slur|Pos:4|Opts:Stem=Down,Beam=End,Muted
|Bar
|Note|Dur:8th|Pos:b7|Opts:Stem=Down,Beam=First,Muted
|Rest|Dur:16th
|Note|Dur:16th,Slur|Pos:7|Opts:Stem=Down,Beam=End,Muted
|Note|Dur:8th|Pos:4|Opts:Stem=Down,Muted|Visibility:Never
|Rest|Dur:8th
|Bar
|Note|Dur:8th,Dotted|Pos:2|Opts:Stem=Down,Beam=First,Muted
|Note|Dur:16th,Slur|Pos:2|Opts:Stem=Down,Beam,Muted
|Note|Dur:8th|Pos:4|Opts:Stem=Down,Beam,Muted
|Rest|Dur:16th
|Note|Dur:16th,Slur|Pos:4|Opts:Stem=Down,Beam=End,Muted
|Bar
|Note|Dur:8th|Pos:n7|Opts:Stem=Down,Beam=First,Muted
|Rest|Dur:16th
|Note|Dur:16th,Slur|Pos:7|Opts:Stem=Down,Beam=End,Muted
|Note|Dur:8th|Pos:4|Opts:Stem=Down,Muted|Visibility:Never
|Rest|Dur:8th
!NoteWorthyComposerClip-End
Finding these things seems a worse problem than fixing them.
3370
General Discussion / Re: Scotch snap workaround
Peter Edwards gives another example in https://forum.noteworthycomposer.com/?topic=5251.msg34618#msg34618.

Easy workaround with a layer, but the larger issue is how much incorrect music is sitting in musicians' folders? (and how often has a note been played at the wrong time?)

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam=First
|Rest|Dur:16th|Opts:VertOffset=2
|Note|Dur:16th|Pos:1|Opts:Stem=Down,Beam,Muted|Visibility:Never
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam,Muted|Visibility:Never
|Rest|Dur:16th|Opts:VertOffset=2|Visibility:Never
|Note|Dur:16th|Pos:1|Opts:Stem=Down,Beam=End,Muted|Visibility:Never
!NoteWorthyComposerClip-End
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Note|Dur:8th,Dotted|Pos:1|Opts:Stem=Down,Beam=First,Muted|Visibility:Never
|Note|Dur:16th|Pos:1|Opts:Stem=Down,Beam
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam
|Rest|Dur:16th|Opts:VertOffset=2
|Note|Dur:16th|Pos:1|Opts:Stem=Down,Beam=End
!NoteWorthyComposerClip-End
3372
General Discussion / Re: Scotch snap workaround
But not so accurate as this:
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Clef|Type:Treble
|Note|Dur:16th|Pos:0|Opts:Stem=Down,Beam=First
|Note|Dur:8th,Dotted|Pos:0|Opts:Stem=Down,Beam
|Note|Dur:4th,Grace|Pos:0^|Visibility:Never
|Note|Dur:16th|Pos:0|Opts:Stem=Down,Beam
|Note|Dur:8th,Dotted|Pos:0|Opts:Stem=Down,Beam=End
!NoteWorthyComposerClip-End
3373
General Discussion / Re: Hidden note display anomaly in Preview 1x
You need to try a PostScript printer.
I'm using "Apple Color LW 12/660 PS" but most any will do.
It's got this little box called Scaling, usually set to 100%.
Works just like a copier. Setting it to 67% gets a lot more on a page.
Getting NWC2 to display it is the easy part.

Getting it to a file or printer is tougher. I use GhostScript and Redmon, both free from Univ of Wisconsin.
~10mb download. Took about a day to figure out how to configure it.
As a bonus, you get 2up & 4up. Great for making study scores.

Eventually, you'll want to be able to roll your own paper size and resolution.
Plan another day to learn how to modify spd files.

Currently, I'm sending NWC2 output to a 1" x 2" 16color bmpfile @ 4096dpi. Filesize: 16mb

David, I can hear you already: "Why on earth would anyone want to do that?"
3374
General Discussion / Re: sheet music
Treble Clef, 2 flats, (4/4 implied)
Bar 17 Master Repeat Open: Chord Bb
d 8th beamed to d 8th tied to d half, 8th rest b 8th

Bar 18: Chord Gm
c 8th beamed to d 8th, d half, 8th rest, c 16th beamed to d 16th

Bar 19: Chord Cm
4 8th notes beamed: efed, c quarter, c 8th beamed to d 8th

Bar 20: Chord F (at beat 3)
4 8th notes beamed: efed, c quarter, quarter rest.

This gets you through:
Ma-ma__    just
killed a man,  Put a
gun a-gainst his head, pulled my
trig-ger, now he's dead.
3375
General Discussion / Scotch snap workaround
Workaround for the problem discussed in https://forum.noteworthycomposer.com/?topic=5251
Measure 1 shows the problem, 2 the solution, 3 for dbl time.
Keep the invisible rests well away from the beams as they affect beam length.

Layer these 2 staves:
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Note|Dur:8th,Dotted|Pos:1|Opts:Stem=Down,Beam=First
|Note|Dur:16th|Pos:0|Opts:Stem=Down,Beam
|Note|Dur:8th,Dotted|Pos:1|Opts:Stem=Down,Beam
|Note|Dur:16th|Pos:0|Opts:Stem=Down,Beam=End
|Note|Dur:16th|Pos:0|Opts:Stem=Down,Beam=First
|Note|Dur:8th,Dotted|Pos:1|Opts:Stem=Down,Beam,Muted
|Note|Dur:16th|Pos:0|Opts:Stem=Down,Beam
|Note|Dur:8th,Dotted|Pos:1|Opts:Stem=Down,Beam=End
|Bar
|Note|Dur:8th,Dotted|Pos:1|Opts:Stem=Down,Beam=First
|Note|Dur:16th|Pos:0|Opts:Stem=Down,Beam
|Note|Dur:8th,Dotted|Pos:1|Opts:Stem=Down,Beam
|Note|Dur:16th|Pos:0|Opts:Stem=Down,Beam=End
|Note|Dur:16th|Pos:0|Opts:Stem=Down,Beam=First
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam,Muted
|Rest|Dur:16th|Opts:VertOffset=4|Visibility:Never
|Note|Dur:16th|Pos:0|Opts:Stem=Down,Beam
|Note|Dur:8th,Dotted|Pos:1|Opts:Stem=Down,Beam=End
|Bar
|Note|Dur:16th,Dotted|Pos:1|Opts:Stem=Down,Beam=First
|Note|Dur:32nd|Pos:0|Opts:Stem=Down,Beam
|Note|Dur:16th,Dotted|Pos:1|Opts:Stem=Down,Beam
|Note|Dur:32nd|Pos:0|Opts:Stem=Down,Beam=End
|Note|Dur:32nd|Pos:0|Opts:Stem=Down,Beam=First
|Note|Dur:16th|Pos:1|Opts:Stem=Down,Beam,Muted
|Rest|Dur:32nd|Opts:VertOffset=4|Visibility:Never
|Note|Dur:32nd|Pos:0|Opts:Stem=Down,Beam
|Note|Dur:16th,Dotted|Pos:1|Opts:Stem=Down,Beam=End
|Rest|Dur:Half
|Bar
!NoteWorthyComposerClip-End
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Rest|Dur:Whole|Opts:VertOffset=4|Visibility:Never
|Bar
|Rest|Dur:Half|Opts:VertOffset=4|Visibility:Never
|Rest|Dur:16th|Opts:VertOffset=4|Visibility:Never
|Note|Dur:8th,Dotted|Pos:1|Opts:Stem=Down,StemLength=0
|Rest|Dur:4th|Opts:VertOffset=4|Visibility:Never
|Bar
|Rest|Dur:4th|Opts:VertOffset=4|Visibility:Never
|Rest|Dur:32nd|Opts:VertOffset=4|Visibility:Never
|Note|Dur:16th,Dotted|Pos:1|Opts:Stem=Down,StemLength=0
|Rest|Dur:8th|Opts:VertOffset=4|Visibility:Never
|Rest|Dur:Half
|Bar
!NoteWorthyComposerClip-End
3376
General Discussion / Re: direction of beams (not stems)
And it probably took several hours to find out just how hard it was to change.

I'll look in to a "workaround" for this. Look For "Scotch Snap" in the NWC2 Forum. (where I can post clips)
3377
General Discussion / Re: Overlapping chords with runs
Peter:
I stand corrected. Why chord entry should care about whether the stem direction is set (and "audit note stems" is so blithely ignorant about it) is still a great mystery.

Chord entry is one of the least user friendly aspects of this program. In NWC2, often I use a User Tool to send it to NotePad and edit chords by hand.
3379
General Discussion / Re: Overlapping chords with runs
NW 1.75b:
If the same duration, you can always add another note with ctrl-enter.

If the note to be added is a different duration:
If higher (on the staff), the stem must be down on the existing note.
If lower, stem must be up upon the existing note.
If the staff positions are equal, the shorter note is considered to be the lower note (regardless of accidentals).

Whole notes have "implicit stems" (which matter)

In NWC2, stem direction does not matter, if it is NOT SET.
(unlike 1.75b, it is tristate). If set, the above rules apply.

In both versions:
To create a rest chord, the rest MUST be entered first.
IOW, ctrl-spacebar does nothing!

In 1.75b, the rest MUST be shorter than the note
In NWC2, the rest must not be longer.

Why any of this matters is a great mystery.

HTH,
Rick G.
3380
General Discussion / Re: sheet music
I have it in "Queen Deluxe Anthology" pg 94-102.
I won't send the whole thing, but if you let me know what you need for your arm, I'll look it up.
3381
General Discussion / Re: Double-barreled notes
Using Staff Bold as a poor stand in for boxmarks:

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Clef|Type:Treble
|TimeSig|Signature:4/2
|Note|Dur:4th,Grace|Pos:-8^|Visibility:Never
|Text|Text:"\|o\|"|Font:StaffBold|Pos:-8|Justify:Center|Placement:AtNextNote
|Note|Dur:Whole|Pos:-9z|Opts:Muted
|Note|Dur:Whole|Pos:-8|Visibility:Never
!NoteWorthyComposerClip-End
3382
General Discussion / Re: RestChord alignment problem
Well Peter, I guess I'm with Eric on this one. I have yet to find a chord accurately notated in commercial music that I could not reproduce with layering. Here's a real beauty (layer the staves):

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Clef|Type:Bass
|TimeSig|Signature:6/8|Visibility:Never
|Note|Dur:8th|Pos:14x|Opts:Stem=Up,StemLength=1,Beam=First,NoLegerLines,Muted|Visibility:Never
|Note|Dur:16th|Pos:#6|Opts:Stem=Up,StemLength=7,Beam
|Note|Dur:16th|Pos:3|Opts:Stem=Up,Beam
|Note|Dur:8th,Slur|Pos:#-1|Opts:Stem=Up,StemLength=11,Beam=End,XNoteSpace=1
|Note|Dur:8th|Pos:0|Opts:Stem=Up,Slur=Upward,StemLength=11,Beam=First,XNoteSpace=1,Muted
|Note|Dur:8th|Pos:b4|Opts:Stem=Up,Beam
|Note|Dur:8th|Pos:b7|Opts:Stem=Up,Beam=End
|Bar
!NoteWorthyComposerClip-End
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Clef|Type:Bass
|TimeSig|Signature:6/8|Visibility:Never
|Chord|Dur:8th,Staccato|Pos:b1,3|Opts:Stem=Down,StemLength=10,Beam=First,ArticulationsOnStem
|Chord|Dur:8th,Staccato|Pos:-4,1|Opts:Stem=Down,Beam,ArticulationsOnStem
|Chord|Dur:8th,Staccato|Pos:1,3|Opts:Stem=Down,StemLength=10,Beam=End,ArticulationsOnStem
|Text|Text:" "|Font:StaffBold|Pos:8|Wide:Y|Justify:Center
|Chord|Dur:8th,Staccato|Pos:b0z,b2,b4|Opts:Stem=Down,StemLength=9,Beam=First,ArticulationsOnStem
|Chord|Dur:8th,Staccato|Pos:b-3,2|Opts:Stem=Down,Beam,ArticulationsOnStem
|Chord|Dur:8th,Staccato|Pos:2,4|Opts:Stem=Down,StemLength=11,Beam=End,ArticulationsOnStem
|Bar
!NoteWorthyComposerClip-End
The muted XNote receives a Dnat from the right hand.
3383
General Discussion / Re: Section Close - Section Open Printing Problem
You're right,  my method trashes numbering.  I would not have suggested it if I had known you needed measure numbers.

With an Orchestral staff, the section opens are ugly wherever they are placed. I should think that the (re)introduction of the TimeSig (without warning at the end of the previous line, which ends with a Section close), should be a fairly strong signal that this is a new section.

You can also indent the previous line from the right margin. The technique uses "digital white-out" which can't easily be shown in a clip.  If you ask in the beta newsgroup, I can post an example.

Sorry I couldn't help more. Control over measure numbering is a long running request that I am tired of rehashing.
3384
General Discussion / Re: RestChord alignment problem
Yes. Certain chord/layer combos need the rest to stay put.
It might be a useful option to have the rest follow the head, but I have yet to find a combo I can't get right without it.

I've found that just about every time I use extra note or accidental  spacing for anything other than the purpose intended, I end up taking it out in the final edit.
3385
General Discussion / RestChord alignment problem
I may be missing something, but shouldn't the second chord align in these 2 clips when layered?

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|RestChord|Dur:8th|Opts:Stem=Up|Dur2:8th|Pos2:-3,-1,1
|RestChord|Dur:8th|Opts:Stem=Up|Dur2:8th|Pos2:#-3,-2,1
|RestChord|Dur:16th|Opts:Stem=Up|Dur2:16th|Pos2:#-6,-3
!NoteWorthyComposerClip-End
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Chord|Dur:8th|Pos:-3,-1,1|Opts:Stem=Down
|Chord|Dur:8th|Pos:#-3,-2,1|Opts:Stem=Down
|Chord|Dur:16th|Pos:#-6,-3|Opts:Stem=Down
!NoteWorthyComposerClip-End
I don't need a fix, just pointing out a possible problem.
Edit: this has been fixed (possible some time ago). The chords now align properly.
3387
General Discussion / Re: Bug: Grace Note Spacing in Preview 1x
I guess I wasn't clear in my intent. I was just reporting a bug on the chance that the coding error might manifest itself elsewhere. I think that's what beta testing is.

It appears to me as though grace notes are skipping some of the setup that other objects do.

I fixed the music I was working on before I posted. It's a 20th century piece that is a printer's nightmare. I'm just using it as a "testbed" to explore NWC2's limits.

Sorry for the confusion.
3388
General Discussion / Re: Bug: Grace Note Spacing in Preview 1x
David: the problem is in Preview (and in printing). Your clip just obscures the problem by forcing a system break. If I don't increase space for longer notes, and print my clips to a file (at 16pt, 300dpi), measure 2 is 125 pixels wide, the others are around 87.

Correction to my original post: making the bar line visible doesn't help. Make the rest visible or add some visible text to see measure 2 shrink.
3390
General Discussion / Bug: Grace Note Spacing in Preview 1x
Put these clips on separate staves. You will notice that measure 2 is wider than the rest. If you layer them, it is apparent that more space preceedes the first note than the second.  If you make the first rest or bar (in the second staff) visible, the problem goes away.  Clefs, KeySigs or TimeSigs seems to have no effect, but outside of these, if a Grace Note is the first visible item on a staff, it gets misaligned.

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Rest|Dur:Whole
|Bar
|Rest|Dur:Whole
|Bar
|Rest|Dur:Whole
|Bar
|Rest|Dur:Whole
|Bar
|Rest|Dur:Whole
!NoteWorthyComposerClip-End
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Rest|Dur:Whole|Visibility:Never
|Bar|Visibility:Never
|Note|Dur:8th,Grace|Pos:-3|Opts:Muted
|Rest|Dur:Whole|Visibility:Never
|Bar|Visibility:Never
|Note|Dur:8th,Grace|Pos:-3|Opts:Muted
|Rest|Dur:Whole|Visibility:Never
|Bar
|Rest|Dur:Whole
|Bar
|Rest|Dur:Whole
!NoteWorthyComposerClip-End
3391
General Discussion / Re: Hidden note display anomaly in Preview 1x
Pär: Not confusing to me. NWC2 calls it a blank space notehead, not an invisible notehead

You might also notice that a "C" key signature takes up space unless you set it to Visibility:Never

I have since found a number of things that display differently in the Editor than in the Preview. IMHO, the clips I posted above display correctly in the Preview window (and when printed)
3392
General Discussion / Re: Bug report - highlighting in Edit window and beyond.
Sounds like a sticky ctrl key. Tap it a few times or try to pull it up with a finger.

You also get this problem if you are running any apps that send keys to another app. If it sends ctrl+<something> as its last key, sometimes you get stuck with the legacy. This happens regularly with VBScript's SendKeys. I make it a habit to send {Esc} somewhere harmless as part of onexit.
3395
General Discussion / Re: What NWC 2 SHOULD HAVE!
The case against forced barlines is:
Sometimes, we just want to quickly bang in a bunch of notes, hit {F5} and hear what it sounds like.  Most of us are not drummers. The meter is not the most important thing in our lives.

Audit Bar Lines is a good way to ruin an hour's work. (just kidding, well, mostly)

If you are willing to learn how to do some advanced layering, you should never need to put a text accidental in.

The newsgroup is the best place to learn.
3396
General Discussion / Re: What NWC 2 SHOULD HAVE!
Please, no forced barlines! Learn to count.

In NWC2:
Octave shifts can be done using an instrument patch.
8va is transpose +8, 8vb is -8
15va is either 15 or 16 (if I ever needed it, I'd know which).
Uncheck &Send Patch. When done, another ipatch with transpose=0 gets you back to loco.  Really simple.

If you cand tolerate 8va instead of 8va (which I can't - grr...), you can even use it for the instrument name (after you uncheck Preserve Width (another grr...)
3397
General Discussion / Re: Un-Install
In my never-ending search for good freeware, I have had to uninstall several hundred apps.

I have found that if a program fails to uninstall (usually due to changes you have made after you installed it, or your failure to accept the defaults that they know you will really want), the best thing to do is reinstall the program (accepting all the defaults), then uninstall it.  This usually cleans up the registry.

Software designers usually spend a lot more time insuring that their program will install over an existing version than they spend on removal.
3398
General Discussion / Re: 2/4 against 6/8
Do it all in 6/8, using dotted quarter for quarter, dotted eighth for eighth etc. this will get it to play (and align) properly.

If it has to look right too, copy what you have done to another staff group.
Then, in the "2/4" sections:

Put a visible 2/4 followed by a hidden 6/8.
Replace each of dotted notes with an visible note and hidden rest.  Replace each of dotted rests with an visible rest and hidden rest. Think of it this way, you have to hide 1/3 of it. trick is to hide the right third.
3399
General Discussion / Re: Hidden note display anomaly in Preview 1x
Layer these two clips. The 2nd pair of eighth notes is the problem. The third pair is the workaround, but there is too much space between the note heads.

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Note|Dur:8th|Pos:9|Opts:Stem=Down,Beam=First
|Note|Dur:8th|Pos:6|Opts:Stem=Down,Beam=End,NoLegerLines,Muted|Visibility:Never
|Note|Dur:8th|Pos:6|Opts:Stem=Down,Beam=First,XNoteSpace=1,NoLegerLines,Muted|Visibility:Never
|Note|Dur:8th|Pos:9|Opts:Stem=Down,Beam=End
|Note|Dur:8th|Pos:6z|Opts:Stem=Down,StemLength=0,Beam=First,XNoteSpace=1,NoLegerLines,Muted
|Note|Dur:8th|Pos:9|Opts:Stem=Down,Beam=End
!NoteWorthyComposerClip-End
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Note|Dur:8th|Pos:-6|Opts:Stem=Up,Beam=First,XAccSpace=1,NoLegerLines,Muted|Visibility:Never
|Note|Dur:8th|Pos:-9|Opts:Stem=Up,Beam=End
|Note|Dur:8th|Pos:-9|Opts:Stem=Up,Beam=First
|Note|Dur:8th|Pos:-6|Opts:Stem=Up,Beam=End,XAccSpace=1,NoLegerLines,Muted|Visibility:Never
|Note|Dur:8th|Pos:-9|Opts:Stem=Up,Beam=First
|Note|Dur:8th|Pos:-6|Opts:Stem=Up,Beam=End,XAccSpace=1,NoLegerLines,Muted|Visibility:Never
!NoteWorthyComposerClip-End