Depends on the order in which the options are checked, different sources are shown.

If you check Output Slider first and Only Active later all active sources are displayed.

But if you check Only Active first and Output Slider later only the filtered source are displayed.

Hi @exeldro !

What a great project again ! I like very all your repos, thank you !

Please, can you add tags when you push commits on all your repos please ? It's more easy to seek and follow versions. And, for obs-audio-monitor, I builded for Linux and the plugin recognize pulseaudio and find sink devices, do you think it's very incompatible ?

Thanks.

I tried with a new scene collection, on the Audio Monitor dock:

-Show Track 1 in Outputs -Scroll down with the mouse wheel -OBS crashes

https://obsproject.com/logs/ptLaG0zHIYOhMOH-

It has also crashed without doing this specifically but it is the easiest way i have found to reproduce the issue.

Goal Ability to control volume on an OBS Audio Track. Ability to monitor this audio Track level. (already the case today, this include suggestion for improvment)

Context One of the feature that is totally missing from OBS ( or this plugin is a way to monitor audio per track or input quickly without going to the advanced audio properties).

One of the great integration to fix this is a work by pvkiet for the OBS Music Edition, but he recently announced that he is dropping the project (he was doing a full fork rather than simply a plugin).

I suggest to implement the following ideas :

• Headphone Icon to quikly enable / disable audio monitoring onthe "Monitoring devices" set in the settings.

this is a better implementation than proposed at : #22 See #39 for more details on this specific use-case.

• Allow for direct volume adjustement on the track 1-6 (I don't think the other features on the master mixer are necessary)

Reference of the project from pvkiet : https://github.com/pkviet/obs-studio/wiki/Master-Mixer-and-Inputs-Mixer

Note : This is linked to #40 for UI impact of adding the output slider for this feature

I experienced obs crashing anytime I opened the advanced audio properties. Windows 64 bit, Audio monitor version 0.3.2. I also just updated to obs websockets 4.9 release, so I do not know if it is due some weird interaction there.

hey Exeldro,

thanks for your great OBS plugins. Can you show us how this plugin looks in OBS? Or at least explain with a little more detail what it does and which problems it solves?

best regards

Since updating to OBS 28, sounds played through the Audio Monitor filter seem to get very choppy whenever the volume slider is adjusted. And I haven't identified what else, specifically, causes it, but it sometimes happens without adjusting the volume. Restarting OBS or deleting and re-adding the filter temporarily fixes the problem, but only temporarily. What's worse is that any stuttering that's audible to me through the Audio Monitor filter appears to also be present in the outgoing stream.

In the process of troubleshooting another, seemingly unrelated, issue with the update to v28, I discovered via WinDbg that this plugin is constantly throwing errors that link to something along the lines of "avcore\audiocore\client\audioclient\mmdeviceactivator.cpp(279)\AUDIOSES.DLL!00007FF9B74C6431."

Reproduction steps:

1. Download & install a fresh copy of OBS Studio 27.2.0 (or use the zip version) in portable mode
2. Load then close OBS
3. 0 memory leaks
4. Install the ZIP version of this plugin
5. Load then close OBS
6. 2 memory leaks

These 2 leaks appear with or without the dock visible, with a fully vanilla configuration.

In summary:

• 2 leaks in default Simple Output mode (1 for each of the default audio sources)
• 18 leaks after switching to Advanced Output mode (number of enabled tracks in Settings -> Output does not matter)
  • down to 17 if Mic/Aux is Disabled in Settings

Log: 2022-02-18 22-29-58.txt

Noticed when trying to track down leaks in my main installation. I'm personally seeing 31 leaks from this plugin there, likely due to source count.

I know this has been reported, but I don't know how to add a reference to that issue, sorry?

Since version 0.7.1 there is a "glitch" that has been driving me crazy, and that is crackling noise and distortion under certain circumstances.

Steps to replicate: 1 - Use the Move transition plugin. 2 - Generate a filter that raises the volume to 100% with a duration of 2300 ms. 3 - Generate a filter that lowers the volume to 0% with a duration of 2300 ms. 4 - Activate the filters randomly without letting the previous one end.

The glitch only occurs when there are two transitions simultaneously on the same audio source.

It is only a matter of time before the glitch occurs; the audio will start to distort and the slider movement will stop being fluid, it will also increase the CPU usage, and the only way to solve this glitch is to restart OBS, it is worth clarifying that the audio distortion is also visible in recordings and live performances.

The only way I have found to avoid the problem is to use version 0.7.0 together with OBS 27.2.4, where curiously it does not occur, no matter how much the simultaneous fade is forced.

I would be very grateful if this problem could be examined as it is a bug that can potentially break a whole recording or live; thank you very much.

Suggestion : Use the track name as set in OBS Settings to target the Track 1-6 in the monitor.

Keep the default "Track 1-6" when field is empty.

Thanks!

Simple UI suggestion.

Use a "headset" icon in place of the speaker icon for the monitor output. This is to avoid confusion between the 2 slider (when you can control monitor & output)

example : https://www.flaticon.com/free-icon/headset_566088?term=headset&page=1&position=36&page=1&position=36&related_id=566088&origin=search

Note : that might be counter intuitive for some users that both use headset. This is not to represent the device type, but the functionnality.

hewwo~ it seems i've finally narrowed the culprit for this~ it was the audio monitor bug which had caused this~

please do refer this issue which i made on obs github for more details -> https://github.com/obsproject/obs-studio/issues/7343

• note that this was affecting the obs audio mixer not the plugin's mixer

Hello, for the past few months I was using exeldro amazing OBS Plugin called 'audio-monitor-0.8.0'. Throughout my time learning and using Audio Monitor, there was two things that are little annoying or "I just have deal with it".

These two small issues I hope the creator would improve/update soon. Which are...

1. Syncing with my chosen Sources: Audio Filter setting within OBS
2. Audio Monitor trap or stuck to single system audio channel only

• Explaining -

1. So whenever I setup my audio input & output setting within OBS like; 'Application Audio Output Capture', 'Audio Output Capture' or 'Audio Input Capture'. I would normally add different kinds of filter to alter and control the sound quality to my liking. But for some reason the 'Audio Monitor' isn't getting or syncing with my audio filter that I just set. It is slightly annoying, but I don't mind. Its just that after I finishing completing my audio filter, within Audio Monitor I would only hear the default original audio instead. So, it would be really helpful if my audio filter (sources) setting is already sync up with Audio Monitor immediately.

2. Okay, this second issue is sometime little annoying. Whenever I begin to open up my OBS app I would normally set my PC audio to my Samsung 1080p TV audio (which is my second Monitor, as well first Monitor is my BenQ EW3270U). While setting up and double checking my chosen setting, whenever I change my PC audio from my Samsung 1080p TV to just my Headphone. For some unknown reason the Audio Monitor is still set on to my Samsung audio instead to my headphone I already selected. (in other words, the Audio Monitor is stuck to a single system audio after when OBS begins opening up).

So the only way to change the Audio Monitor's system channel to my headphone (which I decide), is to close down OBS app and start it up again, so that Audio Monitor would change its audio channel to headphone immediately.

Well, I know that this plugin is still updating. But nevertheless, I hope my critique/opinion would help you to fix these issues.

Hi,

this is the first time I've tried to use this plugin on Linux (Debian Unstable). I followed the instructions to build the plugin and included it in the UI/frontend-plugins CMakeLists.

However, if I try to run OBS with this compilation I get a segmentation fault with the following backtrace:

Thread 12 "audio-io: audio" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffc1dfb640 (LWP 24709)]
0x00007fffda300d10 in AudioOutputControl::OBSOutputAudio(void*, unsigned long, audio_data*) () from /usr/local//lib/obs-plugins/audio-monitor.so
(gdb) bt
#0  0x00007fffda300d10 in AudioOutputControl::OBSOutputAudio(void*, unsigned long, audio_data*) () at /usr/local//lib/obs-plugins/audio-monitor.so
#1  0x00007ffff67bce30 in  () at /usr/local/lib/libobs.so.0
#2  0x00007ffff67bcee7 in  () at /usr/local/lib/libobs.so.0
#3  0x00007ffff3e87b27 in start_thread (arg=<optimized out> at ./nptl/pthread_create.c:435
#4  0x00007ffff3f0a78c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

So far I don't know if there is a workaround to fix this and the plugin is entirely unusable :/

When you add the Audio Monitor to an audio source, and "Hide" the Audio Monitor through OBS, it also mutes the audio source the filter is associated with, although all the mute linking is disabled.

This is unexpected.