As a Noteworthy Composer user new to GPO, I'm discovering some handy hints and tricks that work well in Noteworthy, and might be applicable to some other notation programs, although I can't be sure of how "portable" these techniques are.
To begin with, to produce good performance dynamics requires a lot of manipulation of the mod wheel CC1 values. Working on the score to the first movement of Beethoven's Sixth symphony as my "training piece", I have discovered what I think might be the best way to insert detailed CC1 and velocity controls into the performance.
For each instrument create an extra staff placed immediately below the instrument staff, and assign this to the same Garritan Studio channel as the instrument staff. For example, immediately below the staff labeled "Violins I" I add a staff labeled "Violins I KS and CC". Even though the first violins are in the treble clef I put this extra staff in the bass clef and in the midi properties mark it as transposed -12. That way the KS (Key Switch) note values map into the clef in easily readable positions. For example, "F" for Pizz maps to the high F of the bass clef in the transposed control staff, and is quickly Identifiable as "F", as opposed to having it extended way below the staff by some number of lines that have to be counted to figure out what the KS note is. (KS notes can also be annotated using the "edit Lyrics" command for the controller staff to add text like "KS for Pizz" under the note itself.)
Next, fill the entire control staff with measures filled with short valued rests consistent with the note values of the piece. For example, in Beethoven 6 mv 1 (in 2/4) I fill the entire control staff with eighth rests.
Now I can place MPC controllers between any two rests. (Noteworthy's "Multi-Point Controller" allows any CC, including CC1 mod wheel to be given a single absolute value or a linear sweep over a range of values for a specified time period). In some cases, where the controller value needs to be adjusted just slightly before the note is hit to avoid sudden "jumps" during the first few microseconds of the attack, you can split the 1/16th rest in the controller staff into two 1/32 rests and put the controller value 1/32 before the note is played.
A couple of advantages of this is method are 1) the mod wheel values stand out from the clutter of notes, 2) A controller measure can be copied and pasted into a later spot in the same staff or at a matching spot in another instrument's staff allowing the dynamic contour of a single measure or an entire passage to be duplicated into other measures even when those two measures have completely different sequences of notes. Only the CC1 values are copy-pasted. So when the oboe takes the melody line from the strings, the oboe can be given a copy of the string's CC1 contours for the whole passage with a single copy and paste. 3) If at some later date you wish to "enrich" the string section, for example, by adding a couple layered solo instruments you can copy-paste the entire controller staff from the section instrument staff into the solo instrument staff so that the newly added solo instrument follows the same performance dynamics of the section staff.
In Noteworthy, note velocities are governed by the usual dynamic marks (pp, p, mp, mf, ...), and their default velocity values can be overridden for intermediate velocities. Place your dynamic notations between the note staff and the controller staff for maximum visibility. Here's an example from Beethoven's 6th mv 1, first violins:
I'll add more tips as I discover more ways to use Noteworthy Composer with GPO.