Combine Easy Effects source (processed mic input) with another audio source? (OBS Monitor) #1957
-
|
I use OBS for managing a virtual camera, and would like have the ability to change to a scene in OBS that plays a video with audio. The video appears on the virtual camera, but as apps like Discord and Zoom are using my default mic device for the audio, I need to figure out how to combine the OBS monitor output (or another audio output) into a virtual source that can be mixed with my microphones input (after processing ideally). I don't want most of the processing from Easy Effects on my mic affecting the audio from this additional stream, so I assume I should create a virtual source that can take both the resulting Easy Effects Source device (or default device?) and the application stream (OBS Monitor), and then I should have a new input device I can have Discord + Zoom use? I have seen the maintainer of Easy Effects advise not to use Easy Effects Source, but prefer the default device? But as Easy Effects has been explained as doing some "hijacking" here with that default device, I'm not sure if that complicates things here? Resources:
Looks like I can use some commands detailed in those resources to achieve this, or use a PatchBay UI app. Just seeking guidance on what input source I should be connecting from the Easy Effects side into this new virtual source / mic device? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 10 replies
-
That is for the case where people open apps like Pavucontrol or Gnome Settings to configure the
If you just want to mix the processed mic signal to something else I think that the easiest thing to do would be loading a |
Beta Was this translation helpful? Give feedback.
-
Yes that was enabled. I'll keep it enabled for now.
As it's called "WEBRTC Voice Engine" which seems rather generic - is it specifically Discord? Or anything else that might use this for voice chat that such as a browser or desktop apps like those built off Electron (Chromium)? I assume there is some metadata somewhere that might differentiate instances of nodes like that. In Helvum and QPWGraph GUI apps I have found this a bit confusing to discern. Especially with "Easy Effects Source" that has been getting all these extra "PulseAudio Volume Control" nodes:
|
Beta Was this translation helpful? Give feedback.
-
Oh... I forgot that Discord does not set a proper name to its node. Unfortunately anything with this name will be blocklisted.
These seem to come from |
Beta Was this translation helpful? Give feedback.
-
Good to know, I'll keep that in mind thanks!
That was it! 😅 Thank you for being so quick to respond! :) |
Beta Was this translation helpful? Give feedback.
-
You're welcome :) Always happy when my scribbles helped someone. Totally worth it 😁 |
Beta Was this translation helpful? Give feedback.
-
Pretty sure that's a browser thing. I noticed the same in Jitsi meetings in Firefox 🤷 |
Beta Was this translation helpful? Give feedback.
-
|
Sharing extra information here in case it helps anyone else :) Gotcha - Multiple OBS monitors (one per source) each require routingI have noticed with OBS that each source added (media source in my case) that adds an entry into the "Audio Mixer" adds it's own monitor node (if you toggle on monitoring for that audio stream). The "output" option in OBS for these audio streams presumably only adds an output node when streaming / recording - which I am doing neither. I use the virtual camera feature and wanted the ability to switch to scenes with audio mixed in for video calls, so only the "monitor" nodes will be available (when enabled). OBS setting - Default Monitor device to route each OBS monitor intoTo avoid linking each one via This way the
OBS Limiter filterAnother issue I noticed is depending on the media you might need to account for different volume levels. One could manually adjust the media's volume sliders in OBS, or apply a common Limiter Filter as a way around that. Beko's guide also shows having the virtual sinks in the OBS Audio Mixer settings, "Audio Output Capture (PulseAudio)" source can be added to choose one of those virtual sinks, then each scene can use that source (copy / paste within OBS to each scene shares a reference to the same node in this case). That source can then be the only one that has the Limiter Filter added, which might be more optimal (and easier to manage than adding the same filter to each source).
This source connects a new node in PipeWire to your virtual sink, which you can then route into the The "Easy Effects Source" should probably go directly into
NOTE: I am not sure if it'll make much difference vs the PulseAudio Output Capture source, but there is a third-party option for PipeWire equivalent ( Easy Effects Sink / Output for applying a Limiter instead of via OBSInstead of the OBS Limiter Filter, if including all system / desktop audio is ok - presumably you could keep the default "Easy Effects Sink" as the OBS Monitor, and instead route the processed signal from Easy Effects "Output" into the It's unclear which node is the equivalent of "Easy Effects Source" for that processed Output however. It seems like it might be the It's probably better to just stick with the OBS limiter as Easy Effects does not support configuring effects per Output / Input devices, only a single device. |
Beta Was this translation helpful? Give feedback.
-
|
Not quite solved yet, the commands that created the virtual nodes turns out to be temporary, and they are lost during a restart. You must do that all over again each restart 🤔 Next step I guess is to look into configuration files to handle that, will share when I have more time to investigate :) |
Beta Was this translation helpful? Give feedback.
That is for the case where people open apps like Pavucontrol or Gnome Settings to configure the
system default device. Selecting a device in OBS menu is fine. What should be avoided is setting EasyEffects virtual devices as thewhole systemdefault devices. The main reason for this is that when EasyEffects is initializing it asks PipeWire about the system default devices. It you set our virtual devices as default EasyEffects may not know which device it should use in some situations.