gordo
-
Posts
67 -
Joined
-
Last visited
Posts posted by gordo
-
-
Please see attached vid and its PDF
I also tried duplicating the steps that you followed in your video. But I did not get the same result as you did :-(
I have no idea why it's not working for me. :-(
Hang on, I have an idea. I'll get back in a moment.
-
1 minute ago, walt.farrell said:
As I said, the K Only support/option seems to currently be only in Designer, and possibly only in Designer for Windows. As Publisher clearly has the same issue, I expect we'll see that support in Publisher in an upcoming beta release, too.
This bug has been there over many versions. Considering it's a key issue one would have expected it to be dealt with by now.
-
13 minutes ago, walt.farrell said:
No, .238 is the most current, it simply may not be on auto-update yet. The new releases are always made available via the forums before being made available by other channels.
Goofy.
I downloaded the .238 version and again, the black issue is still there :-(
-
34 minutes ago, nwhit said:
How about in the current beta 238? I also need this to work but have not had time to try in latest.
1.7.0.227 is the most current version (MAC OS) - downloaded it this morning and checked again just now and Affinity Publisher says I'm up to date. Maybe it's different on Windows?
-
1.7.0.227 The black bug continues :-(
-
3 hours ago, Chris_K said:
The devs are working on some more fixes for K only PDF exports so hopefully this will be resolved within the next couple of builds
Cheers
Good, because it’s a show stopper if it’s not fixed. And just to be clear, this refers to a K only graphic in a CMYK document that’s exported as a PDF.
-
Tried that. Doesn't make any difference. The problem remains. :-(
-
-
22 minutes ago, MikeW said:
Oh. Another thing. Did you make certain the drop shadow is really 100K?
Yes. Is your drop shadow K only?
-
-
I was using PDF for print.
When I use the pdf/x-4 stock profile the text is 100K over printing a 4/c drop shadow. Which is still wrong.
-
Sorry, but I didn't use the swatches palette. I specified the text as 100% K. Your version appears identical to mine. And when I export yours as a PDF it also converts from 100K to 4/C and the same wrong profile is embedded.
I.e. There is no difference between your file and mine.
-
A CMYK document in Black only (100K text/50%K drop shadow) with GRACoL profile selected and embedded still converts to a 4/C Black when exported as a PDF and the embedded profile changes to US Sheetfed Coated V2.
-
20 minutes ago, fde101 said:
You need to have Show Text Flow enabled in the View menu for the red dots to show up.
Clicking on the eyeball icon next to the overflow indicator on the right side of the text box toggles clipping of the text vs. allowing it to overflow the container - if you look closely it is crossed out in the second video but not in the first, so this is intended behavior.
Ah, a user bug. I'll have to talk to my developers about it.LOL
I've never had that option with other apps so I never looked for it.
-
No red dots for me.
There is an inconsistency in how the text boxes work.
Video "Text box 1" shows that sometimes you can make the text box shorter and the box gets shorter but the text doesn't disappear.
But sometimes it works properly.
Video "Text box 2" shows that sometimes you can make the text box shorter and the box gets shorter and the text does disappear. Note also that the red flag briefly shows but then disappears as the box gets shorter. However, no red dots appear.
-
Or the flag flipping to inside the text box. I can see a lot of folks not realizing that text is being cut and only discovering it after the document is printed.
-
Not sure if this is a bug or a user issue..sometimes the red flag indicating that there is more text in a text box appears and sometimes it does not. See video that show the red flag appearing with one text box but not another.
-
As far as I can see, if you place an image in PDF format that has one or more spot color channels Publisher doesn't see the extra spot channel(s). Acrobat shows the channels correctly.
If instead of placing the image that has one or more spot color channels you open it in Publisher then the extra spot color appears as a layer below the cmyk and that layer looks correct color-wise however it's no longer a spot color.
Attached is a quickly done image that can be used to test.
(I use this functionality to do packaging and Hi-Fi color separations)
-
-
If you crop an image that has text runaround of a PSD image the text wrap around is lost even though Publisher thinks it's still there.
Attached is a video that demonstrates this as well as the source image and page.
-
12 hours ago, GabrielM said:
See attached. Crash happens with other PShop PSDs. Crash didn't happen with previous versions.
I've also included the crash report if that helps.
Update: Seems to happen when the PSD image has layers as in the attached rather than if the image is flattened.
-
Ooops sorry, This is a duplicate post of the video as I didn't think both videos got attached in my previous post
-
This version crashes when trying to wrap text around an image or if I click on the edit wrap outline before specifying the wrap type - see videos.
This is a placed PSD image from Photoshop with a transparent background. The problem doesn't seem to happen with PSDs (or tiffs) exported from Affinity Photo - although those are sometimes are flipped horizontally when placed.
-
The issue might be related to this this thread about incorrect embedding of icc profiles which causes 100% black to become a 4/C black. The solution at the end of that thread was embedding the correct profile using a different application.
Still converts Black only to 4/C
in [ARCHIVE] Publisher beta on macOS threads
Posted
I think I know what the problem may be.
Although the PDF has an embedded profile it does not have a rendering intent embedded (I believe that InDesign calls this "Output Intent Profile Name")
When Acrobat opens the PDF it expects to see a rendering intent (likely true for many RIPs). If it does not see the rendering intent then it simply ignores the embedded profile and assigns an arbitrary profile and 100K gets rendered as a 4/C rich black.
Depending on how a prepress RIP is set up, you will either correctly get 1 black plate or you will incorrectly get 4 plates (one for each of the colors in the now rich black)
PhotoShop (a simple RIP) opens the Publisher PDF and displays it correctly as a CMYK file with image content only in the K channel.
Affinity Photo, on the other hand, opens the PDF and displays it as a CMYK file with image content in all channels. I.e. Affinity Photo converts the one color (K) PDF into 4/C (rich black)
I can't see a way in Publisher to embed the rendering intent (as can be done in InDesign) which would eliminate the issue.
So this lack of ability to embed the rendering intent will be problematic in production with folks getting unpredictable results. :-(