Menu
What's new
By:
Filters

Logic Pro X multi-screen jumping

Another peculiarity. Sometimes I can’t move windows directly from the 27” monitor to the 32” monitor if they are sized at full screen width. The monitors are both 4K with the same pixel size so it’s not a question of not fitting. I either have to make windows less wide or move the window via another (much smaller) screen, which has the effect of automatically resizing the window in Logic. At other times the windows transfer easily between the two 4K monitors. I also haven’t figured out this behavior.
 
jbuhler said:
I had a weird thing happen last night where I opened an old project and it opened with recent screen sets, but not the screen sets of the most recently opened project before that. [...] This is all most peculiar because this is a new machine with a completely new installation, installed a little over two weeks ago. Nothing was migrated.
Click to expand...
Screensets are exclusively loaded/saved from each project, so they don't need you to migrate anything (apart from the project file, of course!) Your new machine may have a different screen set-up from where the project was saved, of course, so Logic may have trouble placing the windows.

jbuhler said:
This is interesting and I should look into it for a variety of reasons. As far as I know I’m only using a single space. And I can’t have windows span screens so I must have the separate spaces per monitor enabled. I don’t think I’d want to have windows span screens given my configuration.
Click to expand...
This is why I keep asking what everyone's Spaces set-up is :) If you have space-per-monitor enabled, then we're done: that would explain why Logic's windows are getting snapped to a single screen. (There is some variation across MacOS versions on exactly how window grouping happens; IIRC it changed in Ventura.)

Don't worry about windows spanning screens: that was just to illustrate how multiple screens can be views onto [correction] a single desktop, but it may have made everything more confusing.

jbuhler said:
Another peculiarity. Sometimes I can’t move windows directly from the 27” monitor to the 32” monitor if they are sized at full screen width. The monitors are both 4K with the same pixel size so it’s not a question of not fitting. I either have to make windows less wide or move the window via another (much smaller) screen, which has the effect of automatically resizing the window in Logic. At other times the windows transfer easily between the two 4K monitors. I also haven’t figured out this behavior.
Click to expand...
Is your dock/menu bar on the side of one of the screens? Also it may not be measuring window dimensions in pixels (I'd have to look it up.)
 
aldous said:
Is your dock/menu bar on the side of one of the screens? Also it may not be measuring window dimensions in pixels (I'd have to look it up.)
Click to expand...
Bottom. And I have it set to disappear (so it never shows up on the top center monitor).

Here's my arrangement:

Screenshot 2024-01-31 at 10.49.49 AM.png
Left portrait: 1440x2560
Two center landscape: 2560 x 1440 (top 32", bottom 27")
Right portrait: 1200x1920

So it's here that I should set "Displays have separate spaces" to off?

Screenshot 2024-01-31 at 10.54.59 AM.png

These are all default settings.
 
jbuhler said:
Here's my arrangement:[...]
Click to expand...
Thanks... are two of those screens shown as logically overlapping? If so, I guess that would be just like partially mirroring part of a screen, so not too radical... just surprised they support it.

jbuhler said:
So it's here that I should set "Displays have separate spaces" to off?
Click to expand...
Yes, and I believe a restart is necessary. Since you don't have a reliable way to replicate the problem for before/after testing quickly, maybe just take a note of what you changed so you can put it back. (A couple of other things are influenced by that setting - where you get the menu bars and dock, for example - so it may end up being a trade-off.)
 
aldous said:
Thanks... are two of those screens shown as logically overlapping? If so, I guess that would be just like partially mirroring part of a screen, so not too radical... just surprised they support it.
Click to expand...
No, they aren't overlapping. What looks to be an overlap is just the way the menu bar is depicted. The white band between the two center screens just shows that the bottom center screen is the primary one. Beyond the two center screens there are two screens in portrait, one right, and one left.
 
aldous said:
From your screenshot, it looks like you have separate Spaces per monitor enabled, so I wouldn't expect windows to span screens. If you disable that option and restart, then windows should be able to span screens, unless something has changed (I've only got the one screen right now.)
Click to expand...
You're right. Before this I never changed the default settings for Spaces, although at some point I must have set up four of them - i.e. I had no idea what that setting did.

And by "desktops" I meant Finder desktops. Ctrl/right arrow (or sliding the Magic Mouse with two fingers) moves all three monitors to a separate desktop without that option enabled. Ima put it back.
 
aldous said:
Screensets are exclusively loaded/saved from each project, so they don't need you to migrate anything (apart from the project file, of course!) Your new machine may have a different screen set-up from where the project was saved, of course, so Logic may have trouble placing the windows.


This is why I keep asking what everyone's Spaces set-up is :) If you have space-per-monitor enabled, then we're done: that would explain why Logic's windows are getting snapped to a single screen. (There is some variation across MacOS versions on exactly how window grouping happens; IIRC it changed in Ventura.)

Don't worry about windows spanning screens: that was just to illustrate how multiple screens can be views onto [correction] a single desktop, but it may have made everything more confusing.


Is your dock/menu bar on the side of one of the screens? Also it may not be measuring window dimensions in pixels (I'd have to look it up.)
Click to expand...
Sorry! I've been wrapping a show and I didn't get any alerts that this thread was still kicking. I just switched my spaces toggle to span screens and I'll see how it goes. I didn't even know about this preference. Appreciate the insight!
 
Ok! So, this did solve the jumping screen for me. I couldn't seem to replicate the issue with any of the normal triggers. HOWEVER, I'm definitely having some issues with my video playback on my second monitor now -- this is the first time I've had this issue since moving to the M1 Max. I'm wondering if the GPU handling is different when spanning both screens? I don't have time right now to experiment, but I'm going to toggle back later and see if it's still happening. I'm running a very light spotting session with almost no plugins and just audio tracks so the CPU load is at like 13%.
 
Electric Moss said:
Ok! So, this did solve the jumping screen for me. I couldn't seem to replicate the issue with any of the normal triggers.
Click to expand...
Excellent.
Electric Moss said:
HOWEVER, I'm definitely having some issues with my video playback on my second monitor now
Click to expand...
Darn. This is a bit of an emotional rollercoaster isn't it? ;)

Sounds like an instance of this issue, which doesn't sound convincingly fixed... yet.

Re: Issues with Premiere 23.5 on M2 Ultra Studio

Sorry to hear that you are also having an issue. You might want to start a new, separate thread to get troubleshooting suggestions for your 14-inch M1 MacBook Pro with an external monitor. While you could try the solution proposed above (Displays Have Separate Spaces), this is specifically f...
community.adobe.com community.adobe.com
 
aldous said:
Excellent.

Darn. This is a bit of an emotional rollercoaster isn't it? ;)

Sounds like an instance of this issue, which doesn't sound convincingly fixed... yet.

Re: Issues with Premiere 23.5 on M2 Ultra Studio

Sorry to hear that you are also having an issue. You might want to start a new, separate thread to get troubleshooting suggestions for your 14-inch M1 MacBook Pro with an external monitor. While you could try the solution proposed above (Displays Have Separate Spaces), this is specifically f...
community.adobe.com community.adobe.com
Click to expand...
Ah, yep. That seems to check out. Oh well. It was nice, but the video playback will be a dealbreaker.

I mean, like I said from the beginning of this thread, it's totally not the end of world or anything. At least now I can hit "1" and the screen will come back if it jumps or vanishes behind the video playback.

Appreciate all the help and ideas here!
 
Just to confirm, I toggled back to "Displays have separate spaces" and the video playback issues went away immediately. Just for others to be aware, I'm on a M1 Max MacBook Pro, currently on latest version of Sonoma.
 
Electric Moss said:
At least now I can hit "1" and the screen will come back if it jumps or vanishes behind the video playback.
Click to expand...
Haaaang on... there's a detail here that I missed. Is your video playback happening in a Logic window, or a separate application?

Electric Moss said:
I toggled back to "Displays have separate spaces" and the video playback issues went away immediately.
Click to expand...
Yeah - I think I've managed to work out why this is happening (though nobody has documented it, so it's just me inferring stuff.) Some video player apps might perform better than others, but finding ways to work with displays-have-separate-spaces enabled is probably the most robust solution :-(
 
Electric Moss said:
It's the Logic movie window, maximized on the second monitor.
Click to expand...
OK, good - I'd assumed the Logic window, but was worried I'd missed a trick.

Just to be sure: is that maximized as in "zoomed" (i.e. what you get when double-clicking a title bar, or option+clicking the green button, where the window furniture remains visible), or full-screen (normal-clicking the green button, window furniture only appears when moused-over)?
 
aldous said:
OK, good - I'd assumed the Logic window, but was worried I'd missed a trick.

Just to be sure: is that maximized as in "zoomed" (i.e. what you get when double-clicking a title bar, or option+clicking the green button, where the window furniture remains visible), or full-screen (normal-clicking the green button, window furniture only appears when moused-over)?
Click to expand...
Zoomed. Never really been a fan of full screen, but I suppose it wouldn’t really bother anything on that monitor since it’s literally only used for video playback, if you think that’s a better way…?
 
Electric Moss said:
Zoomed. Never really been a fan of full screen, but I suppose it wouldn’t really bother anything on that monitor since it’s literally only used for video playback, if you think that’s a better way…?
Click to expand...
I think it should get your performance back for video when displays-have-separate-spaces is disabled - as long as it full-screens to a single display. Just depends if it's worth the restart to try, I suppose (though I am curious since I've only one display and can't test it myself!)

My reasoning is that a Space in MacOS isn't just a virtual desktop; each one also seems to represent a graphics rendering pipeline. That pipeline performs best when it be tailored to the target display: I'm sure that's why the default changed to displays-have-separate-spaces in the first place. If your Space - hence render pipeline - spans two displays, you can't target a real display any more, which is slow (and may confuse a naive video player, making it slower still.) In MacOS, full-screening a window creates a new Space behind the scenes, and transfers your window into the new Space... so, as long as it full-screens to a single display, that should put your video window back in a single-display Space and recover the performance.
 
aldous said:
I think it should get your performance back for video when displays-have-separate-spaces is disabled - as long as it full-screens to a single display. Just depends if it's worth the restart to try, I suppose (though I am curious since I've only one display and can't test it myself!)

My reasoning is that a Space in MacOS isn't just a virtual desktop; each one also seems to represent a graphics rendering pipeline. That pipeline performs best when it be tailored to the target display: I'm sure that's why the default changed to displays-have-separate-spaces in the first place. If your Space - hence render pipeline - spans two displays, you can't target a real display any more, which is slow (and may confuse a naive video player, making it slower still.) In MacOS, full-screening a window creates a new Space behind the scenes, and transfers your window into the new Space... so, as long as it full-screens to a single display, that should put your video window back in a single-display Space and recover the performance.
Click to expand...
Interesting! I'll try this in the next couple of days and report back. Thank you!
 
You must log in or register to reply here.
Top Bottom