search

t3knomanzer / maxmix-software

Maxmix volume mixer software repository
https://maxmixproject.com
Apache License 2.0
124 stars 30 forks source link

Volume on Teams meeting doesn't change #219

Closed Forgenn closed 3 years ago

Forgenn commented 3 years ago

Guidelines

Describe the bug When selecting Teams on the device, turning the encoder doesn't modify the volume of the meeting.

To Reproduce Steps to reproduce the behavior:

  1. Open Teams
  2. Enter a meeting
  3. Try to modify the volume with the device
  4. It won't work

Expected behavior The volume should change.

System information:

Additional context It seems Teams opens a new audio channel when opening a meeting, but the sound of that meeting is still controlled in the main Teams windows. When selecting the application in the device, only the window of the meeting appears, which can't change the volume of the meeting, a bit confusing. The device should show both of the channels.

Capture

The channel that the device controls is the left one, but the right one is the window that outputs the sound, which doesn't appear. I don't know if this is a problem with Teams or the maxmix software.

pbanj commented 3 years ago

I've noticed this with discord lately. Rebooting the maxmix and software fixed it every time.

Forgenn commented 3 years ago

I've noticed this with discord lately. Rebooting the maxmix and software fixed it every time.

I tried your fix but it didn't work, I think it's a different type of bug, because the problem here is that the maxmix doesn't show the channel where the output is.

pbanj commented 3 years ago

discord is doing the same thing but im not even in a chat with it. so seems it is the same issue but i was getting lucky on restarting the app and maxmix. image

Forgenn commented 3 years ago

Oh I see, it's the same problem then. Reconnecting the maxmix when inside a meeting has fixed it as you said before, but it looks like its doesn't work all the time for me. Thanks for your help.

XScorpion2 commented 3 years ago

should be fixed in 1.4.2 beta

Forgenn commented 3 years ago

should be fixed in 1.4.2 beta

At the moment installing the new 1.4.2 pre-release doesn't work for me, I have to revert to 1.3.2, so I can't check it. Should I close the issue anyways?

Forgenn commented 3 years ago

Fixed with version 1.4.3.