Skip to content

Confirmed to work on 14" M1 MBP + BetterDisplay implementation? #1

Closed

Description

@waydabber

Hi there,

just wanted to confirm that this works with the M1 MBP as well (tested on a 14" MBP with M1 Pro). Works well on a 16" M3 Max too.

I was trying to use various IOMobileFramebuffer stuff in the past (some working, some not), the only actual useful thing came out of it was inverting the screen and turning it to grayscale waydabber/BetterDisplay#2745

Is it ok with you if I add a toggle for temporal dithering in BetterDisplay for built-in screens using this method in the next app version?

https://github.com/waydabber/BetterDisplay/wiki/Eye-care:-prevent-PWM-and-or-temporal-dithering

Thank you!

(ps. an user pointed me to your project here: waydabber/BetterDisplay#1201)

Activity

  1. waydabber commented on Mar 16, 2024

    @waydabber
    Author

    Oh ok, I am just reading the ledstrain.org discussion and see various M1 MBPs working have been confirmed already, so this is not news + I see the project is MIT licensed and the method itself quite generic so my question probably does not make much sense. :) Sorry.

    Anyway, great finding, thanks for all you are doing! 👍

  2. aiaf commented on Mar 16, 2024

    @aiaf
    Owner

    It's been confirmed to work with various configurations, I've personally tested it on M2 and M3.

    Absolutely go ahead, as you mentioned, the project is MIT licensed :)

    I use BetterDisplay, and previously Monitor Control. It would be nice to have a dynamic per-display control over DCP dithering.

    Funnily enough I was testing the BlendOutputCSCMethod property today and it inverted the colors on the screen.

    Which property did you use to toggle grayscale? I can't see the options when I option+click Image Adjustments.

    I'm now focusing my efforts on trying to disable TCON-controlled (reverse temporal) dithering (not 100% proven yet), and perhaps forcing a lower bit depth on the internal display, which is proving to be really challenging.

  3. Repository owner locked and limited conversation to collaborators on Mar 16, 2024
  4. converted this issue into a discussion #2 on Mar 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions