Hi all,
Called MM for an answer, but they are closed for a meeting. Perhaps there’s
someone who can tell me why Finale playback (Mac, Sierra, Finale v25) will only
play back through the internal speakers when the device on the USB output is
selected in the Mac audioMIDI setup. This USB outpu
I found that some file's settings where changed after installing Finale's
2014.5 (couldn't say for the very last version); in a couple of cases I
realised changes under the MIDI/AUDIO menu where 'Play Finale Through Audio
Units' was switched to 'Play Finale Through MIDI' and vice versa. By
re-f
Thanks, Giovanni,
I found the place where there was an incorrect setting. There are two places
under Audio/MIDI device setup where you can choose the output, in the Macs OS
set up, and in Finale’s Device/ Audio Setup. I had missed the Finale setting
that had become reset by the OS upgrade (an
Fin2012c. WIN8.1 64-bit
Never had these problems before:
In the middle of playback some staves get "stuck" and keep holding the same
note(s) until Finale is closed. Or, while playing, inexplicably starts to play
from another spot, on top of the current playback.
And BTW: is it possible to pre
From: "dr.a.s. weinstangel"
To:
Sent: Saturday, April 05, 2014 5:54 PM
Subject: Re: [Finale] PLAYBACK ISSUES
> Fin2012c. WIN8.1 64-bit
>
> Never had these problems before:
>
> In the middle of playback some staves get "stuck" and keep holding the
> sa
gt; From: pe...@euphonium.plus.com
> To: finale@shsu.edu
> Date: Sat, 5 Apr 2014 18:43:41 +0100
> Subject: Re: [Finale] PLAYBACK ISSUES
>
> From: "dr.a.s. weinstangel"
> To:
> Sent: Saturday, April 05, 2014 5:54 PM
> Subject: Re: [Finale] PLAYBACK ISSUES
>
>
instan...@utoronto.ca
>NEW! cel.647-292-4605
>
>
> > From: pe...@euphonium.plus.com
> > To: finale@shsu.edu
> > Date: Sat, 5 Apr 2014 18:43:41 +0100
> > Subject: Re: [Finale] PLAYBACK ISSUES
> >
> > From: "dr.a.s. weinstangel"
> > To
t; From: bloke...@comcast.net
> Subject: Re: [Finale] PLAYBACK ISSUES
>
> I had this problem a while ago, but I can't
> remember the fix. Call tech support - they
> sorted it out with me, no problems. We ran a
> couple of tests and they had the answer. I just
> tried di
