On 29 Jul 2005 at 11:02, Darcy James Argue wrote:
> On 29 Jul 2005, at 10:15 AM, Christopher Smith wrote:
>
> > For the expressions to playback, you would have to delete all the
> > expressions that were imported into the template one by one,
> > subsituting the ones that DO playback that are native to the
> > template, which is what would take the time.
>
> This is no longer necessary in Finale 2006. Human Playback recognizes
> and interprets "arco", "pizz.", "mute", etc. automatically. In other
> words, you just write the expression, and HP handles the keyswitching.
>
> However, one annoyance is that if you have a Fin2k4 or 2k5 file with
> expressions that *are* defined for keyswitching during playback, you
> must set the playback options to "None" for Finale 2k6 (or, at least,
> the ones Human Playback recognizes). . . .
Well, this was not the case in Finale 2005, at least based on my
experiments with the demo. I converted files with trills and turns
already worked out in a hidden layer, and except in a few cases, did
not get duplication -- I got my original trills/turns (which are much
better than HP's, because they aren't mechanical).
So, in Finale 2005, at least, HP is smart enough to be able to
understand when it doesn't need to realize some types of items
because they've already been realized in the musical text. Perhaps
this is because I have the notes with trills and turns on them set
for no playback (edited via frame properties), so HP knows to ignore
those notes. And maybe the cases where I got both were ones that I'd
missed turning off playback.
But, nonetheless, certain kinds of older playback should not conflict
with HP, at least HP as it was implemented in Finale 2005.
> . . . This can get a bit squirrelly
> because there's (AFAIK) no list of exactly what is actually IN the HP
> dictionary in 2k6. So you will discover that it recognizes "mute,"
> but not "st. mute" or "straight mute" -- those last two still need to
> be defined for playback. But once you figure that out, it's
> relatively easy to convert a file set up for GPO Studio and 2k5 to the
> GPO AU/VST plugins and 2k6.
Well, aren't there two independent issues here, GPO issues and HP
issues? Some of the HP issues are specific to GPO, but if you're not
using GPO, you will still get HP.
> The *big* advantage here is that in 2k6, we no longer have to use
> separate "arco" and "pizz" expressions for violins+violas, cellos, and
> basses -- the same expression (provided it is not defined for
> playback) will work with all of them. Same with "mute" for brass.
That's a nice thing, though I'd never found it too hard to deal with
("arco <cello>" always worked fine for me), though, again, it's
exactly the kind of thing that would benefit from the kind of
subclassing I've been arguing for on this list for years, where you'd
have a single expression defined visually and multiple playback
interpretations possible with it. GPO HP makes it irrelevant for this
particular situation, but it would still be useful for other kinds of
cases where you've got a single visual object that means different
things performance-wise according to context.
Question: do pizz/arco work with HP when *not* using GPO? Is HP smart
enough to use General Midi definitions if that's what you've got
available?
--
David W. Fenton http://www.bway.net/~dfenton
David Fenton Associates http://www.bway.net/~dfassoc
_______________________________________________
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale
