What HP setting are you using?

A custom setting (an amalgam of 21st century and Romantic) but the non playback of the tr and three slashes doesn't work on any of the settings I have tried.

I cannot hear the Timpani at all when playing through MIDI. Using the VST sounds I can get trill or tremolo articulations to work as well as the trill smartshape.

Not sure what is wrong with the MIDI iteration.

I set up a default doc, with Play Through MIDI, HP to Standard. I entered a few notes, and used Change Instrument to set it to Timpani. I entered more notes, and assigned the tremolo articulation to half, and the tr smart shape to the others. Both played back properly.

Then, I used the setup wizard, and set for Timpani. Again, both played back correctly.

I changed to Play though Audio, and again, all was well. (No special libraries installed; just the basic Finale sounds.)

Simon (and Adrian), if you send me an email at wawoodman at aol dot com, I will send you my doc, to see if it works for you.

Is there a non-KS Timpani? Have you tried that?

Mike,

Thank you. The difference may be between Mac & Windows versions, so I'm glad you tested it since Simon seems to be using the Mac version.

UPDATE

It seems to be a periodic problem. It started working again a couple of days after my last post, until about three hours ago. Now suddenly, neither tr nor triple slash works on any instrument. It was playing back beautifully when I sat down this morning. Now nada. Rebooted Finale multiple times. Rebooted the computer. Tried several different HP types.  Tried clearing the measures and re-entering. Tried deleting the measure, creating new ones, all to no avail. However, just to add to the confusion, older files WITH EXACTLY THE SAME SETTINGS AND NOTATION play back fine. Open a new doc and start from scratch, playback just fine. I am stumped. Gremlins would appear to be the only explanation. . .

OSX 10.13.3 Finale 25.5.0.259

Well, wouldn't you know. It's working today. Gremlins off bugging someone else I suppose. I haven't rebooted the computer, same apps running in the background (mail, iMessage and Safari). Just opened the same file that wasn't working yesterday and boom, both tr and triple slash functioning within normal parameters. Jolly jolly and off to the races...

One of my favorite computer acronyms: JOOTT

Just one of those things...

Well, wouldn't you know, off again today, but only on timp and bass drum. Cymbal rolls working perfectly.  Douglas Adams Maximum Improbability Drive anyone?

Sorry to wake a sleeping thread, but I've been experiencing this exact same problem. Simon, did you ever figure out what the issue was with intermittent roll playback?

I'm afraid not, it seems to have a mind of its own. Not sure whether it is affected by the phases of the moon, the position of the planets, the DOW Jones. . . seriously, I can see no pattern to it, except that its favourite time to malfunction is when I need to send a conductor a MIDI file that day: then it never works. My only guess is that it might be RAM related - it seems to malfunction more often on scores using a lot of instruments, but even that is not consistent. For example, just this morning my file played back properly for 10 minutes, then the rolls stopped and only to start up again half an hour later. I believe it was the inventor of the Xerox machine that said it contained an invisible sensor that changed the functionality of each copier in inverse proportion to the importance of the task it was performing.  I like Mike Rosen's JOOT, too.

Simon - I actually managed to find something that seems to have improved the likelihood of proper playback on the rolls. If you go into MIDI/Audio > Audio Units Banks & Effects, click on the pencil icon to the right of each drop-down menu under the "Instruments" column, then go to the "Settings" tab in the Audio Unit Viewer, setting the "Max. Engine RAM Allocator" higher (I put mine at 512MB on each bank) and the "Inst. Disk Pre-Caching" higher (I put each bank at 128kB), that seems to greatly diminish anomalous playback issues. So far, at least. Who knows what tomorrow holds.

Thanks, Nate, great idea. I should have thought of doing that. I'll report back

Still no go. I increased the settings to 1GB and 256 KB respectively, to no avail. It is possible that I don't understand how to use the key switches properly, but can find no information in the manual. Timpani 1 KS has three settings Single Hits - Rolls - and Rolls (on release) [what the heck is that used for??!!!!????]. I try to set it to rolls but it won't 'stick' - it changes back to Single Hits as soon as playback starts. What I am missing?

The saga continues. I have discovered a work around to get timpani rolls to play back properly:  create a new staff at the bottom of the score, cut and paste the notes from the original into the new staff - and then it works. I can see no logic to this. Can anyone explain it to me?

Update: the above method works, but only for 8 seconds. Literally. Two bars, and then, without any indication to do so, or for any fathomable reason, the staff just reverts to single hits. This is not how new, single staff files behave. I have increased the RAM allocation to 8GB. I am flummoxed

This is what I found at

https://usermanuals.garritan.com/GPO5/Content/directory.htm?Highlight=timpany%20roll 

The timpani rolls work fine for the included Finale Garritan Instruments for Finale (GIfF) timpani, so there must be some tweaking necessary for the HP settings in GPO5.

There are loads of problems with the GPO5 tymps. Firstly, Timpani 1 KS has the pre-recorded rolls, not Timp 3 as the manual says. Secondly, the rolls are only in the 'right hand' range, so they are in the wrong octave for Finale. Thirdly, they don't even loop! You can check this using the standalone ARIA Player.

Then there's the fact that Timps 1 and 3 have no CC controls in the ARIA Player. (The panel with the knobs is missing.)

And much of the tuning is awful. 

All of these things can be fixed very easily if you know your way around the SFZ instrument format. MM could produce revised instruments for these, and other things, like the Oboe d'amore that pops every time the sample loops. 

I have created edited versions of the sfz files that fix many of these problems, but as 'derivative works' of MM's property, I hesitate to publish them, even though they are only of use to GPO licensed customers.

My impression is that any development on the Garritan sounds has ceased. The last Garritan Blog entry was July 2019; it was a summer sales ad, and the monitors haven't even bothered to take it down. GPO5 seems to have a number of drawbacks even compared to GPO4 (string sounds among others). I find myself using NotePerformer more and more; the sounds may not always be as good, but the built-in balance between instruments and sections has been recommended as better.

(Always enjoy following your contributions elsewhere under your benwiggy handle.)

I spent quite a while 'getting in' to SFZ, and creating new instruments based on the Garritan samples: so 'aggressive' AG strings with complete KSes in one instrument; also Cellos with Double bass down the octave; and various others. (As well as corrections to the mistakes in GPO.) Plus I've created some ARIA instruments for the audio samples that come with Logic.  

I emailed MM directly in November to ask about sharing revised SFZ files from GPO, and I've heard nothing.

So, yes, I've given in and bought Noteperformer. GPO5 is still superior for some things: solo wind and brass, all the keyboards, etc. However, NP is being actively developed and has good support. 

I presume that ARIA Player will be updated for Apple Silicon, but.... 

The Aria Player is a Plogue product ("sub-let" by MakeMusic) so it may be updated without any improvements forthcoming in the Garritan sound libraries.

Indeed. Though when I asked Plogue about creating a Multi-input/output version of VST3 ARIA plug-in, they said that they would only do so if instructed by MakeMusic.

However, Plogue's own VST, Sforzando, will also play the Garritan libraries, so perhaps talk of obsolescence is premature.