org point articulation on rest does not appear

[arsaral]

Hi,
I cannot put an org point articulation on a rest. Have I done anything wrong that I do not know? I use latest version of Finale.

Thanks.

Ali R+

[Peter Thomsen]

Try this:

Change the rest to a note.
Then, add the articulation to the note.
Change the note back to a rest.

[michelp]

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

[Anders Hedelin]

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?

[motet]

I really think real rests with an articulation is better than an expression, since they automatically break multimeasure rests on both sides (which expressions do not).

[motet]

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

[Anders Hedelin]

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.

[motet]

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.

0501.png (11.36 KiB) Viewed 3915 times

0500.png (55.46 KiB) Viewed 3915 times

[Anders Hedelin]

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.

[Anders Hedelin]

FWIW here's how it would work with two expressions that break a MMR: