Jump to content
Jakerlund

[By Design] Outer shadow or blur gets really offset

Recommended Posts

Perhaps 16bit publisher documents are a solution looking for a problem.

Q: "Why did you include that particular feature?"

A: "Because we could."


MacBook Pro (13-inch, Mid 2012) Mac OS 10.12.6 || Mac Pro (Late 2013) Mac OS 10.14.5

Affinity Designer 1.7.3 | Affinity Photo 1.7.3 | Affinity Publisher 1.7.3 | Affinity Designer Beta 1.7.x.x | Affinity Photo Beta 1.7.x.x | Affinity Publisher Beta 1.8.0.499

Share this post


Link to post
Share on other sites

I'm sure there is some reason for the 16 bit option.
You should start a new thread and maybe someone will give you the answers.

Share this post


Link to post
Share on other sites

I can think of at least two reasons:

  • Compatibility with Photo and Designer
  • Future support for digital publishing when producing content for displays with greater than 8-bit color depth (these do exist...)

Share this post


Link to post
Share on other sites
Posted (edited)

The reason for 16 bit doesn't have to be in Publisher.
Possibly it got implemented in Publisher for no purpose but just because the code existed from Photo already. Or as Old Bruce puts it, "Because we could."

EDIT: probably for the same reason – but in Publisher without much sense, too – you can place .RAW and .DNG files in an .afpub document.

Edited by thomaso

macOS 10.12.6,  Macbook Pro 15" + Eizo 24"

Share this post


Link to post
Share on other sites

Hi all,

Definitely a problem with Preview, as everything else seems to be fine. I suggest you log this with Apple. 

I've closed this as By design.

Thanks,

Gabe. 

Share this post


Link to post
Share on other sites
1 hour ago, mac_heibu said:

No logging with Apple necessary, because it is working in Mojave. Apple surly won’t debug and older system version. :)

One of the indications was that it was broken in 10.13 though, so they might considering that 10.13 is the prior version.  Apple usually provides security updates for at least two major versions back, which right now would be 10.12 and 10.13 in addition to the current version of 10.14...  even after 10.15 comes out they would still be providing security updates for 10.13, so an issue like this one in 10.13, before 10.15 is released, just might slip into their queue...

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.