Posts: 5,184
Joined: Jan 2009
Reputation:
131
You can set the volume with Application.SetVolume but you can't set the volume amplification. And as far as I know there's no volume amplification functionality for audio.
Always read the
online manual (wiki),
FAQ (wiki) and search the forum before posting.
Do not e-mail Team Kodi members directly asking for support. Read/follow the
forum rules (wiki).
Please read the pages on
troubleshooting (wiki) and
bug reporting (wiki) before reporting issues.
Posts: 7
Joined: May 2014
Reputation:
0
I think I found it. There is a <volumeamplification> entry under <defaultvideosettings> in the guisettings.xml file saved in %appdata%
I might be able to make it work that way since there is no JSON command for that.
Thanks,
Unifab
Posts: 5,184
Joined: Jan 2009
Reputation:
131
You can but it's not picked up until the next restart of XBMC.
Always read the
online manual (wiki),
FAQ (wiki) and search the forum before posting.
Do not e-mail Team Kodi members directly asking for support. Read/follow the
forum rules (wiki).
Please read the pages on
troubleshooting (wiki) and
bug reporting (wiki) before reporting issues.
Posts: 1,832
Joined: Nov 2010
Reputation:
58
You can set volume amplification up and down by one unit issuing the command Input.ExecuteAction with action parameter "volampup" or "volampdown":
{"method":"Input.ExecuteAction","params":{"action":"volampup"}} --> raise volume amplification +1
{"method":"Input.ExecuteAction","params":{"action":"volampdown"}} --> lower volume amplification -1
Posts: 122
Joined: Sep 2014
Reputation:
1
TimoJ
Senior Member
Posts: 122
Thank you, works fine.
I have made a script assigned to a remote key that toggles between +15 and 0.
Earlier I was using these commands to do the adjustment:
("ActivateWindow(osdaudiosettings)")
("SetFocus(-79)")
("Action(Right)") --> repeated enought times...
Still, it would be even better if there was a direct value input method.
Btw. is it possible to somehow read the currently used volume amplification value?
My script is not able to detect the current value at playback start. So first button press adds +15, even when there already may be +15 amplification (amplification value is stored per file when you stop playback). I have "fixed" this by making the 0 position to go 30 steps down so the level gets reset to zero after second key press. It doesn't of course work correctly if you manually adjust amplification to a higher level than 30.