macOS Screen Capture missing window match priority problem?

[Oat_Porridge]

Context: I’m using an Apple Silicon MacBook Pro (binned M3 pro). I record Celeste (windowed) for deathless challenges using OBS’ macOS screen capture for recording visuals and audio.

Problem: Every time I restart my Mac or close Celeste and reopen it, OBS sources forgets that I set it to record Celeste and needs to be reset. I think this is because the Window Match Priority feature from the Windows version of OBS is missing from the Apple Silicon version.

Any thoughts or work arounds?

 

[watkirod]

is there a fix

 

[Oat_Porridge]

is there a fix

Small update: after the newest update, (which I got today) it seems there is a work around:
Use macOS Audio Capture and the deprecated Window Capture sources together. I just tested it and OBS still remembered the application to look for.

 

[mishakim]

The new MacOS Screen Capture source, when set to window capture mode, is tied to the unique window ID identified by the OS. When the app restarts, or even respawns its window (e.g., Keynote going in and out of presentation mode), the window ID changes and the connection is lost. The deprecated Window Capture source keeps track of this and doesn't lose the window. I raised this as a bug and the maintainers insisted it was working as intended and refused to entertain fixing it. They seemed to think you'd accidentally stream a window you didn't intend to, and that was worse than having to reselect the window you want every time something changes. It makes automation really difficult.

 

[AaronD]

They seemed to think you'd accidentally stream a window you didn't intend to, and that was worse than having to reselect the window you want every time something changes. It makes automation really difficult.

Well, if you're reckless enough to have sensitive things open on the same rig at the same time that you're streaming......

I remember actually answering a question like that on these same forums. Something to the effect of how to guarantee not having <that> appear on stream, not even by accident. The answer, of course, is, "Don't have it up at all!" Understand that your entire machine is almost public, and don't tempt fate.