Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Colour profile is ignored on external monitors #1913

Closed
AlexanderOcias opened this issue Oct 30, 2018 · 2 comments
Closed

Colour profile is ignored on external monitors #1913

AlexanderOcias opened this issue Oct 30, 2018 · 2 comments
Assignees
Milestone

Comments

@AlexanderOcias
Copy link

AlexanderOcias commented Oct 30, 2018

Colour profiles are only correctly used on the first screen, when Aseprite is on an external monitor, it will ignore colour profiles.

For example, to easily see the difference, changing the native screen's profile to the lower gamma "ACES", results in a correctly darkened Aseprite (both screenshots matched to sRGB for clarity):

Native Screen

nativecolour

When doing the same on an external screen, Aseprite ignores the profile change and stays bright:

External Screen

externalcolour

Aseprite and System version

  • Aseprite version: v1.2.10-beta2, portable
  • System: macOS 10.14
@dacap dacap added the macos label Oct 31, 2018
@dacap
Copy link
Member

dacap commented Oct 31, 2018

Yeah 👍 something in my to-do list for the final version is support for multiple monitor with different color profiles (when we move the window from one monitor to another, the color space can change, so we've to update the surface).

You can check if moving the window to the other monitor, and resizing the window does update the color profile correctly. The same when you change the color profile, but it might not work anyway (I think the color space is taken from the main screen only, not the display where the window is located)

@dacap dacap added the bug label Oct 31, 2018
@AlexanderOcias
Copy link
Author

Thanks decap! I experimented and found a temporary workaround to be to put the 'primary menubar' on the display you DON'T need the profile to work on, like so, in this setting:
screen shot 2018-10-31 at 6 16 34 pm

@dacap dacap added refactor complexity This issue needs some refactor / modifying several files / rethinking some part of the architecture and removed refactor complexity This issue needs some refactor / modifying several files / rethinking some part of the architecture labels Nov 5, 2018
@dacap dacap self-assigned this Nov 5, 2018
@dacap dacap added this to the v1.2 milestone Nov 30, 2018
dacap added a commit that referenced this issue Dec 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants