Hi there.
Here two pictures: The original score in Finale:
And the PDF export:
Is there a way to improve this issues?
I remember this was a common thing but it seems that even version 26 has still the same problem.
Luckily I didn't upgrade.
Finale 26 - PDF export issues (still a problem).
Moderators: Peter Thomsen, miker
- castellanos
- Posts: 15
- Joined: Tue May 16, 2017 3:57 pm
- Finale Version: 27.0.0.710
- Operating System: Windows
Finale 27.0.0.710
Gigabyte - Intel Core i7-4790 3.60GHz. / 16GB RAM
Acer Aspire 5951G / Intel Core i7 2670QM - 2.20GHz. / 16GB RAM
Surface Pro 4 / Intel Core i7 6650U - 2.20GHz / 16GB RAM
All running Windows 10 Pro 64-bit.
Gigabyte - Intel Core i7-4790 3.60GHz. / 16GB RAM
Acer Aspire 5951G / Intel Core i7 2670QM - 2.20GHz. / 16GB RAM
Surface Pro 4 / Intel Core i7 6650U - 2.20GHz / 16GB RAM
All running Windows 10 Pro 64-bit.
- zuill
- Posts: 4418
- Joined: Sat Dec 10, 2016 9:35 pm
- Finale Version: Finale 2011-v26.3.1
- Operating System: Windows
If you are using the built-in method to export to pdf, don't. Instead, use the Print menu to print to a pdf writer. I use CutePDF. That should avoid the pdf export issue.
Zuill
Zuill
Windows 10, Finale 2011-v26.3.1
"When all is said and done, more is said than done."
"When all is said and done, more is said than done."
- castellanos
- Posts: 15
- Joined: Tue May 16, 2017 3:57 pm
- Finale Version: 27.0.0.710
- Operating System: Windows
I see... OK. Same as always.zuill wrote:If you are using the built-in method to export to pdf, don't.
Thanks!
Finale 27.0.0.710
Gigabyte - Intel Core i7-4790 3.60GHz. / 16GB RAM
Acer Aspire 5951G / Intel Core i7 2670QM - 2.20GHz. / 16GB RAM
Surface Pro 4 / Intel Core i7 6650U - 2.20GHz / 16GB RAM
All running Windows 10 Pro 64-bit.
Gigabyte - Intel Core i7-4790 3.60GHz. / 16GB RAM
Acer Aspire 5951G / Intel Core i7 2670QM - 2.20GHz. / 16GB RAM
Surface Pro 4 / Intel Core i7 6650U - 2.20GHz / 16GB RAM
All running Windows 10 Pro 64-bit.
- motet
- Posts: 8292
- Joined: Tue Dec 06, 2016 8:33 pm
- Finale Version: 2014.5,2011,2005,27
- Operating System: Windows
I've seldom had a problem with CutePDF, which uses Ghostscript, the GNU open-source Postscript encoder. Finale must use something different (probably something they paid good money to license). There are PDF printers others that use Ghostscript as well (e.g. PDFCreator).
I did have a curious problem recently with CutePDF. This character from the Symbol font
was rendered like this
I couldn't even find which font that second arrow was coming from. The solution was to embed the fonts, though since I have the Symbol font installed I shouldn't need to. The CutePDF people were at a loss to explain it. But this is the only rendering problem I can recall ever having, and I don't mind embedding the fonts.
I did have a curious problem recently with CutePDF. This character from the Symbol font
was rendered like this
I couldn't even find which font that second arrow was coming from. The solution was to embed the fonts, though since I have the Symbol font installed I shouldn't need to. The CutePDF people were at a loss to explain it. But this is the only rendering problem I can recall ever having, and I don't mind embedding the fonts.