View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008017 | MMW v4 | Player | public | 2011-06-24 19:55 | 2011-10-02 21:01 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | feedback | Resolution | reopened | ||
| Product Version | 4.0 | ||||
| Target Version | 4.1 | Fixed in Version | 4.0 | ||
| Summary | 0008017: WASAPI output plugin causes unpredictable changes in volume | ||||
| Description | When using WASAPI in exclusive mode, it causes unpredictable changes to the System volume. This is most easily seen by switching to WASAPI, muting and unmuting the volume in MM and observing the Volume Mixer properties. The only way around this is to manually adjust all volume levels (Speaker, System Sounds, MM, other apps) manually via the Volume Mixer. The effects vary depending on whether exclusive mode is used. i.e. Set mixer properties to normal (e.g. 50% volume for all entries) Switch to Wasapi, play in MM & mute/unmute. Volume levels are normal. Switch back to DS output --> volume levels are low. Set mixer properties to normal (e.g. 50% volume for all entries) Switch to Wasapi, play in MM & mute/unmute. --> Volume levels are abnormally high. Mute/unmute --> Volume levels become normal. Switch back to DS output --> Volume levels are abnormally low. | ||||
| Additional Information | Similar problem reported here: http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=58819 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1408 | ||||
|
|
This is actually expected behavior since the Exclusive mode is quite specific. It's like this: 1. In Shared mode (including out_MMDS, out_wave or any other standard way of sending sounds to output) Windows mixer is involved and its volume control is being controlled by MM. 2. In Exclusive mode, MM is able to control directly the device volume control (i.e. hardware control). So, 1&2 are not compatible, it means setting two different volumes. I think that it doesn't matter at all for most users, but it could be annoying for those who often switch (for whatever reason) between these two modes. We could consider some kind of separation of the volumes for different output plug-ins, or something like that. I'm not sure whether it's really that much needed though. |
|
|
Re-opening. Tested with other apps that use WASAPI output plugins and they have no such effect. i.e. they do not change the Device volume or the System Sounds volume. |
|
|
Fixed in build 1408. On change of mode from Shared to Exclusive or vice versa, MM now adjusts the volume to reflect the system setting and so no abrupt volume changes will occur anymore. That said, the volume slider still works the same way in both modes, since it seems to be correct this way: - Shared Mode - per application volume is changed (same as e.g. WMP). - Exclusive Mode - directly device volume is modified. |
|
|
Verified 1430 |
|
|
As reported at http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=60702, MM seems to reset the volume each time it is restarted when WASAPI is enabled. This is a reflection of the fact that whenever MM is restarted (and when it is running), MM adjusts the system mixer volume for MediaMonkey in proportion to the level of the volume slider, rather than locking the MM volume slider to the level of the volume mixer. Conversely, MM's volume slider doesn't reflect changes to MediaMonkey's volume in the mixer. This is most easily understood by watching this video: http://screencast.com/t/5uYbzyHZ |
|
|
Setting target to 4.1, since it isn't technically trivial and would mean a high risk of regressions. Note that even from the video, I don't see the issue as serious - MM really doesn't react to changes in Windows Mixer, but under standard circumstances, it can't cause any real problem. |
