Repository navigation
Replies: 2 comments
|
This is a very desirable feature, but it I would be careful to go about it in a way that scenes can be backwards compatible with OBS. Note that the Isocast project is designing their entire OBS alternative around this idea. Given that plugins are already able to accomplish this, I think I'd focus on fixing up the core experience for a while before rehashing the main workflow. I for one already do something like this in production with NDI streams from filters pushing specific sources out separately from the main stream. There are so many possible nuances to how workflows can be arranged ... at least to me it's far more important that the bugs get ironed out and things stabilize. I'm using this in production already, but it's complicated to verify each week before live events that nothing has broken that's needed for that specific workflow. |
Will you join our discord group? Your ideas are spot on and i'd love to hear more about what you have to say. |
Uh oh!
There was an error while loading. Please reload this page.
Moved from issue #2231 by the coordinator (listed under "Might move to Discussions" in #2234).
From the Hacker News thread on OBS Studio 33 (https://news.ycombinator.com/item?id=50218430). Part of the meta issue.
Discussion candidate.
What users said
A user wants to record several cameras at once without burning them into one output; replies point to the Branch Output plugin.
Comments: 50219153, 50219617
Discussion prompt
Built-in per-source/per-scene recording, or leave it to plugins? Scope and UI.
If there is no agreed design, move this to Discussions (coordination.md section 5).
All reactions