Doesn't fit multiple screens with different aspect ratios

[theodormarcuOrbital]

Just installed this great screensaver and the video looks distorted (just the edges) on my Macbook's display, but not on the monitor. Any ideas how I could fix this?

[timoa]

+1

[matttargett]

+1

[gabel]

+1 same here - I assume this started with high sierra 10.13.4

[MikhailKaduchka]

+1 same with 10.13.5

[ominixamf]

this started happening my MacBook Air with 10.13.6

I noticed that it happens when the screen brightness is adjusted automatically upon light variations in the environment (or, just when I noticed, when you are coming back to your notebook and passes in front of the screen)

i don't use any external display

[jonnylangefeld]

+1 with 10.13.6

[iamsanteri]

+1 with 10.13.6

[guilherme-simoes]

+1 with 10.13.6

[alistairmcmillan]

A photo of the distortion might help identify what is going on. Hard to understand what the distortion looks like for those unaffected.

Also having said that, this seems like more of a bug with the drivers for the Macbook display than a bug in Aerial.

Might help if people could list which year and make of Mac they're seeing this distortion on.

[theodormarcuOrbital]

Doesn't fix it for me. @mpdifran @alistairmcmillan

[mpdifran]

Yeah, I think I have something similar when connected to my external monitor (21:9 ratio).

[Fastjur]

I also have this issue. When an external monitor is connected, the video on my MacBook is not full screen and zoomed in, looking rather pixelated.

[glouel]

@Fastjur Could you check this build :
https://github.com/JohnCoates/Aerial/releases/tag/v1.4.1beta2

This should fix issues in 10.13 particularly (10.14 seemed ok in 1.4), it also has a display on main monitor only option as a fallback. Can you tell me what it gives you ?

[glouel]

As far as I know this is fixed in 1.4.1, reopen otherwise

[gabel]

Fixed for me with 1.4.1 on macOs Mojave 10.14

Thank you @glouel !!

[Fastjur]

It fixed for me when updating to Mojave. Thank you!

[glouel]

Ok this really looks like a 10.13.6 bug then ! Thanks @gabel and @Fastjur for your feedback !