Hi,
I was testing this Using BT, WiFi, MB integrated, External, USB Headphones for past few days and could not replicate issue.

No matter of playback device MM retains Set Volume on device change eg. BT headphones (38%) <-> USB Headphones (50%)

Can you replicate behavior?

[quote=rusty post_id=479793 time=1616789126 user_id=182]
Thanks! We tested this internally with a dragonfly, but haven't been able to replicate this yet.

Does the issue occur with all 'hi-res' tracks or only those with specific characteristics? Can you share one with us?
If you play the same set of tracks with another player via WASAPI drivers, do you observe a similar issue?

Lastly, do you also observe this issue with MediaMonkey 4 (just wondering if it's a regression or a long-standing bug)?

Thanks!

-Rusty
[/quote]

I would like to add the following similar issues with WASAPI output on MM5 (MM4 works fine). Windows 10, AudioQuest DragonFly, FLAC files.

WASAPI  <Exclusive Mode Off> / < Smooth Stop Off> :
1)Sometimes playback will stop when <Next File> is pressed (Play Shuffled On)

WASAPI <Exclusive Mode On> / <Automatic choice of format per track> / Playing list contains files of various sampling rates (e.g. 44100 and 96000) :
1) Pressing <Stop> and <Play> will result in volume being set to max
2) When the <Next File> sampling rate doesn't match the one currently playing, the volume is set to max when next file starts playing (Play Shuffled On)
                 
WASAPI <Exclusive Mode On> / <Use format of original track> / Playing list contains files of various sampling rates (e.g. 44100 and 96000) :

1) All the above issues +
2) When the <Next File> sampling rate is lower than currently playing one [e.g. from 96000 to 44100] you get loud hiss and crackling in playback when the next file starts playing (Play Shuffled On)

Thanks for the effort.
I really appreciate this and it encourages me to actively report bugs and wishes.

Fixed in build 2332 (see details at https://www.ventismedia.com/mantis/view.php?id=17705 ).

-Rusty

[quote=MusicFanPeter post_id=479843 time=1616949062 user_id=90715]
I followed your suggestion. It works okay for me.
Thanks for the support.
[/quote]It was my pleasure, you made me do additional quality tests that I have not done in years, but at least tests are updated, done and ready for MM5. So we now know MM5 sound output quality. To be honest I enjoyed doing those tests.

Hi Peke,

I followed your suggestion. It works okay for me.
Thanks for the support.

Hi,
I would suggest that you simply disable WASAPI Exclusive Mode. I've done Output Test and recorded 192/24 Output using Audacity on both Exclusive and non exclusive, windows output in sound card driver was set to 192/24 on Focusrite (Pic below) and difference in sound was 0.001-0.002% (THD+N), SNR was 109dB against 111dB in exclusive mode. Which makes me conclude that it is almost same as described here https://www.audiosciencereview.com/forum/index.php?threads/teardown-few-basic-measurements-and-personal-thoughts-of-the-focusrite-solo-gen3.9101/

Using DAW Ableton Live 10 is different case when Keyboard input in WASAPI was 85ms against 45ms in exclusive mode against 27ms in ASIOv2 mode, but that absolutely do not affect playback quality. Only benefit of exclusive mode I see is DAW and Professional Gaming where you need 3D spatial surround in order to be faster in responses.

That said I would suggest that you simply just disable exclusive mode as based on my own experience using Focusrite solo 3rd gen and Audio Technica ATH-M70x headphones I can't hear any difference. I even disabled allowing Apps to take exclusive mode in order to prevent any sound cutoffs.

[quote=MusicFanPeter post_id=479805 time=1616832866 user_id=90715]In my opinion there at least should be a warning as the volume is suddenly set at 100, it blows your ears away with a headphone on.[/quote]Windows and Sound Card (DAC) driver controls this, there is no way for MM to tell what would happen when it asks Windows to open Exclusive Access tunneling :(
[quote=MusicFanPeter post_id=479805 time=1616832866 user_id=90715]I like the thought of MM volume slider affecting the output sound levels, which will make it safer to listen.[/quote]If you disable Exclusive mode it will react and you will not have any issues of sudden volume changes.

[quote=Peke post_id=479802 time=1616809658 user_id=213]
Hi,
Personally as I described at https://www.ventismedia.com/mantis/view.php?id=17705#c62646 if I want real bit perfect output (which exclusive mode is designed for) I would expected that Windows rise system volume to 100% eg. override any windows audio post processing and let output devices and/or actual output device (AMP, Active speakers, Headphones, TV [in case of HDMI is used as DAC] ...) handles volume levels.

As pointed only real question is should internal MM volume slider should affect output sound levels.
[/quote]

In my opinion there at least should be a warning as the volume is suddenly set at 100, it blows your ears away with a headphone on. You will easily forget putting the slicer to low level when you switch from streaming with MM5 or listening to various programs on a laptop like Spotify and YouTube to internal MM5 output. I like the thought of MM volume slider affecting the output sound levels, which will make it safer to listen.

[quote=drakinite post_id=479801 time=1616809386 user_id=107828]
If you could share a video recording, that would be pretty helpful too!
[/quote]In my tests if MM and any other app is full exclusive modethen you should not be able to capture system audio along screen capture.

Hi,
Personally as I described at https://www.ventismedia.com/mantis/view.php?id=17705#c62646 if I want real bit perfect output (which exclusive mode is designed for) I would expected that Windows rise system volume to 100% eg. override any windows audio post processing and let output devices and/or actual output device (AMP, Active speakers, Headphones, TV [in case of HDMI is used as DAC] ...) handles volume levels.

As pointed only real question is should internal MM volume slider should affect output sound levels.

If you could share a video recording, that would be pretty helpful too!

I also did some testing and it also occurs with none hi-res files. It certainly always happens after the first track change. I tried several tracks, all the same issue.

I do not have MM4 on my laptop anymore, but I also use Jriver with WASAPI. No problems with the same tracks.
I could share you a file if still needed.

Thanks! We tested this internally with a dragonfly, but haven't been able to replicate this yet.

Does the issue occur with all 'hi-res' tracks or only those with specific characteristics? Can you share one with us?
If you play the same set of tracks with another player via WASAPI drivers, do you observe a similar issue?

Lastly, do you also observe this issue with MediaMonkey 4 (just wondering if it's a regression or a long-standing bug)?

Thanks!

-Rusty

The system volume is changed.

Could you clarify if it changes the MediaMonkey volume or the system volume?