This could probably be automated using either an OBS plugin (if you really want deep integration and not running another program) or a standalone program (written in whatever language you want) that listens for display changes and pokes OBS using its websocket API. The hooks are definitely there to update source configs.

▲

rwmj an hour ago | parent [-]

Surely the main function of a capture program should be to capture video, no matter what, even if that means capturing too much / uninteresting sources some of the time?

	▲	flaunf221 an hour ago \| parent \| next [-]
		> even if that means capturing too much People streaming things mights disagree.
	▲	RobotToaster 44 minutes ago \| parent \| prev \| next [-]
		As the name (Open Broadcaster Software) suggests, it isn't primarily a capture program.
	▲	structural an hour ago \| parent \| prev [-]
		Except it's really designed to composite video from a bunch of different places and broadcast the result, whether they are windows, screens, cameras, etc. And a rather lot of people don't want every screen to be captured, just the ones that they have selected. It's not a "screen recorder" program, really. And it's explicitly designed with an API to be remote controlled if hardware changes out from under it, so you can encode exactly your own policy logic on what to do. (External display plugged in? Disable my laptop source at full resolution and enable my laptop and monitor sources, side by side, with one scaled as necessary, and in this layout. But if I'm currently recording or streaming, don't do anything. - this is user-specific logic)