Undo/redo would be me :). I put in a lot of effort and spent months working on it to get a basic workable version. I am only just a you g student, so over the last several rcs, Jim refined it and made improvements and bug fixes. I love the team and everyone involved is just a great person.

Thank you for all your work and contributions!

Doing god's work

It was such an obvious missing feature. Though to be fair, implementing undo/redo functionality is often nontrivial.

However, there's still no way to save/export scenes, aside from simply copying your entire app data directory. I just have a basic layout with few tweaks so it's not the worst thing ever, but for any streamer with a complex setup and carefully adjusted filters, moving to a new computer or whatever must be an enormous pain point.

That is an interesting feature. I will work on that for the next version.

Exporting and saving scenes can be done with export scene collection. It’s kind of clunky in terms of workflow but I’ve had success exporting/importing scenes across computers.

You can export your entire scene collection to a json file and import it on another computer.

If you keep all of your media and such in the same folder, then the new Missing Files dialog on startup will also auto detect every source after you point one to the new location.

From my experience the NVIDIA filter is miles better both in detecting noise as well as suppressing just the noise but has significantly more latency and will incur a decent perf hit on the GPU (~10% FPS or so if the GPU is the bottleneck).

These days if it's live is use RNNoise and if it's for a recording I use Nvidia's filter.

Interesting. I have a PC just for streaming (I encode with CPU as well) with a[n] nvidia card, so I'm not concerned about GPU usage. I'll give it a go.

Slight tangent: Is it best to say "An nvidia card" or "A nvidia card"? 'An' sounds better, but 'a' is right according to my 4th grade english lessons. I think 'an' sounds better because you're really saying "(e)nvidia". I don't know if the "an before a vowel led word" rule applies to the pronounced or the written word...

“A” versus “an” is all about the next syllable (and its sound), not the next letter—they’re the same word, just with context-dependent pronunciation which happens to be materialised in the spelling.

My favourite way of demonstrating this practically is to observe usage of “a” versus “an” on words that have developed or lost a silent “h”.

For example, in the days of long ago, “herb” had a silent “h”, so it would be spelled “an herb” as a vowel sound followed; and in American English it still is silent, and is consequently still “an herb”: https://books.google.com/ngrams/graph?content=a+herb,an+herb.... But in British English, people started sounding the “h”, so that in the 1870s, “a herb” became more popular than “an herb”, and it has remained so ever since: https://books.google.com/ngrams/graph?content=a+herb,an+herb... (though “an herb” is still much more common there than I’d have expected).

I normally read more recent translations of the Bible, but still sometimes read the KJV aloud, so there are many cases of silent aitches that are no longer silent (a regular expression search for `\ban h` has 711 matches in the KJV, compared with only 11 in the WEBBE, which are for “honour”, “honest”, “hour” and “heir”); I decided it’s better to read “a house” rather than “an house”, given that the original spelling was only chosen because at that time they pronounced it “an ’ouse”—or at least, I think so; the ngrams there aren’t quite so conclusive, I suspect that one might have already been shifting in some parts of England, as is the case with quite a few other such words; the KJV was written in a style that was already overly formal and sometimes slightly archaic when it was new, let alone 400 years later—Tyndale’s translation from the best part of a hundred years earlier reads much more easily once you normalise spelling as was done in the KJV between 1611 and 1769.

In short: you’ve got an NVIDIA card.

The Nvidia solution also has a great camera background filter for streaming but it's not integrated directly into OBS yet (you have to use it via a virtual camera).

I think you would use an. If you pronounce the letter (like in acronyms) you precede with an.

Anyone care to speculate why this isn't available on Linux? Is it NVIDIA holding us back?

It requires the NVIDIA Audio Effects SDK, which is only on Windows