NoteWorthy Composer Forum

!NoteWorthyComposerClip(2.751,Single)
|Clef|Type:Treble
|Note|Dur:16th,Triplet=First|Pos:5|Opts:Stem=Down,Beam=First
|Spacer|Width:10
|Note|Dur:16th,Triplet|Pos:5|Opts:Stem=Down,Beam
|Spacer|Width:10
|Note|Dur:16th,Triplet=End|Pos:5|Opts:Stem=Down,Beam=End
|Spacer|Width:10
|User|Markup.rg|Pos:-3|Markup:x-4/m4֎|Color:4
|Spacer|Width:10
|Note|Dur:16th,Triplet=First|Pos:5|Opts:Stem=Down,Beam=First
|Spacer|Width:10
|Note|Dur:16th,Triplet|Pos:5|Opts:Stem=Down,Beam
|Spacer|Width:10
|Note|Dur:16th,Triplet=End|Pos:5|Opts:Stem=Down,Beam=End
!NoteWorthyComposerClip-End

!NoteWorthyComposerClip(2.751,Single)
|Clef|Type:Treble
|Note|Dur:16th,Triplet=First|Pos:5|Opts:Stem=Down,Beam=First
|Spacer|Width:10
|Note|Dur:16th,Triplet|Pos:5|Opts:Stem=Down,Beam
|Spacer|Width:10
|Note|Dur:16th,Triplet=End|Pos:5|Opts:Stem=Down,Beam=End
|Spacer|Width:10
|User|Markup.rg|Pos:-3|Class:Span|Markup:x-4/m4֎|Color:4
|Spacer|Width:10
|Note|Dur:16th,Triplet=First|Pos:5|Opts:Stem=Down,Beam=First
|Spacer|Width:10
|Note|Dur:16th,Triplet|Pos:5|Opts:Stem=Down,Beam
|Spacer|Width:10
|Note|Dur:16th,Triplet=End|Pos:5|Opts:Stem=Down,Beam=End
!NoteWorthyComposerClip-End

I believe that Standard and Span objects are rendered last, while StaffSig objects are rendered first, for a given staff.

Eric seems to have nailed your problem as a different font.

!NoteWorthyComposerClip(2.751,Single)
|Instrument|Name:"String Ensemble 1"|Patch:48|Trans:0|DynVel:10,30,45,60,75,92,108,127|Pos:8|Wide:Y
|Note|Dur:Half,Slur|Pos:3
|Note|Dur:Half|Pos:5
|Bar
|Note|Dur:Half,Slur|Pos:4
|Note|Dur:Half|Pos:2
|Bar
!NoteWorthyComposerClip-End

a) Would this not affect 2.75 as well?

!NoteWorthyComposerClip(2.751,Single)
|Chord|Dur:8th|Pos:-1^,1^
|Bar|Style:MasterRepeatClose
|Chord|Dur:4th,Grace|Pos:-1,1|Opts:StemLength=4.7|Visibility:Never
!NoteWorthyComposerClip-End

• apt-get install wine freepats timidity
  (installs the necessary wine and timidity software)
  
• winecfg
  (confirms your wine config)
• wget https://noteworthycomposer.com/setup/setup_nwc275_viewer.exe
  (downloads the NWC Viewer install package)
• timidity -iA
  (Launches TiMidity++ as ALSA sequencer client)
• winefile
  (double click the setup_nwc275_viewer.exe to install the viewer)

I replaced the original bar count with this version.  Please forgive my disappointment with it.
How do i get back my original bar count?

!NoteWorthyComposerClip(2.751,Single)
|Boundary|Style:NewSize|Lower:100
|Note|Dur:8th|Pos:0
|Boundary|Style:Reset
!NoteWorthyComposerClip-End

The duration of the transitional dynamic variance is based on the position of the dynamic that follows the variance in the staff. Note that repeats and flow direction marks are ignored when determining the dynamic that follows the variance. If the variance does not have a dynamic on both sides of it in the staff, it does not alter play back dynamics in any way.

I have toyed with the idea of adding playback to the Glissando.ms object

local PlaybackStyle = {'None','Chromatic','AllNaturals'}
local KeyIntervals = {
	None = {},
	Chromatic = {0,1,2,3,4,5,6,7,8,9,10,11},
	AllNaturals = {0,2,4,5,7,9,11},
	}
...

local _spec = {
...
	{ id='Playback', label='Playback', type='enum', default=PlaybackStyle[1], list=PlaybackStyle },
}

...

local function GlissOctaveNearestNextInterval(t,inOctaveSemiTone)
	for i,v in ipairs(t) do
		if v >= inOctaveSemiTone then return i-1 end
	end
	return 0
end
		
local function CountGlissIntervals(k,v)
	local o = math.floor(v/12)
	local i = v % 12
	
	return #k*o + GlissOctaveNearestNextInterval(k,i)
end

local function GlissNoteFromInterval(k,v)
	local opitches = #k
	local o = math.floor(v/opitches)
	local i = v % opitches
	
	return 12*o + k[i+1]
end

local function _play(t)
	local playback = KeyIntervals[t.Playback]
	if #playback < 1 then return end
	
	if not (hasPriorTargetNote(priorNoteidx) and nextNoteidx:find('span', 1)) then return end
	local startSPP = priorNoteidx:sppOffset()
	local acc = t.TargetAcc
	local dur = -startSPP
	
	local v1 = nwcplay.getNoteNumber(priorNoteidx:notePitchPos(1) or '0')
	local v2 = nwcplay.getNoteNumber(nextNoteidx:notePitchPos(1))
	local inc = (v1<v2) and 1 or -1
	local interval1,interval2 = CountGlissIntervals(playback,v1,inc),CountGlissIntervals(playback,v2,inc)
	local deltav = math.abs(interval1-interval2)-1
	if deltav < 1 then return end
	local deltaSPP = dur/(deltav+1)
	if deltaSPP < 1 then return end
	for i=0,deltav do
		local interval = interval1+(inc*i)
		local notepitch = GlissNoteFromInterval(playback,interval)
		if ((i==0) and (notepitch~=v1)) then notepitch = v1 end
		nwcplay.note(startSPP+(deltaSPP*i),deltaSPP,notepitch)
	end
end

• F11 shows how it really looks
• the TimeSigScaler entry of User Tools,.Plugins adds a scaler object to every time signature in a file
• additional instances can be placed on their own if the time signature is not changing (such as in your example)
• a spacer before the real time signature will prevent extra preceding white space
• a spacer immediately after the TimeSigScaler will prevent extra white space on the right ride
• the scaling can be set using +/- keys while the object is selected by itself

!NoteWorthyComposerClip(2.75,Single)
|Clef|Type:Bass
|Key|Signature:F#|Tonic:G
|TimeSig|Signature:4/4|Visibility:Never
|User|TimeSigScaler.nw|Pos:0
|Spacer|Width:0
|Rest|Dur:Whole
|Bar
|TimeSig|Signature:5/4|Visibility:Never
|User|TimeSigScaler.nw|Pos:0
|Spacer|Width:0
|Rest|Dur:Whole
|Bar
|TimeSig|Signature:4/4|Visibility:Never
|User|TimeSigScaler.nw|Pos:0
|Note|Dur:4th|Pos:1
|Note|Dur:4th|Pos:2
|Note|Dur:4th|Pos:1
|Note|Dur:4th|Pos:0
|Bar
|TimeSig|Signature:9/8|Visibility:Never
|User|TimeSigScaler.nw|Pos:0
|RestMultiBar|NumBars:32|PrintOnce:N|WhenHidden:ShowBars,ShowRests|Visibility:Never
!NoteWorthyComposerClip-End

Occasionally the scores I play for musicals have a time signature that is significantly larger than you would normally expect.  They extend from the centre line the same way that a normal time signature does, but instead of being completely enclosed in the staff (I.E. each number is 2 spaces high), they extend above and below by approximately an additional space to space and a half.  Think scaled by 150% to 175%.  This can be really, really helpful.  Especially if the score is busy.

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.

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