exeldro / obs-audio-monitor

audio monitor filter for OBS Studio
GNU General Public License v2.0
282 stars 29 forks source link

UI/UX redesign suggestion : compact design + icons quick access #40

Open Trouffman opened 2 years ago

Trouffman commented 2 years ago

This is a companion ticket for the issue #39 and #35 with more details on the changes required in UI to streamline usage.

Today's UI

image

Challenges or missing stuff

Suggested UI changes

Obviously this would be up to discussion, but I and couple of my teammates went through multiple rounds of prototyping the following suggestions.

Mockup In vertical layout : OBS-Audio monitor

Change list

Monitoring device control section

Note : Audio meter are irrelevant for this. See point 1. 2. and A. B. C. in issue #39 for the reasons.

Track control section

Some more per device/bus configuration, including name and colors. OBS-Audio-Bus Could be renamed in "Output Device Bus" to avoid confusion maybe. (TBD)

  1. Enable/disable
  2. Volume lock
  3. Select Extra Audio device (or Audio Bus)
  4. Hide (to quickly hide) > To unhide, go to the global settings cogwheel

General UI :

NB: There are limitation here that we have to play with : in OBS Audio Mixer, the icons for enable/disable are not align with the slider but within the width of the meter + slider. It does not work if the icons are next to the meter, only if below

NB 2 : If thinking about "touch based" interface, this would require some work like exra padding, etc, to account for "touch-regions". I do not think this is required for now, it would need to be a special UI thinking as well.

To confirm behavior

Example 1 : A slider on track 1 is set at 100%, and slider on "Audio Moniroting device" at 80% > Track 1 volume on monitoring device is 80%, output stays at 100%

Example 2 : A slider for Track 1 is at 100%, Source 1 at 80%, and Mon Device at 50%.

track1 is heard at "50%" and source 1 at "40%" volume on the monitoring device and the output on track1 is 100%, and 80% for the Source 1.

Devil's advocate section

Some ideas and why I don't think they are to be implemented.

Happy to discuss other possible improvments.

Trouffman commented 2 years ago

Another option that came up as well : For each source add an option for monitoring as "Before / After" filters/properties.

This could help to monitor before any filters are applied (similar to a raw-source monitoring) and as well as "After filters"have been applied