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

51
General Discussion / Re: Chord/measure length problem
Thanks, Bart, for your comment.

After a good night's sleep and a pleasant saturday with my grandchildren, I decided to redesign my tool to create layered staves.

I think the trigger for using layers is  the presence of different 'voice' tags in the xml file. Since I read the file into a graph-like object, I can inspect it to search for these tags and create the layered staves, before starting the actual processing.

So now I'm gonna take a safety copy first and then see how far I will get with this new insight. I may or may not work, and only by trying I will found out...
 
52
General Discussion / Re: Chord/measure length problem
Thanks for your answers, Richard and Melismata.

And I found the explanation in the NWC help file :

Quote
Lastly, it is important to understand that only the smaller duration item is actually used in aligning notes on a score. When creating split-stem chords, the notes in the larger duration are ignored when formatting and alignment is performed with respect to other notes above and around this item
.

So that solved the problem of the reason for the measure misalignment.

BUT!

That leaves me with another problem, because my example was the result of the user tool I'm working on, to convert MusicXML files to nwctxt.

You find in attachment an extraction of the original musicxml file, i.e. the part that concerns the particular measure.
I' ll try to explain the elements that define the notes and their place in the measure:
- Some elements have a 'voice 1' tag, some have 'voice 2'.
- The voice 1 elements are a 'forward' of a quarter, followed by a quarter dotted B and eighth C. So this adds up to 3 quarters.
- Then there's a 'backup' tag of 3 quarters, which brings us back to the start of the measure.
- Then follow the voice 2 elements: a chord quarter D and quarter F, followed by a quarter F and quarter G. This also ads up to 3 quarters.

This seems totally logical to me: because of the 'forward' tag, the dotted quarter of voice 1 starts at the second beat and the eighth note at the second half of beat 3.
The empty place at the start is then filled with a quarter chord for voice 2.
Now, according to the documentation of MusicXML, a forward tag can repressent an invisible rest, which, if applied here, would result in a restchord at the start of the measure, but it would be a quarter rest to be in accordance to the forward tag. But for NWC a restchord with an eighth rest is needed at the third beat. I don't see how to insert this behaviour in my tool.

So the fact that NWC only conciders the shortest length for chords with 2 different lengts, is in contradiction with the logic of MusicXML(which seems more logical to me).

Conclusion: I know now how it should be done in NWC, but I don't know how to automate it n my tool.
53
General Discussion / Chord/measure length problem
When you compare the extracts of the original pdf_score and the resulting nwc-file (see attachments), you notice that the measure in the second staff of the nwc-file is too long.

What's going wrong?

Code: [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|Bar|SysBreak:Y
|Chord|Dur:4th|Pos:-5,-3|Opts:Stem=Up,Lyric=Never
|Chord|Dur:4th,Slur|Pos:-3|Opts:Stem=Down,Slur=Upward,Lyric=Never|Dur2:4th,Dotted|Pos2:0
|Note|Dur:4th,Slur|Pos:-2|Opts:Stem=Down,Slur=Upward,Lyric=Never
|Note|Dur:8th,Slur|Pos:1|Opts:Stem=Up,Lyric=Never
!NoteWorthyComposerClip-End
54
User Tools / Re: Test Release: nwc2musicxml
I started to write a tool for converting musicxml to nwctxt.
Until a month ago I never opened a musicxml file. But I found the documentation on https://www.musicxml.com/. There's a tutorial, but it doesn't cover everything, and the rest of the documantation isn't very easy to master. Another great help was lasonic's tool.  So I could study the xml-files from several of my own nwctxt files, which are all choral scores.
My next step will be to download some bigger files from the scriptorium and run lactoniscs tool on them, so I can compare the output of my tool with the original nwc-file.

But after that I'd like to test with 'external' xml files. So If you could send me such files, with their corresponding pdf, I would be very grateful. You can include them as a reply to this post, or send a personal message.


55
User Tools / Search & Modify
A new tool 'Search & Modify' is added to the multitool PYNWC: https://forum.noteworthycomposer.com/?topic=10042.0 (version 1.4)

With this tool you can search a score for all objects of a given type that have some given properties.
Next you can:
    - Inspect where the occur (staff, measure number), with their nwctxt presentation.
    - Choose an action: 'Modify' or 'Delete.
    - For the action 'Modify':
        - Indicate which property(ies) you want to modify.
        - Fill in the new value(s) in a popup, that resembles the 'Notation Properties' window in NWC for the given object type.
Remarks:
    - At every moment you can leave to undo your choices or modifications.
    - On the main window, every input field is a combo box from you can select the appropriate value.
    Only those values that are of interest are presented.
    For instance: If you specified 'Clef' as object type and all clefs have the same value for 'Octave Shift',
    that property is not present in the 'condition' lines.
    .
Detailed description:
    The main window consists of following parts, from top to bottom:
        - The frame 'Make your choices' to specify:
            - Where to search (selection, active staff, all staves or visible staves).
            - The object type to search for.
        - The 'Conditions' frame where you can set up to 6 search criteria.
          If you specify more than 1 condition for the same property, then all the objects are selected that satisfy any of these criteria.
          Criteria for different properties must be satisfied separately.
          At the bottom of the conditions frame you can see a verbose description of your selection criteria.
          It's updated after every completed condition line.
        - A status line, that indicates:
            - The object type to search for.
            - The number of objects found (dynamically updated).
            - A button 'Show'.
                When clicked a popup window will show the location and nwctxt presentation of the objects that satisfy the criteria.
        - The 'Action' line, with choices 'Modify' or 'Delete'
        - The 'Modifications' frame, where (if your action = 'Modify') you have to specify at least 1 and at most 4 properties.
            Only those properties can be specified that are present in the 'Notation Properties' window for the object type.
            e.g.: for a note you can't change the position, duration, accidental, staccato,....
        - Three buttons:
            - The action button. The caption will indicate the action you chose.
                If the action is 'Modify', a popup is presented that resembles the 'Notation Properties' window of NWC,
                in which the fields contain the values of the first object found.
                Only the fields for the properties you selected in the modification frame will be enabled.
                After you entered your new values, these will be set in each found object.
                All the other properties of each object remain unchanged.
            - The 'Reset' button. When clicked, every input is cleared so you can restart your input.
            - Finally a 'Cancel' button to leave without any action taken.

56
User Tools / Re: Multitool PYNWC
Version 1.4: New tool added : 'Seach & Modify'

With this tool you can search a score for all objects of a given type that have some given properties.
Next you can:
    - Inspect where the occur (staff, measure number), with their nwctxt presentation.
    - Choose an action: 'Modify' or 'Delete.
    - For the action 'Modify':
        - Indicate which property(ies) you want to modify.
        - Fill in the new value(s) in a popup, that resembles the 'Notation Properties' window in NWC for the given object type.
Remarks:
    - At every moment you can leave to undo your choices or modifications.
    - On the main window, every input field is a combo box from you can select the appropriate value.
    Only those values that are of interest are presented.
    For instance: If you specified 'Clef' as object type and all clefs have the same value for 'Octave Shift',
    that property is not present in the 'condition' lines.
    .
Detailed description:
    The main window consists of following parts, from top to bottom:
        - The frame 'Make your choices' to specify:
            - Where to search (selection, active staff, all staves or visible staves).
            - The object type to search for.
        - The 'Conditions' frame where you can set up to 6 search criteria.
          If you specify more than 1 condition for the same property, then all the objects are selected that satisfy any of these criteria.
          Criteria for different properties must be satisfied separately.
          At the bottom of the conditions frame you can see a verbose description of your selection criteria.
          It's updated after every completed condition line.
        - A status line, that indicates:
            - The object type to search for.
            - The number of objects found (dynamically updated).
            - A button 'Show'.
                When clicked a popup window will show the location and nwctxt presentation of the objects that satisfy the criteria.
        - The 'Action' line, with choices 'Modify' or 'Delete'
        - The 'Modifications' frame, where (if your action = 'Modify') you have to specify at least 1 and at most 4 properties.
            Only those properties can be specified that are present in the 'Notation Properties' window for the object type.
            e.g.: for a note you can't change the position, duration, accidental, staccato,....
        - Three buttons:
            - The action button. The caption will indicate the action you chose.
                If the action is 'Modify', a popup is presented that resembles the 'Notation Properties' window of NWC,
                in which the fields contain the values of the first object found.
                Only the fields for the properties you selected in the modification frame will be enabled.
                After you entered your new values, these will be set in each found object.
                All the other properties of each object remain unchanged.
            - The 'Reset' button. When clicked, every input is cleared so you can restart your input.
            - Finally a 'Cancel' button to leave without any action taken.

57
General Discussion / Re: Selectors
This is a selector I made years ago.
It contains all items to control the flow.
Since the title contains '(&f), it pops up when you press the 'f' key ().
The selector files are stored in the config folder with names '100.nwc' to '10f.nwc'
If you want to download this example, make sure not to choose a name that already contains another selector.


Code: [Select · Download]
!NoteWorthyComposer(2.751)
|Editor|ActiveStaff:24|CaretIndex:2|CaretPos:2
|SongInfo|Title:"Flow Selector (&f)"|Author:""|Lyricist:""|Copyright1:""|Copyright2:""
|PgSetup|StaffSize:16|Zoom:5|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|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:"_"|Label:"glyph"|Group:"_"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:7|BoundaryBottom:7|Lines:1|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Spacer|Width:50
|Bar|Style:MasterRepeatClose|Visibility:Always
|Text|Text:"(f)"|Font:StaffItalic|Pos:-3
|Spacer|Width:0
|AddStaff|Name:"Single"|Label:"Single"|Group:"1"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:6|BoundaryBottom:6|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Bar|Visibility:Always
|AddStaff|Name:"Double"|Label:"Double"|Group:"1"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:6|BoundaryBottom:6|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Bar|Style:Double
|AddStaff|Name:"Section Open"|Label:"Section Open"|Group:"1"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:6|BoundaryBottom:6|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Bar|Style:SectionOpen
|AddStaff|Name:"Section Close"|Label:"Section Close"|Group:"1"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:6|BoundaryBottom:6|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Bar|Style:SectionClose
|AddStaff|Name:"Master Repeat Open"|Label:"Master Repeat Open(&r)"|Group:"1"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:6|BoundaryBottom:6|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Bar|Style:MasterRepeatOpen
|AddStaff|Name:"Master Repeat Close"|Label:"Master Repeat Close"|Group:"1"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:6|BoundaryBottom:6|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Bar|Style:MasterRepeatClose
|AddStaff|Name:"Local Repeat Open"|Label:"Local Repeat Open"|Group:"1"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:6|BoundaryBottom:6|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Bar|Style:LocalRepeatOpen
|AddStaff|Name:"Local Repeat Close"|Label:"Local Repeat Close"|Group:"1"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:10|BoundaryBottom:6|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Bar|Style:LocalRepeatClose|Repeat:2
|AddStaff|Name:"Broken Single"|Label:"Broken Single"|Group:"1"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:6|BoundaryBottom:6|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Bar|Style:BrokenSingle
|AddStaff|Name:"Broken Double"|Label:"Broken Double"|Group:"1"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:6|BoundaryBottom:6|Lines:5|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Bar|Style:BrokenDouble
|AddStaff|Name:"1st Ending"|Label:"1st Ending"|Group:"Spcl"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:5|BoundaryBottom:5|Lines:0|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Ending|Endings:1
|AddStaff|Name:"2nd Ending"|Label:"2nd Ending"|Group:"Spcl"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:5|BoundaryBottom:5|Lines:0|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Ending|Endings:2
|AddStaff|Name:"3rd Ending"|Label:"3rd Ending"|Group:"Spcl"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:5|BoundaryBottom:5|Lines:0|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Ending|Endings:3
|AddStaff|Name:"4th Ending"|Label:"4th Ending"|Group:"Spcl"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:5|BoundaryBottom:5|Lines:0|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Ending|Endings:4
|AddStaff|Name:"Continue Ending"|Label:"Continue Ending"|Group:"Spcl"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:5|BoundaryBottom:5|Lines:0|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Ending
|AddStaff|Name:"Conclude Ending"|Label:"Conclude Ending"|Group:"Spcl"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:5|BoundaryBottom:5|Lines:0|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:1
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Ending|ClosedBracket:Y
|AddStaff|Name:"Segno"|Label:"Segno"|Group:"Flows"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:5|BoundaryBottom:5|Lines:0|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
|Flow|Style:Segno|Pos:0|Wide:Y|Color:1|Visibility:Always
|AddStaff|Name:"D.S. al Coda"|Label:"D.S. al Coda"|Group:"Flows"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:5|BoundaryBottom:5|Lines:0|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:3
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Flow|Style:DSalCoda|Pos:0|Wide:Y|Color:1|Visibility:Always
|AddStaff|Name:"To Coda"|Label:"To Coda"|Group:"Flows"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:5|BoundaryBottom:5|Lines:0|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
|Flow|Style:ToCoda|Pos:0|Wide:Y|Color:1|Visibility:Always
|AddStaff|Name:"Coda"|Label:"Coda"|Group:"Flows"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:5|BoundaryBottom:5|Lines:0|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:5
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Flow|Style:Coda|Pos:0|Wide:Y|Color:1|Visibility:Always
|AddStaff|Name:"Fine"|Label:"Fine"|Group:"Flows"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:5|BoundaryBottom:5|Lines:0|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:5
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Flow|Style:Fine|Pos:0|Wide:Y|Color:1|Visibility:Always
|AddStaff|Name:"Da Capo"|Label:"Da capo"|Group:"Flows"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:5|BoundaryBottom:5|Lines:0|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:5
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Flow|Style:DaCapo|Pos:0|Wide:Y|Color:1|Visibility:Always
|AddStaff|Name:"D.C. al Coda"|Label:"D.C. al Coda"|Group:"Flows"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:5|BoundaryBottom:5|Lines:0|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:5
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Flow|Style:DCalCoda|Pos:-1|Wide:Y|Color:1|Visibility:Always
|AddStaff|Name:"D.C. al Fine"|Label:"D.C. al Fine"|Group:"Flows"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:5|BoundaryBottom:5|Lines:0|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:5
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Flow|Style:DCalFine|Pos:1|Wide:Y|Color:1|Visibility:Always
|AddStaff|Name:"Dal Segno"|Label:"Dal Segno"|Group:"Flows"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:5|BoundaryBottom:5|Lines:0|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:5
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Flow|Style:DalSegno|Pos:-1|Wide:Y|Color:1|Visibility:Always
|AddStaff|Name:"D.S. al  Fine"|Label:"D.S. al  Fine"|Group:"Flows"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:5|BoundaryBottom:5|Lines:0|Color:Default
|StaffProperties|Muted:N|Volume:127|StereoPan:64|Device:0|Channel:5
|StaffInstrument|Trans:0|DynVel:10,30,45,60,75,92,108,127
|Flow|Style:DSalFine|Pos:1|Wide:Y|Color:1|Visibility:Always
!NoteWorthyComposer-End
58
User Tools / Re: Multitool PYNWC
Version 1.3, new tools added:
- Configure new song
- Show collapsible sections

Tool 'Configure new song':
Run this tool after you created and saved a new file from a template, and before you start changing staff labels, channels,
..., removing some staves, inserting tempo, key and time signatures, dynamics, copying and pasting...
All that can be done in one go, with this tool.

On the main dialog window, you see on the left a list of all the staves with attributes name, label, group, channel, volume, stereo pan, muted and visible.
Each of these attributes is changeable. In front of each staff line is a checked check box. Unchecking a box will remove the corresponding staff from the file (1).

Via the buttons at the right you can configure the properties of objects you want to be inserted.
Clicking one of them will open a dialog window, similar to the correspondent 'Notation Properties' window of NWC.
They have 4 buttons at the right; 'Create', 'Modify', 'Remove' and 'Cancel'.
    - With 'Create you schedule the insertion of the correspondent object.
    - With 'Modify' you can change the properties of a scheduled object.
    - With 'Remove' you undo a scheduled insertion.
    - With 'Cancel' you quit the window without any resulting action.
At the bottom of the main window is indicated which objects are scheduled for insertion.

When clicking the 'OK' button at the bottom of the main dialog window (2):
    - the staff changes will be carried out (3);
    - the unchecked staves will be removed;
    - the scheduled objects will be created and inserted in every staff, after the clef;

(1) Hint: You may want to use a template with all the staves that you'll ever be needing, and uncheck those that  you
don't want to be present in the new file.

(2) As in every other tool, the changes will not be saved until after your confirmation.

(3) As a next step you may want to run the tool 'Set staff properties' to carry out within one dialog window all
other needed staff changes (general, visual, midi, instrument, default dynamic velocities).

Tool 'Show collapsible sections':
In NWC you can mark collapsible sections with the boundary objects 'Start a collapsible section' and 'Cancel/forbid collapse from this bar'.
But then it's very hard to see them in the editor, you'll have to use 'Print preview' to see the effect.

This tool is intended to solve that problem by coloring the notes, chords and rests of a collapsible section with a color of your choice.
After that it's easy to locate these sections in the editor.

Remark: You still have to do a print preview to see the real effect, since collapsing will only start and end at system breaks.
But at least now you know in what part of your score they occur.

The tool show a window consisting of 4 frames:
    - 'Collapsible sections': Shows the staves with collapsible sections and the measures from - to.
    - 'Choose Collapse Color'
    - 'Colors in collapsible sections': Shows which colors are now present in the collapsible sections for the notes, chords and rests.
    - 'Options': If there's both 'Default' and at least 1 'Highlight' color in the collapsible sections, you can indicate:
        - Change the color of all notes/chords/rests in the collapsible sections.
        - Keep the non default color(s) unchanged.

You can click 'OK' to do the changes, or 'Cancel' to leave without changing anything.
61
General Discussion / Where are the colors from Tools/Options/Color Tab stored?
Hello,
Via 'Tools/Options/Color Tab' you can change the colors. But I wonder: where are the stored?
I have written some tools where one can set the color of an object or staff, but I can't show the exact color next to the names ('Highlight 1', ...) in the dialog box.
If I knew where I could find the color values from the Tool/Options, I could present a more user friendly dialog box.
63
User Tools / Audit score
A new tool 'Audit score' is added to the multitool PYNWC: https://forum.noteworthycomposer.com/?topic=10042.0 (version 1.3)

Before running this tool, be sure to select in the tool parameter window the audit you want to be performed.
Also specify the process mode: all staves, visible staves, active staff or the selection.
Depending on the audit you choose, additional options will be shown. See below for details per audit.

- Audit accidentals:
    Via the tool parameters you can select one of this options for handling natural accidentals:

        - Leave naturals unchanged
        - Make courtesy accidentals
        - Remove accidentals

    This audit acts on any unnecessary accidentals assigned to notes.
    It compares a note with an accidental with the 'running' key signature, which is determined by the previous key
    signature + the preceding accidentals in the measure.
    If the accidental matches the running signature, and it's not a courtesy accidental, it will be removed if it's
    not a natural.
    For naturals the action taken depends on the option in the tool parameters.

- Audit bar lines:
    Audits the bar line alignment.
    In the tool parameters you can indicate whether you want to admit a short first measure (anacrusis).
    If the audit finds a standard bar line that is not aligned properly, it is removed and a new bar line is added in
    the proper place. As a result, notes and chords can be split and tied.

    * Measures with a special ending that is not at the beginning of the measure, are not audited.

- Audit enharmonic spelling:
    Replaces notes with their enharmonic equivalents.
    There are several options you can choose from (see below), via the tool parameters.
    If your process mode = 'Process selection', and an enharmonic change is to be done on a note, the following notes
    in the same measure or which are tied to the changed note, are investigated to determine if they need to be changed
    also. If affirmative, they will be added to the selection.

    Available options:
     - 'No sharps': All sharps are replaced.
     - 'No flats': All flats are replaced.
     - 'Reverse sharps/flats'.
     - 'No doubles': All double sharps and double flats are replaced.
     - 'Preferably naturals': If a enharmonic equivalent without accidental is possible, it's used.
     - 'No 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 preferred accidentals': A# -> Bb, Db -> C#, D# -> Eb, Gb -> F#, Ab -> G#.
     - 'Sharps up, flats down':
        If the next note is a tone or a semitone higher, a sharp is used; if it is a tone or a semitone lower, a flat is
        used (not applicable to chords and restchords).
     - 'Custom changes': You can choose one or more items from a list of all possible enharmonic changes.

- Audit note length and beaming:
    Splits notes and group beamings, according to the time signatures.
    Upon start, a window is shown with the default groupings for note length and beaming, for each found time signature.
    You can accept or modify them.

    The specifications mainly come from @hmmueler
    (see https://forum.noteworthycomposer.com/?topic=10050.msg72212#msg72212).

    - Note, chord and rest lengths are distributed in each measure according to standard rules(see e.g. Elaine Gould, Behind Bars, pp. 160-164, 166-169, 171).

        * Rest chords, chords with different durations, triplets, or notes with a 'Staccato', 'Staccatissimo', 'Accent' or 'Marcato' articulations will not be split.

    - Beams connect notes and chords according to standard rules (see e.g. Elaine Gould, Behind Bars, pp. 153-155).

    - The main and secondary beat patterns are derived from the currently active time signature.

    - It 's possible to specify alternative beat patterns for a time signature, both for the note lengths and beams.

    - A long note that starts at a beat and spans over several beats, will not be split.

    - If the first measure of the score or selection is a short measure, it is treated as the right part of the full beat pattern.

    - When a special ending is found that's not at the beginning of the measure, the remaining of the measure is not audited.

    - A measure that is longer than the current time signature indicates causes an error message.

 - Audit note stems:
    Removes unnecessary stem up or down attributes and resets stem directions for note beams and triplets.


64
User Tools / Re: Multitool PYNWC
    Version 1.2:

        - Redesign of the tool parameter handling (Existing configuration files become obsolete).
            - New option in the 'tool parameters' window: 'Always show this window when selecting this tool.'
            - New directory for the configuration file: '%LOCALAPPDATA%\PYNWC' (previously in the same directory as the input score).
            - New name for the configuration file: 'pynwc.cfg' (previously: 'config.txt').
       
       - Tool 'audit score' added:

Before running this tool, be sure to select in the tool parameter window the audit you want to be performed.
Also specify the process mode: all staves, visible staves, active staff or the selection.
Depending on the audit you choose, additional options will be shown. See below for details per audit.

- Audit accidentals:
    Via the tool parameters you can select one of this options for handling natural accidentals:

        - Leave naturals unchanged
        - Make courtesy accidentals
        - Remove accidentals

    This audit acts on any unnecessary accidentals assigned to notes.
    It compares a note with an accidental with the 'running' key signature, which is determined by the previous key
    signature + the preceding accidentals in the measure.
    If the accidental matches the running signature, and it's not a courtesy accidental, it will be removed if it's
    not a natural.
    For naturals the action taken depends on the option in the tool parameters.

- Audit bar lines:
    Audits the bar line alignment.
    In the tool parameters you can indicate whether you want to admit a short first measure (anacrusis).
    If the audit finds a standard bar line that is not aligned properly, it is removed and a new bar line is added in
    the proper place. As a result, notes and chords can be split and tied.

    * Measures with a special ending that is not at the beginning of the measure, are not audited.

- Audit enharmonic spelling:
    Replaces notes with their enharmonic equivalents.
    There are several options you can choose from (see below), via the tool parameters.
    If your process mode = 'Process selection', and an enharmonic change is to be done on a note, the following notes
    in the same measure or which are tied to the changed note, are investigated to determine if they need to be changed
    also. If affirmative, they will be added to the selection.

    Available options:
     - 'No sharps': All sharps are replaced.
     - 'No flats': All flats are replaced.
     - 'Reverse sharps/flats'.
     - 'No doubles': All double sharps and double flats are replaced.
     - 'Preferably naturals': If a enharmonic equivalent without accidental is possible, it's used.
     - 'No 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 preferred accidentals': A# -> Bb, Db -> C#, D# -> Eb, Gb -> F#, Ab -> G#.
     - 'Sharps up, flats down':
        If the next note is a tone or a semitone higher, a sharp is used; if it is a tone or a semitone lower, a flat is
        used (not applicable to chords and restchords).
     - 'Custom changes': You can choose one or more items from a list of all possible enharmonic changes.

- Audit note length and beaming:
    Splits notes and group beamings, according to the time signatures.
    Upon start, a window is shown with the default groupings for note length and beaming, for each found time signature.
    You can accept or modify them.

    The specifications mainly come from @hmmueler
    (see https://forum.noteworthycomposer.com/?topic=10050.msg72212#msg72212).

    - Note, chord and rest lengths are distributed in each measure according to standard rules(see e.g. Elaine Gould, Behind Bars, pp. 160-164, 166-169, 171).

        * Rest chords, chords with different durations, triplets, or notes with a 'Staccato', 'Staccatissimo', 'Accent' or 'Marcato' articulations will not be split.

    - Beams connect notes and chords according to standard rules (see e.g. Elaine Gould, Behind Bars, pp. 153-155).

    - The main and secondary beat patterns are derived from the currently active time signature.

    - It 's possible to specify alternative beat patterns for a time signature, both for the note lengths and beams.

    - A long note that starts at a beat and spans over several beats, will not be split.

    - If the first measure of the score or selection is a short measure, it is treated as the right part of the full beat pattern.

    - When a special ending is found that's not at the beginning of the measure, the remaining of the measure is not audited.

    - A measure that is longer than the current time signature indicates causes an error message.

 - Audit note stems:
    Removes unnecessary stem up or down attributes and resets stem directions for note beams and triplets.


SEE LINK IN ORIGINAL POST
68
General Discussion / Re: Duration parts in NwcTxt
When something on the staff has a duration, can there be anything else in the Dur: field outside of note length, dot or triplet status, and presence of a slur?  If I need to change the duration of a note or chord, I need to keep the slur intact.

Anything else to be on the alert for? I need to clear this up before converting ThreeEight.html to a user tool.

TIA

Here are some possible combinations:

Code: (nwc) [Select · Download]
NoteWorthyComposerClip(2.751,Single)
|Note|Dur:8th,Grace,Slur|Pos:0
|Note|Dur:8th,Triplet=First|Pos:2|Opts:Stem=Down,Beam=First
|Note|Dur:8th,Triplet,Staccato,Tenuto,Slur|Pos:2^|Opts:Stem=Down,Beam=End
|Note|Dur:8th,Triplet=End,Staccatissimo,Slur,Marcato|Pos:2
!NoteWorthyComposerClip-End
70
General Discussion / Re: Beaming compound-time
What I can do is to search through Behind Bars for the relevant details/rules, since I happen to own a copy, and I can try to summarize them here if there is interest in creating a tool.

A few years ago I wrote the enharmonic.og tool where one could choose among various options. Now I'm working on a tool (to include in my multitool PYNWC), where one could select one or more of the audit functions and run them on a selection, a staff, all staves or the visible staves.
If you can specify the rules for an extra 'audit compound times(?)' function, I maybe can look if it can be added in that tool.  But as I already stated in other topics: my music theory knowledge is very poor, so the rules should be unambiguous for me in order to understand them.
72
User Tools / Re: ColoringBeamsSlursTriplets.og
Hello Wilm,

Can you clarify your problem?
- When I download, open and print your NWC file, it shows the stems and beams (see attachment).
- What do you mean by "the color shown in NWC is not my (modified) Color:7"
73
User Tools / Construct a medley
A new tool 'Construct a medley' is added to the multitool PYNWC (version 1.1)

Combine several song files into 1 medley file.

    To create a medley file, you have to start this tool from a blank score:
    Choose 'File/New' and select <blank score> from the 'Song Templates/General' tab and save it before you go to 'Tools/User Tools'.
    This file will be the destination file, in which you add the songs that will make up the medley.
    You can create the medley file in several steps, so you can also start this tool from an earlier created medley file.
    (The tool checks the presence of 'song lines'(1) in the Comments section of the Song Info to decide whether it's a valid medley file.)

    Via the tool parameters you can specify:
   
     - Include song titles at the start of each song (top staff).
     - Position, scale and font for the Song Title text objects.
     - Type of separation bar between the songs (except when the previous song ends with a Repeat Close): Single, Double or Section Close.
     - Page break, System Break or no break between the songs.

    The tool consists of several stages:

     - A popup window 'Select Songs'.
        - If you press 'Add a file', a Windows Explorer window will be opened.
        - Important: Only files in NWC Text format can be processed. So maybe you'll have to open and 'save as' one or more of your songs first.
        - A selected song can be removed from the list by clicking on it.
        - In this stage you can also set or change the Medley Title.
        - 'Cancel' will exit the tool without any changes.
        - If you have chosen your files, press 'Continue >'.

     - A popup window 'Arrange Staves'. Via this window you can:
        - Reorder the staves
        - Change song titles(2)
        - Change staff names and labels
        - Join staves (by assigning the same name and label)
        - Press '?' to see more detailed help info
        - Press '< Back' to return to the 'Adding Songs' window.

     - Review of the staff properties:
        - For each staff that appears in several songs, the properties from the different songs are compared.
          For each mismatch(except for 'visibility' and 'muted'), a popup window is presented where you can choose which values to retain(2).
          If there are to many mismatches, you may want to  press 'Cancel', in which the tool is ended without any change.
          When there's a mismatch for 'visibility', the part of the song with property invisible will be collapsed.
          When there's a mismatch for 'muted', the appropriate notes will be muted.

     - Construction of the medley, according the choices in the Tool Parameters:
        - Adding 'song lines(1)' to the Comments Section of the Song Info.
        - Adding song titles at the start of each song.
        - Creating delimiter objects: separation bar, new system or new page.
        - Inserting rests measures in staves that aren't part of every song, surrounded by boundary collapse and end collapse objects (3).

    Notes:
        (1) A 'song line' is of the form "Song:{song title}#{starting measure}-{ending measure}"
        (2) Changing the song titles and/or staff properties has only effect in the destination file. The original song files will not be modified.
        (3) The inserted boundary changes don't always give the expected result between the songs, so may be you'll have to delete or replace some of them.

74
User Tools / Re: Multitool PYNWC
Version 1.1 added wit a new tool 'Construct a medley'


Combine several song files into 1 medley file.

    To create a medley file, you have to start this tool from a blank score:
    Choose 'File/New' and select <blank score> from the 'Song Templates/General' tab and save it before you go to 'Tools/User Tools'.
    This file will be the destination file, in which you add the songs that will make up the medley.
    You can create the medley file in several steps, so you can also start this tool from an earlier created medley file.
    (The tool checks the presence of 'song lines'(1) in the Comments section of the Song Info to decide whether it's a valid medley file.)

    Via the tool parameters you can specify:
   
     - Include song titles at the start of each song (top staff).
     - Position, scale and font for the Song Title text objects.
     - Type of separation bar between the songs (except when the previous song ends with a Repeat Close): Single, Double or Section Close.
     - Page break, System Break or no break between the songs.

    The tool consists of several stages:

     - A popup window 'Select Songs'.
        - If you press 'Add a file', a Windows Explorer window will be opened.
        - Important: Only files in NWC Text format can be processed. So maybe you'll have to open and 'save as' one or more of your songs first.
        - A selected song can be removed from the list by clicking on it.
        - In this stage you can also set or change the Medley Title.
        - 'Cancel' will exit the tool without any changes.
        - If you have chosen your files, press 'Continue >'.

     - A popup window 'Arrange Staves'. Via this window you can:
        - Reorder the staves
        - Change song titles(2)
        - Change staff names and labels
        - Join staves (by assigning the same name and label)
        - Press '?' to see more detailed help info
        - Press '< Back' to return to the 'Adding Songs' window.

     - Review of the staff properties:
        - For each staff that appears in several songs, the properties from the different songs are compared.
          For each mismatch(except for 'visibility' and 'muted'), a popup window is presented where you can choose which values to retain(2).
          If there are to many mismatches, you may want to  press 'Cancel', in which the tool is ended without any change.
          When there's a mismatch for 'visibility', the part of the song with property invisible will be collapsed.
          When there's a mismatch for 'muted', the appropriate notes will be muted.

     - Construction of the medley, according the choices in the Tool Parameters:
        - Adding 'song lines(1)' to the Comments Section of the Song Info.
        - Adding song titles at the start of each song.
        - Creating delimiter objects: separation bar, new system or new page.
        - Inserting rests measures in staves that aren't part of every song, surrounded by boundary collapse and end collapse objects (3).

    Notes:
        (1) A 'song line' is of the form "Song:{song title}#{starting measure}-{ending measure}"
        (2) Changing the song titles and/or staff properties has only effect in the destination file. The original song files will not be modified.
        (3) The inserted boundary changes don't always give the expected result between the songs, so may be you'll have to delete or replace some of them.

See link in original post
75
General Discussion / Re: Creating a .bat file to convert all files of a folder to NWCTXT.
This worked fine
Code: [Select · Download]
cd C:\Program Files (x86)\Noteworthy Software\NoteWorthy Composer 2
for /F "delims=" %%i in ('dir /b C:\Users\gustv\Documents\Music\NWC2\Kaaterliedjes\*.nwc ^| findstr /e .nwc') do (
nwc-conv  "C:\Users\gustv\Documents\Music\NWC2\Kaaterliedjes\%%i" NWCTXT > "C:\Users\gustv\Documents\Music\NWC2\Kaaterliedjes\NWCTXT\%%itxt".
)
79
General Discussion / Re: Creating a .bat file to convert all files of a folder to NWCTXT.
Code: [Select · Download]
for %%i in (*.nwc) do "C:\Programs\NoteWorthy Composer 2\nwc2.exe" -convert "%%i" "%%~dpni.nwctxt"

Edit: N.B. this is for a batch file!
For the command line:
Code: [Select · Download]
for %i in (*.nwc) do "C:\Programs\NoteWorthy Composer 2\nwc2.exe" -convert "%i" "%~dpni.nwctxt"

Thanks for the quick answer. I like this solution without any goto (Sory H.M :)) ), but I can't get it right.

I changed it a little bit to include my input folder, to: 
Code: [Select · Download]
for %%i in (C:\Users\gustv\Documents\Music\NWC2\Kaaterliedjes\Testcopies\*.nwc) do "C:\Programs\NoteWorthy Composer 2\nwc2.exe" -convert "%%i" "%%~dpni.nwctxt
But that gave errors "Het systeem kan het opgegeven pad niet vinden.", which means, according to Google translate: "The system cannot find the path specified."
My input folder is correct (I can see all the input files in the echo lines), so maybe I have to specify the output path also, but how?
I don't know what "~dpni" means.
80
General Discussion / Creating a .bat file to convert all files of a folder to NWCTXT.
I'd like to convert all my NWC files to NWCTXT.

For 1 file, I know I can do this with a command like:
"C:\Program Files (x86)\Noteworthy Software\NoteWorthy Composer 2\nwc-conv  "nwc_folder\song.nwc" NWCTXT > "nwctxt_folder\song.nwctxt".

So what I need is a .bat file where I can specify the input and output folder and create a loop to convert every file with .nwc extension from the input folder to a .nwctxt file in the output folder.

But my knowledge of the syntax of .bat files is hidden far away in my memory.

So any help would be appreciated.
84
User Tools / Multitool PYNWC
In NWC you'll have to install PYNWC as 1 tool, but when invoking it, it's like a second layer: the PYNWC environment, where you have access to a number of tools that I developed using the Python programming language. The reason is that Python has several possibilities that are missing in the Lua language, of which on of the most important is the use of a flexible graphical user interface.

Within this environment you can:
 - see information about the score
 - see help information about the PYNWC environment
 - select a tool
 - see help information about the selected tool
 - see and change parameters for the selected tool
 - run the selected tool
 - see the results after running a tool (before saving)
 - save the changes to the score (if any) in the input file
 - depending on the tool:
   - save the changed score as another NWC file
   - save a generated report into a txt file
   - save a generated worksheet into a xlsx file

You can download the Windows installation file and a link to the full documentation (including installation instructions) in:
https://www.opagust.be/content/nwctools-environment.
85
General Discussion / Re: Using Soundfonts with NoteWorthy Composer
Thanks Rich!

Very cool and comprehensive.
I knew about soundfonts but never got into it. But this pdf was very very useful.
I'm  now exploring the 'Top 15 free Choir Soundfonts'.

And it set me to read further about nwcitrees, and I even managed to create one (for the 'all voices.sf'), and it works.

So again: many thanks!
90
User Tools / Re: File Organization
In the statistics of my website I noticed that there ware recently some downloads of another tool: NWCTOOLS ENVIRONMENT.
This is a tool which is still in development. The version on my website is a test version from two months ago.
I hope I will be able to publish the final version 1.0 in the near future.
But in the mean time: if you downloaded the tesst version an tried it out: all feedback is welcome!
91
General Discussion / Re: Arpeggio settings in NWC2.75a
Quote
And I just did my own "undo" tests, confirming what you said. It even supports multiple undo levels (which after thinking about it, it only makes sense that this should work fine).


If you have to change to input type 'File Text' in your 'Test Toggle' tool,  instead of 'Clip Text', the undo won't do anymore.
92
User Tools / Re: File Organization
28/07/2020: version 1.1 added: see https://www.opagust.be/?q=content/nwc-file-organization

- correction of a bug when reading 'localrepeatclose' bar from the inputfile.

- Added possibility to change the default location of the 'print object' via arguments in the command line of the User Tool Description window.
* Arguments (with the dashes, without the quotes, case sensitive): '-XLoc', '-YLoc', '-X', '-Y', each followed by the desired value.
* Leave a space between the argument names and the values, use no commas.
*Valid values:
   -XLoc: Left, Center, Right (default = Left)
   -YLoc: Top, Bottom (default = Top)
   -X and -Y: horizontal and vertical offset (default = 0)
* Example: With the arguments "-XLoc Left -Yloc Bottom -Y 10", the date modified will be printed at the bottom left of the page, with a vertical offset of 10.
95
User Tools / Re: File Organization
I’m getting an error message when I try to use that function. It asks me if I want to save the change. I say yes. And then it takes me to the screen with my score and I can’t do anything else from there except cancel. I cannot do a print preview. What am I doing wrong?
It's not sure that you did something wrong, maybe the program did (wich implies it was me that did something wrong ::) )
Have you tried it on another file with the same result?
You mention you get an error message, what does it exactly say?
Maybe you can include the file, then I can try it myself to search what causes the problem.
96
User Tools / Re: File Organization
Can you explain how to use the "create user objects to print date modified" option?
Thanks
If you check this action, and  save the changes, a user object 'PageTxtMaestro.nw' (if not already present) and  'PageTxt.nw' with 'Page Style' = 'Modified' will be inserted in your score.
This will print the date modified in the bottom left corner of each page. If you want it to be printed at another position, you can change the PageTxt object.
I suggest you just try it and do a 'Print Review'.
97
General Discussion / Re: Deciding About BAK files
I've recently started having that message pop up when saving that the program is unable to save a BAK file, and do I want to save anyway (which I do). It's possible that I have changed something I shouldn't during a computer housecleaning episode.
I've had the same message and after investigating the properties of the BAK file I discovered it was read-only. When testing my tool 'File Organization' I had locked and unlocked the original nwc file. I presume that the BAK file was last created when the original file was locked.