wm4 d8aeeaa4b1 command: always allow setting volume/mute properties ... This seems generally easier when using libmpv (and was already requested and implemented before: see commit 327a779a; it was reverted some time later). With the weird internal logic we have to deal with, in particular the --softvol=no case (using system volume), and using the audio API's mixer (--softvol=auto on some systems), we still can't avoid all glitches and corner cases that complicate this issue so much. The API user is either recommended to use --softvol=yes or auto, or to watch the new mixer-active property, and assume the volume/mute properties have significant values if the mixer is active. Remaining glitches: - changing the volume/mute properties has no effect if no internal mixer is used (--softvol=no) and the mixer is not active; the actual mixer controls do not change, only the property values - --volume/--mute do not have an effect on the volume/mute properties before mixer initialization (the options strictly are only applied during mixer init) - volume-max is 100 while the mixer is not active		2016-01-26 15:23:09 +01:00
..
client_api_examples	examples/qt_opengl: Use fbo of the widget and not the thread context	2015-12-03 10:41:49 +01:00
man	command: always allow setting volume/mute properties	2016-01-26 15:23:09 +01:00
client-api-changes.rst	client API: rename GL_MP_D3D_interfaces	2015-09-24 21:07:37 +02:00
compile-windows.md	DOCS/compile-windows: pthreads is not needed anymore	2015-12-20 11:18:02 +01:00
contribute.md	Add a CONTRIBUTING.md file	2015-12-22 23:18:46 +01:00
edl-mpv.rst
encoding.rst
interface-changes.rst	command: always allow setting volume/mute properties	2016-01-26 15:23:09 +01:00
mplayer-changes.rst	Disable DVD and BD menu support (to be removed)	2015-06-26 23:37:30 +02:00
release-policy.md	DOCS: update release policy	2015-09-23 01:07:52 +02:00
tech-overview.txt
waf-buildsystem.rst