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 - NoteWorthy Online

One observation - What I meant by "make sure it's been made invisible" was that the object would modify the existing time signature to make it invisible, not detect one that is already invisible...  I don't know if the API's will allow for this.

They don't.

Eric, I notice with your version that the time sig. gets placed on every new system...

Not exactly. It has to accompany any actual time signature that is placed. The plugin code could be enhanced to support standard sizes on new printed systems after its first appearance.

Update: Post and attachment removed; replaced by TimeSigScaler.nw.
General Discussion / Re: Beam Direction
Currently, the drawing of a fractional beam is not time signature/beat aware. It simply gravitates toward a preceding dot (in the primary voicing), if one is present. This situation will be reviewed.
The nwc-conv tool is nothing but a front-end for the NWC2 program.

Version 2.75 exports MIDI text as utf-8, which is probably causing your problem.

Version 2.75a provides for ANSI text during MIDI export from the Tools, Options, File, ANSI text encoding option.
Object Plugins / Re: ChordPlay.nw
Updated to protect from a song position out of range error when playing or exporting to a MIDI file.
Updated to return the number of object instances that were actually moved. The return report now looks like this:

Code: [Select · Download]
Results for (file mode)

Objects found:    390
Objects moved:    85
Objects deleted:  0
Object Plugins / Re: Melismatic.nw
The plugin has been updated. It now supports minimum lengths down to 0.
A support incident with the object type led to the attached user tool. This user tool can be run in Clip or File Text modes. When run in file mode, it returns file text.

This tool attaches all instances of the designated user object type to the target note that follows it, skipping any rests or bar lines that separate the object from its target note. This has been designed to work with objects, but would work for other objects that specifically target notes, and not rests or bar lines.

In version 2.75a, you can install this tool directly from Tools, User Tools, Download by entering its name at the prompt:

Code: (txt) [Select · Download]
Attach Objects To Next Note.nw


Spoiler (click to show/hide)
Currently, plugins are not without a cost, as they impact startup time and memory footprint, as well as potentially expanding the Add Object and Plugin Tool lists.

I don't see NWC offering a facility to encourage installing everything. However, the community could create a *.nwc master file of objects that demonstrates a large collection of them. This master file would enable something similar to what you describe, as it could be used to quickly download and install a large collection of plugins, and also demo their capabilities.

Alternately, perhaps an overview page that demonstrates many of the objects would be helpful.

I'll think about it. This Plugin board is meant to provide much of this now, as it can be casually browsed.

Fixed in 2.75a Beta 9.
fixed the prior post's bad formatting...looking into the issue
I made some additional changes in an attempt to eliminate any possible causes for Flurmy's troubles.
I don't know what is happening for you, although the filename character issue is mentioned above. If you are not getting a report after running the tool, then the batch command is not concluding properly (the exit /b 99 call triggers report mode back to NWC).

It might help if you explained more details about your system. Also, are you able to run the user tool command shown below? If so, what do you get?

Code: [Select · Download]
cmd.exe /C "set && exit /b 99"
Fixed numerous problems with initial command.
nwc-conv just acts as a front end to the nwc2 program.
I just posted a batch file that might be useful here.

NWC 2.75 has a builtin INFO method that can be accessed from the command line. It shows you some summary stats about a file, including NWC version used to create it, play time, and fonts used. You can access this facility from the User Tool mechanism using the attached Windows batch file...
NWC 2.75 has a builtin INFO method that can be accessed from the command line. It shows you some summary stats about a file, including NWC version used to create it, play time, and fonts used. You can access this facility from the User Tool mechanism using the attached Windows batch file. The recommended user tool settings are also shown.

Additional Details: A file's path name is sent to user tools that handle File Text. The file path is only provided for existing non-sample files. If you want to retrieve the version info for an old file, you must make sure that you do not save it prior to invoking this tool. Once you save a file in a new version of NWC, the old information is lost.

Additionally, user tools receive input encoded as utf-8. If your files are named with characters beyond simple ASCII, you will likely experience issues with this tool.

Spoiler (click to show/hide)
You might not change it, but you do use it. It is either on or off.
We are reviewing the need for the Smart Insertion Point setting in Tools, Options, Editor. It would help us to know how you currently use this setting. Your answer will greatly help in this process.
2.75a Beta 7 includes a subtle change that might make this work better for those using  Smart Insertion Point.

I just noticed that when zoomed out, the clef can still get missed when changing staff. Perhaps this can still be improved a bit more...
The ChordPlay.nw object now detects use of Lawrie's Germanic fonts and remaps the B and Bb accordingly.
Object Plugins / Re: ChordPlay.nw
Updated as follows:

  • When not using Lawrie Pardy's chord fonts, '#' and 'b' are automatically mapped to true flat and sharp characters for display purposes.
  • When using one of Lawrie Pardy's Germanic chord fonts, B and Bb are automatically remapped to H and B for display purposes.
Regarding the ChordPlay.nw object, it can be changed to allow 'H' named chords. I have also been playing with a unicode conversion mechanism so that #/b get displayed as ♯/♭ (unicode variant).

Treating 'B' named chords as B♭ is a little trickier.
The cursor behaviour is simply wrong and should be fixed so other users won't encounter it.

If you turn off Smart Insertion Point (in Options, Editor), the current behavior will be more apparent.

I'll look into ways to improve this behavior; perhaps using the actual position of the insertion point from the user's vantage point.
General Discussion / Re: Hyphenation
I'll give you a hint. One of the samples...
It uses the stem direction, which can be set on those whole notes. Just flip the stem direction...

Code: (nwc) [Select · Download]
General Discussion / Re: Hyphenation
You can use a different hyphen character, which will not be recognized by NWC.

For example, you could change to a non-breaking hyphen (U+2011):

Code: [Select · Download]

would become:

Code: [Select · Download]
re‑ cline
Object Plugins / Re: LineSpan.nw
Updated to take advantage of the new features in NWC 2.75a Beta 6.
This should be fixed in 2.75a Beta 6.
Thanks. Looking into it...
Seems to work for me:

Code: (nwc) [Select · Download]
Object Plugins / Re: LineSpan.nw
MMRs are always an afterthought. :(

The plugin has now been updated to handle them properly.
Object Plugins / Re: LineSpan.nw
I would prefer the text above the line.

Code: (nwc) [Select · Download]
|Text|Text:"Text Above Line"|Font:StaffItalic|Pos:9
Object Plugins / LineSpan.nw
This object can be used to add special lines that span across a selection of notes. An optional text instruction can accompany the line.

Code: (nwc) [Select · Download]
A LineSpan.nw object plugin will be available soon. It will handle this scenario.
A plugin based feature that needs to visually span bar lines/systems has two techniques that can be used to fully implement this:

  • Use two objects, with special handling of cases for one or the other not in the current system
  • Use the StaffSig class to draw in target systems beyond its home system (indicated by isAutoInsert)

Some additional examples of these techniques can also be seen in BarCounter.nw, PageTxtMaestro.nw, and TabStaff.nw.
The notehead is blank, as opposed to hidden, which is an important distinction. If you want the chord to behave as though the note is not there, then removing it is the only way.

As for showing an indication in edit mode, this is certainly doable. No promises at this point...
Object Plugins / Re: (1.3)
FYI: Your second chord in the upper staff is not muted.
It is probably reasonable to consider any dots extending more than a staff position beyond the chord to be unnecessary.
Object Plugins / Re: BarCounter.nw
Updated with a new Show on all bars option.

The next beta will simplify the grace slurs, which should improve this significantly.
Object Plugins / Re: ChordPlay.nw
Updated to include an integrated user tool, ChordPlay.nw: Convert Text Chords (new tool requires 2.75a Beta 2 or later)
Updated for the 2.75a beta. It now includes an integrated user tool for making a TabStaff based on an existing standard note staff. You must be using version 2.75a Beta 2 or later to take advantage of the user tool.
Have you tried the and ChordPlay.nw objects? They are built-in objects...
The user tool naming is evolving. I'll have to get back to you on that...
Nice might consider using the nwc.txt options, where possible. For example:

Code: (Lua) [Select · Download]
local function toParmString(fld)
 local s =
 for _,v in ipairs(nwc.txt[fld]) do s:add('|',v) end
 return tostring(s)

local Values = {
Text = "*",
Visibility = toParmString('ItemVisibility') ,
Color = toParmString('ItemColor'),
['Dynamic.Style'] = toParmString('DynamicLevels'),
['DynamicVariance.Style'] = toParmString('DynamicVariance'),
A user tool, TabStaffMaker, has been attached to the topic. It can be helpful in the initial generation of tablature on an existing staff. However, it does not flag any errors that occur, so you will have to manually review the results for accuracy.
Support for 4 string tab has been added.
The original post in this topic has been updated for version 2.75.