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 present
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
cisra...
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 series of piano reductions, w
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 pian
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. I
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 reductions, which I import
> i
