Repository navigation
Replies: 3 comments 4 replies
|
i'd like a plugin that can automagically analyse my camera and create custom filters to correct for lens distortion and colour innacuracies. There are a couple i use in OBS but they are very manual, and this is 2026 |
|
I like this. Both removing the arbitrary split between filter sections that doesn't even make it clear what the order is, and also having a side by side before/after preview. For audio it should probably be two waveforms above and below rather than a side to side scrub, but the overall idea is good. My main caveat would be that this should all be done without breaking plugin compatibility with the existing OBS APIs. |
|
+1 for one graph per signal. A list as a straight-line graph also answers @alerque's point: the existing filter API ( One suggestion for the model behind the dialog: keep the graph as data in libobs, not only as Qt widgets. Nodes, typed ports, wires and the
That is the API-first part of a remote UI that I put up as a separate discussion: #2509. The graph is one of three gaps there, next to a properties schema and a preview stream. |
Uh oh!
There was an error while loading. Please reload this page.
This proposes the next version of the Filters dialog in obs-studio-rust: one graph per source for video and one for audio, a before/after split preview, and a quick swap between the preview and the graph editor. It follows the AI-pipeline research in #842, where the AI webcam and mic effects need to chain together.
All images are from an interactive browser mockup. The effects in it are simulated, and the camera frame is a drawn stand-in.
1. The problem with today's dialog
OBS shows a camera's filters in two lists, Audio/Video Filters and Effect Filters. The split describes where a filter runs, not what it does:
Every frame runs list 1, then the upload, then list 2. Users have to know about that upload to understand the UI, and a list can't branch. "Blur only the background" needs the camera to feed a person mask and a blur, then join them. Two ordered lists can't express that.
2. Proposal: one graph per signal, with a tag for where each node runs
AI,GPUorCPU. When a wire crosses from a CPU or AI node into a GPU node, OBS inserts the upload itself. The editor draws that wire dashed.image(blue),mask(white),audio(green). Mismatched connections and loops are refused.3. Preview first, with a vertical before/after bar
The dialog opens on a large preview. A vertical split bar shows the raw source on the left and the processed result on the right. Drag it to compare. Under the preview, the pipeline appears as a strip of chips in run order. Click a chip to bypass that node. Hold Space to bypass the whole pipeline for a quick A/B.
Audio works the same way. The bar splits the raw mic waveform from the processed one. Here Voice Cleanup removes the hiss and Voice Gate silences the gaps between words.
4. Swap to the graph editor
Press Tab, click Graph, or click the corner thumbnail. The graph editor takes over the main area and the preview shrinks into the corner, still live, so every rewire shows up right away. Click the thumbnail again to go back.
Editor interactions:
5. What this needs underneath
obs_source_filter_*API maps onto a straight-line graph, so the C API/ABI and saved scenes stay compatible. A new API adds branch, merge and typed ports.Questions for feedback
All reactions