NoteWorthy Composer Forum

FWIW my Backup Files location appears to be OK, but the Auto Save/Recovery location is empty...

The way I do parts is to hide the staves that aren't relevant to the part I want to save, then print that part to a PDF, I do NOT create a separate NWC file for each part.

Grazie Ricco

PS:I hope the Google traductor works clearly!

Press M - like "mute": There you can select the staffs that should NOT be audible on the right.

the letter e, is "and" in French

Was sich liebt, neckt sich - Polka-française, Op. 399
Schubert, Franz (1797-1828), Austrian    Woodroffe, Richard

Mike's comment about an "experimental feature" strikes a vague memory.  For some reason I think this was actually the case.

after just trying it, I find it very hard on the eyes...

Cool.  The limit is in the dialogue rather than the data store.

Attribute value not quoted in 'measure number = "1"'

missing double beams - two layered staves would help

All very nice this updates but when NWC is not working you get no support.
is NWC composer and NWC software support DEAD?

WSH can run scripts written in VBScript and Jscript (java).

I'm confused here by the time notation. Is Flurmy saying 23 minutes and 12 seconds, or 23 hours and 12 minutes? And are the rest of you saying 8 minutes or 8 seconds?
I generally would use : notation, but I realize that can be ambiguous also, unless you specify all 3 numbers.

The primary reason I'm actively changing over is the inbuilt transposition facility.  While I can transpose text chords with the Transpose_Text_Chords user tool from Andrew Purdam, by using ChordPlay I have one less step to worry about.

When I write an arrangement or compose a piece I usually do everything in concert pitch, then transpose as required once it's all finished.  It is far, far easier to see chordal relationships if everything is in concert when writing.

It would be nice if, when the conversion tool is changing a text chord to a ChordPlay object, it could (perhaps optionally) automatically take into account the number of notes/chords on a staff until the next occurrence of a text chord to be converted and instruct ChordPlay to span that number of notes.  This might not be a perfect solution, but it would reduce labour a lot if one wanted to implement the playback feature.

I think using Global_Mod to change from text object to user object would not be very successful, if it's even possible at all.  I haven't investigated that.
ChangeOjectType does not recognise a text entry as an object.  The code specifically confirms that the object type is "user".

Allows custom key sequences, which allows it to be used to retime grace notes:

OK, the one in the ".automatic" area is definitely a separate piece of code and works just fine

I confirmed that the object embedded user tool for text conversion does not seem to work.  Not in my modified version nor in NWC's version so this is not an error on my part.  This tool appears in the ".plugins" section of the user tool dialogue

There is also a user tool created in the ".automatic" area of the user tool dialogue which is stored as a lua file in the
"C:\Program Files (x86)\Noteworthy Software\NoteWorthy Composer 2\AutoUserTools"
section of the filesystem. 

Easy for you to say

it appears to me that it is not written to take into account all the possible additional characters in my *dings chord fonts.

You seem to have made additions to broaden its capabilities WRT: 4, 4/9, 5+, 7+, 7/9+, -, -7, -7/5+, -6 type chords.
I noticed changes to the code in the comment section near the top of the file, AND in the "chordKeySeqList" section (function?)

Do you recall if these the only locations where you needed to make changes?  If so I can probably have a hack at it myself otherwise any pointers you can give would be most welcome.

It would be nice to be able to continue using the extended glyphs in the *chord fonts with ChordPlay without having a spurious <?> appear on chords that ChordPlay doesn't currently understand.

Of course, a good proportion of those glyphs appear in the range of chr$128 to chr$255 and might be problematic to match in the code as straight characters.

my font suites seem to have become something of a de-facto standard

don't know whether the "bug fixes" were ever sent to @NoteWorthy Online to be incorporated into the .nw version.

I have named ChordPlay.fl, although it appears that Flurmy never requested a plugin ID

Incidentally, I too have always had the "download" naming problem both for this and the previous program and have always had to copy the name before clicking it to download and then renaming.

The font sizing is weird - much, much smaller than it should be - E.G. 32 in the chordplay object is about the same as 8 for normal text objects.

-- Version 1.7
-- Flurmy 2021/08/23:
--   extended the allowed chord list
--   allowed the use of the solfeggio style note/chord
--   corrected a bug that crashed the plugin if MusikChordSerif is not available
--   corrected a bug in doFontChange for the font size

-convert: This option can be used to convert a file from one format to another.
Usage: nwc2.exe -convert "[input-file]" "[output-file]"

Both files are required on the command line and the file extension determines the conversion.
Supported conversions include:
.nwc    -> .nwctxt, .mid, or .info
.nwctxt -> .nwc, .mid, or .info
Conversions to .mid support a "-0" option for type 0 files.