Reply to thread

Message

<blockquote data-quote="Owlsroost" data-source="post: 1256185" data-attributes="member: 83973">If you look at MediaPortal.log, the 'internal' volume and mute updates (i.e. when *MP* is adjusting the Windows audio mixer settings) look like this:[code][2019-03-14 17:59:46,669] [Log&nbsp; &nbsp; ] [MPMain&nbsp;&nbsp; ] [DEBUG] - Mixer: Set new Volume = 61439, old Volume = 62914....[2019-03-14 18:00:07,205] [Log&nbsp; &nbsp; ] [MPMain&nbsp;&nbsp; ] [DEBUG] - Mixer: Set new IsMuted = True, old IsMuted = False[/code]....and the 'external' changes (i.e. when MP is notified of changes to the audio mixer settings made by *other* software/drivers/OS) look like this:[code][2019-03-14 17:59:56,485] [Log&nbsp; &nbsp; ] [23&nbsp; &nbsp; &nbsp;&nbsp; ] [DEBUG] - Mixer: AudioEndpointVolume change, new muted = False, new volume = 58981, old muted = False, old volume = 45055[/code]...so you can relate the remote control HID entries in the log to the volume/mute changes.I *think* RC6 log you posted earlier doesn't show any 'internal' volume changes, so MP wasn't actioning the volume up/down commands from the remote internally.(The Ortek VRC-1100 remote is creating *both* kinds of log entries, so it looks like it's directly manipulating the Windows audio mixer settings *and* the volume/mute commands from it are being actioned internally by MP - I think this is what was causing the lock-ups, and may be causing the odd behaviour you reported in post #46).</blockquote>

[QUOTE="Owlsroost, post: 1256185, member: 83973"] If you look at MediaPortal.log, the 'internal' volume and mute updates (i.e. when *MP* is adjusting the Windows audio mixer settings) look like this: [code][2019-03-14 17:59:46,669] [Log ] [MPMain ] [DEBUG] - Mixer: Set new Volume = 61439, old Volume = 62914 .... [2019-03-14 18:00:07,205] [Log ] [MPMain ] [DEBUG] - Mixer: Set new IsMuted = True, old IsMuted = False [/code] ....and the 'external' changes (i.e. when MP is notified of changes to the audio mixer settings made by *other* software/drivers/OS) look like this: [code][2019-03-14 17:59:56,485] [Log ] [23 ] [DEBUG] - Mixer: AudioEndpointVolume change, new muted = False, new volume = 58981, old muted = False, old volume = 45055 [/code] ...so you can relate the remote control HID entries in the log to the volume/mute changes. I *think* RC6 log you posted earlier doesn't show any 'internal' volume changes, so MP wasn't actioning the volume up/down commands from the remote internally. (The Ortek VRC-1100 remote is creating *both* kinds of log entries, so it looks like it's directly manipulating the Windows audio mixer settings *and* the volume/mute commands from it are being actioned internally by MP - I think this is what was causing the lock-ups, and may be causing the odd behaviour you reported in post #46). [/QUOTE]

Verification