Skip to main content

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Opagust

General Discussion / Chorus online
Message to all the singers: you can join a GLOBAL CHORUS!
General Discussion / Re: Multi staves
Is there a way of transferring common features from the top stave to all subsequent.

I wrote a tool that may do what you want.
To install: download the attached lua file, open any file in NWC an drag and drop the lua file onto the NWC window.
With the Beam.hmm object, it's not too hard, I'd say - see example.

I agree it's not too hard, but nevertheless I thought 'Maybe it can be made even easier', so I wrote ColoringBeamsSlursTriplets.og

Credits for @Rick G. and @hmmueller !
Quote from @fathafluff in topic Note Color Question

When I select the notes and change the color, the note heads, stems and accents change to the new color, but the beams, slurs and leger lines do not.

Thanks to the replies of @Rick G. and @hmmueller, we know there are workarounds: markers for slurs and triplets, user object beam.hmm for the beams (with the appropriate color set).

With this tool, the necessary markers and beam objects are cretaed. It contains an algorithm to determine the position and final stemlength of the beam object and the position af the triplet marker, but maybe you need to change them for an optimal result.

Installation: After downloading this tool, start NWC, open any file and drag and drop the tool onto the NWC window and confirm.

Use: Select a group of notes ( only the first note needs to be colored), and press ALt-F8 to run the tool.
User Tools / Re: ExportImportMeasures.og
Thanks Horst, for these useful remarks.

Just one small clarification: the size restriction is not on the clipboard, but on the input box of the user tool environment, during import. After some trial and error, I found that the maximum size was something above 5000 characters. Since the output size during export doesn't have that restriction, my tool now checks for that limit in the export phase (after a suggestion of you, Horst).
User Tools / Re: ExportImportMeasures.og
Version 2.0 is now available (see original post).
It has been thorougly test by Horst H., thanks!

Apart from fixing some bugs, following modifications are added:
* Extending incomplete staves, not only before, but also after the import.
* Warning at the export stage for possible exceeding the maximum length for import.
* The medley title in the commnents section should be in the last line. This is now added in the help text.
General Discussion / Re: NWC on Facebook
Me three.  A very long time ago I had a Facebook account, but I chose to delete it, and have never gone back.

Hi Mike,
The NoteWorthy Composer Facebook account published this today:
Hey! What about Ukulele Chord Charts?
Insert: Object (0.5)
User Tools / Re: ExportImportMeasures.og
Hmm.  Not sure what I'm doing wrong but on a simple 2 staff, one lyric song I get the following error message when trying to import the results to a new file:

C:\ProgramData\Noteworthy Software\nwc2\UserPlugins\ExportImportMeasures.lua:121: bad argument #1 to 'sub' (string expected, got nil)

I took a quick look and I think this error occurs when the comments section in the SongInfo panel is empty. I wait for the next comments of Horst to include that change. In the mean time, maybe you can just enter something in the comments section (a space would be enough). If you retry whithout the error occurring, then my suspect was right.
I've put the final(? ::) ) version in a seperate post.

See ExportImportMeasures.og.

All comments or bug reports are welcome.
User Tools / ExportImportMeasures.og
Version 2.0 is now added.
Apart from fixing some bugs, following modifications are added:
* Extending incomplete staves, not only before, but also after the import.
* Warning at the export stage for possible exceeding the maximum length for import.
* The medley title in the commnents section should be in the last line. This is now added in the help text.

* With this tool you can copy all or selected measures (of all staves), including the lyrics, and pasting them in another file. A possible use is to reassemble a medley from its separate songs.

* In order to do this, you have to run the tool from a source file to 'export' a selection or all measures.
You'll be shown an output window, which you have to copy into your clipboard.

* Then you have to rerun the tool from your 'destination file' to import (append or insert after a specified measure) the exported items . An input window will be presented where you have to paste the content of your clipboard.

* The input screen for the import seems to be limited. The tool will check if the input contains the trailer line and ends with an error message if not. In that case, use smaller selections for exporting.

* In the selection box for last measure to export, a default value of 1024 is prefilled. Leave that unchanged if you want to specify the last measure of your file.

* Linking the import staves to the corresponding staves in the destination file is done by comparing the staff labels.
If no matching is found, you'll be presented two options: specify the staff to link with, or add a new staff.
If you have specified a linking staff, you'll be asked wich label has to be withheld.

* A text marker with the song title will be added in the first imported measure of the first staff. 

*It's recommended that, before importing, you add the medley title as a line in the comments section of the Song Info window. This line should start with "MedleyTitle:", without a space.
You can start with a copy of the first song as destination file. At the fist import (of the second song), the song title of the first song will be added as a text marker in the first measure, and the medley title from the comments will be used as new song title.

* The following properties of a staff will be compared with those in its corresponding imported staff: visibility, muted, layered, ending bar, volume, stereopan, channel, play back device, instrument, default dynamic velocities and trasposition.
Difference will be reported and you have the choice to proceed or cancel. If you proceed, the propertied of the destination file will be withheld.
* Before appending or inserting the imported staves, incomplete staves in the destination file will be extended with measures containins rests, up to the insertion measure.

* If a stave contains few lyric lines than the corresponding imported staff, the number of lyric lines of the destination file will be augmented and the lower boundary increased accordingly.
* Incomplete lyric lines in the destination files will be filled with underscores, separated with blanks.
I also get these messages each time I change a template, but that does'nt prevent me to save the change anyway.
Don't know why your save isn't succesful.

Maybe the object/user tool combination rehearsal.og can be helpful.
Its purpose is creating seperate files for the different voices, by specifyng a.o foreground and background volumes and stereo pan.

(I myself am not a musician, but a tech guy who likes to sing in a choir, and with that tool I've become much more confident during the repetitions (and performances).)
I'm popping to say that I look forward to trying out this tool, and to ask if you could let me know when you've finished the tweaks (posting in this thread should be enough). I was using your other cut/paste tool recently and thinking again about how thankful I was for the time savings!
Best wishes with your surgery recovery.
I'm still working on it, but I want it to be as good as I think it can be, so there's also quite a bit testing involved.
As to my surgery recovery: better than I thought it would be  :D , but as a consequence I spent less time in my sofa with my laptop >:( .
So please a little patience.

Hi Horst,

Here are my thaughts on your comments:

- Bar Lines: I think I should insert a double bar if neither the end of the  destination staff ends, nor the start of the imported staff starts with a bar of some type.
- Song Titles: I use the font 'Staff Title Text', the actual size depends on the options of the destination file, but by definition it will always be large. Scaling to 75% is indeed a good idea, as is moving it to position 21.
- Quotaion marks within text markers: I don't see that im my test files. I'm using NWC version 2.8 Beta 1, maybe that's the reason. I will look if I can intercept it.
- Medley Title: I have the following idea, that might solve this problem.
Add a line with the medley title in the comments area of each of the separate songs, in the form 'medley title:' + the title.
If you take the first song file as destination file to start with, then on the first import (of the 2nd song), the destination file will still have it's original song title. The tool can copy that title to a text marker in the first measure, and change the song title to the medley title. It then copies the song title of the 2nd song in the first measure of the imported song. On te next imports, the song title of the destination file will match tke medley title in the comments area of the imported song, so only the song title of the imported song will be copied to a text marker. It will be necessary of course that all songs contain the medley title.
I hope I did clearly explain my thaughts about this.
- Truncation of overflowing text: Unfortunaly, when the import is truncated, it will not leave a clean result that can be pasted, because the truncation will occur somewhere in the middle of a staff, so some staves may be complete, while others won't be.
- Incomplete or fewer lyric lines in the destination file: the tool will take care of that.
- The same applies to incomplete or fewer staves.
Congratulations, Opagust: You've made it!
I have just completed the first medley out of 5 songs. The look of it appears really OK after a few manual modifications.
Sound check will follow tomorrow, and then, of course, a couple of comments.
Hope I can find sleep now, excited as I am...
Hi Horst,
I'm glad it worked out well for you!

Now I'm working on a new version, after some thoughts of David PalmQuist.
This version includes:
* more elaborate checking and reporting on staf property mismatches
* automatically extend incomplete lyric lines in the destination file with spaces and underscores
The coding for these additions is done, testing seems OK.
Next I will try to accomplish the automatically extension or creation  of incomplete or absent staves in the destination file.
If that woks out well, I expect the manual modifications to be reduced to a minimum.
Hi David, thanks for your response.

First of all: this isn't an object, but a tool. The difference might not be clear for every user, so let me explain:
* an object is inserted in a file, you do it once, and it'll do whatever it's supposed to do every time the file is shwon, printed, played.
* a tool can be invoked from within a file and does then his job with the file, but the tool itself is not permanently included in the file.

That said, let me comment on your thoughts:

1.I have been thinking of it, but I wanted to keep the dialog short. The user can easily insert a system or page break himself.

2. At the start of the first measure of the top staf of the imported part, the tool will insert a text marker above the staff with the song title with the font 'Page Title Text'. Again, the user might insert a boundary offset change, if needed.

3. For as it is now, the tool checks that, for every staff in the imported part, there's a staff in the destination file wit the same name. If not, the tool ends with a simple error message (on the first mismatch). If all the imported staves have a match, they inherit all properties of the matching staff in the destination file.
Maybe I should check more then the name alone and provide more elaborate information when there's a mismatch. The properties shown in the score review panel might be an inspiration?

4. The song title is now a text marker at the beginning. Maybe I can also insert the song tile + ' - end' in a text market at the end (with a smaller font).

Again, thanks for your input,


(And whoever wants to comment on this, please don't hesitate!
So here is my first version of  'ExportImportMeasures.og'. Please let me know if it covers your needs or you've find any bugs.
When running, you can choose Action = 'Show Help' and 'Show Conditions' for further useful information.

I'm looking forward for your response(s).
A final version will be published in a separate post.

I'm in the stage of testing a new tool 'ExportImportMeasures'.
The bridge between the export and the import should ideally be the clipboard, but I don't think that's possible in a lua user tool. So one has to copy the exported side from the output screen and then pasting it back in the input screen for the import run.
But there seems to be a size limit on the input screen, so that a part or the exported part can be lost. So it will be necessary to check if the import is complete. If negative, you should use partial import/exports.
I know lua must have a library for copying and pasting to/from the windows clipboard, but within a user tool libraries can't be included. So I suppose it's not possible?
Some people (e.g. my wife ...) inadvertently touch the touchpad while using the keyboard, and then weird things start to happen

After a long time of suffering from the same problem, I found for myself a solution: in the settings of the touchpad, I unchecked "tap with one finger to click". Since then inadvertently touching the touchpad isn't causing any weird things anymore, like suddenly  jumping to the mouse pointer when typing text.
Just as a note: I'm quite opposed to using measure numbers in a tool. Measure numbers are for musicians in the final product; but while editing, they are ill-defined, especially over multiple staves. Better, in my experience, are simple text markers put into the staves - they remain stable even when things are added or removed before them; and can easily by copied and removed by small helper tools.


In the tool I'm writing now, measure numbers are used as 'coördinates' to know which part of a file is to be exported, and where in the destination file the import has to be inserted. There will be no manipulation of measure numbers. The only and logical effect will be that NWC will adjust the measure numbers in the destination file.
Wow, Opagust: You appear already deeply immersed in my issue!
My pleasure! (I'm recovering from a hip implant, so I have some free time to spend)

I have some more questions for the import side:
- Should the exported stuff always be added at the end of the destination file or have I to provide an option to insert after a specific measure?
- If desirable, I could add a text item above the first imported measure with the song title.

After rereading your replies, I think I'm gonna write a seperate tool for this.

- As I understand, your aim is to export all measures and lyrics from all staves of a 'source file' and import them at the end of a 'destination file'?  Or should there be a possibility to select the staves and the measures, as in CopyPasteMeasures?

- You're talking about "types varying between SAB and SSAATTBB". So it will be necessary to provide all the voices in the first song of the medley (wich will be your destination file). The other songs that have to be added may have less voice parts, but the staff names will have to match with one of the destination file. The staves of the destination file that are not present in the source file, can then be extended with a boundary collapse and a multimeasure rest.

- I suppose the number of verses of the seperate songs can vary. That also will necassitate special treatment.
Doesn't that cry for a synthesis?
CopyPasteMeasures.og would need another option of 'Just Copy' which should finally provide the address of the copied stuff.
Then, the 'Paste' part of that tool would have to be separated into a stand-alone tool, to be operated from the destination file  and receiving the 'clipboard' address. It would, however, have to ask for the starting point in terms of first staff to be pasted to, and start measure (but why not, just the cursor position?).

I don't promise anything by now, but I think it's possible to extend the tool to satisfy your needs.

A usertool can only be run within an open NWC file and can only do things with that file.
But 3 years ago Rick G. has written 2 tools:
1. for copying a staff from one file
2. for pasting that staff into another file

I think that's what you need.
The playlist feature alone is much more useful than trying to use a simple PDF reader.

I'm experimenting now with Xodo PDF Reader & Annotator and I discovered a feature to merge multiple PDFs. If I then save them as 'my playlist', I can read it in as one file.
So, for the time being, I'll stick with this free program, thanks to Mike.

I downloaded MusicreaderPDF and at first glance, I don't like it:
  • Odd user interface
  • few contrast, pale score
  • last staff on last page was cutten off
  • I don't need clouds, I prefer the sunlight
I use a free program called Xodo PDF Reader & Annotator on my Surface Pro tablet, which has a stylus. It has very nice annotation features, including automatic recognition of the stylus for marking up PDFs. I use it for choir music (much of which is NWC scores). You can check it out at
Thanks, Mike.
I downloaded it and experimented a bit on my old laptop and it seems very good. On my new computer I will have a touch screen and a stylus pen, so I think this will do the job well!
Thanks again.
Object Plugins / Re: Rehearsal.og
Update to version 1.1 (see attachment in original post)
New in version 1.1:
  - test on NWC version: it has to be > 2.75
  - correction of a bug: dynamic velocities from the parameters were not copied into the staff instruments.
I introduced another bug, trying to comment the changes :-[ .
So I replaced the file. It was already downloaded 3 times, so please redo.
Object Plugins / Re: Rehearsal.og
Update to version 1.1 (see attachment in original post)
New in version 1.1:
   - test on NWC version: it has to be > 2.75
   - correction of a bug: dynamic velocities from the parameters were not copied into the staff instruments.
I have another question.
I want to use my knew ordered '2 in 1' laptop in tablet mode on my music stand to replace my scores on paper.
It comes with a active stylus pen (from ACER), so I wonder, will I be able to make remarks on my (pfd)-scores and save them. I know I can upgrade Acrobat Adobe but that will cost me 18€/month.
Or should I copy my scores as image in a word-document?
Has anyone some experience with this?
Object Plugins / Re: Rehearsal.og
You don't hear or see any difference.
  • hear: Do you listen with a headphone, then you should hear the foreground staff on the left, the background staves on the right and witt a lower volume (but that's three against one stave).
  • see: The foreground stave should be in the 'Highlight 2' color (green for me, but that depends of your settings 'Tools/Options/Color'.
    If you add some dynamics, you should see different Volume settings for equal dynamics in Fore- vs Backgrouns staves.

My version is 2.8 Beta 1. I don't know if that could be the reason?

Anyone else out there with a satisfying answer?
Object Plugins / Re: Rehearsal.og
You should see this information screen when you run the tool and then press the 'OK' button
Object Plugins / Re: Rehearsal.og
Hello Bart,

I downloaded your file and ran the tool: result as expected, see attachment.
I don't know why it doesn't work for you.
Maybe you should re-install it?
Object Plugins / Re: Rehearsal.og

You don't want to manually create a user tool entry for Opagust's plugin. Once the plugin is installed, it will automatically add a user tool named "Rehearsal.og: Create a rehearsal score" in the .Plugins group in the User Tools window.  That is the one you want to run.
Hello Bart,
Mike beat me.
So look in the .Plugins Group (second line in the left window) of the User Tools window. It should be there. If not, you can try to reinstall it via 'Tools/Manage Objects'

Object Plugins / Rehearsal.og
Five years ago I wrote the usertool 'MakeRehearsalFile, which had several upates until 2 years ago.
One of these updates made it possible to add arguments to the command line to set the value or default for one or more parameters.

Since it's now possible (for NWC version 2.75a Beta 2 or later) to integrate a user tool into a user object, I decided to write a whole new version. Apart from foreground and background voices, it also supports 'center voices', 'velocity instruments' and volume instruments'.

With this plugin you can transform a (vocal) score into a rehearsal score, by specifying different channel volume, stereopan and dynamic volumes and velocities for each staff, according to its 'Staff Type'. You can also specify a different color for a 'Foreground voice'.

To do that you have to create one rehearsal object subtype 'Parameters' (anywhere in the score), and a subtype 'Staff Type' in each staff you want to change.
Hint: create rehearsal objects in your template file.

Staff Types are: 'Backgroud voice', 'Center voice', 'Foreground voice', 'Velocity instrument' and 'Volume Instrument'.

Parameters are: Foreground color, Channel Volume and Stereopan for each staff type and dynamic velocities for each dynamic (ppp ... fff). They all have predefined default settings, which you can change or leave unchanged.

After creation of your objects, they can be processed by the integrated 'Rehearsal.og' user tool in the .Plugins group (which you can invoke via 'Tools/User Tool...' or ALT-F8).

Velocities and Volumes of the dynamics are calculated as follows (for more information: see document 'Dynamics.pdf' in
- for a voice staff or volume instrument staff:
  ° The Velocity of each dynamic is set equal to the highest Staff Velocity ('fff').
  ° The Volume is set using Tina Billet's formula :
      Volume  = Velocity * Staff Volume) / highest Staff Velocity.
- for a velocity staff: the custom velocity and volume settings are set to nil, which means that they get the dynamic velocity and channel volume from the parameters (which are stored in the staff properties).

7dec2020: Update to version 1.1:
New in version 1.1:
  - test on NWC version: it has to be > 2.75
  - correction of a bug: dynamic velocities from the parameters were not copied into the staff instruments.
The Coda signs before measure 25, just before the 2nd ending, are the reason why it gets back to that measure. You should remove them.
The Coda's before measure 26 are OK,  but you also have to remove the 3rd ending.
If you look in your Noteworthy directory (programs not Noteworthy files) you will find a directory called "Setups"
In there you will find an executable for the last Noteworthy program you installed. Use this to install on your new machine.
The viewer you can install from the internet.

I think this is the easiest route.
In C:\Program Files (x86)\Noteworthy Software\NoteWorthy Composer 2\Setups , you'll find all the installers used to get you to this point. Copy this folder to a flash drive, install the installers oldest to newest, and you should be golden.

... though it looks like Richard beat me to it!
Thank you both, I copied the folder to my external hard disk.
Or buy it anew. That's what I did. The price of NWC is laughable compared to its features: I think paying anew for the goodies we got is not wrong, and its affordable, I'd believe.


And it's problably the simplest solution. I will consider it.
Long Live NWC! (I hope)
I'm planning to replace my good old laptop by a two-in-one, without CD drive.
So my question is: how should I re-install NWC, if I can't read my original installation CD?
If you are willing to use a 2-key shortcut with the Alt key, there's a shortcut for everything.
Use Alt-ch to open the menu-item of with the first character = ch (So "Alt-f" will open the File submenu).
Then look at the underlined character of the submenu you want to use and press that key (So "Alt-f a" will open the  "save as" dialog box).
Remark: opening a menu directly from the menu bar won't show underlines characters, but some of them mention a alternative shortcut.
So you don't have to memorise all shortcuts, but the ones you use frequently will be anchored in the memory of your fingers.

Single or double bar lines don't make any difference.
There are two situtations where the measurenumber is not increased on encountering a barline:
  • when the box 'Exclude from barcount' is checked
  • when there was no item with a duration after the previous barline

One glitch that happened twice (I redid it to check and see) was that one stave had one extra measure cut out of it. I'm not sure why this would be. Any insights?

I looked at the code and couldn't find anything that could cause that glitch, unless: if in one of the staves a barline is missing in some place, the tool will count one measure for that stave, while two in the others.

So, maybe that was the cause? (That would be a glitch in your score  ;))

It's FYI indeed.

Seel also this 4 year old tool : Score Analysis
I'm glad you find this tool useful.

When I find the time I'll look into the 'glitch' that you mentioned.

As to the 'undo' function:  I don't think it can be included in the tool: NWC automaticcally closes down the tool after each modification and is not possible for the tool to save the old situtation in another file. But that shouldn"t be a problem: As long as you haven't saved your file, you can reopen it instead, which is infact an 'undo'. And when you run the tool for a second time for another chance, NWC shows a dialog box to ask if you want to save first.

The tool seems to run flawlessly on staves with not too many items. But from a certain number of items (for instance on the whole percussion staff of "stairway to heaven"), the tool doesn't give the desired output anymore on my computer but just shows a window with nothing more then "ERROR".  (see SplitStaff_error.jpg)

If a window with 'ERROR' is shown, click the radiobutton 'STDERR' to see the error(s).
Maybe I don't understand the problem, but using the right arrow key I can scroll an active  shorter staff  until the end of it is on the left edge of the window.
Isn't that what you're asking for?
I was thinking: perhaps I could write a user tool to automatically insert the white text objects.
But I have one problem: I can't control the width of the text objects. I added some lyrics in your example file. Result: the white text objects don't completely span the measure anymore (see attachment).
I don't know how to solve this in a user tool.
But perhaps it is possible with a user object plugin, to draw a white rectangle of the correct size? I don't have enough knowledge for writing such an plugin, but maybe someone else?
This is great.  One useful additions would be the option to cut rather than copy.  Moving sections around is quite common (for me).
New version with cut option: see original post
General Discussion / Re: text position
Perhaps @Opagust should edit the forum post title so its name agrees with the attachment, in case other people are trying to find it in the future.

Done :-[
Thanks, Mike, I humbly apologize.