If you want to use Finale on a Mac you had better get familiar with the “trash
prefs” routine. I don’t like it either, but it’s practical because it works.
Christopher
> On Jun 6, 2016, at 6:14 AM, Graeme Gerrard wrote:
>
> Haha! That’s so funny!
> Does anyone
Haha! That’s so funny!
Does anyone still regard this as a practical fix that works with their workflow?
Is this still 1990?
> On 6 Jun 2016, at 5:29 AM, Chuck Israels wrote:
>
> And when your Preferences are set up as you like them, make duplicates of
> this Preference
Amen. Been doing that also. There is an odd problem
with these files and MakeMusic says they are working
on a fix -- same with the issues in the unstoppable
playback -- which is tolerable on a lead sheet but
impossible when writing a concerto movement.
Thanks.
Jon
On Sun, Jun 5, 2016 at 1:29
And when your Preferences are set up as you like them, make duplicates of this
Preference file (Finale 2014.5 Preferences - copy 1 - etc.), so that when one
file becomes corrupted, you can replace it with a copy (simply remove the “copy
x” from the name) without having to rebuild your entire
JD:
Check out my reply to Ray. There is a fix. If you are running
on a Mac -- this from MakeMusic Tech support -- it works,
but you are likely to have to keep doing it -- if you are running
on a Windows platform you will need to check in with MakeMusic
Tech support:
Hi Jonathan,
Thank you for
Ray:
Check in with MakeMusic tech support. They told me
to delete the Finale 2014.5 preferences file (this is on
a Mac -- but there should be an equivalent fix for
Windows)
Jon
On Sun, Jun 5, 2016 at 1:13 PM, Raymond Horton
wrote:
> I have had two experiences with
Not meaning to hijack this thread, but I agree with Jon about 2014.5 being an
absolute slug when editing a large orchestral file. I am working on an opera
that ballooned to 7.3MB from 3MB when I converted it from Finale 2012 to 2014.
Everything takes an eternity when editing: changing tools,
Chuck:
Have you had any issues using the playback function?
I have been unable to get it to stop. This is one I raised
with MakeMusic Tech Support and they told me that
this is a problem they are trying to fix. Also, they
acknowledged the issue with notation input to large
scores (orchestral
I have had two experiences with trying to do very large scores in 2014.5
and I always have had extremely slow response. I always export back to 2012
and work in 2012 as much as possible. Saving files , changing time
signatures, and other routine tasks always take an extremely long time in
2014.
Really appreciate the feedback. What I'm hearing is, suck it up until I'm
finished with this orchestration, then upgrade to Finale 2014.5, especially
because I heard 2012 has problems with .asv files (which would really scare
me, because I average a few crashes a month). Anyone have an experience
I am using 2014.5 -- sorry to have called it b
Do you have an issue stopping the playback?
That is an issue for me and MakeMusic confirmed
it was an problem they are trying to fix. You will
also find that notation is extremely slow in large
scored (full orchestral).
On Sun, Jun 5, 2016 at 1:49
Why are using 2014b and not 2014.5? I am using 2014.5 on PC and Mac and have
noticed major performance improvements and less bugs.
Best
Raphael.
> Am 05.06.2016 um 03:47 schrieb Jon Block :
>
> Chuck:
> There are some major issues with 2014b. Playback does not stop when
Chuck:
There are some major issues with 2014b. Playback does not stop when one hits
stop; orchestral scores cause glitches in notation. I have had to delete the
preferences file each time I start inputs to my orchestral scores. MakeMusic
has confirmed these are issues without a fix at
John, This has not been my experience. Familiarity with how 2014 operates
(and there have been some changes since 2012) allows things to work at least as
easily and, in some cases, more easily than they do in 2012. I believe this
will be the prevailing opinion.
Chuck
Chuck Israels
Keep away from 2014 and 2014b at all costs!
They are filled with impossible bugs.
On Sat, Jun 4, 2016 at 2:04 AM, David H. Bailey
wrote:
> On 6/3/2016 9:08 PM, Michael Dutka wrote:
> > Hi, folks. Running 2010 on a Macbook pro.
> >
> > Orchestrating an opera from a
On 6/3/2016 9:08 PM, Michael Dutka wrote:
> Hi, folks. Running 2010 on a Macbook pro.
>
> Orchestrating an opera from a series of piano reductions, which I import
> into a standard orchestra template, with a standard two-stave piano line
> between the singers and the strings (then I delete the
I'm on the latest and I see what you've described a lot. I've never got to the
bottom of it. Sometimes reload all instruments from the MIDI menu sorts it, but
often that changes half the instruments to piano.
Steve P.
> On 4 Jun 2016, at 08:04, Michael wrote:
>
>
You’re using Finale 2010. In 2012 the Score Manager was introduced, making
adding and editing instruments much easier.
> On 4 Jun 2016, at 03:08, Michael Dutka wrote:
>
> Hi, folks. Running 2010 on a Macbook pro.
>
> Orchestrating an opera from a series of piano
I'm not sure what the problem is but I've never had any difficulty in doing
what you're trying to achieve. I'm away from my computer at the moment but will
check tomorrow.
Cheers
Lawrence
Sent from my iPhone
> On 4 Jun 2016, at 2:08 am, Michael Dutka wrote:
>
> Hi,
Hi, folks. Running 2010 on a Macbook pro.
Orchestrating an opera from a series of piano reductions, which I import
into a standard orchestra template, with a standard two-stave piano line
between the singers and the strings (then I delete the piano line when I'm
done with each number).
This
20 matches
Mail list logo