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 - Peter Edwards

351
General Discussion / Re: third verse doesn't play but first two will
If you just want to repeat a piece of music three times then the simplest way is to make the ending bar (In [Staff Properties]/[General]) a [Master Repeat Close] and insert an invisible [Special Ending], with 1 and 2 checked, immediately before the final bar line.
352
General Discussion / Re: double f sharp
You use Fx in G# minor (instead of a G nat) for the same reason that you use B# in C# minor (instead of a C nat).

That way the written interval of a second is preserved. otherwise the interval would appear to be an augmented unison
354
General Discussion / Re: Rests in Chords - a fix discovered!
That's why the rest needs to be hidden. Then the bar looks as it should. It already plays and lines up properly.

The only function of the rest is to shorten the chord so that the next note position falls after a quaver rather than a crotchet, thus fixing the original problem as shown in the first bar.
355
General Discussion / Re: Rests in Chords - a fix discovered!
Your third bar - even if the rest is invisible - has an extra quaver!

No it doesn't. It plays like a 2/4 bar, lines up like a 2/4 bar, and, if you hide the rest, looks like a 2/4 bar. What more could you ask?

Layering is the answer to multi-part writing on one staff, but not to the occasional syncopation. I can quite understand NoteWorthy's reluctance to implement multi-parts on on staff, and what has been implemented is at least understandable. A multi-duration chord acts exactly (for timing/positioning purposes) as its shortest component would on its own, then everything starts again. That would work for any number of durations in a chord.

That in its turn would imply the need for invisible multi-rest 'chords', but that's another story!
356
General Discussion / Re: Rests in Chords - a fix discovered!
Neither request is new  - in fact both are positively ancient.

The invisible rest is needed to fix problem illustrated here:

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Clef|Type:Treble
|Chord|Dur:4th|Pos:1|Opts:Stem=Down|Dur2:4th,Dotted|Pos2:3
|Note|Dur:4th|Pos:1
|Note|Dur:8th|Pos:3|Opts:Stem=Up
|Bar
|Chord|Dur:4th|Pos:1|Opts:Stem=Down|Dur2:4th|Pos2:3^
|Chord|Dur:8th|Pos:3|Opts:Stem=Up|Dur2:4th|Pos2:1
|Note|Dur:8th|Pos:3|Opts:Stem=Up
|Bar
|Chord|Dur:4th|Pos:1|Opts:Stem=Down|Dur2:4th,Dotted|Pos2:3
|RestChord|Dur:8th|Opts:Stem=Up,ArticulationsOnStem,VertOffset=7|Dur2:4th|Pos2:1
|Note|Dur:8th|Pos:3|Opts:Stem=Up
!NoteWorthyComposerClip-End
The first bar is a quaver too long.

The second shows a fix, but it is notationally confusing and not standard.

The third bar shows a potential fix, but only if you can make the rest invisible.

To be fair NoteWorthy fixed it by introducing layering, but that brings its own problems and shortcomings (previously discussed at length in many places).
357
General Discussion / Re: slur technicals
Sorry to disagree, Robin, but technically a learning curve shows how much you have learned plotted against time. Eventually the curve gets to 100% when you have learned everything. So a steep learning curve means that you are learning rapidly. A shallow curve implies that you are learning slowly and taking longer to reach total knowledge. The curve itself has no information about the amount to be learned.

Strictly therefore we should talk about a long learning curve.

It's the same with Lowest Common Denominator being used to denote something so basic that everyone can understand it, when Highest Common Factor is really the expression which should be used.

To answer my own question, the technical terms have words in them that imply the opposite of the actual meaning. So steep implies difficult, and lowest implies basic. But the expressions actually mean precisely the opposite.
359
General Discussion / Re: slur technicals
How has the expression steep learning curve come to mean exactly the opposite of what it represents? Steepness actually indicates that the learning is rapid (and therefore easy!)
360
General Discussion / Re: FEATURE: Under the hood....
128th notes? Not on my machine. Four flags is the max.

To get a rolled chord try the following:

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Clef|Type:Treble
|Note|Dur:8th,Grace|Pos:-3^|Opts:Stem=Up,Beam=First|Visibility:Never
|Note|Dur:8th,Grace|Pos:-1^|Opts:Stem=Up,Beam|Visibility:Never
|Note|Dur:8th,Grace|Pos:1^|Opts:Stem=Up,Beam=End|Visibility:Never
|Chord|Dur:Half|Pos:-3,-1,1,4
|Note|Dur:8th,Grace|Pos:-3^|Opts:Stem=Up,Beam=First|Visibility:Never
|Note|Dur:8th,Grace|Pos:-3^|Opts:Stem=Up,Beam|Visibility:Never
|Note|Dur:8th,Grace|Pos:-1^|Opts:Stem=Up,Beam|Visibility:Never
|Note|Dur:8th,Grace|Pos:-1^|Opts:Stem=Up,Beam|Visibility:Never
|Note|Dur:8th,Grace|Pos:1^|Opts:Stem=Up,Beam|Visibility:Never
|Note|Dur:8th,Grace|Pos:1^|Opts:Stem=Up,Beam=End|Visibility:Never
|Chord|Dur:Half|Pos:-3,-1,1,4
!NoteWorthyComposerClip-End
A grace note is always a 1/32 in playing duration, whatever its notated length :-(

You can double it by tying, as in the second example.
362
General Discussion / Re: Big bottom margin --Why?
You can't change it. There was a problem with copyright notices being chopped off; which was fixed – and, boy!, how it was fixed!

Now the first page is a mess and there just doesn't seem to be any willpower being applied to sorting it out.
363
General Discussion / Re: NWC files not found by browser
The Viewer certainly has the capability of printing (although you can't tweak margins etc) but there is a curious difference compared to the output of NWC itself. The bar numbers in NWC are placed at the beginning of each system: in NWV they are every 5 bars. Curious.
365
General Discussion / Re: Possible bug report - hanging tie from accidental?
Amused - OK

not concerned - for a notation/sequencer program to have an obvious (I'll go for authoritative reference over unsubstantiated opinion every time) fault is a matter for concern.

David, your music teachers are talking nonsense, and you know it. Augmented octaves happen surprisingly frequently, and as mentioned above Schubert actually employs an augmented unison on occasion!
366
General Discussion / Re: Possible bug report - hanging tie from accidental?
A natural sign inside a key signature actually changes the key, so yes it does affect all octaves. A natural on a note would only affect subsequent notes at that particular octave.

The treatment of tied notes is interesting. NWC insists that the incorrect notation is necessary (although it prints it correctly). The notationally correct notation of course is incorrect inside NWC and results in hanging notes!

Tied notes over a bar-line does should not have an accidental, but the first subsequent free note at that pitch does need its own specific accidental.
367
General Discussion / Re: Possible bug report - hanging tie from accidental?
There's no difference between countries. Alfred (US) and ABRSM (UK) (AB Guide to Music Theory) are explicit that the accidental only applies to the staff position on which it lies, and I've never seen any exceptions in published continental music.

NW's explanations are not helpful because they are trying to explain incorrect behaviour.

If you want an example which is ludicrously wrong then look at this:
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Clef|Type:Treble
|Chord|Dur:4th|Pos:n-6,#1
|Note|Dur:4th|Pos:-6
!NoteWorthyComposerClip-End
368
General Discussion / Re: tying chords
Audibly, it stops when it hits an identical note/element.

Not quite! It stops when a MIDI note event happens at the same pitch (MIDI Note number) on the same channel.

So a Db can cancel a C#. And that could be on a separate staff assigned to the same channel.
369
General Discussion / Re: Possible bug report - hanging tie from accidental?
For this behaviour to be correct you would have to insert a natural sign to indicate that there are two different pitches.

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Clef|Type:Treble
|Chord|Dur:Half|Pos:#1|Opts:Stem=Down|Dur2:Half|Pos2:n1
|Chord|Dur:Half|Pos:n1|Opts:Stem=Down|Dur2:Half|Pos2:#1
!NoteWorthyComposerClip-End
As notated without the natural sign the playback is simply incorrect.

(BTW if the notational behaviour is what you'd expect then toggling the sharp key (9) on the chord ought to toggle each note independently, but in fact it makes them both natural.)

For an invaluable reference do get a copy of Alfred's Essential Dictionary of Music Notation ($9.95) which includes a comprehensive discussion of the application of accidentals. although interestingly it is silent on the correct treatment of the minor second chord we are discussing. In a Schubert piece ABRSM prints it as separated notes each with its own accidental. Certainly the second chord in my example could be construed as an old fashioned cancelled double sharp.
370
General Discussion / Re: Possible bug report - hanging tie from accidental?
Note accidentals apply in all octaves within the bar.

But not, apparently, when it's supposed to be the same note.

Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Clef|Type:Treble
|TimeSig|Signature:4/4
|Chord|Dur:Half|Pos:1|Opts:Stem=Down|Dur2:Half|Pos2:#1
!NoteWorthyComposerClip-End
I would expect that a note added to a chord should pick up any accidentals already there.

I'm sorry to harp on about a notator that does not play back correctly what is written correctly: it has to be a definite minus point. And I'd have thought that a major revision such as NWC2 would have sorted this out.

Let's just hope that at present means just that, and that the near future holds something better
371
General Discussion / Re: feature request: live scrolling
I assume you meant horizontal scrolling.

I'm not sure how you would use vertical scrolling to alter playback position! ;-)

It is after all quite trivial to click once with the mouse button

I was talking about the viewer. You can click it as much as you want, you won't achieve anything.
373
General Discussion / Re: Possible bug report - hanging tie from accidental?
The behaviour is absolutely incorrect. Accidentals affect only notes at the same pitch. This is another glaring and oft commented on fault which should have been corrected a long time ago.

Why can't NWC do accidentals properly? ;-)

The easiest work round is to tie an invisible grace note with the right accidental to the offending note. Or, indeed as suggested, to insert a courtesy accidental.

Although all the variations of staff are permissible, I would suggest that the plural is almost always staves. There's not much to choose between the singular versions but staff is my preference.
374
General Discussion / Re: tying chords
An outgoing tie won't stop going out until it hits an identical note/element.

Just a small correction to that, and to belabour a glaring and oft commented on fault in NWC,

until it hits a note at the same staff position.
375
General Discussion / Re: feature request: individual note attributes
Sorry, Rob and Geoff, but User 111 has already improved beyond measure and your remarks are not helpful. David's on the other hand struck the right responsive note.

For better or worse, we are what we are on the forum. Geoff, would you really tell (say) a French speaker whose grasp of English is not perfect to go to a translation agency?

I must admit that there are indeed times when I say "Why can't NWC do ...?" and feel quite frustrated that a simple feature is still missing.

Why can't NWC do 8va?
378
General Discussion / Re: feature request: individual note attributes
Nevertheless this is a perfectly valid request, and one which I have made several times in the past. And personally I believe that it is right and valid to air our requirements in the forums and news groups where they can be discussed and improved on.
379
General Discussion / Re: feature request: empty and duplicate staff names
The staff names for various reasons ought be different, but there is no reason why the displayed names should not be the same, just put them in the Staff Label field.

There was a work round before staff labels were invented - pad the names with hard spaces; but that is no longer necessary.
382
General Discussion / Re: Subtitles
Well that's right, but in this instance I suggest that it is used to pad the front or the back of the title to get it exactly centered once you have positioned it as near as you can get using other NWC constructs.
383
General Discussion / Re: Subtitles
Select the most central bar on the top staff of the top system and insert a text item in a suitable (user) font positioned quite a bit above the staff. Subtle positioning, justification and padding with alt+0160 will achieve the effect you want.
385
General Discussion / Re: Automatic insertion of bar lines..?
RICHARD DOUGLAS FOSBURY (b. March 6, 1947, Portland, Ore., U.S.), American high jumper who revolutionized the sport by replacing the traditional approach to jumping with an innovative backward style that became known as the "Fosbury flop."
386
General Discussion / Re: Multiple measures of rest
David

Suppressible works on a full score on a system by system basis. The stave is only suppressed when the instrument is silent. Look at an orchestral score where the number of staves varies continually system by system depending on which instruments are playing.
387
General Discussion / Re: Multiple measures of rest
They're not! That's the point, we are trying to devise a way of implementing suppression of staves and grouping of silent bars into multi-bar rests without the hassle of doing it intelligently. At the moment neither is possible although the multi-bar rest is fudgeable with Boxmarks.

So to restate my reply #7, as modified by #11. A bar-line should have two extra properties. Suppressible and Collapsible.

If all the bar-lines on a stave on any particular system are suppressible then the stave should be suppressed regardless of what notes etc are actually on it.

If a bar-line is collapsible then the subsequent bar(s) can be amalgamated with the previous bar and a multi-bar rest inserted. Again regardless of what is actually in the bars - that is up to the user to sort out.

The two attributes are used in different circumstances. The collapsible is where you are printing out a subset of the full score. Suppressible where you don't want all the instruments all the time in the full score. Although, to be fair, there is considerable potential for overlap.

The difference is that bar-lines with rehearsal marks and bars with tempo changes and pauses still need to be printed out in a single part, but should be suppressed when there are other staves already visible.

So not difficult to implement but, with care, fully effective.
390
General Discussion / Re: Muting a staff
One way to achieve what you want is to 'absorb' the 1st or 2nd time repeats into a single local repeat bar.

So for the first verse: switch the special endings (the real first time bar will never actually happen) and then turn the real second time bar into a local repeat bar with a repeat count of 28 (the skipped first time bar plus 27 bars of the tune). You should hide the local repeat bar lines. So this verse plays and then seems to stand still as the second verse plays.

For the second verse: construct the first bar in the same way as the last bar in the first verse. Again swap the special endings. This verse will seem to stand still for the first verse and then miraculously spring into life.

To get the page to look right you'll need to layer a conductor track as the top staff with the special endings the right way round!
391
General Discussion / Re: Number shortcuts to toggle accidentals
I hadn't actually ever used the number keys for note lengths (relying on + and - instead) so hadn't noticed that the shortest note (1/64th) can't be selected by that method. I'd also assumed that breves (double whole notes)  had not been implemented (in part at least) because there was no number key for them. But that's obviously not the reason - so roll on breves!
392
General Discussion / Re: Cnage from Treble to Bass staff
The question was clarified in https://forum.noteworthycomposer.com/?topic=4544.msg28413#msg28413 where Tony explicitly states that he is talking about an octave shifted treble clef.

In general Tenors sing from the treble clef (unless sharing a staff with the basses) but the notes sound an octave down. You will often see a little 8 appended to the bottom of the clef sign to signify this. Since the Tenor range is typically A below to A above the treble clef, using it is quite appropriate.
394
General Discussion / Re: Cnage from Treble to Bass staff
Before you give the answer you should always read the question! Tony and I are in unambiguous agreement that I answered the question he asked.

Now it is up to you to work out why it is not an octave too low.
397
General Discussion / Re: Record MIDI Keyboard
Try Tools/Options/Import/Maximum Single track Chord Size. If you set the number large enough you can accommodate even the biggest ones on one staff.
398
General Discussion / Re: Cnage from Treble to Bass staff
There's no need to transpose anything. Just change the clef to a bass clef, select all the notes, and then move them all up five staff positions with Shift/Control/Up Arrow.

Essentially you are moving a C written on the treble clef to a middle C above the bass clef etc.
399
General Discussion / Re: Transpose Staff dynamically
You can use a Pitch Bend MPC to achieve a small transposition dynamically, but you'll need to go to NWC2  and use an Instrument change (which includes transposition) for larger values.
400
General Discussion / Re: Mute Staff dynamically
The question refers to dynamic (on the fly) muting, which on a per staff basis is probably not achievable, but you can mute a channel using an Expression or Volume MPC, and then later restore the channel with another MPC.