org point articulation on rest does not appear
Moderators: Peter Thomsen, miker
- Peter Thomsen
- Posts: 6629
- Joined: Fri Jul 25, 2003 6:47 pm
- Finale Version: Finale v27.4
- Operating System: Mac
Try this:
Change the rest to a note.
Then, add the articulation to the note.
Change the note back to a rest.
Change the rest to a note.
Then, add the articulation to the note.
Change the note back to a rest.
Mac OS X 12.6.9 (Monterey), Finale user since 1996
- michelp
- Posts: 2057
- Joined: Fri Jul 25, 2003 3:35 pm
- Finale Version: 27.4.1,26.3.1, Mont.
- Operating System: Mac
A fermata (= point d'orgue in French) can be applied to a "real rest", not to a default rest (option defined in Staff Attributes : "Display Rests in Empty Measures").
Michel
MacOsX 12.7.4, Finale 27.4.1 & 26.3.1, Mac Mini Intel Dual Core i7 3Ghz, 16 Go Ram. Azerty kb. MOTU Midi Express XT USB, Roland Sound Canvas SC-88vl, MOTU Audio Express. 2 monitors (27"' pivot, 24'"), JW Lua, RGP Lua
MacOsX 12.7.4, Finale 27.4.1 & 26.3.1, Mac Mini Intel Dual Core i7 3Ghz, 16 Go Ram. Azerty kb. MOTU Midi Express XT USB, Roland Sound Canvas SC-88vl, MOTU Audio Express. 2 monitors (27"' pivot, 24'"), JW Lua, RGP Lua
-
- Posts: 760
- Joined: Wed Jan 11, 2017 1:34 am
- Finale Version: Finale 26, 27.4.1
- Operating System: Windows
Or, you might create the fermata as an expression which is independent of the content in the measure.
Do you need it for just one staff, or all staves?
Do you need it for just one staff, or all staves?
Finale 26.3, 27.4.1
Windows 10
Windows 10
- motet
- Posts: 8294
- Joined: Tue Dec 06, 2016 8:33 pm
- Finale Version: 2014.5,2011,2005,27
- Operating System: Windows
Here's a LUA script which will add a whole rest with fermata to any measure in the selection which is empty (that is, with a default whole rests). If some parts have music with fermatas and some don't, you can select the whole measure stack and run this and it will only fill in the empty measures.
Code: Select all
-- Add whole rests with fermatas to empty measures --
function plugindef()
-- This function and the 'finaleplugin' namespace
-- are both reserved for the plug-in definition.
finaleplugin.RequireSelection = true
finaleplugin.Author = "Motet"
finaleplugin.Copyright = "none"
finaleplugin.Version = "1.0"
finaleplugin.Notes = [[
Assumes the F metatool is mapped to Finale's default fermata articulation.
Altered fermata articulations may not work.
]]
finaleplugin.Date = "September 30, 2018"
return "Fermatas", "", "Add whole rests with fermatas to empty measures"
end
local metakey = string.byte("F")
local fermatadef = finale.FCArticulationDef()
local metatools = finale.FCMetatoolAssignments()
metatools:SetMode(finale.MTOOLMODE_ARTICULATION)
metatools:LoadAll()
for metatool in each(metatools) do
if metatool.Keystroke == metakey then
fermatadef:Load(metatool:GetDefID())
break
end
end
if fermatadef.ItemNo == 0 then
finenv.UI():AlertError("Fermata metatool not found", "Fermatas")
return
end
for m, s in eachcell(finenv.Region()) do
local cell = finale.FCCell(m, s)
notecell = finale.FCNoteEntryCell(m, s)
notecell:Load()
if notecell:IsEmpty() then
entry = notecell:AppendEntriesInLayer(1, 1)
if entry then
entry.Duration = finale.WHOLE_NOTE
entry.Legality = true
entry:MakeRest()
notecell:Save()
local index = notecell:GetIndexOf(entry)
notecell:Load()
entry = notecell:GetItemAt(index)
local fermata = finale.FCArticulation()
fermata:SetArticulationDef(fermatadef)
fermata:SetNoteEntry(entry)
fermata:ResetPos(fermatadef)
fermata.HorizontalPos = -14
fermata:SaveNew()
notecell:Save()
end
end
end
-
- Posts: 760
- Joined: Wed Jan 11, 2017 1:34 am
- Finale Version: Finale 26, 27.4.1
- Operating System: Windows
The LUA script seems brilliant. But you are not quite right about expressions not breaking MM rests. You might put them in a category, fx. Tempo Alterations, which allows breaking MMR. (For some strange reason tempo marks are preset to do this, but not tempo alterations. Never mind, you just have to select "break MM rests" in the tempo alterations' Edit categories.)
Or you can copy the tempo alterations category to a 'fermata category', giving it a staff list of its own. I usually do that, not being a script fan myself.
Or you can copy the tempo alterations category to a 'fermata category', giving it a staff list of its own. I usually do that, not being a script fan myself.
Finale 26.3, 27.4.1
Windows 10
Windows 10
- motet
- Posts: 8294
- Joined: Tue Dec 06, 2016 8:33 pm
- Finale Version: 2014.5,2011,2005,27
- Operating System: Windows
Break Multimeasure Rest only breaks it before the measure with the expression. It needs to be broken both before and after, so you'd need to set a measure attribute as well (which breaks after). If for some reason you later remove the fermata, you'd have to fix the measure attribute.
-
- Posts: 760
- Joined: Wed Jan 11, 2017 1:34 am
- Finale Version: Finale 26, 27.4.1
- Operating System: Windows
Yes, I think we had a discussion about the double MM breaking before. Possibly it was me who suggested that measure attribute. And that it shouldn't be invisible, just hidden (greyed out), for the reason you mentioned.
Maybe your script method is more practical - for those who like working with scripts.
Maybe your script method is more practical - for those who like working with scripts.
Finale 26.3, 27.4.1
Windows 10
Windows 10
-
- Posts: 760
- Joined: Wed Jan 11, 2017 1:34 am
- Finale Version: Finale 26, 27.4.1
- Operating System: Windows
FWIW here's how it would work with two expressions that break a MMR:
Finale 26.3, 27.4.1
Windows 10
Windows 10