After volumeControl.setVolume(0) and get again, it's return 0 (this's ok)
but this does not effect to my speaker (the volume level of speaker still
the same, look at Control Panel/Sound/Playback volume control),
volumeControl.setMute(true) --> it's same, nothing change in Control
Panel/Sound/Playback volume control)
As Emil answered already, libjitsi does not modify the output volume
of the underlying OS (in contrast to the input volume) so the
behaviour that you observe is the expected.
I am playing sound files using AudioNotifierServiceImpl/SCAudioClip, is
there any way to control output volume for this player?
It shouldn't be hard to add support for an output VolumeControl for
the purposes of notification sounds in libjitsi, the implementation
should pretty much be the same as for the in-call playback.
Is there any other player (not SCAudioClip) that i can use to play a sound
No. There are multiple threads on the dev mailing list discussion
playback of files in calls which could help you get started.
Unfortunately, we've seen no contributions on the subject from
developers utilizing libjitsi in that way.
When i make a voice call, what is the output device which is chosen as
default to play the voice? is that same with AudioNotifier device?
AudioNotifier uses the user's choice with respect to a "notification"
device (expressed through the ConfigurationService). Similarly,
in-call audio employs a "playback" device. The default selections for
the "notification" and "playback" devices point to one and the same
device but they are separate ConfigurationService properties so it is
possible to specify different devices.
The attachment video shows:
1. When i change the input volume, Window recoding device's volume is also
changed. ---> This work perfectly
Libjitsi does implement this functionality so the behaviour is expected.
2. When i change the output volume (mediaService.getOutputVolumeControl),
Window playback device's volume does not change --> This does not work.
Libjitsi does NOT implement this functionality so the behaviour is expected.
2013/5/23 Nguyen Dang Hieu <email@example.com>: