This section allows you to view all Show Posts made by this member. Note that you can only see Show Posts made in areas you currently have access to.
Messages - Mike Shawaluk
Now, if there isn't even a clef present, then all bets are off.
How do you open an nwctxt file in the form that appears in the forum? That is in code form, see attachment. I am only able to open the file with notepad, which is another matter entirely.Click "Select" which will highlight the text. Then click "Download" and your browser should prompt you to save the file with an extension of .nwctxt. Then, double click the file you saved, and it should open in NWC.
If double clicking opens the file in Notepad, then run NWC separately and click the "Open" button and browse to the folder where you saved the .nwctxt file. Then select and open it.
- The instrument you choose for the score will affect the volume. Some instruments are louder than others.
- You can insert a Fortissimo (fff) in your score so that the notes which follow are at the maximum volume.
- Be aware that YouTube has its own volume control, which operates in conjunction with your computer's or phone's volume setting.
There are others as well.
I figure if we can't make everyone happy, then we ought to try to make everyone equally miserable.
Hello, I refer to this topic with two specific questions.For most objects, including Slur and SlurCubic, the units of measure in the vertical and horizontal directions are different. In the vertical, the unit is 1 for each note value. For example, if the object is positioned at G, then a value of 1 would represent the position of an A note (the space between the two lines) and a -2 would represent the position of an E note. In the horizontal, the unit of measure is the width of a small notehead, i.e., the width of a quarter note. Try adjusting the various parameters for a slur and you'll see how this works.
1. the numerical values of slur.ms, slurCubic.ms, alt ctrl + @, how are they chosen? In other words, 0 (zero) corresponds to the position of the notehead, to the center line of the staff (in which each space is equal to 1?)...
1. I'm not sure what the "12" is, but there are special fonts that can be used to create something like that. I'll let Lawrie answer that one.
2. You can use the "brace with next" function to create the bracket. With a score containing multiple staves that are not layered, you would put your cursor in the upper staff and choose menu Staff > Brace with next. The style of the brace is slightly different on the following systems, but I believe it is the same intent.
3. I think the text is "drum fill" not "drum all", which is just a note to the musician to do a "fill" with drums at the beginning of the song. The notes with the "x" noteheads are typically drum beats.
4. For the more complex title, there is a custom object called PageTxtMaestro.nw that can create this, but it takes some experience to use, and I've not used it very much. Perhaps another forum member here can tackle that one.
I will jump in here to explain the two whole notes you are seeing. You are correct that one note is for the soprano and one is for the alto. When two parts sing the same note and the duration is shorter, the stems are set to opposite directions so the singers can tell there are two layered notes. But since there are no stems on whole notes, they are shown offset.
To show this with layered staves, you would need to set the Extra Note Spacing of one of the whole notes to 1.3.
[ code=nwc][ /code].
This will work slightly nicer for users who wish to download your NWC clip.
I might suggest using a SlurCubic.ms for this case, since you can adjust the shape of the curve to more closely match the appearance of a tie. Although they are similar in appearance, ties and slurs have slightly difference shapes and rules for positioning. I'm attaching a sample I created.
Yes, go to the properties for the note where the tie startsI don't know if reversing the tie direction will be what he wants. If you do that, the tie will cut through the half note stem. But maybe that is preferable to having it cut through the note head.
(highlight note and then ALT and ENTER)
Then select Tie Direction "Downward" instead of "Default"
And now for a bit of personal opinion. I don't like the scrolling note chase mode, and I almost never turn it on. It always has seemed jerky/jittery even when it's not outright glitchy as for this score. I consider the scrolling note chase an "experimental feature", even though it's part of the latest official release. It was introduced somewhat late in the most recent release cycle, and I think it's always been a YMMV type of feature. Given the current development status of NWC (or lack thereof), I don't expect the note chase to be changed or fixed any time soon.
Another way to do this would be to select the first barline, choose Properties, and check "Exclude from bar count". This will also set the first full measure to be measure 1. However, if you have multiple staves, you will need to do this on every stave.
Experiment. Spacers are wonderful positioning gadgetsAlso, remember that spacers don't just add space, they can actually remove space. When you insert a spacer, it replaces whatever space is between those two objects by default, so if the width of the spacer is less than the natural space, they will get closer together, or they will actually touch, if you set the spacer width to zero.
As a side note, I'd suggest to use slur markers to "flatten" the long slurs - I have added a few in m.3 and 5 of the upper staff.While the slur markers do help with the shape of the slurs, they can only do so much. I've added SlurCubic.ms objects to my example (attached), They use cubic Bezier curves, and can be adjusted more subtlely than the standard curves of the native NWC slur. In practice if you want to use this approach, you will generally want to add a "real" slur to the score, for the proper playback and lyric effects, but then hide it with a single "Visible=never" slur marker at the start of the slur.
Regarding whether the option should be set or not set by default, I'd say that the default setting needs to be how the current version behaves, for backward compatibility with existing saved scores. There are probably some people who expect (and prefer) the current behavior.
<edit> One thing has just come to mind. I'm using the 2.8 beta, not 2.75a - could this explain the putative API change?This is a somewhat tardy reply, but I have just confirmed that the
o:Get('Text')issue is specific to the 2.8 beta.
A single (that is, non-split-stem) note can have three stem directions: up, down or automatic. However, once you beam notes, it forces their stem directions to be either up or down. Actually, in the user interface, the "stem up" and "stem down" buttons are only enabled when the first note of the beamed set is selected. Attempting to change the stem direction of the first note in a beamed set will unbeam the notes.
A pair of split-stem notes can also have stem direction, but it is always either up or down; there is no "automatic" choice available. Depending on the duration, the note spacing can be different for up vs. down stem direction, as seen in this example:
Of course, when you beam split-stem notes, only the upper or lower notes will be beamed, depending on the stem direction, and any specified stem length will apply to both notes in the set. (Which is why Rick G. and others have generally avoided split-stem notes in favor of layering.)
Regarding the editor "quirk" that Lawrie mentioned, NWC appears to influence the automatic stem direction when you are entering split-stem chords, so that the following note will inherit the stem direction of the prior note. There also seems to be some different behavior when the durations of the upper and lower split-stem notes are different, but it is hard to describe.
I hope this has added some extra confusion to the discussion.
However, I think that if you change the URL to:
Then the file will be saved with the original name (although Windows might warn you that it's not a frequently downloaded file, and make you choose "Keep anyway")
I generally would use : notation, but I realize that can be ambiguous also, unless you specify all 3 numbers.
-- Version 1.7I don't know whether the "bug fixes" were ever sent to @NoteWorthy Online to be incorporated into the .nw version.
-- Flurmy 2021/08/20:
-- 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
And I think that playback should be left off the table (for now), unless there is something obvious I'm missing that tells how it should work.
If the above does not make sense, I can create an example for you.
Many thanks to him for this addition!
I too hope that 2022 is a better year than this past one has been.
The small vertical bars cannot be moved to a different place - they are always at the top or bottom staff line (which makes them only usable for 5-line staffs, I guess).Although it's unlikely that people will use these objects with number of staff lines other than 5, you can make the following code changes to make them independent of staff line count:
local sl = nwcdraw.getStaffProp('Lines')
as remarked by Mike in this posting from 2017There are two signs that you are growing old. One of them is loss of memory, and I can't recall what the other one is.
I really don't remember that specific posting, although I do remember using Arial Unicode MS for certain characters that Times New Roman doesn't have.
Side note: I found the Unicode check mark character by googling "unicode check mark", so I wasn't aware that Charmap or NWC didn't show it.
For the "English" version of the V, which looks like a "tick mark", I have used the "square root" symbol - this is not correct (see attached example from a Rutter score), but I'm right now too lazy to rebuild this with some sort of lines or beziers or whatever.That sounds very much like a gauntlet being thrown. Let me take a look at that (I used beziers in my Arpeggio and Brace objects)
Edit: Might not have to resort to beziers after all. There is a Unicode check mark symbol that appears to be present in Times New Roman. I'm attaching a snippet with the symbol inserted as text. Unicode character U+2713
I haven't yet experimented with the new objects, but I think I see how they might be very useful.
Version 1.1.1 is now available in https://www.opagust.be/?q=content/mxml2nwc
* More permissive treatment for 'line' value in the 'clef' element
* Omitting linebreaks in 'Text' objects.
* Bug fix in slur processing
I'm seeing the correct slur handling for the sample file I sent you, but I'm getting the same mangled |Text and |Tempo objects as before (line break inserted before |Pos)
Edit: My bad, I just realized that the sample file I sent you already had the line breaks stripped out Let me forward a copy of the original XML that hasn't been fixed.
I have tried out your converter on a score that I created in MuseScore some time ago for our choir, namely Randall Thompson's "Alleluia". For the most part it created a very faithful rendition, comparing side by side with the page view in MuseScore. There were a few anomalies:
- I was informed that there were 3 unknown user objects in the score. Going to Manage Objects... I saw the unlikely names of Pos:11.612, Pos:16.046 and Pos:5.522. Opening the nwctxt file in a text editor, I searched for these strings and found the following elements:
It looks like your converter inserted a stray newline for those three elements. I decided to look at the MusicXML file to see whether there were newlines after those elements, and indeed there were. I deleted the trailing newlines and reimported the score, and there were no extraneous user objects. Perhaps your converter could strip any trailing newlines from text elements to prevent this from occurring.
- There were a few instances of incorrectly applied slurs, where the slur did not extend far enough. The slur looks correct in MuseScore, and I did not try to decode what was in the MusicXML file to see if that was causing the problem. If you wish, I can forward the .mxl file to you (along with the MuseScore score, if that helps).
There are a few new Windows 11 features that aren't 100% available yet that I'm interested in checking out once they get rolled out to the general public, including the Linux subsystem and the ability to run Android apps.