Recent Posts

Object Plugins / Re: ChordPlay.nw

Last post by Mike Shawaluk - 2024-03-25 02:44 pm

Quote from: Lawrie Pardy – 2024-03-25 02:31 pm

I note that in my installation the function is called this:
play_ChordPlay(t)

instead of this:
play_ChordPlay()

I omitted the parameter when I typed the name of the function in my post, but as you observed, it needs to be there

Object Plugins / Re: ChordPlay.nw

Last post by Lawrie Pardy - 2024-03-25 02:31 pm

Thanks Mike,
works a treat once I found the code section... and made ALL the changes

I note that in my installation the function is called this:
play_ChordPlay(t)

instead of this:
play_ChordPlay()

Object Plugins / Re: ChordPlay.nw

Last post by Mike Shawaluk - 2024-03-25 01:57 pm

I should add a caveat to that fix. Namely, if you are using ChordPlay.nw in a passage that uses the Ottavamatic.ms object, you will get some strange sounding chords in the 8va sections

Object Plugins / Re: ChordPlay.nw

Last post by Mike Shawaluk - 2024-03-25 01:50 pm

And... it turns out the fix is very simple. The API has a convenient function named nwcplay.getTransposition() which will take into account staff transpositions, as well as octave shifts for a treble clef.

Make these changes to the code toward the end of the play_ChordPlay() function:

   local noteCount = #k
   local arpeggioShift = (strum ~= 'No') and math.floor(math.min(duration,nwcplay.PPQ)/math.max(12,noteCount+1)) or 0
   local trans = nwcplay.getTransposition()
   for i, v in ipairs(k) do
      local thisShift = math.min(duration-arpeggioShift, arpeggioShift * ((strum == 'Down') and (noteCount-i) or i))
      nwcplay.note(thisShift, duration-thisShift, startPitch+v+nshift+trans)
   end

(Note: I would have used the "code" block feature, but that wouldn't let me use colored text)

Object Plugins / Re: ChordPlay.nw

Last post by Mike Shawaluk - 2024-03-25 01:27 pm

It turns out that this problem isn't unique to ChordPlay.nw. GuitarChord.ms has the same problem. (I was going to add Banjo.ms and Ukulele.ms to the list, but then I remembered that those objects don't include playback.)

When I saw this, I thought that perhaps more of my objects that have playback would suffer from this, but it appears that objects that look at existing notes, like Arpeggio and Trill, are getting the staff transposition information. I will look at the code for GuitarChord.ms to see if there is an easy fix for this, which hopefully could be applied to the other objects.

Object Plugins / Re: ChordPlay.nw

Last post by Lawrie Pardy - 2024-03-25 12:08 pm

Thanks for the confirmation mate.

It isn't important enough to me to warrant any real effort to correct, I was more wanting confirmation that I hadn't lost what's left of my tiny, little mind

Object Plugins / Re: ChordPlay.nw

Last post by Flurmy - 2024-03-25 09:49 am

Of course, you're right. Chordplay ignores the staff transposition.

Quote from: Lawrie Pardy – 2024-03-25 02:38 am

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

Object Plugins / Re: ChordPlay.nw

Last post by Lawrie Pardy - 2024-03-25 02:38 am

Hi peoples, especially @Flurmy and @Mike Shawaluk,
do any of you regularly use Chordplay, and if so, do you use it to create chords for transposing instruments?
Today I tried to do something a little different to what I usually do* in that I activated playback for chordplay chords on a staff for a Concert pitch instrument. This has always been fine.
Then I copied that entire staff to new one and transposed it for a Bb instrument (+2 semitones) with playback transposition checked. The cacophony was dreadful. The staff was playing back at concert pitch, as it should, BUT the Chordplay objects were not. Unless I'm badly mistaken it appears that Chordplay ignores the staff playback transposition.

Has anybody else noticed this? Or do I have something very unusual going on. This enquiring mind would like to know.

FYI I also tried my unedited copy of Chordplay.nw and it was the same.

* 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.

General Discussion / Re: Scriptorium Update

Last post by Richard Woodroffe - 2024-03-22 10:50 pm

Folks,

The Scriptorium has been updated with works submitted by :

John Hooper    Save us, O Lord, waking (Bairstow)
Yann Forestier   Sinfonia Concertante No.4 in F major   (Devienne)
Richard Woodroffe   Naturgenuss D188 (Schubert)
Lorenzo Prada   Santa Lucia   (Cottrau)Lorenzo Prada
Lorenzo Prada Gaudeamus igitur   (Traditional Latin)

If you would like to be notified every time the Scriptorium is updated, please send an e-mail requesting Scriptorium Update    notification to nwcscriptorium "at" gmail "dot" com

https://nwc-scriptorium.org/whatsnew.html

Stay safe

Richard

Object Plugins / Re: TremoloSingle.ms (2.1)

Last post by Mike Shawaluk - 2024-03-20 03:03 pm

You might be wondering why the tremolo beams are positioned so high on some of the notes, especially the eighth note (quaver) in measure 2. The object sets the default vertical position of the beams/strokes differently for single notes with plain stems, single notes with flags, beamed notes, and whole notes. The position is a small offset from either the end of the stem, the tip of the flag, or the inside edge of the beam closest to the notehead. In general, the preferred way to adjust the vertical position is to increase the note's stem length, but if you don't care if the tremolo beam collides with the note's actual beam or flag, you can use the Offset parameter, which I see you have already done in a few cases.