NoteWorthy Composer Forum

• the double bar notehead is taken from the standard NWC font;
• the single bar notehead is drawn as a semibreve (whole) notehead with a line on each side;
• the square notehead is created by two Times New Roman letters 'I' that are rotated by 90 degrees (which makes the notehead a little too short).

• 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.

• 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)?

• 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.

• "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.
  

• "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.

  ['%%1/8%%']     = 'H',
  ['%%ppp%%']     = 'P',
...
    for k, v in pairs(replacements) do
      text = string.gsub(text, k, v)
    end

  ['%1/8%']     = 'H',
  ['%ppp%']     = 'P',

• delete it
• copy it and paste it somewhere else (with accepted shaky semantics if boundaries at source or target location do not line up exactly)
• change properties (as with current single-staff selections)

|User|EnvelopeMaestro.hmm|Pos:-6.5|Class:StaffSig|Bottom:-6|Top:-1|ShowLocation:below|MinValue:60|Pen:dash|PenWidth:0.7|Controller:71|ShowAs:Blend|ControllerName:"Select by number"

• dynamics: %ppp%, %pp%, %p%, %mp%, %mf%, %f%, %ff%, %fff%
• notes: %1/2%, %1/4%, %1/8%, %breve%
• clefs: %gclef%, %fclef%, %cclef%
• accidentals: %sharp% or %#%, %natural% or %=%, %flat% or %b%, %##% or %x%, %bb%
• rests: %rbreve%, %r/1%, %r/2%, %r/4%, %r/8%, %r/16%, %r/32%, %r/64%
• others: %turn%, %tr%, %coda%, %segno%, %|% or %bar%

• decimal codes: e.g. %177%
• hexadecimal codes: e.g. %0xf123%

• Controller selection is now via a drop down list for predefined controllers; and, additionally, by number if one selects 'Select by number' in the dropdown. I think this is a good compromise between pure "magic numbers" and the necessary flexibility for accessing arbitrary CCs (like my 71).*
• Text fonts are still fixed, but a scale can be used to make texts larger or smaller.
• Both plugins got useful header comments.**

• MP3 with "muted" (disabled) volume envelopes
• MP3 with active volume envelopes

• No volume envelope: www.hmmueller.de/NoteworthyComposer/IchWünscheDir_NoVol.mp3
• Scratch volume: www.hmmueller.de/NoteworthyComposer/IchWünscheDir_Vol1.mp3
• Better volume: www.hmmueller.de/NoteworthyComposer/IchWünscheDir_Vol2.mp3

• (free) loopMIDI as virtual MIDI cable
• Reaper 5.80 as VST container
• (free) Kontakt Player 5.0 as instrument container for the choir; (free) sfz player for SFZ soundfonts
• Soundiron Olympus Micro Choir for choir voices
• (free) Sonatina Symphony Orchestra Keyboard sound for piano

• No volume envelopes: IchWünscheDir_AllNoVol.mp3
• With volume envelopes: IchWünscheDir_AllWithVol.mp3

• it is very easy to understand the envelope: It is immediately clear where the volume goes up or down, or where it remains constant.
• Moreover, it is also very easy to change the envelope: In Reaper, as an example, you just shift-click on it somewhere and pull the line segments up and down with the mouse - "direct manipulation".

• At the beginning of the score, an "EnvelopeMaestro" object defines up to 10 value ranges with their own names (this is useful for showing "ppp"..."fff" for a volume controller - see examples) and some presentation parameters for a controller.
• The value of each controller is set by "Envelope" objects along the score that define the current value and possibly a value step.
• The value line is visibly shown, like with DAW envelopes.
• The value and the step are manipulated directly: The value is derived from the staff position (which can be changed conveniently with ctrl-shift-up and ctrl-shift-down), and the span is controlled by the built-in spinner, i.e., the + and - keys.
• As a special feature, a step can be "inclined" a little so that the value changes not to abruptly; this so-called "attack" can be changed directly
  with the , and . keys.

• Put each controller on a separate staff with a single line. This allows muting of each staff, which disables the controller; and it allows for more graphical control. On the other hand, the "Staff range", "Line Type" and "Line Offset" options allow placing two or more controllers on a single staff to save "GUI real estate". Last, it is also possible to put the envelope objects into a note staff, e.g. by setting the "Staff range" high above the notes.
• Use half and eighth rests on the controller staffs to allow for coarser and finer spans. Quarter rests take up a lot of space and are visually more disturbing. Hidden rests do not really work, as they huddle together at the left side of the bars and therefore distort the span slopes.
• When copying envelopes to another staff, make sure that their Maestros have similar range definitions so that the effect rates do not change.
• Don't use a volume controller with piano, harpsichord, guitar and other instruments where the volume cannot be arbitrarily changed after note started.

• As I see it, the multi-point controller does only support a predefined list of controllers (1, 2, 4, 5, 6, 7, 8, 10, 11, 12, 13, 91, 92, 93, 94, and 95, according to the documentation)
• So the only way to send a CC 71 etc. seems to be via an object that calls nwcplay.midi(#offsetSPP,'Command',#midiData1,[#midiData2]). The documentation does not indiciate that there are any limits to the sent data, so by using 'controller' as Command, 71 as #midiData1 and some value which the "choir instrument" understands as #midiData2, I should be able to do what I want, shouldn't I?

[HMM]
1 Remove Top NoSingle=2,php\php.exe scripts\adp_Parts.php remove top nosingle
2 Remove Top=2,php\php.exe scripts\adp_Parts.php remove top
3 Retain Top=2,php\php.exe scripts\adp_Parts.php retain top
4 Retain Bottom=2,php\php.exe scripts\adp_Parts.php retain bottom
5 Remove Bottom=2,php\php.exe scripts\adp_Parts.php remove bottom
6 Remove Bottom NoSingle=2,php\php.exe scripts\adp_Parts.php remove bottom nosingle

• The top staff shows a segment newly composed in "chord notation"
• The three staffs below were created from it, by first copying in the upper staff (or a piece of it), then selecting (highlighting) some segment, and then execute suitable user tools; e.g. for the middle staff "Remove Top" and "Retain Top" (or "Remove Bottom")