NoteWorthy Composer Forum

Rick, what do you mean with:?

Or I missed something?

I enforce this with: |Boundary|Style:NewSize items.

I'm now using PageTxt to put the page number, the title and the name of the part (staff label) on each page after the first one.
Of course this is no rocket science and maybe neither the best solution (Rick?)

When I print the single parts, hiding what's not needed, at the bottom of the pages, except the first one, I get "Harp 1" or "Harp 2" or...
When I print the conductor score I get 4 overprinted titles and page numbers and, and this is the big hurdle, all the staff labels overlapped.

(There are 541 tremolo objects in the score, so it took a while to track this down ) <snip> I am looking into a fix to the object that will prevent this sort of behavior, for this and other objects for which Class=StaffSig does not make sense.

a) could the object be modified to have an additional variable available that permits printing the total number of pages?  Is this data even available?  Surely it would be at print time...

Thank you for the answers!

I wanted the slur above and below two chords. so that is impossible without adding the extra overlapping staff.

I want to add a slur on the top and bottom notes between 2 chords. How do I do that?

The version difference makes your results more understandable Rick.

Hopefully Eric will know what's wrong and be able to update adp_GlobalMod.php fairly soon.

I am running the same version of adp_GlobalMod.php as Lawrie is using.

I have a template that has this object on every staff.  The contents of the Text field are:
%Title% - %StaffLabel% - Page %PageNum,1%

As you know, I'm a big user of Global_Mod, and it seems each time I run Global_Mod on a staff the contents of the Text field of PageTxt.nw objects gets a double quote or apparently escaped characters added at each end so this:
%Title% - %StaffLabel% - Page %PageNum,1%
becomes this (changes in red to stand out):
"%Title% - %StaffLabel% - Page %PageNum,1%"
then the next time I run a Global_Mod command I get this:
"\"%Title% - %StaffLabel% - Page %PageNum,1%\""
then this:
"\"\]\"%Title% - %StaffLabel% - Page %PageNum,1%\]\"\""
then this:
"\"\]\"\]]\]\"%Title% - %StaffLabel% - Page %PageNum,1%\]]\]\"\]\"\""
and so on.

I see that you're using the mezzo forte to change the volume of the notes, and a grace note that is a rest to get a little pause in there.

What's the difference between a mezzo forte and a mezzo piano?

I opened the Score Review but how can I delete the 'Y' in the 'Hide' column in order to show these staves as well ?

Currently, if I were to just put 8 of the same 1/8 notes in a row, it sounds dull and robotic

I am still learning to find a way to change the colour of noteheads...

I think it's more the other way round: What you get from NWC, is the standard Windows print dialog.

Does Noteworthy Composer suppress certain options in the printer Driver?

I don't know of any hard and fast rule that states that a status bar must be at the bottom of the screen

The default position of a status bar is along the bottom of the parent window, but you can specify the CCS_TOP style to have it appear at the top of the parent window's client area.

I only include the "off" option as it has been suggested, but I would happily do without that option.

I see no value in it being dockable like a toolbar.

if the Status Bar were to be moved to the top of the active window

This would also put the moving bar that appears during playback, showing how much of the piece has been played, close to the playback controls.

Not worth the hassle

No, Rick, this is not an indication that it's time that I learned how to use user tools.

A user tool shouldn't be necessary here.

Isn't it time to actually address this, instead of throwing a user tool at it and hoping for the best?

In the meantime, does anyone have a trick to pass on?

I'm looking for a method that will only look at double sharps, double flats, C flats, F flats, B sharps and E sharps, and will correct those in a way that doesn't change chord interval structures.

To quantify things, here: I need to transpose a four-measure, highly chromatic phrase up half a step.

Is anyone aware of a way to increase the space between lines of lyrics?

When whole notes are on adjacent staff positions, the "weak side" note is moved by more than one note width, so notes on a layered staff that have extra note spacing of 1 will not quite line up.

(the dummy bar is there to force the first boundary to take effect):

a custom object's spec table can have a maximum of 16 parameters.

changing chord color don't affect to the cue noteheads.

NoteWorthy Support: Please add to the bug list

it was a font I created for the task, called "SwingBars".

this is an example of the font approach I tried with my SwingDings typeface.

Is it possible to send a single staff to 2 or more midi channels instead of having to duplicate the staff?

* Or ... ?

Thank you very much

Is there no easier method than writing the italicised text, character by character (selected from the symbol table set to the Romital font) into a word processor then cutting and pasting the result into NWC?

a way for a clip text user tool to "chain" to a separate tool that runs in file text mode. Or perhaps this is already possible and I haven't figured it out yet?

do you know a way to make the program produce more hyphens between the syllables in case of long melismas?

it doesn't find all of them.

Has anyone found a way to do this? Failing that, can it be a future change along the lines suggested by SimonJShaw?

I see the change, but why is it necessary?

MFile 1 2 192
MTrk
0 Meta Text "By <Name>"
0 Meta Copyright "Copyright \xc2\xa9 2015 <Name>"
0 Meta Copyright "All Rights Reserved"
0 Meta Text "Generated by NoteWorthy Composer"
0 Meta TrkEnd
TrkEnd
MTrk
0 Meta 0x21 00
0 Meta TrkName "Staff"
0 Par ch=1 c=7 v=127
0 Par ch=1 c=10 v=64
0 PrCh ch=1 p=73
0 Pb ch=1 v=16383
0 On ch=1 n=71 v=110
192 Pb ch=1 v=8192
768 Pb ch=1 v=16383
960 Pb ch=1 v=16352
960 Pb ch=1 v=8192
1488 On ch=1 n=71 v=0
1488 Meta TrkEnd
TrkEnd

How can I fix it?

You should be able to use both midiData1 and midiData2 to construct a 14 bit value

Really ?? it would be great if you could explain it a little more.

I cannot get this to be seen/loaded into nwc.  All other lua scripts install and work fine and update regularly.  This one cannot be "seen" by nwc.  Am I doing something wrong ?