by Muffinman » 08 Jan 2016, 19:21
by Orion » 11 Jan 2016, 14:52
by jcoman » 01 Apr 2016, 20:49
ACX wrote:That's the approach we are talking about, both ways (-M option or accurate hw values) need direct amixer control. No problem to code that (and also adapt the range to different DACs), but it will work only using RuneUI (and not with other MPD clients).
by ACX » 09 Apr 2016, 08:05
jcoman wrote:If you bypass the MPD for the volume control, it might be good to still expose the functionality to MPD clients (or the like) by redirecting the volume requests to the Rune back-end, or something like that.
by bloodnok » 12 Dec 2016, 03:25
by taravasya » 19 Oct 2017, 20:44