4.2.2 STOP command wont work

[sub]

While checking other video renderers, I wasn't getting any click events with the "VMR9" renderer, but I've added some logic to fix that for the next build.

[eastavin]

What video card are you using?

When you move the mouse over the buttons, do you see them change from white to grey?

If you temporarily try the "VMR9 Custom" renderer, do clicks work then?

There is no extra video card in this machine. It is using onboard intel HD Graphics 405. The manufacturer machine spec is here https://www.acer.com/datasheets/2016/487...A.001.html

Yes the buttons do change from white to grey... all of them. But only the STOP function fails to work as expected during LIVE TV for OSD. In the case of the right click menu with the "stop" and "Main menu" on it neither of these commands work when this problem is on going either.

VMR9 custom does not appear to affect the outcome for the STOP button during livetv in a five minute test I just did. I have to go out until tonight when I will try it again.

[eastavin]

While checking other video renderers, I wasn't getting any click events with the "VMR9" renderer, but I've added some logic to fix that for the next build.

What is your forecast timeframe for delivery of the next build with the modified logic? I could test any beta type software if you want. I ask this question as I am trying to decide if I should reload Directx9.

Which is the preferred renderer? EVR?


Thank you for everything. Edward

[sub]

Yes, EVR is the preferred renderer.

Short term you might as well just install DirectX9 - it's not going to cause any harm having it there.

[eastavin]

Yes, EVR is the preferred renderer.

Short term you might as well just install DirectX9 - it's not going to cause any harm having it there.

A quick update for you on this Sub. Somewhere over the last month the problem has mysteriously vanished. I think its been working fine since early September. I had removed all the LAV stuff and DirectX 9 around July 26 by reverting to a state prior to installing these things in Windows 10 and decided to live with the problem that had existed since 4.2.2 was installed. Now its gone. I did nothing else to the machine. I can only speculate the problem was caused by some Windows update that has since been corrected? I am now on Version 1803 OS Build 17134.285

[sub]

I don't know. Good to hear it's working for you though.