Screen Savers broken function on 2+ monitor system in Ventura 13.3 beta (FB12023530) about aerial HOT 154 CLOSED

I, too, am seeing the correct monitor coordinates in my logs, but then the playback on the second screen (which seems to actually be the first screen's process) is offset.

My monitor setup:

• M1 Macbook Air Built in display : Default scaling (frame = 0,0, 1440x900)
• External 24" monitor Default scaling (frame = 1440, -250, 1680x1050)

Arrangement:

However, if I mess around with monitor arrangement, it always looks the same, so I suspect it's not the monitor's relative locations, but perhaps their Sizes which is relevant?

Here's what I see when running. The built-in screen is blank, and the 2nd monitor is offset:

Edit to add: in fact, I'm pretty sure that's the issue, the first screen is playing on the second screen, and since they aren't the same size, no wonder it doesn't fill the screen!

from aerial.

Oh this is fun. With four monitors it does this.

from aerial.

This issue is occurring on my production Ventura 13.3. In fact here is Activity, note the %100 percent CPU as well.

from aerial.

To recap again, this is only (kinda) fixed in 13.4 for people with 2 monitors only (it still randomly fails 5% of the time).

Setups with 3 or more screens still fail all the time. Hopes for those are on 13.5 beta now.

Edit : 13.5beta1 shows no progress, sadly.

from aerial.

@Retroghost-X so yes, they fixed the issue for their own 1st party screensavers (like Messages), we mentioned it above, around beta 4 if I recall correctly. As we pointed at the time, that was disappointing. Precisely because I knew I'd get comments like that.

However, nope this is not an Aerial issue, I can confirm to you that this is an issue with every single 3rd party screen saver (feel free to try any yourself).

The issue is precisely around legacyScreenSaver.appex, which is the macOS bridge that Apple made to run all 3rd party screen savers (and some 1st party, but they changed that to fix their issue) since Catalina. This thing has been the root cause of many many issues, and still is. I've lost countless hours to this thing, reporting bugs to Apple, working around their bugs, or just doing support every time something breaks. This is exhausting.

Apple has a new API for their own screensavers, which we can't use yet. And even they don't use it all the time themselves (they do have other "bridges"). It's a real mess, but there's nothing I can do about it.

from aerial.

From further debugging it appears as if:

• Screen[0] is basically working normally, except the display is showing up on Screen[1]
• Screen[1] gets the initialize call, hasConfigureScheet but nothing after that (No StartAnimation event, etc. )

from aerial.

I updated my feedback with Apple but please file one so they get what they need to reproduce.

Yup filed as FB12085443

from aerial.

Related discussion on Apple Developer Forums: https://developer.apple.com/forums/thread/727168

from aerial.

@Fofer this is not an Aerial bug, it affects every single 3rd party screen saver and some 1st party screensaver (for example the Message one from Apple). As to why it worked once, the bug happen about 80-90% of the time, so you may see the odd time when everything works.

The bug is in macOS Ventura 13.3 specifically and 13.4 has a (partial for now) fix for the issue.

from aerial.

I can confirm that the issue is intermittent. I just opened System Settings and hit Preview, and Aerial showed the laptop-sized image on my 27-inch external, and nothing on the laptop screen. I then quit System Settings and initiated Aerial via a hot corner, and it behaved correctly. Exited Aerial, then re-initiated it via the hot corner, and it was borked again. Hope this might help troubleshoot the issue somehow?

[16-inch M1 Max MacBook Pro, running Ventura 13.3]

from aerial.

I will add that the bug still occurs even with 2 monitors, some of the time, maybe 5% ? And I still had it in beta2 right now :(

from aerial.

Confirmed still broken with 3 monitors on Beta3

from aerial.

@nickroberts apologies, you are correct, I just tried with beta4 and Messages does work in beta4 unlike previous macOS builds. This is not a particularly good omen for a complete fix if they just fixed their own stuff (again) and not 3rd parties.

(And reinstalling Aerial won't do anything at this point, this is a bug in macOS if that wasn't clear)

from aerial.

Still broken on 13.5 Beta (22G5027e) for >= 3 monitors.

Not sure why I even bother anymore. Haha. Hopefully someday we can get a fix! I so miss my Aerial!

from aerial.

Good point, I think you are right.

I just did a bunch of tests in a row with both the Aerial and macOS Messages screensaver and you seem to be correct - it's failing pretty much randomly now, working about 20%-30% of the time.

X = fail
√ = works

Messages: X X X X X √ X X X √ X X √ √√ √ X X √
Aerial: X √ X X X X X X X X X √ X X √ √ X √ √ X X X

I did not do this sort of repeated testing in 13.3 beta 3 or earlier, so I can't say if anything has changed in beta 4.

from aerial.

Unfortunately, updating to 13.4beta1 did not resolve this bug for me. I am running a three monitor system on a Mac Studio

Do you have more info ? Can you replicate with the built-in Messages screensaver ? If so please make a bug report to Apple and mention FB12007471

I cannot reproduce the issue with the built in Messages screensaver, it only happens with Aerial and other third party screensavers. I am seeing a single video playing on one of my secondary monitors but offset and smaller like shown above.

from aerial.

@spawnofbill How are you launching the screensaver? Letting it time out? Using a Hot Corner? Using the "Preview" button (which means the System Settings panel is open. These situations are different and relevant for how the legacyScreenSaver process works...

Also, if you are able, would you please try a demo screensaver from iScreensaver, such as: https://iscreensaver.com/downloads/savers/InstallSpaceSaver.app.zip

Preview, Hot Corner and letting the display time out all display the same symptoms with Aerial. iScreensaver does the same.

from aerial.

So interesting update, I just unplugged one of my monitors and Aerial worked perfectly fine. So something is wrong with how MacOS 13.4 handles more than two monitors now instead of just more than one.

from aerial.

Well did the update, NOT FIXED.
I guess my question is how hard is this to fix? It worked fine before and then it stopped, so what did they change?
Let me guess..... Apple added some new, improved, great features that no one will really like or use.

from aerial.

I have noticed, being on macOS 13.3.1,

When screensavers are coming due to inactivity timeout they are working fine, but when forced using preview or alfred screen saver command they result in this issue.

from aerial.

macOS Ventura 13.3.1 (a)
If I could figure out how to revert to the previous version, whatever that was I would test.

@jamesrn you can find every version here : https://github.com/JohnCoates/Aerial/releases

Make sure you quit Companion if you are running it, close System Settings, and double click the .saver file from the zip you downloaded.

But at this point I'm 100000% confident this issue is not linked to today's release. We got it pretty well documented, we know there's a partial fix in 13.4, and we know how partial it is. We also have good reasons to believe Apple is actilvely working on it.

Also, know that it's not a 100% failure rate, it's more like 80/90% so that could impact your perception too. I wouldn't waste time to try older versions, but if you do, don't just test once, as it usually works the first time anyway.

from aerial.

I came here to report the same with macOS 13.3. I just added a 2nd 4K Dell display to enjoy it with Ventura on my M1 Mac mini. Only once, did I see Aerial display with the video "spanning" across both screens, and now I can't get it to display that way again. I've tried everything, It's only showing up on the left screen, not my primary.

glouel wrote:

@Fofer this is not an Aerial bug, it affects every single 3rd party screen saver and some 1st party screensaver (for example the Message one from Apple). As to why it worked once, the bug happen about 80-90% of the time, so you may see the odd time when everything works.

The bug is in macOS Ventura 13.3 specifically and 13.4 has a (partial for now) fix for the issue.

Yep! Thanks for that response. Just wanted to followup, I upgraded to Ventura 13.4 today and this functionality is working just fine now on my M1 Mac mini setup. Two displays, one horizontal and one vertical, with the "spanning" feature including both nicely. Super cool! Hopefully others with similar setups experience the same, because as far as screensavers go, Aerial is the best.

from aerial.

macOS 13.4 (22F66) on a 2020 M1 Mac Mini. I have one LG display as my primary and a Dell 27" as a secondary, in vertical orientation.

from aerial.

from aerial.

@glouel - many thanks for that reply, that is really helpful for me. Apologies for causing annoyance as a newbie. Your work and effort is really appreciate across the world.

What you describe sounds intensely frustrating and unhelpful on Apple's part.

from aerial.

Thanks, can confirm, I also reported it. I did see we were initialized on both screen but didn't catch that no StartAnimation event was sent. I'll update my FB with a referal here. The issue appeared in the 1st beta also, fyi.

from aerial.

In a prior version of macOS (can't remember if it was Monterey or Big Sur?) there was a bug where StartAnimation never fired, so I simply added a flag and a callback timer, e.g.

Init
  Set 1 second timer

StartAnimation
   bStartAnimationCalled=true

TimerCallback
   if bStartanimationCalled  == false
     StartAnimation()  // in case StartAnimation wasn't called, call it now

I wonder if this trick would help in Ventura?

from aerial.

I was having a second look, more precisely this part of your message :

Actual behavior: the screen’s rectangle seems to be offset by about 100 pixels (as if the NSView is not set to the actual screen coordinates)

I can't say I'm seeing this here, I get the correct coordinates passed in the init at least :

2023-03-01 18:11:12.711 : avInit .saver (0.0, 0.0, 2560.0, 1440.0) p: false o: false
2023-03-01 18:11:12.859 : avInit .saver (2560.0, 0.0, 2560.0, 1440.0) p: false o: false

(this is one 5K monitor and one 2560x 1440 monitor, so retina factor 2 and 1 respectively)

So at least here I can correctly match to the monitor informations. I don't seem to see an offset although maybe there's one and I didn't notice it with the videos. There's no black part anywhere at least.

Regarding startAnimation, this was on a run where it launched correctly on both :

2023-03-01 18:11:13.221 : <AerialView: 0x12a767eb0> startAnimation frame (0.0, 0.0, 2560.0, 1440.0) bounds (0.0, 0.0, 2560.0, 1440.0)
2023-03-01 18:11:13.383 : <AerialView: 0x12b8058c0> startAnimation frame (0.0, 0.0, 2560.0, 1440.0) bounds (0.0, 0.0, 2560.0, 1440.0)

This is however what I get with a more failed on first monitor launch :

2023-03-01 18:21:07.325 : <AerialView: 0x13e80a610> startAnimation frame (0.0, 0.0, 2560.0, 1440.0) bounds (0.0, 0.0, 2560.0, 1440.0)

Only one call of startAnimation.

So yeah, there's a good chance your workaround could actually work, I'll see if I can give it a shot quickly, it's likely you got the root cause here.

from aerial.

Yeah I was going to say, this looks like the size of your main monitor running on the second, because mine are similar sized I didn't see that part.

I'm wondering at what point the coordinates get wrecked, I'll try messing with resolution to dig a bit more.

from aerial.

Ok so, I tried your idea for a workaround but I think that the original issue that you noted is not allowing us to fix it ourselves :

2023-03-01 18:40:39.752 : avInit .saver (0.0, 0.0, 2560.0, 1440.0) p: false o: false
2023-03-01 18:40:39.753 : <AerialView: 0x13f13cd60> AerialView setup init (V3.2.4) preview: false

0x13f13cd60 : This is the init on main screen

2023-03-01 18:40:39.921 : avInit .saver (2560.0, 0.0, 2560.0, 1440.0) p: false o: false
2023-03-01 18:40:39.922 : <AerialView: 0x139922a60> AerialView setup init (V3.2.4) preview: false

0x139922a60 : This is the second screen, correct coordinates here

Now, this is the startAnimation that goes through :

2023-03-01 18:40:40.274 : <AerialView: 0x13f13cd60> startAnimation frame (0.0, 0.0, 2560.0, 1440.0) bounds (0.0, 0.0, 2560.0, 1440.0)

This is the init of the main screen. But we know it shows up on the secondary despite correct frame and bounds.

The workaround does kick in for the secondary monitor :

2023-03-01 18:40:40.967 : forcing startAnimation (workaround Ventura 13.3beta
2023-03-01 18:40:40.968 : <AerialView: 0x139922a60> startAnimation frame (2560.0, 0.0, 2560.0, 1440.0) bounds (0.0, 0.0, 2560.0, 1440.0)

This does not do anything for me, it doesn't replace the first one for example.

Again coordinates are correct, but the view is not displayed where it should despite what it says. So I think you're correct here, for some reason in some cases, the main screen thread's NSView is mistakenly put on the second monitor. I'll try to double check by changing resolution.

from aerial.

yeah, it feels as if this is an OS bug.

If I run Console set to show Errors and Warnings, and test using apple's Message screensaver, I see errors which are suggestive of some sort of problem:

error	09:49:11.053147-0800	CoreFoundation	ScreenSaverEngine	Attempt to load executable of a type that cannot be dynamically loaded for CFBundle 0x60000103a000 </System/Library/Frameworks/ScreenSaver.framework/PlugIns/Computer Name.appex> (executable, not loaded)
error	09:49:11.056956-0800	ExtensionFoundation	ScreenSaverEngine	Extension request contains input items but the extension point does not specify a set of allowed payload classes. The extension point's NSExtensionContext subclass must implement `+_allowedItemPayloadClasses`. This must return the set of allowed NSExtensionItem payload classes. In future, this request will fail with an error.
error	09:49:11.062119-0800	SkyLight	WindowServer	CGLayerKit called back with no connection
error	09:49:11.073596-0800	SkyLight	WindowServer	CGLayerKit called back with no connection
error	09:49:11.064167-0800	pkd	pkd	could not fetch persona generation ID (Error Domain=PlugInKit Code=-1 "persona generation ID unavailable" UserInfo={NSLocalizedDescription=persona generation ID unavailable}), flushing cache
error	09:49:11.074242-0800	SkyLight	WindowServer	CGLayerKit called back with no connection
error	09:49:11.075145-0800	SkyLight	WindowServer	CGLayerKit called back with no connection
error	09:49:11.079260-0800	SkyLight	WindowServer	CGLayerKit called back with no connection
error	09:49:11.093786-0800	RunningBoard	runningboardd	memorystatus_control error: MEMORYSTATUS_CMD_CONVERT_MEMLIMIT_MB(-1) returned -1 22 (Invalid argument)
error	09:49:11.093914-0800	RunningBoard	runningboardd	memorystatus_control error: MEMORYSTATUS_CMD_CONVERT_MEMLIMIT_MB(0) returned -1 22 (Invalid argument)
error	09:49:11.100191-0800	SkyLight	WindowServer	CGLayerKit called back with no connection
error	09:49:11.107122-0800	AppKit	loginwindow	Warning: Window LUI2Window 0x143b1c060 ordered front from a non-active application and may order beneath the active application's windows.
error	09:49:11.107300-0800	AppKit	loginwindow	Warning: Window LUI2Window 0x143940890 ordered front from a non-active application and may order beneath the active application's windows.
error	09:49:11.107395-0800	AppKit	loginwindow	Warning: Window LUI2Window 0x143d1c110 ordered front from a non-active application and may order beneath the active application's windows.
error	09:49:11.107772-0800	AppKit	loginwindow	Warning: Window LUI2Window 0x143a0f780 ordered front from a non-active application and may order beneath the active application's windows.
error	09:49:11.108216-0800	AppKit	loginwindow	Warning: Window LUI2Window 0x143b1c060 ordered front from a non-active application and may order beneath the active application's windows.
error	09:49:11.109992-0800	launchservicesd	launchservicesd	Application App:"loginwindow" asn:0x0-2002 pid:568 refs=7 @ 0x1294098e0 tried to be brought forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x1bd1bd pid=6021 "Screen Saver"")), so denying.
error	09:49:11.110061-0800	SkyLight	WindowServer	0[SetFrontProcess]: [cps/setfront] Failed setting the front application to <private>, psn 0x0-0x2002, securitySessionID=0x186ad, err=-13066

from aerial.

Test with resolution changed to 1920 on secondary :

[id=7, width=2560, height=1440, bottomLeftFrame=(0.0, 0.0, 2560.0, 1440.0), topRightCorner=(2560.0, 1440.0), isMain=true, backingScaleFactor=2.0]
[id=6, width=1920, height=1080, bottomLeftFrame=(2560.0, 360.0, 1920.0, 1080.0), topRightCorner=(4480.0, 1440.0), isMain=false, backingScaleFactor=1.0]

What I get

2023-03-01 18:47:50.789 : avInit .saver (0.0, 0.0, 2560.0, 1440.0) p: false o: false
2023-03-01 18:47:50.789 : <AerialView: 0x13b033b30> AerialView setup init (V3.2.4) preview: false

0x13b033b30 : First screen

2023-03-01 18:47:50.950 : avInit .saver (2560.0, 360.0, 1920.0, 1080.0) p: false o: false
2023-03-01 18:47:50.951 : <AerialView: 0x13b0dfe50> AerialView setup init (V3.2.4) preview: false

Second thread with correct coordinates + size.

2023-03-01 18:47:51.311 : <AerialView: 0x13b033b30> startAnimation frame (0.0, 0.0, 2560.0, 1440.0) bounds (0.0, 0.0, 2560.0, 1440.0)

This is the main screen frame that is started ! And visually I can confirm, in my case it shows blown up (missing top/right part) on the secondary screen.

2023-03-01 18:47:51.994 : forcing startAnimation (workaround Ventura 13.3beta
2023-03-01 18:47:51.996 : <AerialView: 0x13b0dfe50> startAnimation frame (2560.0, 360.0, 1920.0, 1080.0) bounds (0.0, 0.0, 1920.0, 1080.0)

The secondary thread is force started but this is irrelevant.

So again thanks for your input on this, I'll update the FB again (I reported it as FB12007471).

from aerial.

I just tested 13.3 beta 3 - no change, it's still malfunctioning. :(

from aerial.

Hello, I have this issue. If someone needs help with testing or if I can help please let me know.

from aerial.

I just tested 13.3 beta 4, and had very weird results.

Tried Aerial: worked
Tried a screensaver built using iScreensaver: did work.
Tried a different screensaver saver built using iScreensaver: did not work

Went back and tried the prior screensaver: did not work.

Went back and tried Aerial again. did not work.

This seems reproducible:

• Restart in 13.3 beta 4
• Launch Aerial (using Hot Corner). Result: works on 2 monitors
• Exit screensaver
• Launch Aerial (using Hot Corner). Result: fails: only shows on 2nd monitor

Advice: If you test with 13.3 beta 4, don't just do a single test and say "good" - do some repeated tests.

Further testing:

• restarting restores normal operation (but only for 1 launch)
• logging out, back in: does not restore normal operation.

from aerial.

So I'm not sure if anything really changed, because it worked some of the time previously here, and maybe it works a bit more often but if I launch 10 times in a row I still get some working and some failings. It may work more often that before, but it's not as clear as you described at least here, failures and workings are still intertwined (just testing with Aerial multiple times in a row).

from aerial.

Afternoon, I just updated to the Beta 4 & Aerial is still not working, I tried to start it by using my Hot Corner.

I will see if a different SS has any better success.

from aerial.

Tried the following

Message - Did not do anything, tried preview & hot corner activation
Word Of Day - worked HC Activation
Ventura - worked HC Activation
Album Artwork - worked HC Activation
Monterey - worked HC Activation

from aerial.

pretty much randomly now, working about 20%-30% of the time.

Can confirm I have the same in b4

I did not do this sort of repeated testing in 13.3 beta 3 or earlier, so I can't say if anything has changed in beta 4.

I didn't either, but I would have said it worked less frequently than that, maybe 15-20% ? At this point who knows. I updated my radar with the relevant info, I'm hopeful they are actively looking at it. Fingers crossed !

from aerial.

You know My I-Mac woke me up the other day, it had a Panic Attack, I did not think about it till now, wonder if it had something to do with all this.....

Would the Diag Dump be some where ? If so would it help you ?

from aerial.

@DSBlackHeart did it fully woke up or did the screen just woke up (staying black) ?

I've had the second bug on my secondary screen for months (a regular non apple monitor, connected via USB-C to DP cable), it wakes up (staying black) and goes back to real sleep after 20-30s, maybe once an hour and I never bothered to look up what was happening.

In any case it's likely not related to this, at least not on the screen saver side as the screen saver has no power to either put your mac to sleep or wake it up, macOS is always the one in control.

Should this happen again, use Feedback assistant to collect the relevant data as soon as you see it waking up and note the time it happened, as only Apple can fix those issues.

from aerial.

Panic attack - it restarted the system

The stuff above i tested the screen is black but backlight is lit

from aerial.

Kernel Panic ? Definitely report those to Apple, likely unrelated !

from aerial.

I just tested the latest beta, which no longer says Beta, version = 13.3 (22E252) and the bug is still there. Various websites are saying this version of 13.3 is the RC (Release Candidate) version.

Does anyone know a way to get some attention at Apple for this to escalate it?

from aerial.

I still have the issue as well, I looked in the release notes and did not see any mention of a fix. The only problem with trying to get someone at Apple to do something about it is you have to go through about 10+ dumb people before you find someone who knows what is happening.
The standard:
Delete the Prefs
reset the SMC
do a clean system install

Things you know 110% are not going to fix the problem.

from aerial.

@xmddmx @DSBlackHeart

Just installed 13.4beta1 (released today) and thankfully, they fixed it! Let's hope they don't break it again and they release 13.4 quickly now ;)

from aerial.

13.4 beta 1 also working for me in initial tests on a 2 monitor system.

from aerial.

I am looking forward to trying out the update, I dont see it posted on my end yet but looking forward to the install. :)

from aerial.

Unfortunately, updating to 13.4beta1 did not resolve this bug for me. I am running a three monitor system on a Mac Studio

from aerial.

Unfortunately, updating to 13.4beta1 did not resolve this bug for me. I am running a three monitor system on a Mac Studio

Do you have more info ? Can you replicate with the built-in Messages screensaver ? If so please make a bug report to Apple and mention FB12007471

from aerial.

That's weird, thanks for following up. Please make a report to Apple as they might gather some information from your report to see why it's not fixed in your specific case, looks like they missed something.

from aerial.

@spawnofbill How are you launching the screensaver? Letting it time out? Using a Hot Corner? Using the "Preview" button (which means the System Settings panel is open. These situations are different and relevant for how the legacyScreenSaver process works...

Also, if you are able, would you please try a demo screensaver from iScreensaver, such as: https://iscreensaver.com/downloads/savers/InstallSpaceSaver.app.zip

from aerial.

I updated my feedback with Apple but please file one so they get what they need to reproduce.

from aerial.

I know this feeling....

from aerial.

I have checked several times but i dont see this update posted yet, I am still at 13.3 ( 22E252 )

from aerial.

I, too, am seeing the correct monitor coordinates in my logs, but then the playback on the second screen (which seems to actually be the first screen's process) is offset.

My monitor setup:

• M1 Macbook Air Built in display : Default scaling (frame = 0,0, 1440x900)
• External 24" monitor Default scaling (frame = 1440, -250, 1680x1050)

Arrangement:

However, if I mess around with monitor arrangement, it always looks the same, so I suspect it's not the monitor's relative locations, but perhaps their Sizes which is relevant?

Here's what I see when running. The built-in screen is blank, and the 2nd monitor is offset:

Edit to add: in fact, I'm pretty sure that's the issue, the first screen is playing on the second screen, and since they aren't the same size, no wonder it doesn't fill the screen!

I'm seeing this exact same behaviour on Ventura 13.3 after the recent security update. I can confirm that Aerial was working just fine before. When Aerial is set to main display or the Macbook display it doesn't show on the macbook, only the external screen.

from aerial.

Probably related, though not exactly the same - on a rotated screen, the video rotates wrong on the second screen and also cuts off (the video on the vertical screen is rotated 90 degrees, wrongly). On an M1 MBP

from aerial.

@jbkkd the puzzling part to me on that one is that you have the text at the correct position at the bottom, so that means Aerial gets the correct stuff . It looks like a regression of an old bug though with the quicktime APIs not getting the rotation information, or getting wrong screen somehow. Weird.

This is on 13.4beta1?

from aerial.

Nope - I'm on 13.2.1, running Aerial 3.2.3

from aerial.

Just an open thought....

Has anyone tried to replicate this on the production release?

Ventura 13.3 use "terminal" to download the full installer and then install it in a disk partition to see if it still fails ?

Or did I just volunteer to have something to do on my day off ? LOL

from aerial.

Yes, I came here to report the same with macOS 13.3. I just added a 2nd 4K Dell display to enjoy it with Ventura on my M1 Mac mini. Only once, did I see Aerial display with the video "spanning" across both screens, and now I can't get it to display that way again. I've tried everything, It's only showing up on the left screen, not my primary. The other screensavers I have installed are working fine. Sad, as Aerial is, by far, the best screensaver in the universe! Hopefully it can be addressed, otherwise I'll miss it greatly :(

from aerial.

I installed MacOS 13.3 release version. I have 4 monitors (M1 Mackbook built in, 1 FHD and 2 4K monitors). Desktop Aerial background works great. Screensaver won't launch (screen just goes black). I have updated to the latest beta of both Companion and Aerial. Latest GA version had the same issue. I can view them via the app, but the screensaver won't start. Options via Settings doesn't work, but does via the Companion app. I tried having the video play on all monitors (independently - which I've used for years) as well as one by one individual windows and it won't start. I also found that while I can use Aerial on my main screen for desktop, on all secondary screens I just get the usual Wallpaper setting. I wondered after read the Docs and FAQs if it might be an advanced setting, so I disabled Brightness control and Vibrance (under Filters). I'm using 4K videos as the format. Overlays seem to make no difference. Looking forward to a resolution to this!!

from aerial.

I installed MacOS 13.3 release version.

Please see my message above. If you have access to macOS Betas, the bug is partially fixed in 13.4beta1, although it seems it doesn't work with 3 monitors (and likely not 4 either).

Options via Settings doesn't work, but does via the Companion app.

Yes there's something weird with System Settings, again. Closing and reopening System Settings seems to fix it.

from aerial.

I installed MacOS 13.3 release version.

Please see my message above. If you have access to macOS Betas, the bug is partially fixed in 13.4beta1, although it seems it doesn't work with 3 monitors (and likely not 4 either).

I figured. I'm not on the Apple Betas as I use it for work, but will update as soon as it is released.

Options via Settings doesn't work, but does via the Companion app.

Yes there's something weird with System Settings, again. Closing and reopening System Settings seems to fix it.

I realized that it works the first time you open it after starting Settings, but if you close the Options window and try and reopen it, it doesn't open. The fi is to close and restart Settings.

from aerial.

Same here.

If you go to Experimental - Launch settings - Displays and select to only show on Main, it will only show on the external, if you chose external only - you get no screen saver. The laptop screen never shows the screen saver atm. For me, using hot corners didn't change anything

from aerial.

@glaphi @jiclark just in case you missed it in the amount of messages, the bug is in macOS 13.3 specifically, and is partially fixed in macOS 13.4beta1 (at least for 2 monitors, jury is still out on more monitors on latest beta).

See the message I added at the very top of the post here for more details, as much as I'd like to, there's nothing I can do :(

from aerial.

On my system, it only appears on 1 display. so not a complete fix

from aerial.

Thanks @glouel; I did see that above, but wanted you to know that it still works intermittently, in case that helps somehow. I absolutely adore this screensaver, so I can be patient while we wait for Apple to fix the damn bug...

from aerial.

I just experienced this as well. Ventura 13.3.1 (not beta). I don't usually have a second monitor connected so I didn't see it until today. I also didn't update to Ventura until a couple weeks ago. I went to download an update to Aerial thinking I probably had an outdated version and it had probably been fixed but found this fun thread. I haven't tried it with a beta of macOS.

from aerial.

from aerial.

I have noticed, being on macOS 13.3.1,

When screensavers are coming due to inactivity timeout they are working fine, but when forced using preview or alfred screen saver command they result in this issue.

Exactly the same for me on 13.3.1 - inactivity screensaver works fine. Any attempt to manually start the screensaver (I use a hotkey which also locks the screen), will result in a broken screensaver.

from aerial.

I'm running 13.3.1 and it never shows the screensaver video on my main monitor — only the second. It happens whether or not it is initiated by itself (due to inactivity) or if I initiate it manually.

My machine, in case it matters:
Model Name: iMac
Model Identifier: iMac18,3
Processor Name: Quad-Core Intel Core i7
Processor Speed: 4.2 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Hyper-Threading Technology: Enabled
Memory: 32 GB
System Firmware Version: 509.0.0.0.0
OS Loader Version: 577~129
SMC Version (system): 2.41f2

from aerial.

Mac OS Ventura 13.3.1 the screensaver on my primary 4k display stopped working.The screensaver on my secondary 1080 display still works. Glad it's not just me! 2023 MacBook Pro M2

from aerial.

It has been a problem for a while, I miss my Aerial.... All 120+ GB of Aerial Videos....

from aerial.

13.4beta 3 is out today. Testing on a 2 monitor system (Macbook Air M1) shows what appears to be normal behavior: 20 consecutive HotCorner invocations of Aerial, 100% successful operation on both montiors.

I need to get 13.4 beta 3 installed on a system which can do 3+ monitors for futher testing. Anyone out there have a 3+ monitor system who can test 13.4 beta 3?

Edit: nope, I spoke too soon. Just had one failure when testing an iScreensaver-built screensaver, in the same failure mode as we've seen before (content from 1st monitor shows on 2nd monitor, 1st monitor is blank). I did have the Screen Savers panel open at the time, but I think that was unrelated.

I did another ~30 tests (iScreensaver / using HotCorner) and had one more failure, so I would have to agree with @glouel above that even in 13.4 beta 3, on just 2 monitors, there is still an issue, and we are seeing failures something like 2% to 5% of the time. Bummer.

from aerial.

@xmddmx do you allow your mac to control with mouse keyboard an ipad maybe ? I know that this scenario failed for me with 2 monitor +iPad.

I tried 2 monitors + iPad in extend mode (so kinda 3 monitors) and can confirm it still fails in that case in beta3.

from aerial.

3 monitors here...still only on half of one. Maybe some day! (DualUp + 38" Ultrawide + DualUp)

from aerial.

After upgrading the operating system to 13.3.1, problems began to occur: the extended screen cannot be displayed in full screen (the laptop screen is black and not displayed). However, this situation does not happen every time, sometimes the display is good.

I set a 4k screensaver. I am currently using version 3.2.4beta1 (other versions do not work).

In addition, here are my hardware configurations.

from aerial.

Thanks for the report @mysoko. Per the other messages, the bug is in process of being fixed by Apple in macOS 13.4. For your case, only 2 monitors, the current 13.4 developer beta does (mostly) fix the issue.

To all, I did file again a new bug specific to the 3+ monitor situation (the one that is still not fixed in current betas) with Apple, and am - amongst other unspeakable methods - currently crossing fingers it will be picked up and acted upon 🤞

from aerial.

For your case, only 2 monitors, the current 13.4 developer beta does fix the issue.

I'm still seeing occasional (like 1% to 5%) failure rate on a 2 monitor system under 13.4 beta 3, so I would clarify this to say "it's improving" but I hesitate to say it's fixed.

from aerial.

Yeah sorry, I should have expanded on that.

I did report the small failure rate on 2 monitors as part of my aforementionned 3+ monitor bug report too, to be clear.

from aerial.

Just updated to 13.4 beta 4...no change. 3 monitors, only visible on a single external (and only part of the bottom of the screen).

All of the built-in screensavers seem to work across all 3 monitors (although they aren't spanned).

from aerial.

Thanks for confirming @nickroberts

Regarding built in, it's not all, but Messages is an example of a built in one that fails (again remember the failure rate is around 80% so it anything can work occasionnally).

from aerial.

Thanks for confirming @nickroberts

Regarding built in, it's not all, but Messages is an example of a built in one that fails (again remember the failure rate is around 80% so it anything can work occasionnally).

That may be the case, but I have started (hot corner) the Message screen saver probably at least 50 times, and not once has it failed. It always shows up on all monitors.

That's at least my experience.

Side note: I also tried removing all traces of Aerial, reinstalling the companion and trying again...still, only works on the bottom half of my right monitor (DualUp + 38" Ultrawide + DualUp).

from aerial.

Did this update today, Still no go.

from aerial.

So just curious is anyone after this last update having one of their monitors turn off?

It is not disconnected from the system " If I have a web browser open on it and playing Netflix for example I still hear sound and the monitor shows in the Displays Prefs pane "

If I restart it comes back.

I turned my hot corners off for now

If it continues to do this I will switch the input on the back of my I-Mac to rule out a bad monitor/adapter.

from aerial.

Just tested in today's 13.4 (22F62) and see no change - 2 monitors works perhaps 95% to 99% of the time.

3+ monitors fails 100% of the time.

The only noticeable change from earlier is that Apple's Message screensaver now works properly, whereas before it was the one Apple screensaver that also showed the bug.

My prior submission said "If this issue is not resolved for you [...] please file a new feedback report" so I have done so:

New report: FB12179420

from aerial.

Can confirm all the things :

• they only fixed Messages in 13.4beta 4 (and now RC).
• 3+ fails 95%+ of the time
• 2 still fails 2/5% of the time

I updated my bug reports but at this point it's clear we won't get any resolution prior to 13.5beta1 at best.

Again, sorry to everyone affected by this. I'm as frustrated as everyone on this but I'm still confident this will get fixed by Apple.

from aerial.

There's a report over on MacRumors about failures using Apple's "Shifting Tiles" screensaver, and I am seeing some weirdness as well. Basically, if you use Shifting Tiles with colors only, it works fine, but if you are using a photo album or folder of pictures, there are strange delays on 2 or 3 monitors.

I don't know if this is the same bug, or perhpas a new bug? However, I think the more bugs we can find which also affect Apple's own screensavers, the better.

If anyone can reproduce problems with Shifting Tiles it would be good to add that to your FB case (or make a new FB case?)

See https://forums.macrumors.com/threads/multimonitor-screensaver-bug-in-ventura-13-3.2384444/post-32155590

from aerial.

What I find strange is that this issue only occurred for me once I upgraded Aerials to 3.2.5 today. There was no change to macOS between when it was working well, and when it failed to work on my dual screen setup.
MacBook Pro M1 Dual Display.
macOS Ventura 13.3.1 (a)
If I could figure out how to revert to the previous version, whatever that was I would test.

from aerial.

Morning,

Well, I found out that my "Display Turning Off" problem was due to a faulty display, One of my 2 - 27" Thunderbolts finally bit the dust. So I replaced them both with the Apple Studio Display's ....

Beautiful displays. Aerial still does not work ( GRRRRRRRR )

What I have noticed is with the recent update that when My I-Mac wakes from screen saver or sleep it acts as if it has a hang-over. Everything reacts slowly, it takes 15 to 20 seconds for it to catch up. My I-mac is no slouch, I have never seen this thing bogged down by something.

Is anyone else seeing this?

I can't believe this is the same issue with displays & Aerial. ( We have documented this thing to death )

If it is something new is there a documented report already made?

Thanks in advance

Stu

from aerial.

Just curious what build of 13.4 are you on ? I am using 13.4 9 (22F66)

On both my M1 PowerBook & Intel I-Mac

from aerial.

To confirm others comments but to add a little.

MacOS 13.4, m1 mac, three monitors, Aerial only displays on one monitor in full screen. Internal Apple screen savers all work across all monitors at once - this is different to 13.3 where Apple screensavers had issues too for me. So this is now Aerial restricted under 13.4. I am not sure 13.5 will actually fix it as it may not be a macOS issue.

from aerial.

@Retroghost-X no worries, please don't take this personally, I can assure you my frustration is directed at Apple and their bug report process 😩

I've reported this precise issue the first day of the 13.3 beta cycle in february. Yet we're still here mid may!

from aerial.

@glouel
I have a curious question? And outside the BOX

What if one were to copy the "legacyScreenSaver.appex" from say Monetry or Catalina and then insert it into Ventura ? Would it work ?
I realize to do it you may have to disable SIP to get it done, but has the app changed so much that it would not work or are there other apps that would just cause a crash ?

from aerial.

@DSBlackHeart so as far as I understand, nowadays macOS stores all its files in a read only boot volume. This means you can't replace system files, and disabling SIP won't be enough to get around it. They are reusing what they did with iOS, the system is mounted as read only, you can't modify it, and then it's super easy to handle the upgrades/reinstall. It's pretty good for security, but it's annoying in some instances, like here.

There's more details here : https://superuser.com/questions/1495124/read-only-file-system-when-i-try-to-touch-in-mac-os-catalina

There was a workaround early on but it doesn't seem to work anymore. There might be another workaround but who knows.

To your specific question, even if you could replace (and in this case I would suggest, use the file from 13.2), this may not solve the issue as, as I understand it, there's some new security feature that gets triggered and "blocks" legacyScreenSaver.appex from running on those screens (I have no idea what that security feature is trying to do, it could be just a side effect they didn't anticipate).

from aerial.

Ok that is what I thought, I know to do custom ringtones you have to disable SIP & use a hack tool to get around, it is a pain. Not for the timid, average user, you can open the system up to some pretty bad crap.

from aerial.

Well Apple is notorious for including things "As Features" that no one will ever use.

from aerial.

For those of you with 3+ monitors, please also test using Apple's Sliding Shifting Tiles screensaver, set to use Photo Library -- in our tests, this is behaving strangely on 3+ monitors, suggesting that this is indeed an Apple bug, and not something limited only to third-party screensavers.

from aerial.

@xmddmx What am I looking for ?

from aerial.