Print color problem

New post

Gualtiero De Pippis Posted October 09, 2017 20:54

Hi everyone!

I have a strange problem.

I tried to print 2 differents PDF files created with Finale 25.4.1.163: the first one appeared really black (noteheads, beams, etc...), the second one appeared not black like the first.

My "print-man" operator tells me that the second file appeared "print with color" and so not black but like " a scale of gray".

Can anyone help me?

Thanks!

Mac OS 10.13 (High Sierra) with Finale 25.4.1.163

8 comments

Date Votes

PETER THOMSEN Posted October 09, 2017 21:40

To get true Black-and-White PDF, use the Graphics Tool.

Graphics menu > Export Pages…

In the dialog box Export Pages, set the Type to PDF.

Gualtiero De Pippis Posted October 10, 2017 08:34

Thanks, Peter...seems to work fine!

One question: why did it happen? And...why there's a difference between Export->PDF and Print->PDF ?

PETER THOMSEN Posted October 10, 2017 14:21

… why there's a difference between Export->PDF and Print->PDF ? …

Both ways ought to give a true Black-and-White PDF.

That the Print data are not true Black-and-White, is an old bug, IIRC.

Gualtiero De Pippis Posted October 10, 2017 15:44

Very very grateful!

Bye!

MIKE HALLORAN Posted October 10, 2017 15:44

Not certain it’s a bug but I have no idea why this change was made for Finale 25.

VAUGHAN SCHLEPP Posted October 10, 2017 18:05

I've occasionally had this problem with some publishers who claimed that the PDFs I sent them from Finale were about 87% grey. It may have to do with Finale's colour output and it's indeed an old bug. Peter's solution above works, but you can also take the offending PDF and load it into a program like ColorSync (part of the OS, included in the Applications/Utilities folder) and use the filters to create a B/W and save it as a PDF-X3 document. If you have a number of PDFs you've already created or you need to make many of them, this method might be faster in the long run.

MIKE HALLORAN Posted October 10, 2017 18:36

> and it's indeed an old bug.<

If so, it is not one that affects 2014.5. This showed up in 25. There's an old thread where I examined this in F-1998, 2003, 2011, 2014, 2014.5 and 25. Again, I'm not certain that it's a bug but, if they did it on purpose, I don't understand why.

Gualtiero De Pippis Posted October 11, 2017 06:30

Thanks guys!

Please sign in to leave a comment.