Volume Controls

By default, the Kodi driver overrides the Mute, Vol+, and Vol- commands assigned at the project level.

I know I can change this in MyDesigner, but why are the defaults set this way?
 

You configure that in Macros, not myDesigner.

Don't I just use MyDesigner, and delete the overrides from the Hard Buttons in the Scene Properties?

I am not trying to change the Kodi Macro, just restore the default behavior of the button.

Why were the defaults overridden in the first place?

The box running Kodi doesn't have any speakers, so it doesn't require volume control.

The default Kodi page will define volume up/down and mute commands that use native Kodi commands.

If you do not want to use them simply edit the hardbutton properties of the Kodi page in the designer and clear the three entries for Volume Up, Down and Mute. Make sure to tab off the grid cell to commit the changes.

Clearing these three fields will let the default Volume commands defined in the project properties to take over.
The project level volume commands will use the Volume.<room name> and VolumeMute.<room name> macros for adjusting volume and mute.
 

davep wrote:

The default Kodi page will define volume up/down and mute commands that use native Kodi commands.

If you do not want to use them simply edit the hardbutton properties of the Kodi page in the designer and clear the three entries for Volume Up, Down and Mute. Make sure to tab off the grid cell to commit the changes.

Clearing these three fields will let the default Volume commands defined in the project properties to take over.
The project level volume commands will use the Volume.<room name> and VolumeMute.<room name> macros for adjusting volume and mute.

 

Yes, this is what I did.  I was confused by David's response.

Let me rephrase my question:

Is there anyone using the Kodi driver that doesn't do this?

I wasn't even aware there was a Kodi volume control till I saw that you were using it.  Any audio that is bitstreamed bypasses the Kodi volume control.  I can see where some simpler setups might use it.  For example, running Kodi on a PC that is directly connected to speakers.  But are those users likely to purchase an Allonis remote?

I know is is wrong to assume that everyone is doing what I am doing.  But can someone describe a use-case that justifies this default setup for volume control?

If the goal is to create a useful remote with little to no programming, then the choices for system defaults are important.  This is why I raised the issue.
 

I agree, there are few, if any, people that would use the native Kodi volume commands. I have changed the default Kodi page on the SmartRemote template to not use the volume commands. The updated page will be there in the next template release.