Strange blending / alpha issue in -qt version vs. chrome.

[Sloanstar]

There's a strange alpha blend / dithering effect / encoding effect that goes across the screen when compared to chrome version.

All -qt versions released up to and including v0.1.0

Lenovo Yoga 720-15ikb
GFE 3.14.1.48
GF Drivers 398.82
Win10 1803 (x64)

Bitrate 150Mbps
1080p
60 FPS
All other moonlight client settings Automatic/Autodetect/Defaults

[cgutman]

Can you attach the Moonlight log file? On Windows, it's in %TEMP% and will be called Moonlight-<some numbers>.log.

After getting the log of your current configuration, do you see the same issue if you force software decoding in the settings?

[Sloanstar]

Moonlight-1533957233.log

[Sloanstar]

Selecting force software decoding - I no longer see the issue.

[cgutman]

@Sloanstar ok, do you still see the issue if you go back to Auto decoder and switch to "Force H.264"?

[Sloanstar]

Software render log, in case it is useful.

Moonlight-1533957641.log

[Sloanstar]

H.264 looks clean too. I'll leave it on this since it is probably faster/less resource intensive and the picture is definitely cleaner.

[cgutman]

Very odd. The closest machine I have to yours is a Windows 10 laptop with Intel HD 615 graphics and it doesn't seem to display the issue. Does it always occur or is there something that seems to trigger it? Are there any other settings that make it appear or disappear?

[Sloanstar]

I'll see if I can find some other settings that trigger it, but it only started occurring since I started using -qt. Never had the effect on Chrome.

[Sloanstar]

Looks like Hardware HEVC only. I tried installing the HEVC codec from the windows store and a reboot, no change.

[cgutman]

I wonder if it's a GPU driver bug. Moonlight Chrome never could support HEVC, so you didn't see the bug there.

Can you screenshot the Driver tab in Device Manager for your client PC's GPU? I can try to find it and install it on my laptop to try to reproduce the issue.

Is your client machine also running Windows 10 1803?

Does lowering the bitrate to 20 Mbps change anything?

[Sloanstar]

[Sloanstar]

Yes, client machine is also Windows 10 1803.
No change at 20 Mbps.

[Sloanstar]

I have an older Asus laptop I can try on if you think it is a client/driver issue but I dont think the windows versions are the same, so there might be too much introduction of change there to be a viable test.

[Sloanstar]

I have a "fix" and it's an issue with the laptop and Intel/Nvidia GPU selection, not anything in your code per se, unless there's a way to force select between the rendering GPU at launch and -qt isn't doing that.

In the mean time, configuring the GF Control Panel to force the NV GPU for the executable addresses the blending.

If you give me Wiki access I can write it up with screenshots, or if you prefer it here in the issue I can do that too, let me know.

[Sloanstar]

Video Issues

Devices with Multiple Video Cards
Open the Control Panel for your video card. (nVidia shown – AMD assumed similar)

Option 1 – Globally change the preferred video card.
Pro: This should cover future application automatically.
Con: You may use more battery on applications that don’t require discrete GPU.

Option 2 – Specify GPU for Moonlight Executable.

1. Select manage 3d Settings
2. Add the Moonlight application (Does not normally appear in the list)
   
   
   

Click Apply & Enjoy.

[rogeriskira]

Unfortunately on the laptop that I am using I don't have a graphics card.
i5-7200U
Intel HD 620
8GB ram
I realize that I have the same fix by using software decoding with HEVC. Should I also provide my log?

[cgutman]

Yeah, attach your log from the %TEMP% folder if you can. Additionally, a screenshot of your Intel GPU's properties page in Device Manager (like the one above) would be greatly appreciated.

To work around the bug, set the codec option to Force H.264 and set decoder back to Automatic.

[Sloanstar]

Make sure the Intel gfx drivers are up to date as well.

…

On Wed, Sep 12, 2018, 10:42 AM Cameron Gutman ***@***.***> wrote: Yeah, attach your log from the %TEMP% folder if you can. Additionally, a screenshot of your Intel GPU's properties page in Device Manager (like the one above) would be greatly appreciated. To work around the bug, set the codec option to Force H.264 and set decoder back to Automatic. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#32 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AP-WAU6nJWlfwwReAwTz4CrCsrr0OdWuks5uaR04gaJpZM4V3bTi> .

[rogeriskira]

Moonlight-1536778620.log

I added the log file in which I used Force Hardware decoding, and Force HEVC. But as you mentioned force h.264 and Automatic do the trick. It would be nice if I could use HEVC to save on some bandwidth.

[cgutman]

I implemented a check to avoid HEVC on Intel drivers older than build 4836.

@rogeriskira You should be able to use HEVC properly if you update your GPU driver to the latest version from Intel's website

[cgutman]

Fix released in v0.5.0 (Beta 2)

[rogeriskira]

Thank so much! I can confirm it works as intended now.