Does anyone have any advice about setting up an organ template?
I have the Garritan (GPO5) Organ Console.
I can create a registration and trigger additional stops on/off with playing techniques.
I can create different consoles (great, swell etc) by creating multiple instances of Aria. And switch between them with channel changes
Where I am struggling is to switch a particular stave to a particular registration (without it affecting the other staves), whilst retaining the ability to add extra stops in the new registration on the original stave.
I suspect it is a question of managing voices and IVR…(but I lose the will to live in the attempt!)
Any suggestions on how to proceed would be most welcome. Is the flogged horse dead?
OK. I’m getting myself in a pickle! Yes, your GPO Organ Console was most informative. I think I am struggling with understanding the basic notation of organ registration.
A score will typically have a registration setup at the start. OK. I can do that.
Next there will be playing instructions on each stave to play a particular console (Sw., Gt. etc.). OK, your expression map can do that, but only if IRV is switched on (else the expression map applies to all 3 staves).
What confuses me are instructions like “Gt. Diapason” - is this to be interpreted as an addition or a substitution?
Lastly coupling. I understand the principle, but how to implement it…?
I got around to trying your playback template, having previously just read your informative manual.
It failed to load with this error…
I can find no reference to Aria 2.001 on the makemusic site, and the Aria VST itself reports that 1.971 is the latest update!
[EDIT: I discovered this… “Note that the ARIA Player version 2.001 is a Mac-only update and is not needed for Windows users.” - An explanation, but not a solution! Is this a glitch in the Dorico playback template machinery?]
Actually I do have an idea that may be useful. That is, perhaps if @benwiggy can save the template while running his Mac and Dorico in Rosetta translation mode this wouldn’t involve the troublesome coding for M1 Macs. Only a guess, though, as I am not a real computer guru.
Unfortunately there’s nothing we can do about this, because it’s not Dorico that’s doing anything: it’s simply passing the saved plug-in state to ARIA and asking ARIA to load it. ARIA is then refusing.
So it seems that really there are some differences in the data expected by those two different versions of the ARIA plug-in.
I think you’ll need to contact the people at Plogue and ask them how to proceed.