My comments below
On 11/18/2015 9:40 AM, Jan Angermüller wrote:
> Have you checked the HP settings for portamento/chromatic gliss ?
> Maybe they changed the default setting ? But I can't believe that you
> open a file that was set to chromatic gliss now automatically becomes a
> portamento. At
> In 2014, it plays distinct
> notes in that run, which is how the flute will sound. In 2014.5, it is
> a portamento. That's OK for this project. Anyway, my point is that
> they did something in that area,
Have you checked the HP settings for portamento/chromatic gliss ?
Maybe they changed the
Yes, it is a mixed bag. So far, the biggest problem I have seen is that
it knocks out VST playback after doing an export to WAV. I have to
restart Finale to get sound going again.
They seemed to have done a few things affecting HP. For example I am
working on an arrangement where the flutes
It confazzled me for 30 seconds too…
> On 17 Nov 2015, at 22:12, Dean Rosenthal wrote:
> The oddest first thing I found about Finale 2014.5 (before taking it for a
> drive) is that after reading the list of fixes and improvements, there is
The oddest first thing I found about Finale 2014.5 (before taking it for a
drive) is that after reading the list of fixes and improvements, there is
no indication anywhere on the pop-up menu as to how to download it!
After some confusion, you discover you have to click on "*learn more*" –
A lot longer than 30 seconds for me. If you do "check for updates" from
within Finale, then you get useful instructions, but none of that is in
the Readme or in the announcement email.
You won't find this in the downloads section like other patches. The
procedure is to log onto you account
> Even though it says it is 2014, it is actually 2014.5
I don’t understand how things like this get rolled out in 2015. We were
laughing about it when I was still working in tech back in 1992. Disconcerting.
Like a trumpet player who shows up without any valve oil.
I’m happy the update was