Re: [Finale] Finale 2014a and Lion (OS X 10.7.5)

2014-01-17 Thread Doug Walter
Thanks, Eric. I know I'm headed that way eventually, so maybe I'll do it sooner 
rather than later if I can verify that all the software I'm using will work 
with Mavericks on this system.

Meanwhile, since we now have the ability in Finale 2014 to export a file as a 
2012 version, I did that and *the same file* opens fine in 2012 and behaves as 
expected - none of the delays I was experiencing in 2014 on the same file on 
the same system.

I know this doesn't really isolate the cause of the problem in 2014 on my 
machine, but it suggests to me that there's no obvious reason why the same 
document should behave differently (worse) in the newer version than the older, 
and that it's not necessarily a corrupt file.

And it makes me really skittish about doing any real work in Finale 2014 on 
this computer till I know what's going on.

Doug


On Jan 16, 2014, at 10:30 PM, Eric Dannewitz wrote:

 If you can, upgrade to 10.9.1 finale 2015 works fine and so do the
 original bill Duncan fonts
 
 Sent from my iSomething
 --
 Eric Dannewitz
 Musician/Polymath/Evil Genius
 http://www.ericdannewitz.com
 
 On Jan 16, 2014, at 10:03 PM, Doug Walter dew...@earthlink.net wrote:
 
 Despite the almost constant appearance of the dreaded Mac beach ball, my 
 first project in Finale 2014 has been no day at the beach . . .
 
 The issue is extremely - agonizingly - unacceptably - sluggish behavior when 
 doing ANYTHING. Changing tools, scrolling pages, anything. I'm on an 8-core 
 2.26 GHz Mac Pro with 18GB of RAM, and it's always been plenty fast on even 
 the largest scores up till now (in Finale 2012).
 
 Disclaimer(s): this project involved expanding a score originally done years 
 ago in a much earlier version of Finale (not even sure which one at the 
 moment) from a 6-piece combo to a 17-piece big band with vocal. So I know 
 I'm possibly asking for trouble by not copying and pasting the previous 
 information (or re-entering it from scratch) into a new native 2014 
 document. I know there can be lots of left-over garbage that can slow 
 things down.
 
 That being said, in every version up till this one, when I've had to do 
 exactly what I described above, I've still been able to work efficiently 
 with only the most minimal occasional slowdown or glitch, even in an 
 orchestral score that started life years earlier in another version. So I'm 
 wondering if some combination of old file format, custom fonts (Bill Duncan 
 chord symbol), older OS and machine, and who knows what else might be 
 causing this.
 
 I called tech support and his best guess was that it was file specific, and 
 I'm certainly hoping that's the case. I'll just have to finish this and then 
 start the next large score from scratch in 2014 and see if the same thing 
 develops as the score grows. Meanwhile, has anyone found that OS X10.7.5 
 (Lion) is just not up to the task of handling Finale 2014, as opposed to 
 Mountain Lion or Mavericks?
 
 Thanks for any insight. I'm not ready to upgrade to Mavericks on the Mac Pro 
 yet, although Mountain Lion would be easy enough if that would help.
 
 Doug
 
 P.S. I'm not (knowingly) experiencing any loss of data or crashes or 
 anything of the sort - just a sluggishness that will have me running back to 
 2012 to do any real work from now on if this can't be solved.
 
 
 
 
 ___
 Finale mailing list
 Finale@shsu.edu
 http://lists.shsu.edu/mailman/listinfo/finale
 
 
 
 ___
 Finale mailing list
 Finale@shsu.edu
 http://lists.shsu.edu/mailman/listinfo/finale
 



___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale



[Finale] Finale 2014a and Lion (OS X 10.7.5)

2014-01-16 Thread Doug Walter
Despite the almost constant appearance of the dreaded Mac beach ball, my first 
project in Finale 2014 has been no day at the beach . . .

The issue is extremely - agonizingly - unacceptably - sluggish behavior when 
doing ANYTHING. Changing tools, scrolling pages, anything. I'm on an 8-core 
2.26 GHz Mac Pro with 18GB of RAM, and it's always been plenty fast on even the 
largest scores up till now (in Finale 2012).

Disclaimer(s): this project involved expanding a score originally done years 
ago in a much earlier version of Finale (not even sure which one at the moment) 
from a 6-piece combo to a 17-piece big band with vocal. So I know I'm possibly 
asking for trouble by not copying and pasting the previous information (or 
re-entering it from scratch) into a new native 2014 document. I know there can 
be lots of left-over garbage that can slow things down.

That being said, in every version up till this one, when I've had to do exactly 
what I described above, I've still been able to work efficiently with only the 
most minimal occasional slowdown or glitch, even in an orchestral score that 
started life years earlier in another version. So I'm wondering if some 
combination of old file format, custom fonts (Bill Duncan chord symbol), 
older OS and machine, and who knows what else might be causing this.

I called tech support and his best guess was that it was file specific, and I'm 
certainly hoping that's the case. I'll just have to finish this and then start 
the next large score from scratch in 2014 and see if the same thing develops as 
the score grows. Meanwhile, has anyone found that OS X10.7.5 (Lion) is just not 
up to the task of handling Finale 2014, as opposed to Mountain Lion or 
Mavericks?

Thanks for any insight. I'm not ready to upgrade to Mavericks on the Mac Pro 
yet, although Mountain Lion would be easy enough if that would help.

Doug

P.S. I'm not (knowingly) experiencing any loss of data or crashes or anything 
of the sort - just a sluggishness that will have me running back to 2012 to do 
any real work from now on if this can't be solved.




___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale



Re: [Finale] Finale 2014a and Lion (OS X 10.7.5)

2014-01-16 Thread Eric Dannewitz
If you can, upgrade to 10.9.1 finale 2015 works fine and so do the
original bill Duncan fonts

Sent from my iSomething
--
Eric Dannewitz
Musician/Polymath/Evil Genius
http://www.ericdannewitz.com

 On Jan 16, 2014, at 10:03 PM, Doug Walter dew...@earthlink.net wrote:

 Despite the almost constant appearance of the dreaded Mac beach ball, my 
 first project in Finale 2014 has been no day at the beach . . .

 The issue is extremely - agonizingly - unacceptably - sluggish behavior when 
 doing ANYTHING. Changing tools, scrolling pages, anything. I'm on an 8-core 
 2.26 GHz Mac Pro with 18GB of RAM, and it's always been plenty fast on even 
 the largest scores up till now (in Finale 2012).

 Disclaimer(s): this project involved expanding a score originally done years 
 ago in a much earlier version of Finale (not even sure which one at the 
 moment) from a 6-piece combo to a 17-piece big band with vocal. So I know I'm 
 possibly asking for trouble by not copying and pasting the previous 
 information (or re-entering it from scratch) into a new native 2014 document. 
 I know there can be lots of left-over garbage that can slow things down.

 That being said, in every version up till this one, when I've had to do 
 exactly what I described above, I've still been able to work efficiently with 
 only the most minimal occasional slowdown or glitch, even in an orchestral 
 score that started life years earlier in another version. So I'm wondering if 
 some combination of old file format, custom fonts (Bill Duncan chord symbol), 
 older OS and machine, and who knows what else might be causing this.

 I called tech support and his best guess was that it was file specific, and 
 I'm certainly hoping that's the case. I'll just have to finish this and then 
 start the next large score from scratch in 2014 and see if the same thing 
 develops as the score grows. Meanwhile, has anyone found that OS X10.7.5 
 (Lion) is just not up to the task of handling Finale 2014, as opposed to 
 Mountain Lion or Mavericks?

 Thanks for any insight. I'm not ready to upgrade to Mavericks on the Mac Pro 
 yet, although Mountain Lion would be easy enough if that would help.

 Doug

 P.S. I'm not (knowingly) experiencing any loss of data or crashes or anything 
 of the sort - just a sluggishness that will have me running back to 2012 to 
 do any real work from now on if this can't be solved.




 ___
 Finale mailing list
 Finale@shsu.edu
 http://lists.shsu.edu/mailman/listinfo/finale



___
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale