Split: Publisher v2 Bug: Adjustment Layers don't export to PDF properly

[Guillermo Espertino]

On 1/6/2023 at 7:15 AM, EmT said:

Hi @PaintNut

Could you attach a copy of the file for investigation? I can provide a private upload link if needed.

 

Hi, I've been experiencing the same issues, and iirc it's something that was also present in v1.
I'm attaching an afpub file and the exported PDF showing the problem. It seems that the HSL adjustments applied to the master node get passed correctly to the PDF export, but the channel nodes are ignored.

In my example you can see the overall desaturation applied got exported correctly, but the individual channels (cyans and magentas) seem to be ignored.

This bug affects also the PDF export from the other apps, not just Publisher.

HSL-bug-PublisherV2.afpub HSL-bug-PublisherV2.pdf

[stokerg]

Hi @Guillermo Espertino,

If you select the Picture in the Frame and click on the Transparency tool and set that to none on the context toolbar and export to PDF, it exports fine.  You can also leave the transparency in place and move the HSL adjustment to the top of the Layers Stack and the PDF will export fine.  You can also export to PDF/X-4 and the PDF will look fine.

So this appears to be caused by a combination of the Transparency tool and the HSL adjustment.  I'm trying to replicate this from scratch but haven't been able to as of yet.  Can you remember the workflow you used?  I'm likely missing a step somewhere or doing things in the wrong order to cause this.

 

[Guillermo Espertino]

@stokerghi, Normally I place the assets in the design and leave the color correction and grading for the last step. So it most likely went this way:

• Create an Picture frame
• select the image inside the picture frame with double click or via the layers panel
• Use the transparency tool to blend it over the background with a linear gradient
• Select the picture frame and add the HSL adjustment.

I don't know if this helps, but I normally use linked images, not embedded (I embedded the image in the sample file for convenience afterwards, but originally it was linked).

As a temporary measure I solved this by rasterizing the bitmap assets affected by this issue in a duplicate file, and as I expected worked fine. Of course it's not a desirable solution as it makes the workflow destructive.

Just a moment ago I discovered that if I group the picture frame and apply the HSL adjustment to the group it also solves the problem. As you suggested, moving the adjustment to the top level of the layer stack worked, so using a group in order to create a top-level element for the picture frame worked as well. This serves as a reasonable workaround without losing non-destructive editing, but imho this inconsistent behavior is still a bug and should be taken care of.

Thanks for your help.