MakeMusic Forum

Home | Log In | Register | Search | Help

MakeMusic Forum > Public Forums > Finale - Macintosh - FORUM HAS MOVED! > 2014.5 issues

Forum Quick Jump

[ << Previous Thread | Next Thread >> | Show Newest Post First ]

Peter West
Registered Member

Date Joined Dec 2002
Total Posts : 4272

Posted 12/14/2015 8:51 AM (GMT -6)

Hopefully these teething problems can be ironed out, but for now I'm not comfortable using Finale 2014.5. So far there are two main problems:

1. opening files created in 2014d, some text blocks have different fonts (Parisine changed to Sabon, Minion changed to Helvetica. It seems to be random, and certainly not all text blocks

2. Some articulations are moved vertically away from the noteheads. Not everything within a font, but the items moving are consistent. Probably a font metrics issue which should restive easily enough.

Peter
Music Publishing Services

*********************
iMac 27 inch, 8GB RAM /OSX.10.10.1 +20 inch Cinema Display
Finale 2008 2009 2010 2011 2012 2014d/Logic Pro X

https://www.facebook.com/MusicPublishing
http://musicpublishing.moonfruit.com

Vaughan
Registered Member

Date Joined Jun 1999
Total Posts : 4984

Posted 12/14/2015 9:07 AM (GMT -6)

Finale 2014.5 ironed out some font problems which have been around for several versions. The result is that 2014.5 sometimes claims to be unable to find a font which is nevertheless installed and active. I had this issue with Stempel Garamond and a few others, all of which got changed to some sans serif font. I made a QuicKeys macro to take care of these. An additional problem was that not every file had the same 'missing' fonts or, when running Check Document Fonts Against System Fonts, not every missing font would be presented in the same order. I therefore created a few macros to take care of most of the situations and I made educated guesses as to how much I could automate and how much would need to be done by hand. This sounds a lot worse than it actually turned out to be!
Your second issue sounds like a FAN problem.

Vaughan

Finale 3.2 - 2014.5, Sibelius 4 - 7
Tobias Giesen's plugins, full version, Robert Patterson plugins, Dolet 6 plugin
MacOS 10.11.1
MacPro 6GB, MacBookPro (2011) 8GB

Amsterdam

Dr. Wiggy
Early music: modern methods

Date Joined Jun 2006
Total Posts : 12628

Posted 12/14/2015 9:25 AM (GMT -6)

As Vaughan says, 2014.5 fixes a font issue which has lingered for several versions, but as a result of which, the font and style of some text will appear to be "missing" or incorrect and need to be re-applied.

The second is indicative of a FAN issue: make sure you've got Finale looking at the correct FAN folder, particularly for third-party/addition fonts.

"This is me helping."

Finale 2014.5, 2012 MacMini; 2012 MacBook Pro (10.11.1)
Edirol FA-66; Roland A-49, HP Laserjet 5200 DTN
Ancient Groove Music www.ancientgroove.co.uk

N. Grossingink
Registered Member

Date Joined Nov 2002
Total Posts : 3991

Posted 12/14/2015 9:44 AM (GMT -6)

Peter West said...
2. Some articulations are moved vertically away from the noteheads. Not everything within a font, but the items moving are consistent. Probably a font metrics issue which should restive easily enough.

Are the slurs positioned exactly as you would expect, or have they shifted vertically (up or down)? It may be just a small shift.

I opened a test file in 2014.5 and found some articulations and slurs had shifted. I removed the FAN file for that particular music font, restarted Finale and reopened the file. Upon getting the "Missing Font Annotation" dialog, I specified "Auto Generate New FAN". That solved the problem. The problem is, I can't work like that. My clients and I need to have the exact same FAN files installed in working order to be able to see the file displayed in exactly the same way.

That's one of the reasons why my 2 clients have opted to not use any version of Finale 2014. There are just too many variable behaviors when passing files from composer to editor to engraver and back again, in various different directions. Many others, probably with more-self contained workflows, use 2014 with satisfaction. For a publishing situation with many people involved in the chain, maybe not so much.

N.

OSX 10.8.5
Finale 2011c, 2012c for production work
Finale 2014.5

TgTools, Patterson Plugins, JW Change and Staff Polyphony, QuicKeys 4
Mac Mini 2.4 Ghz Intel, 8GB RAM
New Belgium Fat Tire Ale

“I’m all for giving grants to musicians. Or any other good brand of Scotch.”
–Pepper Adams

Peter West
Registered Member

Date Joined Dec 2002
Total Posts : 4272

Posted 12/14/2015 11:53 AM (GMT -6)

Generally I present everything as pdf, so as long as I can generate a reliable pdf, the Finale file is not the main concern, as far as sharing is concerned.

Thanks everyone for sharing your experience and solutions. I have had to revert to 2014d for now just to get up to speed, but I'll look at this again soon when i have some free minutes

Peter West
Registered Member

Date Joined Dec 2002
Total Posts : 4272

Posted 12/14/2015 12:20 PM (GMT -6)

I see what's happening with the fonts:Previously in 2014, if a font family had italic bold and bold italic as separate fonts, then selecting the typeface worked, but selecting the style caused a double bolding, or double italicising effect. So in 2014 it was important with those fonts to select the typeface and keep the style as regular.

In 2014.5 the reverse is true, so where I have Parisine Bold - regular selected, I now need to change that to parson regular - bold, or it will substitute Sabon Italic, for whatever reason...

OK, so I'll have to stick to 2014 for old files and start creating new ones in 2014.5. I suppose this means upgrading to El Capitan is out of the question till the 2014d files are all out of the system (about 3 - 4 years), or I have to set up a macro to convert fonts in all (estimate) 6, 000 current 2014d files.

Christopher Smith
Registered Member

Date Joined Sep 2007
Total Posts : 2290

Posted 12/14/2015 12:49 PM (GMT -6)

Peter, I wrote in to tech support with the same problem. I also have thousands of older files that would require conversion. Can we lean on them to come up with a more suitable (read, transparent) solution?

Christopher Smith

Mac Mini (Late 2014) 2.8 Ghz Intel Core i5, 8GB RAM
OSX Yosemite 10.10.5
Finale 2014.5
or
Macbook Pro (Retina, 13 inch, early 2015) 2.7 Ghz Intel Core i5, 8 GB RAM
OSX Yosemite 10.10.5
Finale 2014.5

Peter West
Registered Member

Date Joined Dec 2002
Total Posts : 4272

Posted 12/15/2015 4:18 AM (GMT -6)

I just read elsewhere that 2014 is now compatible with El Capitan, so it may not be necessary...I lost the link just now, hopefully pick it up again in a while

Vaughan
Registered Member

Date Joined Jun 1999
Total Posts : 4984

Posted 12/15/2015 6:24 AM (GMT -6)

Unfortunately, due to a programming deficiency in the last couple of versions of Finale, it will eventually and inevitably be necessary to update your old files to adhere to 2014.5's (and future versions) correcter way of dealing with font styles. It might be possible to get MM (or someone else... via a lua script?) to write some kind of conversion patch.

Vaughan

Finale 3.2 - 2014.5, Sibelius 4 - 7
Tobias Giesen's plugins, full version, Robert Patterson plugins, Dolet 6 plugin
MacOS 10.11.1
MacPro 6GB, MacBookPro (2011) 8GB

Amsterdam

Forum Information

Currently it is Tuesday, December 19, 2023 8:32 PM (GMT -6)
There are a total of 403,820 posts in 58,165 threads.
In the last 3 days there were 0 new threads and 0 reply posts. View Active Threads

Need Support? | Forum Help Manual