MVP: volume works on TV but not music

[BobAtTorrey]

I'm using GBPVR via a MediaMVP with 34-button remote. The volume keys (Vol+ and Vol-) work for live TV and watching recordings. However, they don't work for music. (I've tried with both the GBPVR native Music Library, and with the Music Player plugin.)

Can someone point me to a solution?

Once that's solved, is there any way to get visual feedback when setting volume? (e.g., a volume bar?)

Many thanks in advance.

[sub]

Did you try on the main menu? Since they double as left and right keys, GB-PVR cant assume that the users is intending to control the volume. On the main menu it does make this assumption.

[BobAtTorrey]

Sub,
Right you are. If I exit the music menus back to the main menu, then the MVP remote control volume keys (Vol+, Vol-) changes the volume.
BUT, there is about a 40 second delay from the time you push a button until it has an effect. I presume that rather than send a volume control to the MVP, what is happening is that the volume is adjusted in the data sent by GBPVR to the MVP, and since it plays slowly compared to network speeds, much is buffered in the MVP that has to play out before it gets to data with the new volume. (Is that the explanation?)
Is there any way to correct this? The problem this causes is that with no response or other kind of feedback you tend to press additional volume buttons , and when the system finally responds you've dramatically overshot the goal, and then you repeat the process in the opposite direction, (nearly) ad nauseum.
If there is no way to fix this, like by sending volume up/down commands to the MVP rather than changing the data stream, then at least a mitigating alternative would be to see volume bars while you're hitting Volume buttons. So, while the volume won't have changed yet, you'd be able to tell by the movement in the bars whether you've gotten to the level you want.

[BobAtTorrey]

Or, it occurs to me, an alternative explanation is that you're indeed sending volume-change commands to the MVP, but the commands are queued behind the data stream rather than bypassing it.

[sub]

I've just tried it here now and changed pretty much instantly for me.

presume that rather than send a volume control to the MVP, what is happening is that the volume is adjusted in the data sent by GBPVR to the MVP, and since it plays slowly compared to network speeds, much is buffered in the MVP that has to play out before it gets to data with the new volume. (Is that the explanation?)

No, I'm not doing anything like that. When the user press the volume buttons, I just send a message to the MVP immediately which tells it to change the volume.

Or, it occurs to me, an alternative explanation is that you're indeed sending volume-change commands to the MVP, but the commands are queued behind the data stream rather than bypassing it.

This uses the control channel, not the media channel, so its not queued up or anything.

[BobAtTorrey]

Thanks, Sub. The good news is it's designed as it should be. The bad news is now I can't replicate the problem. Delay is now ~4 secs. Before it was, I swear, ~50 seconds. (I've changed skins in the interim, but I can't imagine that's related.) Oh well.

[sub]

Sometimes the MVP can get itself in "a bit of a state" while it is playing media. I'm not sure why it happens, but some times I've seen it take a very very long time to send me notification that a key has been pressed. You may have seen this.