There are a handful of comments here rueing buggy behaviors. These days with nearly the same amount of effort to post a complaint you can delegate the task of reproducing the issue, diagnosing the root cause, and proposing a fix. Yes, it may incur a small to moderate cost, but it's a contribution to an open source project that apparently provides some value in return.
Did they finally fix the bug where if you have less than ~40gb storage the recording will just randomly die for no reason with no notice, it is unimaginably annoying
OBS is much more aimed at livestreaming to platforms like Twitch and managing multiple cameras incl one of you, one of your screen etc. Well beyond what Cap is for.
But yes, use the most specialized tool for the task at hand.
While we're here, does anyone know a screen recording application that automatically takes into account display changes, audio device changes, camera resets, etc.?
I'm making do with OBS, but I lose more video to "plugged in external monitor and forgot to update OBS config" than I actually record.
Yes, please, that would help so much. OBS seems to be designed for static setups and a single output stream. In my case, I have a setup that changes often (for example, connect a USB video device that processes input from a microscope). I thought I would be able to record multiple video streams at once without burning them into a single output stream (e.g. to multiple files, or a multi-stream file), but this turned out to be difficult without hacks.
I too frequently plug and unplug dock and external displays. It's a little painful to keep checking and sometimes re-add display source to get the default screen and voice recording working.
I wonder if the "modern" way for problems of this nature is to fork the open-source repo and ask your favourite agent to strip it down to bare essentials that you need (performance gains) and add the specific feature enhancements you want (needs to work only for your configuration -- may not pass the quality standard needed for a PR)
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.
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?
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)
The plugin-loading overhaul and improved source snapping look like useful updates. OBS continues to show how much attention to detail matters in open-source software. Excited to see how creators and plugin developers adapt to version 33.0!
There are a handful of comments here rueing buggy behaviors. These days with nearly the same amount of effort to post a complaint you can delegate the task of reproducing the issue, diagnosing the root cause, and proposing a fix. Yes, it may incur a small to moderate cost, but it's a contribution to an open source project that apparently provides some value in return.
Did they finally fix the bug where if you have less than ~40gb storage the recording will just randomly die for no reason with no notice, it is unimaginably annoying
This is happening all time time and I lost countless video recordings because of it...
Using OBS only when it’s a must
Much happier with Cap for screencast recording https://github.com/capsoftware/cap
OBS is much more aimed at livestreaming to platforms like Twitch and managing multiple cameras incl one of you, one of your screen etc. Well beyond what Cap is for.
But yes, use the most specialized tool for the task at hand.
Why are the binary releases hosted on a 3rd party site and not on Github?
While we're here, does anyone know a screen recording application that automatically takes into account display changes, audio device changes, camera resets, etc.?
I'm making do with OBS, but I lose more video to "plugged in external monitor and forgot to update OBS config" than I actually record.
Yes, please, that would help so much. OBS seems to be designed for static setups and a single output stream. In my case, I have a setup that changes often (for example, connect a USB video device that processes input from a microscope). I thought I would be able to record multiple video streams at once without burning them into a single output stream (e.g. to multiple files, or a multi-stream file), but this turned out to be difficult without hacks.
I too frequently plug and unplug dock and external displays. It's a little painful to keep checking and sometimes re-add display source to get the default screen and voice recording working.
I wonder if the "modern" way for problems of this nature is to fork the open-source repo and ask your favourite agent to strip it down to bare essentials that you need (performance gains) and add the specific feature enhancements you want (needs to work only for your configuration -- may not pass the quality standard needed for a PR)
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.
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?
> even if that means capturing too much
People streaming things mights disagree.
As the name (Open Broadcaster Software) suggests, it isn't primarily a capture program.
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)
I made a little script that reconnects everything the way I want it on launch via WebSocket. Works great
which OS ?
Love OBS! It's so far ahead of proprietary apps in so many areas, it's incredibly impressive
Is solved the source disconnection with macOS ? Even it's an OS problem.
Easily fixable with a script that sets things up as you want it on launch via websocket
Do you have that posted anywhere? I'd love to peek at it
No, but it was very trivial (Claude did it in maybe a minute). It just made a new launcher that opens OBS, then refreshes/checks all my sources.
Answer this thread if you struggle and I can post when I get to the office
The plugin-loading overhaul and improved source snapping look like useful updates. OBS continues to show how much attention to detail matters in open-source software. Excited to see how creators and plugin developers adapt to version 33.0!
I use Lifelog Timeline