Skip to main content ↑ ↓

Messages

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

Messages - Opagust

301
General Discussion / Re: Buglet in printing?
Hallo David,
The rehearsal letter is after a collpase command, so why do you think it should be printed?
In the attacment picture I see a light grey 'F' in the second staff. I think your problem will be solved if you set its visiblity to 'Always'.
302
General Discussion / Re: Copying staffs more efficiently
Quote from: Rick G. –
Good luck tring to use the Windows API in a script.
My code uses the "htmlfile" COM object to get text from the Clipboard.
To put text into the Clipboard, it writes and runs a hypertext application.
This latter step raised security flags when it tied to do in PHP.

I don't know how to do any of this in Lua.

In Lua it's possible to access the clipboard via the extern library 'Clipboard'. Unfortunally, the run time environment of NWC does not allow to use extern libraries, so it can't be done in a user tool. :'( 
304
General Discussion / Re: Repeat whole song including repeats
Have you tried a combination of a  master repeat within a local repeat?

Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|Clef|Type:Treble
|Bar|Style:LocalRepeatClose|Repeat:2
|Note|Dur:Whole|Pos:-6
|Bar|Style:MasterRepeatOpen
|Note|Dur:Whole|Pos:-5
|Bar
|Note|Dur:Whole|Pos:-4
|Bar
|Note|Dur:Whole|Pos:-3
|Bar
|Ending|Endings:1
|Note|Dur:Whole|Pos:-2
|Bar|Style:MasterRepeatClose
|Ending|Endings:2
|Note|Dur:Whole|Pos:-1
|Bar
|Note|Dur:Whole|Pos:0
|Bar|Style:LocalRepeatClose|Repeat:2
!NoteWorthyComposerClip-End
305
General Discussion / Re: Copying staffs more efficiently
Quote from: Opagust –
No, there isn't. A user tool can't process two files at a time.
So the only way is to do it manually.

I wasn't pleased with my quick answer, so did a little thinking and came up with a 2 step solution. Attached is a new version of the tool CopyStaff, with the possibility to choose the option 'another file' as target. I you do so, the text representation of the staff and its lyrics will be shown in the output window. You then have to select all (CTRL+A) and copy it in your clipboard(CTRL+C).
The other attached user tool 'PasteStaff' is then to be run on the target file, where you have to  paste the content of your clipboard in the input window.
307
General Discussion / Re: Windows Media Player: no sound when playing midi files
Quote from: Lawrie Pardy –
I like Van Bascos Karaoke player for MIDI - pretty sure it still works for 10...

http://www.vanbasco.com/karaokeplayer/

It took me some time to find the setup window to choose the MIDI output, but now it works perfectly!
It even shows the lyrics (it's a karaokeplayer afer all). But I wonder: if I have different lyrics on different staffs (channels), can I choose which one is showed? I'm planning to look for it myself but now my grandchildren are asking for priority.
310
User Tools / Re: Dialog based Global Modification Tool: GlobMod.og
Version 1.2.4 :
 - If 1 or more User Objects GlobModParms are present, you can specify whether they should be processed (for each of them) and/or if you want to process a new set of parameters.
 - Correction or a bug for inserting 'Endings'.

See new attachment in original post.
Remark: you need NWC version 2.75 or higher.
311
General Discussion / Re: Windows Media Player: no sound when playing midi files
Quote from: Richard Woodroffe –
I imagine that it's the Windows 10 creators update.

They did quite a bit of work with sound and audio processes. In my case, it cured a problemWM I was having that I actually thought was a hardware problem.  However, you do a Google search for "Windows 10 creators update audio not working", you will see that there are many problems with the update from an audio point of view.

I have no problem with sound in general, and Windows Media Player has no problem with mp3 files. It's WMP + midi that doesn't work anymore.
313
General Discussion / Re: Enharmonic Spelling - Note Entry
Another revision attached.
  • Processing of tied notes: Corrected.
  • Change report:
    • Intermediate changes are now omitted in the report. E.g. when C# is changed to Db, a following C in the same measure will first recieve the explicit accidental #, next the enharmonic change to Db will be applied to that note as well, and after processing all notes of that measure, the accidental b wil be removed due to the preceding Db. In short: C -> Db/ Db -> D will now be reported as C -> D.
    • Line feed after all changes in a  measure, instead of after each change.


316
General Discussion / Re: Enharmonic Spelling - Note Entry
Quote from: Opagust –
I give up...  :'(
No, I didn't. It was a challenge I could not resist.
Before I will publish it in the User Tools subforum, I look forward to your expressions of gratitude, comments, more wishes, criticism, bug reports,...

With this tool you can replace notes with their enharmonic equivalents. It works on a selection of a staff, or the whole active staff, if you don't select anything.
There are several options you can choose from(see below).
Independent of the chosen option:
- if a note gets an accidental that's also present in the key signature, it will be omitted;
- if a note is to be be changed, all following notes in the same measure or tied in the next measure are investigated, even when they are not part of your selection:
  ° before the change: a following note with an implicit accidental, inherited from the preceding note will receive a forced accidental (e.g. if C# is changed to Db, a following C will be changed to C#);
  ° after the change: if a following note has no accidental and has the same name as the changed note (with accidental), it will recieve a natural accidental.
- if one or more notes in a measure had to be changed, all unnessary accidentals in that measure are removed(e.g. if C# is changed to Db, a following Db will be changed to D)..
 
Available options:
- 'No sharps': All sharps are replaced.
- 'No flats': All flats are replaced.
- 'No doubles': All double sharps and double flats are replaced.
- 'Preferably naturals': If a enharmonic equivalent without accidental is possible, use that.
- 'Avoid forced naturals': if a natural accidental is caused by an preceding note with an accidental, this preceding note is replaced by its enharmonic equivalent.
- 'Common prefered accidentals': A# becomes Bb, Db becomes C#, D# becomes Eb, Gb becomes F#, Ab becomes G#.
- 'Sharps up, flats down': if the next note is a tone or a semitone higher, use a sharp; if it is a tone or a semitone lower, use a flat (not applicable to chords and restchords).
- 'Your changes': You can choose one or more items from a list of all possible enharmonic changes. (You need version 2.75a beta 11 or higher to use this option).

25/07/2017: removed attachment, see revised version in reply #30 .
320
User Tools / Re: Audit ties
I just realised I didn't take accidentals into account. Correction will follow...
322
General Discussion / Re: Enharmonic Spelling - Note Entry
Quote from: William Ashworth –
In sharp keys, leave everything sharp; in flat keys, make everything flat; in C (or when no signature exists), follow my original "brute force" recommendation. Then adjust as suggested in my second refinement.

If I do understand, if there's no key, there are two options: most common and with refinement:

Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.751)
|Editor|ActiveStaff:1|CaretIndex:6|CaretPos:-2
|SongInfo|Title:"Enharmonic Test"|Author:"<Name>"|Lyricist:""|Copyright1:"Copyright © 2017 <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:"Most common"|Label:"Most common"|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:Treble
|Note|Dur:4th|Pos:-6
|Note|Dur:4th|Pos:#-6
|Note|Dur:4th|Pos:-5
|Note|Dur:4th|Pos:b-4
|Bar
|Note|Dur:4th|Pos:-4
|Note|Dur:4th|Pos:-3
|Note|Dur:4th|Pos:#-3
|Note|Dur:4th|Pos:-2
|Bar
|Note|Dur:4th|Pos:#-2
|Note|Dur:4th|Pos:-1
|Note|Dur:4th|Pos:b0
|Note|Dur:4th|Pos:0
|Bar
|Note|Dur:4th|Pos:#1
|Note|Dur:4th|Pos:1
|Note|Dur:4th|Pos:0
|Note|Dur:4th|Pos:b0
|Bar
|Note|Dur:4th|Pos:-1
|Note|Dur:4th|Pos:#-2
|Note|Dur:4th|Pos:n-2
|Note|Dur:4th|Pos:#-3
|Bar
|Note|Dur:4th|Pos:-3
|Note|Dur:4th|Pos:-4
|Note|Dur:4th|Pos:b-4
|Note|Dur:4th|Pos:-5
|Bar
|Note|Dur:4th|Pos:#-6
|Note|Dur:4th|Pos:n-6
|Note|Dur:4th|Pos:-7
|AddStaff|Name:"Refinement"|Label:"Refinement"|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:4
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Clef|Type:Treble
|Note|Dur:4th|Pos:-6
|Note|Dur:4th|Pos:#-6
|Note|Dur:4th|Pos:-5
|Note|Dur:4th|Pos:#-5
|Bar
|Note|Dur:4th|Pos:-4
|Note|Dur:4th|Pos:-3
|Note|Dur:4th|Pos:#-3
|Note|Dur:4th|Pos:-2
|Bar
|Note|Dur:4th|Pos:#-2
|Note|Dur:4th|Pos:-1
|Note|Dur:4th|Pos:#-1
|Note|Dur:4th|Pos:0
|Bar
|Note|Dur:4th|Pos:b2
|Note|Dur:4th|Pos:1
|Note|Dur:4th|Pos:0
|Note|Dur:4th|Pos:b0
|Bar
|Note|Dur:4th|Pos:-1
|Note|Dur:4th|Pos:b-1
|Note|Dur:4th|Pos:-2
|Note|Dur:4th|Pos:b-2
|Bar
|Note|Dur:4th|Pos:-3
|Note|Dur:4th|Pos:-4
|Note|Dur:4th|Pos:b-4
|Note|Dur:4th|Pos:-5
|Bar
|Note|Dur:4th|Pos:b-5
|Note|Dur:4th|Pos:-6
|Note|Dur:4th|Pos:-7
!NoteWorthyComposer-End
323
General Discussion / Re: Enharmonic Spelling - Note Entry
Quote from: William Ashworth –
(..)Two refinements would help:

  • First(..)
  • Second(..)

Over to you....

Do you mean: first do the first refinement and next the second? In that case, with a flat key G# would be first changed to Ab and, if the next note has a higher pitch, back to G#. Is that what you mean?

BTW, I did know the relation between the black and white keys. I didn't know what enharmonic meant and was to lazy to google it.
324
General Discussion / Re: Enharmonic Spelling - Note Entry
Quote from: pianist14 –
Is it possible for Noteworthy to favor flats over sharps in note entry? It seems the default is to favor sharps. For example in the Key of C if I want B flat, or D flat etc.  How do I get the program to select these notes as opposed to A# or C#.  Is there an option to toggle this default?
Maybe I can write a user tool for this, but therefor I need more precise specifications.
(I'm not a musician, just a singer with no knowledge of enharmonic spelling. I think I know that C major means no key signature, but that's about everything.)
Note that a user tool can't change the way NWC chooses between flat or sharp when using the piano toolbar, but you could modify them afterwards by  running the tool and give the needed input.
So what user input is required and what should be the resulting action for each possible input?
326
User Tools / Audit ties
I wrote this tool in response to this topic: Persistent (stuck) notes

It inspects all tied notes in all staves and reports the folllowing situations:
1. The destination note of a tie is muted and the source note is not, or vice versa.
2. A tie has no destination.
3. There are 1 or more notes between cource and destination note.

The first and second situation cause a hanging sound on playback and should be corrected, the 3th is just a notification.

Installation:Download the attached file and drag and drop it upon any open NWC file
Any suggestions or bug reports are welcome!

11/07/2017: new version to take accidentals into account
327
General Discussion / Re: Persistent (stuck) notes
I just discovered something that might be useful:
The bar number panel shows a (very) small red 'x' above a muted note in the active staff.
See measure 8 in the attachment
329
User Tools / Re: How to (1) alter code and (2) get it back into the notation file
Quote from: William Ashworth –
The usual approach for situations like that is layering  - especially when it involves two independent voices, like soprano and alto. One voice on one staff, the other voice on a second staff that is layered with the first. This allows you to cross voices, as well.

Just layering two voices  entered on seperate staves can give a messy result. I wrote a user tool that tries to do better  ;D :
Layering voices
330
User Tools / Re: How to (1) alter code and (2) get it back into the notation file
Quote from: wal –
One reason I want to do this is to get RestChords into the music.  I see the notation and the code for it in a piece I downloaded, but I don't think it's possible to insert a RestChord in NWC itself. 
Yes, it's possible: first enter the rest (space bar) and then the note(s) with CTRL/Enter. Limitation: the note must not be shorter than the rest.

Note: I hadn't seen the post of hmmueller when I was typing mine. It's more complete.
331
User Tools / Re: Number notation tool
As I explained in an earlier reply, I didn't know about number notation until recently and I wrote this tool based on the explanation by a fellow choir member. So I don't have any written documentation. (The wikipedia link describes 1 version, but it doesn't correspond in all details to the method used in my tool.)
So my tool is just what it is: it's written for the persons that are using that particular method and eliminates the need to rewrite a classical score by hand. If you don't need it, you don't have to download and use it.
But if you do, I would be happy to receive suggestions for improvements.
Quote
NWC uses double sharps and double flats, and number-notation doesn't
Double sharps and double flats could be added ('//' and '\\' ?), if needed.
Quote
Special attention has to be paid on the staccato dot since it looks like the octave changer...
Staccato is designated by a single quote above the number.
332
User Tools / Re: Number notation tool
Quote from: David Palmquist –
I'm not sure I understand the purpose or usage of number notation, but that doesn't matter. 
I gather a whole note is created with a plain number followed by three dots and a half note is a plain number with one dot following it.
Does this type of notation provide for double sharps and double flats?

I didn't know myself of any number notation method until recently, when a new member joined our choir. He's also singing in another choir for many years and they use this number notation for learning their songs. So for the songs of our choir, he had to write himself  the number notation above the staff of his voice, since he's not familiar to sing from a 'normal' score.
When I noticed his notations, I was intrigued and asked him to explain it to me. I then wrote a first version of my tool. I received also feedback from the director of his other choir, which finally lead to a version  believed I could share with the NWC community.

You're right about the whole and halve notes.

Double sharps and double flats are indeed not supported (and I don't think they occur in any of our songs).

333
User Tools / Re: Number notation tool / Bug fix!
I fixed a bug in my latest version: when recreating a number notation staff, the old one was removed (OK) but the new created one was for the staff following the active staff (not OK).
New version in original post
334
User Tools / Re: Number notation tool
I replaced the file in the original post with an updated version to automatically replace a previously created number notation staff (instead of adding a new one)
335
User Tools / Re: Number notation tool
Quote from: Mike Shawaluk –
  • I noticed that running the tool a second time (for example, after making changes to the source staff), it will insert an additional number notation staff, rather than replace the previous one. I assume that is intended behavior, and that the user would need to manually delete the staff added by the tool's previous invocation.
  • I am curious why you elected the user tool approach for this add-on, instead of perhaps creating this with a StaffSig plugin object.  On the surface, it seems to me that such an object could be created that would render the number notation above the existing notes automatically, and would effectively auto-refresh whenever changes were made to the underlying notation.

  • I made a change to automatically delete a previous created number notation staff.
  • That crossed my mind, but I'm not ver experienced in writing user object plugins. I would have to find out how to draw everything with keeping the alignment above the lyrics. Maybe it's not that difficult, but that's something you would know better than me.

336
User Tools / Number notation tool
This tool inserts a 'number notation staff' above the active staff. The inserted staff doesn't have ledger lines and has the notes made invisible.

* Each note is then represented with a number from 1 to 7 (a rest = 0). Notes with accidentals are denoted with a '/' (sharp) or '\' (flat) strikethrough. A dot above or under the number means an octave higher or lower.

* The plain number represents a quarter note. Each dash above the number halves the note length: one dash represents an eighth note, two represent a sixteenth note, and so on (analogous to the number of flags and beaming). Dots after a note lengthen it, each dot by the length of a quarter note (these dots are also used for slured notes). 

* If a key signature is present, you have to choose between two base methods to assign numbers to the notes:
  1. '1=C', that means 2=D, 3=E, ... . In this method, every accidental according to the key signature is denoted by a strikethrough number.
  2. 'According to Key Signature'. In this method the base number is chosen thru a transposition. The key signature is indicated by '1=x' for a major signature, '6=x' for a minor one. The transposition is determined in a way that only the explicit accidentals need a strikethrough number.
  Remark: In both methods the distance between 3 and 4, resp. 7 and 1 is a semitone.
 
 
* You also have the option to make the active staff invisible. In that case, the lyrics are copied to the created number notation staff. If you choose to leave the active staff visible, the lyrics are moved above the staff (unless they are placed already there).

*Two special typefaces are needed:
° for dots and dashes, a 'Symbol' typeface of size 16
° for the strikethrough, the same typeface as for the numbers (i.e. StaffLyric), but with a larger size (+3)
Therefor,  unless they are  already present, the tool will set such fonts in 2 unused 'User Fonts'.  If no free user font can be found, an error message will be displayed.

Remark: Chords are not supported.

02/05/2017: Modification: removing of previously created number notation staff.
08/05/2017: I fixed a bug in my latest version: when recreating a number notation staff, the old one was removed (OK) but the new created one was for the staff following the active staff (not OK).
16/06/2023: Changes to properly create text items.
17/06/2023: Additional changes for NWC v2.8 Beta1 + check on chords and restchords .
21/06/2023: Show slurs and ties (User object 'slur.ms' needs to be installed)
08/07/2023:
- Some positional finetuning.
- Correction of bugs that caused an error.
- Chords and restchords are now permitted, but when they are present, a warning is shown that only one note of the chord gets a number in the number staff.
18/07/2023: Correction: whole note translates to number + dot instead of 2 numbers
337
User Tools / Re: Dialog based Global Modification Tool: GlobMod.og
Version 1.2.3 : Correction of 2 bugs
- Prompts for numerical values didn't work anymore
- Modification of vertical offset in special endings: incorrect property name

See attachment in original post
Installation:
- Download the new version from the original post
- Drag and drop it upon any open NWC file.
338
User Tools / Re: Layering voices
I discovered and corrected a bug in the lua script (removing articulations in the lower staff was also done on multi measure rests, wich caused an error).
You can download the new version in the original post
342
User Tools / Re: Dialog based Global Modification Tool: GlobMod.og
Version 1.2.2
- Attempt to make this tool more user friendly
   * Presenting only the Object Types that are present in the selection or active staff
   * Presenting the items of the selection lists in alphabetical order
   * Additional helpscreen when prompting for saving the parameters
- Correction of a bug when modifying triplets

Installation:
- Download the new version from the original post
- Drag and drop it upon any open NWC file.
343
General Discussion / Re: Dynamic variance in trill, tremolo and arpeggio
You have to edit the properties of the dynamics :  set 'Change Channel Volume' to the value of 'Custom Note Velocity'. (Don't forget to check the 2nd box).

Code: [Select · Download]
!NoteWorthyComposerClip(2.75,Single)
|Dynamic|Style:f|Opts:Volume=92|Pos:-9.5|Wide:Y
|RestChord|Dur:Half|Opts:Stem=Down,Diminuendo,ArticulationsOnStem,Muted,HideRest|Dur2:Whole|Pos2:10
|User|Tremolo.ms|Pos:1
|RestChord|Dur:Half|Opts:Stem=Down,Diminuendo,ArticulationsOnStem,Muted,HideRest|Dur2:Whole|Pos2:b11
|Bar
|Dynamic|Style:pp|Opts:Volume=30|Pos:-10|Wide:Y
!NoteWorthyComposerClip-End
You were a little faster, Rick! ;)
344
User Tools / Re: Make Rehearsal File
I rewrote this tool in Lua, see attachment in first post.
Changes:
- If the active staff's name ends with '/Layered'(*)or '/Muted', then a staff with a name = the part before the '/' will also be treated as Foreground Staff.
- The help text is rewritten (less technical and hopefully more comprehensible). I also included a reference to Tina Billet's formula, with is used to calculate the Volumes and Velocities of the dynamics (Document 'Dynamics.pdf' in http://nwc-scriptorium.org/helpful.html#Explanations).

(*) If you executed the tool 'LayerVoices.og', the original staves were set invisible and the layering was done on visible, muted copies of these staves.
345
User Tools / Re: Layering voices
I rewrote this tool in lua (see attachment in previous post).
Changes: 
- Articulations are only preserved on the upper staff.
- The 'Unlayer' action has been removed. Instead the original, unlayered staves are made invisible and the layering + modifications are done on copies if those staves (with names ending with'/layered'), which are muted.
346
General Discussion / Re: Lyric Placement on Layered Staves
If the bass lyrics clash with the soprano lyrics, they're on different systems.
I think that can't be changed with a boundary offset.
Maybe you can solve it with the insert of a page break to have less systems on one page?
Be sure that the option 'Justify printed systems vertically' is checked.
347
General Discussion / Re: Copying staffs more efficiently
Maybe this tool can ease your life, David.
It copies the active staff .
To install, just download it, start NWC, open a file and drag the downloaded file upon it.

You can then run it via 'Tools/User Tool..' or just ALt+F8.
348
Object Plugins / Re: LineSpan.nw
Quote from: NoteWorthy Online –
Notice: This object plugin requires NWC 2.75a, which is currently in beta. It cannot be used in Version 2.75.
Actually, it requires beta 5.

Quote
An optional text instruction can accompany the line.
The text 'eats' the start of the line. This is espacially annoying when you set Front Cap to 'stroke' or 'arrow'. I would prefer the text above the line.
350
General Discussion / Re: Boundary offset works strangely - and looks strange
I also have encountered this problem several times. Rick's solution seems (as always) to solve the problem in a nice way. I'll try it next time.

But what I noticed now when looking at and experimenting a bit with the example files in that topic: Increasing the 'Line Count' for the lyrics  automatically increases the 'Lower Boundary' (for lyrics under the staff) in the Staff Properties by 4 for every added line.

The 'Change Boundary Offset' on the other hand is not affected by changing the number of lyric lines.

BTW: After lowering the 'Line Count' by 1, a line of lyrics disappears (as expected), but it won't reappear if you restore the line count to its original value!