Skip to main content

Show Posts

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 - Flurmy

1
General Discussion / Re: Just a weekend story
Gosh! But the official Java site, were I expected to find the real java platform, has only version 8, up to date, with no hint suggesting it's (very) old!  >:(
Looking at the Oracle page instead, I see "Java 22, Java 21, and Java 17 available now". No comment  :-X
And there is more: if you're looking just for JRE, like I do, in the Oracle page there is a button saying "JRE for consumers" and, guess what?, it sends you to the official java site with version 8...
Don't let me say what I'm thinking...

(I think it's the same with e.g. Windows versions: You can have "the newest version of Windows 10" - i.e., with all the latest fixes -; but you won't be automatically upgraded to e.g. Windows 11; and other "more complex" software products, like database systems, IDEs, etc.etc.)
Well, my daughter's computer surreptitiously switched from Win10 to Win11, with her great sorrow...  :(

Thank you very much, HM!
2
General Discussion / Re: Just a weekend story
Harald, how were you able to use audiveris?
I tried many times but, even if I have the last audiveris and the latest JRE (updated automatically a few minutes ago), the result is always:
Quote
java version "1.8.0_411"
Java(TM) SE Runtime Environment (build 1.8.0_411-b09)
Java HotSpot(TM) Client VM (build 25.411-b09, mixed mode, sharing)

Exception in thread "main" java.lang.UnsupportedClassVersionError: Audiveris has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 52.0
What I'm doing wrong?
3
Object Plugins / Re: Trill.ms (2.4)
Quote
Trill objects will be avoided when a trill note is tied.
and the trill at the first note will have the "note span" automatically set to the relevant number to show the extender line.
5
General Discussion / Re: View from DownUnder?
Thanks, Mike.
I missed that info. But you must admit the thing is funny!  ;)

Quote
and give you a Vegemite sandwich
Thanks, but I already had supper.  I'll keep il for tomorrow breakfast (time zone adjusted).  :)
6
General Discussion / View from DownUnder?
Lawrie,
was NWC intended for you?  :)  :)  :)

Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|Text|Text:"Stem=Up"|Font:StaffItalic|Pos:15.5
|RestChord|Dur:4th|Opts:Stem=Up|Dur2:4th|Pos2:2
|Text|Text:"Stem=Down"|Font:StaffItalic|Pos:-10
|RestChord|Dur:4th|Opts:Stem=Down|Dur2:4th|Pos2:2
!NoteWorthyComposerClip-End
9
General Discussion / Funny notation
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|Note|Dur:8th|Pos:2|Opts:Stem=Down,Beam=First
|Note|Dur:8th|Pos:1|Opts:Stem=Down,Beam
|Note|Dur:16th|Pos:2|Opts:Stem=Down,Beam
|Note|Dur:8th,Dotted|Pos:5|Opts:Stem=Down,Beam=End
!NoteWorthyComposerClip-End
11
Object Plugins / Re: ChordPlay.nw
Of course, you're right. Chordplay ignores the staff transposition.

I regularly create charts for several transposing instruments that are identical except for the transpositions (C, Bb and Eb usually) but this is the first time I activated playback of the Chordplay objects on all staves.
Very often I make use of Chordplay but very rarely, if ever, used the play option, so I was unaware of this problem.

I have to investigate what can be done. I think it can be corrected.
Maybe Mike already knows a solution...
13
Object Plugins / Re: TremoloSingle.ms (2.1)
Once you're aware of it it's not absurd, but maybe changing it to take care of the already present beams would be more intuitive.
In this optic, there is also the problem of manually lengthen the note stem to make room for the tremolo.
14
Object Plugins / Re: TremoloSingle.ms (2.1)
Mike, I don't know, otherwise I'd have discussed it with you.
I'll try looking at some books, unless someone else here already knows the answer.
Anyway, as I wrote, the thing is rational.
15
Object Plugins / Re: TremoloSingle.ms (2.1)
I recently made the same discovery.
The fact is that the speed of the tremolo is computed by dividing the note duration by the number of beams of the tremolo.
So, if the note already has some beams...
Indeed, if you lengthen the note stem as you should to have something decent to show, the thing starts having sense.
16
General Discussion / Re: Layering troubles
N.B. The score very often notates the chords and the arpeggi with about half notes stem down and the other half stem up.
Has this some significance, beside aestetics?  :)
I don't think so, even if the score is a "didactical" one.
18
General Discussion / Re: Layering troubles
2/4, of course, given the upper staff bar duration.
Maybe it could be better putting the rest in (vertical) line with the initial chord.
N.B. the original score, although being in print (1974), is not very well engraved...
19
General Discussion / Layering troubles
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.751)
|Editor|ActiveStaff:2|CaretIndex:1|CaretPos:0
|SongInfo|Title:""|Author:""|Lyricist:""|Copyright1:""|Copyright2:""
|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:"Staff"|Group:"Standard"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:12|BoundaryBottom:12|Lines:5|WithNextStaff:Layer|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
|Clef|Type:Treble
|Bar
|Chord|Dur:Half|Pos:#-2,0,3|Opts:Stem=Up|Dur2:Half|Pos2:-11,-7,-4
|Bar
|AddStaff|Name:"Staff-1"|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
|Bar
|Rest|Dur:8th|Opts:Stem=Down
|Note|Dur:8th|Pos:-2|Opts:Stem=Down
|Note|Dur:8th|Pos:0|Opts:Stem=Down,Beam=First
|Note|Dur:8th|Pos:3|Opts:Stem=Down,Beam=End
|Bar
!NoteWorthyComposer-End
My best solution:
Code: (nwc) [Select · Download]
!NoteWorthyComposer(2.751)
|Editor|ActiveStaff:2|CaretIndex:5|CaretPos:0
|SongInfo|Title:""|Author:""|Lyricist:""|Copyright1:""|Copyright2:""
|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:"Staff"|Group:"Standard"
|StaffProperties|EndingBar:Section Close|Visible:Y|BoundaryTop:12|BoundaryBottom:12|Lines:5|WithNextStaff:Layer|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
|Clef|Type:Treble
|Bar
|Chord|Dur:Half|Pos:#-2,0,3|Opts:Stem=Up|Dur2:Half|Pos2:-11,-7,-4
|Bar
|AddStaff|Name:"Staff-1"|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
|Bar
|Rest|Dur:8th|Opts:Stem=Down|Visibility:Never
|Spacer|Width:150
|Text|Text:""|Font:StaffSymbols|Pos:-3.5|Wide:Y
|Spacer|Width:75
|Note|Dur:8th|Pos:-2|Opts:Stem=Down
|Note|Dur:8th|Pos:0|Opts:Stem=Down,Beam=First
|Note|Dur:8th|Pos:3|Opts:Stem=Down,Beam=End
|Bar
!NoteWorthyComposer-End
Any better idea?
23
General Discussion / Re: Lyric positioning after a new boundary
Yes, Mike, that's what I do usually, but here it doesn't work.
Why? Because I'm an idiot!

The first line is written "strophe, chorus" and is fine.
All the others are written as "strophe, chorus, strophe", with the chorus replaced by underscores to avoid repeating it.
As you can easily understand, in all the lines except the first the second strophe never appears because is after the end of the staff.  :-[
So, guess what happens if I add the first line chorus after the second strophe of the last line!

Forgive me and forget it all. Sorry.   ::)
26
User Tools / Re: Repeated Measures
Some notes:
  • if the tool is in the standard directory (usually your suggested path) the calling line can be simply
    Code: [Select · Download]
    wscript Scripts\repMeas.js <PROMPT:Tot Times?=#>
  • Boxmark2 as User 1 can seamlessly be replaced by one of the most recent  ;)  fonts created by Lawrie: MusikDingsSans.ttf or MusikDingsSerif.ttf
  • I usually use the same size of Staff Metrics for User 1 in the whole score. Warren, you can add your scaling factor 1.375 to that specific text only.
27
User Tools / Re: Examine clipboard
N.B. of course you can always change the return code of the tool.
Quote
The following return codes are recognized:
  • 0 Text in STDOUT is processed and anything found in STDERR is presented as a warning to the user
  • 1 Anything found in STDERR is shown to the user, and nothing else is done
  • 99 Anything found in STDOUT is shown to the user, and nothing else is done
28
User Tools / Re: Examine clipboard
It's already visible in the stdin tab of the tool result dialog.
There is also the stdout tab.
The only problem is that, as far as I know, it's visible only if there is something in the stderr.
29
General Discussion / Re: Percusion
You can look at File -> Open sample -> Drumref.nwc for the standard MIDI percussions normally available with channel 10 in NWC.
For the percussion in the scores, the standard should be the one attached here.
30
General Discussion / Re: Repeated measures
You should include/specify which font is used as "User 1".
I suppose, using one of the "MusicDings*" font, the char could be "\".
31
Object Plugins / Re: MarkupPage.rg
Rick the magician was a genius, but cryptic and always very scarce of explications.
After a full immersion in the meanders of the NWC plugins with the help of Mike, I felt brave enough to delve into his opera.
I just did for MarkupPage.rg more or less (much "less" than "more"  :D ) what Harald did for Markup.rg.
Here is what I was able to discover. Part of it are Rick's words.

This is a plugin for putting text on a page that is unrelated to the staves: titles, dedications, lyricists, copyrights, catalog numbers and the like.
Up to 9 markups can be defined from each object.
Setting the Class to StaffSig allows the markup to be repeated for subsequent pages.

Markup commands are prefixed by '/'. Supported commands are:
 /a - angle
 /c - character[.repeat]
 /d - duplicate or transparent
 /f - font[.styleDigit[size]]
 /h - home[ x]
 /p - page[offset]
 /r - return[y]
 /x - add to horizontal position
 /y - set vertical position

/a is in degrees (°) counterclockwise
/h, /r, /x and /y are in points (1/72 inch, 0.353 mm), positive is upward
/c is the (unicode) char decimal code
/p prints the page number (adding the optional [offset] starting page number)
/d repeats the following item the specified number of times; if the number is negative then it doesn't print but updates the x position as if it had written
/r resets the x position and increments the y position by the amount specified

The vertical positions are relative to the plugin marker position.
All that is not a command is written verbatim.
Items are displayed using Staff Italic (3) unless preceeded by /f

In /f the integer part of the number is the font number in NWC's scheme of things:
 1 = Staff symbols
 2 = Staff small symbols
 3 = Staff italic
 4 = Staff bold
 5 = Staff lyric
 6 = Page title text
 7 = Page text
 8 = Page small text
 9 = User1
10 = User2
11 = User3
12 = User4
13 = User5
14 = User6

If the font number is negative (e.g. /f-9) then the whiteout mode is used: everything is drawn in the background color.

In /f the first digit after the decimal point (styleDigit) is the font style:
0 = as specified in the font number
1 = normal
2 = bold
3 = italic
4 = bold italic
5 = as specified in the font number but as contour
6 = contour normal
7 = contour bold
8 = contour italic
9 = contour bold italic

Additional digits specify the fraction of the size (always < 1), e.g., /f9.03 means 30% of the size, /f9.015 means 15%.

"Menu options" ("Opts:") is a list of options, one for each possible markup: 1 Type, 2 Type, …, 9 Type, 1 Page, 2 Page, …, 9 Page

Options set to their default values appear empty.
Empty values at the end of the list are removed.

"Type" and "Page" for each item can also be set by the Context Menu. (Right click on the object in the score, then select "object")

"Type" list
 1 - 'Top left' (default)
 2 - 'Top center'
 3 - 'Top right',
 4 - 'Bottom left'
 5 - 'Bottom center'
 6 - 'Bottom right'
 7 - 'Staff left'
 8 - 'Staff center'
 9 - 'Staff right'

"Page" list
 1 - 'All' (default)
 2 - 'Odd'
 3 - 'Odd (except 1)'
 4 - 'Even'

Items of the same "Type" need to be located with /y

How many (so far) undocumented features!
Quote
"It is easier to write a new code than to understand an old one." - John von Neumann
36
General Discussion / Re: Ridimensionamento Partitura
From Mel Brooks "Silent movie":
Quote
Funn phones mime artist Marcel Marceau, who responds in French with the only spoken word in the film: a resounding "Non!"
Dom Bell: [seen as an insert title after Mel hangs up the phone] What did he say?
Mel Funn: [seen as an insert title] I don't know. I don't speak French!
  :))  :))

I think Windows has some API calls to get the locale for "yes", "no", "cancel", "abort", "retry", "ignore", the days of week, the months etc. but I think it's too much trouble for too little.
Yes, many languages have the negation starting with 'n': "no", "nein", "non", "não", "niet" so it's easy to check for it instead of the affermative form. But NWC is in english without any hint of translation anywhere, so I think that even the casual user is well accustomed to "yes" and "no".
37
General Discussion / Re: NWC bug
To be more specific, let's start with:
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|Note|Dur:4th|Pos:b0^
|Bar
|Note|Dur:4th|Pos:0
!NoteWorthyComposerClip-End
Then right click on the last (the tie receiver) note and select "coutesy accidental".
Voilà... wrong.
39
General Discussion / NWC bug
Working on the glissando plugin with the help of Mike, I discovered a bug in NWC that's visible also to non-programmers.
The API functions doesn't take care of an accidental "inherited" via  a tie from a previous measure.
For the common user this is apparent, as far as I can tell, only if you try to use the courtesy accidentals like here:
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|Note|Dur:4th|Pos:b0^
|Bar
|Note|Dur:4th|Pos:n0)
!NoteWorthyComposerClip-End
Not such a big trouble, luckily.
But, as programmer, I had to reinvent the wheel performing a lot of the parsing NWC already does normally...  :(
40
General Discussion / Re: Too much swing!
Possible, in special mode if for some reason (like a glitch in my old computer) the connection is in USB 1 mode.
Sometimes my computer says, with a USB memory stick, "the device could operate faster if"... (I don't remember the suggestion) even if the socket is always the same.
41
Object Plugins / Re: Glissando.ms (2.3)
Sorry for having mixed different problems.

The problem with the pitch bend arises because there is a big difference in the two cases:
in a case the bending starts from 0 and goes to target, then quickly returns to 0 while the note is still somehow sounding (release time). This is quite difficult to manage.
In the other case the bendings starts from target and ends to 0, so the playing can continue normally.

For the other problems I need to think more, and here is bed time. I already said too many stupid things for today.  ;D
42
Object Plugins / Re: Glissando.ms (2.3)
The odd effect I have is voice related since the MIDI gets note-off and immediately "pitch bend = 0".
My synth sax seems to need about 50 ticks to stop the note.
It all depends on the release time of the voice!
44
Object Plugins / Re: Glissando.ms (2.3)
I am not certain why you muted the tied-from note; I would think you want that to sound.
Me too, but if that note is unmuted, that note (F5) stops sounding when the glissando is already at G4, overlapping part ot the glissando.
Code: [Select · Download]
Note On: F5, Velocity: 110
Note On: E5, Velocity: 110
Note On: E5, Velocity: 0 = Off
Note On: Eb5, Velocity: 110
Note On: Eb5, Velocity: 0 = Off
Note On: D5, Velocity: 110
Note On: D5, Velocity: 0 = Off
Note On: Db5, Velocity: 110
Note On: Db5, Velocity: 0 = Off
Note On: C5, Velocity: 110
Note On: C5, Velocity: 0 = Off
Note On: B4, Velocity: 110
Note On: B4, Velocity: 0 = Off
Note On: Bb4, Velocity: 110
Note On: Bb4, Velocity: 0 = Off
Note On: A4, Velocity: 110
Note On: A4, Velocity: 0 = Off
Note On: Ab4, Velocity: 110
Note On: Ab4, Velocity: 0 = Off
Note On: G4, Velocity: 110
Note On: F5, Velocity: 0 = Off
Note On: G4, Velocity: 0 = Off
Note On: F#4, Velocity: 110
Note On: F#4, Velocity: 0 = Off
Note On: F4, Velocity: 110
Note On: F4, Velocity: 0 = Off
Note On: E4, Velocity: 110
Note On: E4, Velocity: 0 = Off
45
General Discussion / Too much swing!
In a score for (jazz) orchestra I'm working on, I put four hi-hat beats before the start to get the tempo.
All was fine with my computer and his synth.
With my great surprise, when I connected an external keyboard via an USB-MIDI converter the third beat, and only that, was syncopated!
I checked a rechecked everything with no avail.

My hypothesys is that it's a case of MIDI overload. Too many MIDI messages.
Indeed, removing some instruments all becomes regular.
Sic!  :o
47
Object Plugins / Re: Glissando.ms (2.3)
Similar problem:
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|Instrument|Name:"Alto Sax"|Patch:65|Trans:0|BendRange:24|DynVel:10,30,45,60,75,92,108,127|Pos:8|Wide:Y
|Note|Dur:8th|Pos:1|Opts:Stem=Down
|User|Glissando.ms|Pos:3|Pen:wavy|Text:|Playback:PitchBend
|Note|Dur:8th|Pos:-1^|Opts:Muted
|Note|Dur:Half|Pos:-1
!NoteWorthyComposerClip-End
If the target note is unmuted there is an unwanted attack instead of a smooth continuation.
48
Object Plugins / Re: Glissando.ms (2.3)
One more problem:
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|Instrument|Name:"Alto Sax"|Patch:65|Trans:0|BendRange:24|DynVel:10,30,45,60,75,92,108,127|Pos:8|Wide:Y
|Rest|Dur:4th,Triplet=First
|Note|Dur:8th,Triplet=End|Pos:1|Opts:Stem=Down
|User|Glissando.ms|Pos:3|Pen:wavy|Text:|Playback:PitchBend
|Note|Dur:8th,Grace|Pos:-3|Opts:Muted|Visibility:Never
|Spacer|Width:100
|Rest|Dur:4th
!NoteWorthyComposerClip-End
Probably an incorrect computation of the times. (I didn't check the source)

Edit: Easily solved: simply muting the first note. But why we get that odd effect otherwise?
Exporting to MIDI has no problem.
Because in a case the bending starts from 0 and goes to target, then quickly return to 0 while the note is still somehow sounding. In the other case the bendings starts from target and ends to 0.
Better think more... sorry.
49
Object Plugins / Re: Glissando.ms (2.3)
Using glissando with a play mode different from pitch bend it is now necessary to mute the first (left) note.
But see what happens in this case:
Code: (nwc) [Select · Download]
!NoteWorthyComposerClip(2.751,Single)
|Instrument|Name:"Alto Sax"|Patch:65|Trans:0|DynVel:10,30,45,60,75,92,108,127|Pos:8|Wide:Y
|Note|Dur:Whole|Pos:4^|Opts:Muted
|Note|Dur:4th|Pos:4
|User|Glissando.ms|Pos:-4|Class:Span|Playback:Chromatic
|Note|Dur:4th|Pos:-4
!NoteWorthyComposerClip-End
Possible solution: adding a note off of the starting note before starting the glissato. (positive side effect: no need to mute any note, an annoying task)

More: what if the glissato needs to be the whole length of the tied first notes?
50
User Tools / Re: Swing triplets
Tool updated.
Now the accidentals and the attributes are not replicated in each tied note.