Skip to main content ↑ ↓
Topic: Beam.hmm (0.91) (Read 23094 times) previous topic - next topic

Beam.hmm (0.91)

NWC is missing cross-staff beams, unison beams, more complex grouping (where some group have one running beam, others two), overhanging fractional beams, beam groups for speed variation, stemlets, single notes with beams, and double beams (double stem chords with beams on both sides). I thought this could be remedied by creating a versatile Beam object, which is attached to this posting.
In addition, there are ten example files, which mainly use examples from "Behind Bars":

  • "UnisonBeams" has three unison beam examples;
  • "CrossStaffBeams" has a percussion example and two piano examples; the last - an excerpt from a piece by Webern - is, I would say, quite interesting ...
  • "OppositeStemDirectionBeams" has some examples with stems in opposite directions (but the previous file also has some ...);
  • "ComplexGrouping" has a single example with different numbers of connecting beams - NWC cannot do this, but I doubt that this is really an important feature;
  • "FractionalBeams" shows an interesting way to indicate complex rhythms, which I have yet to see outside B.B.; and has single notes with beams.

The remaining examples are attached to the next posting.

The maximum span for a Beam object is 16 notes and rests. If a longer beam group is needed, two or more overlapping beam objects can be defined (see example in "ComplexGrouping.nwctxt").

Breaking beams at a line break does not work - you have to provide a separate Beam object for each line.

(If you possess "Behind Bars", I am interested in whether you see problems with my example scores; and if you have suggestions for interesting examples I could or should add).

H.M.

Re: Beam.test (0.91)

Reply #1 –
0.2 has an additional property to keep non-through-running beams together - the problem came up with an example on page 315 of B.B.
0.91 provides smaller beams for grace notes as well as CueHead notes.

Here are the six remaining example files:

  • "SpeedVariationBeams" shows a notation that would drive our church choir crazy. This notation requires that all notes are eighths, because otherwise each user object (there is one for each slanting beam) would draw a second, unwanted parallel bar; if one wanted to play this, the varying tempo would have to be created by a tempo track.
  • "Stemlets" shows a notation that connects rests to a beamed group. E.Gould writes: "This notation is helpful for passages of complex rhythms, especially where rests occupy the start or finish of a subdivision of a beat". One could also use it to mark special notes under a beam, as my last example shows.
  • "DoubleBeams" shows double beams on a single staff, which can e.g. help with quickly notating SATB scores on two staffs.
  • "Tuplets" shows how with tuplets, one can e.g. draw one single beam above somewhat lengthened sixteenth to create the impression of "short eighths".
  • "DoubleStemmedBeams" (since 0.7) shows overlapping beams, with additional non-beamed notes on double-stemmed chords.
  • "GraceBeams" (since 0.91) shows small to tiny beams with grace notes as well as CueHeads.

H.M.

Re: Beam.test (0.2)

Reply #2 –
Quite impressive. I have a very small suggestion: for your "spin" function (to alter the final stem length), you should use an increment/decrement of 0.5, to match the step value for the parameter on the properties window.

I look forward to experimenting with this new object.

Mike

Re: Beam.test (0.3)

Reply #3 –
0.3 has rounding at some crucial places, so that one can always (I hope) create horizontal beams; and, after the suggestion of Mike, the spinner now uses 0.5 increments. Also, I added another example file.

H.M.

Re: Beam.hmm (0.4)

Reply #4 –
I have now upgraded the Beam object from .test to .hmm. There are quite a few changes for this first "production ready" version:

  • Most important, the beam options for notes and rests under the beam have been changed from obscure symbols to (somewhat) understandable texts.
  • The selection of the number of beams for a beam group is now on the start note of the beam group , i.e. the note after the reduced number of beams (similar to NWC's "Beam group start" option) - this seems a little more intuitive than the previous attempt, where one specified the beam reduction on its left side.
  • The maximum span of a Beam object is now 16 notes and rests. If a longer beam group is needed, two or more overlapping beam objects can be defined (see extreme example in "ComplexGrouping.nwctxt").
  • A span of 1 is also supported; this can be used for single beamed notes (see last example in "FractionalBeams.nwctxt").
  • Stemlets for rests compute their length correctly.
  • There is a rudimentary option for stemlets on notes (see last example in "Stemlets.nwctxt").
  • Some more examples have been added.

As always, I'm happy about any comments!

H.M.

Re: Beam.hmm (0.4)

Reply #5 –

Looking forward to seeing your examples, HMMM, but I can't see any of these beam variations in the nwctxt files I downloaded/opened. 

It seems to be a matter of not having the right fonts, or just not having set the fonts up in Page Setup. 

What are the font settings?
(It might be a good idea to add a small note to the tool popup saying which fonts are needed.)

David 

This might be good to explain

What fonts . 

Re: Beam.hmm (0.4)

Reply #6 –
Hi -

I don't think it has to do with fonts. First, the .nwctxt files do contain the font names embedded, so one should see in the page setup whether there would be any unusual fonts.
But second and more important, I do not use fonts, but rather draw the beams with NWC's plugin machinery (in concrete, the nwcdraw module; the code for drawing a beam is copied verbatim from the nwcdraw documentation).

Just to make sure - I use NWC version 2.75a.2.

And I have attached an image on how "Stemlets.nwctxt" looks in my NWC ... what does yours look like?

//Edit:
Do you see any alerts - either
  • when opening NWC (which would indicate a problem with Beam.hmm's source code),
  • or when opening an example .nwctxt file (which would either indicate that Beam.hmm is not installed at the expected folder, or again an error in the source code which for some reason does not occur on my computer)?

H.M.
 

Re: Beam.hmm (0.4)

Reply #7 –
Quote from: hmmueller –
I do not use fonts
Not completely exact: CrossStaffBeams.nwctxt uses MusikChordSansGermanic.
But after having said so, I agree with you: I don't think it has to do with fonts.
(N.B. Everything is fine here with XP.)
And... thank you for all your work!

Re: Beam.hmm (0.4)

Reply #8 –
Quote from: Flurmy –
Not completely exact: ...
Ah - I meant the Beam plugin itself. But thanks for that hint - I'll remove that incidental dependency in an example. & thanks for the confirmation that it works on (at least) one other computer :)

H.M.

Re: Beam.hmm (0.4)

Reply #9 –
Interesting that we can now produce the correct spacing between beams (a quarter of a staff space). But not terribly useful until NWC does the same for ordinary beams, or at least offers the option.

Re: Beam.hmm (0.4)

Reply #10 –
Quote from: hmmueller –
Hi -
...I don't think it has to do with fonts. First, the .nwctxt files do contain the font names embedded, so one should see in the page setup whether there would be any unusual fonts.
But second and more important, I do not use fonts, but rather draw the beams with NWC's plugin machinery (in concrete, the nwcdraw module; the code for drawing a beam is copied verbatim from the nwcdraw documentation).

Just to make sure - I use NWC version 2.75a.2.

And I have attached an image on how "Stemlets.nwctxt" looks in my NWC ... what does yours look like?

//Edit:
Do you see any alerts - either
  • when opening NWC (which would indicate a problem with Beam.hmm's source code),
  • or when opening an example .nwctxt file (which would either indicate that Beam.hmm is not installed at the expected folder, or again an error in the source code which for some reason does not occur on my computer)?

H.M.
1.  I don't have MusikChordSansGermanic and it isn't listed in the Fonts section of the Scriptorium.  Where can I download it? Does it need to be set up as Userfont1, or something else in Page Setup Fonts?
2.  I also use NWC version 2.75a.2.
3.  Alert = "Detected 4 unknown user objects in Stemlets.nwctxt"
4.  See attached Stemlets.PHN (9.79 KB) 
5.  I opened the nwctxt file in an already open NWC2 session.  NWC2 never generates error messages for me when I open the program.

d




Re: Beam.hmm (0.4)

Reply #11 –
Quote from: David Palmquist –
1.  I don't have MusikChordSansGermanic and it isn't listed in the Fonts section of the Scriptorium.  Where can I download it? Does it need to be set up as Userfont1, or something else in Page Setup Fonts?
Dont set it up - I'll repair the examples so that they dont need it ... just my error. But this is no problem for your scores.

Quote from: David Palmquist –
3.  Alert = "Detected 4 unknown user objects in Stemlets.nwctxt"
If you go to Tools-->Options-->Folders, what is the folder near "Object Plugins"? Is this exactly the folder where you installed (copied) the Beam.hmm.nwcuser.lua file to?
  • If not, then this is the problem: The file is not where NWC looks for user plugins. Place the file in that folder, and then hopefully all works fine.
  • If it is, please check whether you installed it under some non-admin rights, so that it is not visible under normal Windows user rights. I confess I dont fully understand Windows here, but I know form first-hand experience that such things happen - I then open a cmd shell as "Administrator" and do the copying of the file in it, and then all works ... maybe you could try that.

Quote from: David Palmquist –
4.  See attached Stemlets.PHN (9.79 KB) 
Thanks - that's why I am quite sure that the plugin is "somewhere else" than NWC looks for plugins.

Quote from: David Palmquist –
5.  I opened the nwctxt file in an already open NWC2 session.  NWC2 never generates error messages for me when I open the program.
Good to know! - if that had happened, there would be an error in some source code which NWC finds on startup.

I hope that helps ...

H.M.



Re: Beam.hmm (0.4)

Reply #12 –
Quote from: David Palmquist –
1.  I don't have MusikChordSansGermanic and it isn't listed in the Fonts section of the Scriptorium.  Where can I download it? Does it need to be set up as Userfont1, or something else in Page Setup Fonts?

Hi David, though you don't really need it for this, it is available as part of an optional suite upgrade I did in 2009:
http://zoundz.pardyline.com.au/SupportFiles/Fonts/ChordFontsDoSiGermanic.zip

The link is on the Scripto in the same place as my other suites:
https://nwc-scriptorium.org/helpful.html#Fonts
I plays 'Bones, crumpets, coronets, floosgals, youfonymums 'n tubies.

Re: Beam.hmm (0.4)

Reply #13 –
I have now looked into the plugin and into the examples - none of them contains any string that contains the letters "German" anywhere. So how can it be David stumbles over that font??? :o - any help is appreciated!

H.M.

Re: Beam.hmm (0.4)

Reply #14 –
File CrossStaffBeams.nwctxt still has Germanic fonts specified as User1 and User5.

Re: Beam.hmm (0.4)

Reply #15 –
Thanks (I had a wrong option in my string search ...) - I have now replaced the file with one that has all User Fonts set to Times New Roman.

H.M.

Re: Beam.hmm (0.4)

Reply #16 –
Quote from: hmmueller –
...If you go to Tools-->Options-->Folders, what is the folder near "Object Plugins"? Is this exactly the folder where you installed (copied) the Beam.hmm.nwcuser.lua file to?

Hi H.M.,
You hit the nail on the head.  I didn't know I had to download/install the LUA file.  The demo files open correctly now. Good stuff!
Thank you.
d

Re: Beam.hmm (0.4)

Reply #17 –
Quote from: Lawrie Pardy –
Hi David, though you don't really need it for this, it is available as part of an optional suite upgrade I did in 2009:
http://zoundz.pardyline.com.au/SupportFiles/Fonts/ChordFontsDoSiGermanic.zip

The link is on the Scripto in the same place as my other suites:
https://nwc-scriptorium.org/helpful.html#Fonts

Hi Lawrie, thanks! 
Don't know how I missed it.  I'll blame it on my recent retina surgery.
d



Re: Beam.hmm (0.5)

Reply #18 –
Version 0.5 has improved support for double beams. The example file DoubleBeams.nwctxt (attached to the second posting of the thread) shows that one can (or could) now write typical SATB scores without layered staffs, even if there are parallel runs of eighths - for example, Händel's "See, the conqu’ring hero comes" (in Germany, this melody is mainly known as a Christmas song "Tochter Zion", with lyrics by F.Ranke).

However, the plugin does not yet work correctly on double-stemmed chords with two different durations - it always takes the shorter duration, instead of the one of the "right stem". I suspect fixing this requires a major rewrite, so it may make some time.

H.M.

Re: Beam.hmm (0.6)

Reply #19 –
Version 0.6 has an additional option "one beam less", which draws one beam less than the tails of the notes request. This can be useful for drawing certain tuplets.

Re: Beam.hmm (0.6)

Reply #20 –
There seems to be so much in this object which needs lots of investigation, all in due time.

But of course, the real winner is when you get it to do something that you personally want to achieve and Noteworthy does not yet support.

This happened for me today when I realised that I could use beam.hmm to achieve cross bar line beaming.
For those of you that have tried doing this, you will know that the page printing mechanism can easily go disastrously awry when employing tricks to achieve a beam across a bar line.

So - thank you Harald for a use that you did not specify (at least I don't think you did) when introducing your object plugin (Cross staff mentioned - not cross bar line)


Rich.

Re: Beam.hmm (0.6)

Reply #21 –
Quote from: Richard Woodroffe –
... for a use that you did not specify ...

Well, no, I did not specify it, and didn't think of it! As a writer of a plugin, it feels like a real winner when someone else finds a good new use of a plugin ... so thank you for this! When I find time, I might/should add an example for this also to the initial posting(s) ... and check out a littel what happens at line and page breaks ... ...

H.M.

Re: Beam.hmm (0.8)

Reply #22 –
With just a handful of changed lines, version 0.7 makes it possible to limit the number of beams at a note to a fixed number of zero to three beams, irrespective of the actual note length.

This is very useful for two-stemmed chords. Actually, the beam object could always be applied twice to two-stemmed chords - however, up to now it looked only at the shorter note length for beaming both stems. With the new options for drawing a fixed number of beams, one can now also draw the correct number of beams for the longer note length.

The additional option to draw zero beams is useful if a two-stemmed chord does not require a beam for its longer note: The beam object now nicely draws the stem for the non-beamed note (which is not drawn by Noteworthy, as overriding the stem to zero removes both stems).

The attached example (also attached to the second posting of the thread for completeness) shows a two-stemmed chord at the beginning of the measure, with two beam objects applied to it: The upper has fixed number of zero beams and therefore only draws the stem for the half note; the lower one takes care of the beam for the eights. However, at the fifth eighth, another two-stemmed chord with a sixteenth tries to interfere. But the beam object for the lower notes here fixes its number of beams to 1, so that no fractional beams for a sixteenth are drawn. In the meantime, yet another beam object connects the four sixteenths on top with two beams.

H.M.

Re: Beam.hmm (0.8)

Reply #23 –
A small change in version 0.8 now makes RestChords behave as expected - see the (modified) example in the previous posting.

H.M.

P.S. ... but the spacing of the dot and the notes is not nice. This is probably still a kludge, at least in more complexe cases like these.

Re: Beam.hmm (0.8)

Reply #24 –
... and I just found another use for this object with the 0.7 modifications: Creating a double-stemmed chord with different stem lengths (which, AFAIK, NWC does not support out of te box). See attached example!

Re: Beam.hmm (0.8)

Reply #25 –
How would I use this object to achieve cross stave beaming?

Here is the lower stave

!NoteWorthyComposerClip(2.751,Single)
|Chord|Dur:8th|Pos:2|Opts:Stem=Down,Beam=First|Dur2:4th|Pos2:6
|Note|Dur:8th|Pos:4|Opts:Stem=Down,Beam=End
|Rest|Dur:8th
|Note|Dur:8th|Pos:6|Opts:Stem=Down
|Note|Dur:8th|Pos:6|Opts:StemLength=7
|Rest|Dur:8th
!NoteWorthyComposerClip-End

and here is the middle stave:
!NoteWorthyComposerClip(2.751,Single)
|Rest|Dur:4th|Visibility:Never
|Note|Dur:8th|Pos:-5|Opts:Stem=Down,StemLength=7
|Rest|Dur:8th|Opts:Stem=Down,VertOffset=-6
|Rest|Dur:8th|Opts:Stem=Down,VertOffset=-6
|Note|Dur:8th|Pos:-5|Opts:Stem=Down,StemLength=7
!NoteWorthyComposerClip-End

which is layer with the upper stave:

!NoteWorthyComposerClip(2.751,Single)
|Chord|Dur:4th|Pos:-1,6
|Chord|Dur:4th|Pos:0,7|Opts:Stem=Up
|Chord|Dur:4th|Pos:-1,6|Opts:Stem=Up
!NoteWorthyComposerClip-End

Would it look better to have the eighth notes on beats 2 and 3 beamed across the staves? If so, how is this achieved. I could not figure out how to get the middle stave stems to show up without the flags.

Thanks for your help.

Re: Beam.hmm (0.8)

Reply #26 –
There's some musical information missing here - for my answer, I assume that this is a keyboard (piano, ...) piece, with treble clef on the upper staff and bass clef on the lower:

<Image Link>

and that you want to indicate that the right hand should play the two low f's:

<Image Link>

I do not know much about (more complex) keyboard writing - maybe others know how it should be done. But I think attaching some text notes (m.s. = mano sinistra = left hand; and m.d. = mano destra = right hand; or l.h. and r.h.) makes clear what should happen (and yes, I would leave in the rests):

<Image Link>

I tried it with cross-beaming (see attached .nwctxt file) - but first, I cannot see a way to route the lines so that it looks acceptable. And second, the Beam.hmm object limits the lengths of the stems (starting with the second note) to 20 - I never thought anyone would need more. Here, it seems, the second note of the first cross-beam would need a beam length of 30 or so to get it working more or less:

<Image Link>

... however, as I said, cross-beaming seems overkill to me, here. Let me know if you need longer stems, I can most probably change that easily.

Re your question "how to get the middle stave stems to show up without the flags", setting the stem length to zero worked for me. But there seems to be a bug in the Beam object: The left beam suddenly vanishes if it is short than 7 or something like that. In my experiment above, it worked because the length is a little larger ... I'll look into that problem when Ihave time.

EDIT: Ah - there is a solution that looks somewhat acceptable (the nwc file is now also attached):

<Image Link>

And I cannot reproduce the problem with the vanishing stem - don't know what happened there.
Lastly, I have uploaded a new versin (0.9) which has the "final stem length" limits increased to -50...50.

H.M.

Re: Beam.hmm (0.8)

Reply #27 –
Harald,

I think you have the staves switched. Check SEBC's notes again: the first snippet she lists is for the lowest staff, and the next two are the upper layered staves.

Those should be much more straight forward to beam.

Re: Beam.hmm (0.9)

Reply #28 –
Quote from: Mike Shawaluk –
I think you have the staves switched. Check SEBC's notes again ...
Ah - one word overlooked (but clefs would have been helpful, I whisper ...). Well, it made an "interesting" example, didn't it? So let me try the (hopefully) intended version ...

EDIT: Here is a picture of what it could look like; nwctxt file is attached. By moving down the object you can alter the layout of the left note, pressing +/- changes the layout of the right stem - this could be used to place the beam between the staves. Also note that I have removed or made invisble the rests - I think they would be wrong, as the voice itself does not pause:

<Image Link>

Re "Would it look better to have the eighth notes on beats 2 and 3 beamed across the staves?": If you actually want to place the notes on the two staves, cross-beaming makes sense. However, if these are staves with treble and bass keys (e.g. for piano), I, personally, think no-one would do that for these notes that are close to the middle c. The main reason against this notation is that the long stems make it appear that the notes are rather far from each other, when, on the contrary, c-d is a very small interval. A simple ledger-line d would suffice and be standard notation and be much quicker to comprehend.

H.M.

Re: Beam.hmm (0.9)

Reply #29 –
Sorry for the confusion caused by a hasty post without enough musical information such as clefs and instrumentation.

This is actually a handbell score which looks a bit like a very busy piano score but these notes are possibly played by separate ringers, depending upon the bell distribution. There is also a convention that the score splits at middle D so anything below D is placed in the bass staff.

Re: Beam.hmm (0.9)

Reply #30 –
Would it be possible to add a feature whereby the beam width could be adjusted.

I have in mind a written out cadenza which uses cueheads.ms to write small noteheads (on blank notes) and would use beam.hmm to add the beams. But then, ideally, the beams should be more like the thickness of grace note beams.

Of course one can use grace notes on their own but playback is not ideal :(

Re: Beam.hmm (0.91)

Reply #31 –
I've quickly added a "Beam width" property in version 0.91. 1 is the default width. An example file is in Reply #1 near the top of the thread. I hope I have not introduced any (new) errors - if so, please notify me!

H.M.

Re: Beam.hmm (0.91)

Reply #32 –
Excellent, thank you.

Re: Beam.hmm (0.91)

Reply #33 –
This is probably a daft question, how do I get the beam to reach the D on the upper stave - I've tried everything I can think of.
<Image Link>
Current notation below
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.751)
|Editor|ActiveStaff:2|CaretIndex:11|CaretPos:-4
|SongInfo|Title:""|Author:"<Name>"|Lyricist:""|Copyright1:"Copyright © 2024 <Name>"|Copyright2:"All Rights Reserved"
|PgSetup|StaffSize:16|Zoom:4|TitlePage:Y|JustifyVertically:Y|PrintSystemSepMark:N|ExtendLastSystem:N|DurationPadding:Y|PageNumbers:0|StaffLabels:None|BarNumbers:None|StartingBar:1
|Font|Style:StaffItalic|Typeface:"Times New Roman"|Size:10|Bold:Y|Italic:Y|CharSet:0
|Font|Style:StaffBold|Typeface:"Times New Roman"|Size:8|Bold:Y|Italic:N|CharSet:0
|Font|Style:StaffLyric|Typeface:"Times New Roman"|Size:7.2|Bold:N|Italic:N|CharSet:0
|Font|Style:PageTitleText|Typeface:"Times New Roman"|Size:24|Bold:Y|Italic:N|CharSet:0
|Font|Style:PageText|Typeface:"Times New Roman"|Size:12|Bold:N|Italic:N|CharSet:0
|Font|Style:PageSmallText|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User1|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User2|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User3|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User4|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User5|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User6|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|PgMargins|Left:1.27|Top:1.27|Right:1.27|Bottom:1.27|Mirror:N
|AddStaff|Name:"Staff"|Group:"Standard"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:12|BoundaryBottom:12|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Clef|Type:Treble
|TimeSig|Signature:3/4
|Dynamic|Style:ff|Opts:Velocity=108,Volume=108|Pos:-7|Justify:Right
|Note|Dur:8th,Dotted|Pos:-4|Opts:Stem=Up,Beam=First
|Note|Dur:16th|Pos:-5|Opts:Stem=Up,Beam=End,ArticulationsOnStem
|Rest|Dur:8th
|Rest|Dur:4th,Dotted
|Bar
|Rest|Dur:Whole
|AddStaff|Name:"Staff-1"|Group:"Standard"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:10|BoundaryBottom:10|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:2
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Clef|Type:Bass
|TimeSig|Signature:3/4
|Dynamic|Style:f|Opts:Velocity=92,Volume=92|Pos:-8|Justify:Right|Visibility:Never
|Rest|Dur:8th
|Rest|Dur:8th
|User|Beam.hmm|Pos:11.5|Beam1:"Max.1 @ left, frac @ left"|FinalStemLength:9|Beam2:"Max.1 @ left, frac @ left"|Beam3:Ignore|BeamGap:1.5|Beam4:Ignore
|Note|Dur:8th|Pos:5|Opts:Stem=Up,StemLength=0
|Note|Dur:4th,Dotted|Pos:4^
|Bar
|Note|Dur:Half,Dotted|Pos:4
!NoteWorthyComposer-End
Geoff

Re: Beam.hmm (0.91)

Reply #34 –
Not sure if I'm understanding exactly what you want but I don't think you need to use Harald's excellent beam program for this.

Try this solution - or have I misunderstood ?

R.

Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.751)
|Editor|ActiveStaff:1|CaretIndex:1|CaretPos:1
|SongInfo|Title:""|Author:"<Name>"|Lyricist:""|Copyright1:"Copyright © 2024 <Name>"|Copyright2:"All Rights Reserved"
|PgSetup|StaffSize:16|Zoom:4|TitlePage:Y|JustifyVertically:Y|PrintSystemSepMark:N|ExtendLastSystem:N|DurationPadding:Y|PageNumbers:0|StaffLabels:None|BarNumbers:None|StartingBar:1
|Font|Style:StaffItalic|Typeface:"Times New Roman"|Size:10|Bold:Y|Italic:Y|CharSet:0
|Font|Style:StaffBold|Typeface:"Times New Roman"|Size:8|Bold:Y|Italic:N|CharSet:0
|Font|Style:StaffLyric|Typeface:"Times New Roman"|Size:7.2|Bold:N|Italic:N|CharSet:0
|Font|Style:PageTitleText|Typeface:"Times New Roman"|Size:24|Bold:Y|Italic:N|CharSet:0
|Font|Style:PageText|Typeface:"Times New Roman"|Size:12|Bold:N|Italic:N|CharSet:0
|Font|Style:PageSmallText|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User1|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User2|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User3|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User4|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User5|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|Font|Style:User6|Typeface:"Times New Roman"|Size:8|Bold:N|Italic:N|CharSet:0
|PgMargins|Left:1.27|Top:1.27|Right:1.27|Bottom:1.27|Mirror:N
|AddStaff|Name:"Staff"|Group:"Standard"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:12|BoundaryBottom:12|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Clef|Type:Treble
|TimeSig|Signature:3/4
|Dynamic|Style:ff|Opts:Velocity=108,Volume=108|Pos:-7|Justify:Right
|Note|Dur:8th,Dotted|Pos:-4|Opts:Stem=Up,Beam=First
|Note|Dur:16th|Pos:-5|Opts:Stem=Up,Beam,ArticulationsOnStem
|Note|Dur:8th|Pos:-17|Opts:Stem=Up,Beam=End,NoLegerLines,Muted
|Rest|Dur:4th,Dotted
|Bar
|Rest|Dur:Whole
|AddStaff|Name:"Staff-1"|Group:"Standard"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:10|BoundaryBottom:10|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:2
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Clef|Type:Bass
|TimeSig|Signature:3/4
|Dynamic|Style:f|Opts:Velocity=92,Volume=92|Pos:-8|Justify:Right|Visibility:Never
|Rest|Dur:8th
|Rest|Dur:8th
|Note|Dur:8th|Pos:5|Opts:Stem=Up,StemLength=0
|Note|Dur:4th,Dotted|Pos:4^
|Bar
|Note|Dur:Half,Dotted|Pos:4
!NoteWorthyComposer-End
Rich.

Re: Beam.hmm (0.91)

Reply #35 –
Oh thanks Rich - great solution - I was looking at the problem from the wrong end !!
Geoff