fenrirthviti

Joined 6 years ago

Karma

Submissions

Member since

Apr 1

Recent submissions

Correct, our service integrations are reliant on CEF and the browser source features. Our Flatpak is an option if your distro's repo doesn't have it compiled for some reason.

Comment · 4 years ago

Nothing else at the moment, even as opt-in. We're considering this in the future, but want to make sure we do it right.

Comment · 6 years ago

We'd like to merge it as well, but it's still very much a work in progress, and there's some major hurdles with both Wayland itself and Qt that need to be addressed first.

Comment · 6 years ago

OBS Studio is a full rewrite of OBS, and the old version was renamed to Classic to avoid confusion. It's been deprecated for many years now, and is no longer maintained. There is no real reason to use it anymore. If I had to guess the issue here, you're on a laptop with two GPUs and OBS Studio is running on a different GPU than OBS Classic is, which is why you're running in to issues. We'd need a log file to know for sure, but it's likely a simple fix (which you can stop by our Discord or forums with and we can take a closer look, feel free to ping me @fenrir in either location).

If you'd rather do your own testing, here's a starting point for my guess as to the issue: https://obsproject.com/wiki/Laptop-GPU-Selection-Windows-10

Comment · 6 years ago

This is effectively our single biggest requested feature right now:

https://ideas.obsproject.com/posts/41/multiple-video-outputs https://ideas.obsproject.com/posts/7/multi-service-streaming... https://github.com/obsproject/rfcs/pull/8

Much more details in those links than the forum thread you posted that explains why we haven't done it already. Most of the issue is UI, which is most of what is discussed in that RFC. We need to change the paradigm on how outputs are handled in the UI to support things, and UI is really, really hard. We basically have to throw out a large portion of the application UI and start over to accomplish this, which is a monumental undertaking, and we just haven't had the time or resources to devote to it with all the other higher priority items that keep coming up.

We want it. Users want it. It's definitely not an if, it's a when. Unfortunately, I don't have any timeframe I can give you. OBS still only has one single full-time developer working on it, so resources are limited.

Comment · 6 years ago

You can hold alt+drag the red bounding box to crop easily. Screen-region select is on our to-do list, but hasn't been a high priority as it's technically already possible to get the same end result, just not as simple.

Comment · 6 years ago

You can use groups to accomplish this currently, but it's not the most obvious thing. Just create two groups, and add the shared source to each group, then apply your filter to the group itself. Scene-specific filters and other scene-specific features is something that is on our to-do list, but very tricky at best.

Comment · 6 years ago

This is something we want to do, but there are some complications both in the design of the program and getting the UI balance between "normal" users and users familiar with professional equipment/DAWs. There's been some proposals, but we haven't reached a consensus yet.

Comment · 6 years ago

It's a mitsudomoe, a common Japanese symbol. Jim picked it because he liked how it looked: https://en.wikipedia.org/wiki/Tomoe

Comment · 6 years ago

Hey there, OBS team member here. Want to get some clarification on these issues, as they are not really things we hear commonly, outside the lack of desktop audio capture.

First, for clarity, the macOS version of OBS Studio is not a "port". It's a native application designed to run on macOS.

The mentioned audio issues are not unique to OBS. Apple does not feel that applications need to directly capture desktop audio, so third-party programs that inject themselves in to the desktop audio using kernel drivers (iirc) and create a loopback device are required to capture desktop audio. We have a guide on how to do that here: https://obsproject.com/forum/resources/505/

Can you be more specific about how "none of the widgets work properly"? Which features are you referring to (outside the aforementioned audio limitations) that are not implemented?

System shortcuts like find don't really make sense in an application like OBS. There's very few things you'd need to run a find operation on. Communicating shortcuts is something we could do better, however. We are working on an undo function that will help here in case anything is accidentally changed, but with the complexity of operations available in OBS this is a bit of a challenge and will take time to get right.

Our mixer levels are using a global audio industry standard for levels, you can see more about that in our guide here: https://obsproject.com/wiki/Understanding-The-Mixer

Comment · 6 years ago

Almost all of their changes are UI changes. They use our core OBS Studio code, with an Electron GUI instead of Qt. Not easy/basically impossible to port back over. We monitor any back end changes they make, and pull when appropriate. They do not collaborate with us, however, so it's rare they make changes that we can use.

Comment · 6 years ago

Love hearing stories like this! Often, we only hear the negative or when people are having issues (it's rare for folks to speak up when everything is working well!), so it's genuinely heartwarming to hear how much people are able to use our program to keep their livelihoods moving.

Comment · 6 years ago

OBS core team member here, just a quick clarification on this post. OBS will not run without a supported GPU for compositing; that is always handled by the GPU running on OpenGL (for macOS and Linux, we use Direct3D on Windows). The available encoders, however, might change based on the available hardware. Hardware encoders are, generally, much faster and lower impact on system resources, but may have lower quality per bitrate as a trade-off.