Transparency + Fill Layer = Vector Crop issue

[thomaso]

If an image has reduced opacity (e.g. by a blend range curve or a transparency gradient) then a Fill Layer below is unintentionally affected as soon the image gets clipped by a nested object, e.g. via the Vector Crop Tool.

 

 

[Dan C]

Hi @thomaso,

Thanks for your report!

I've been trying to replicate this here and thus far have been unable, both when using the Transparency Tool or with a Hard Light set and the Blend Ranges edited.

Are you able to provide a sample document which shows this for me?

[thomaso]

Here it is: v1105 Transpar_FillLayer_VectorCrop.afpub

p.s.: With embedding the images for this sample .afpub I noticed that copies of an image get embedded as separate files – not as instances of 1 identical image with different DPI, like with linked images. – Is this in purpose? Any chance to get it optimized? As long a placed image is not rasterized it can't be modified and thus a copy can / must base on 1 same embedded resource, correct?

[Dan C]

Thanks for that, I'm able to replicate this in a new file now I better understand the layer composition and I don't personally believe this to be expected (as it doesn't happen with a (Pixel) layer) - however I'm not 100% certain so I have requested further investigation from our team for a definitive answer and I will be sure to update you here ASAP!

23 minutes ago, thomaso said:

With embedding the images for this sample .afpub I noticed that copies of an image get embedded as separate files – not as instances of 1 identical image with different DPI, like with linked images. – Is this in purpose?

I believe this is happening due to the 'conversion' process, from linked to embedded - as if you simply embed one version of this file and then duplicate it, they will appear under the same entry in the resource manager. Currently the app simply isn't 'smart' enough to recognise they are the same linked object being converted.

26 minutes ago, thomaso said:

Any chance to get it optimized? As long a placed image is not rasterized it can't be modified and thus a copy can / must base on 1 same embedded resource, correct?

I agree that this could be possible, so I'll get this logged with our developers as an improvement now

[Dan C]

19 hours ago, Dan C said:

Thanks for that, I'm able to replicate this in a new file now I better understand the layer composition and I don't personally believe this to be expected (as it doesn't happen with a (Pixel) layer) - however I'm not 100% certain so I have requested further investigation from our team for a definitive answer and I will be sure to update you here ASAP!

I can confirm our team believes this to be a bug with the app, so I've logged it as required with our developers - thanks for your report once again!