Do knewc UI Client Screen resolution and "high quality screens" settings work with V5

[BrettB]

On my test v5 server, I've got some failed recordings. And I'm really noticing when viewing them in the Recordings list (on RPi in kodi via knewc) that the red text (in the black box on the right over the blue background) is really blurry from the screen image compression:    

In the knewc Client Settings | UI Client, I tried changing both the Screen resolution (to 1920x1080) and the Enable high quality screens (to on), but I am not seeing any noticeable difference. Should those options be working currently against a v5 server?

[mvallevand]

This certainly was a problem in pre-release testing the summer, and my linux server is still sending 50% quality 1280x720 images and ignoring the initial setup string that knewc sends

http://172.16.3.105:8866/control?size=19...ality=high...

Martin

[BrettB]

This certainly was a problem in pre-release testing the summer, and my linux server is still sending 50% quality 1280x720 images and ignoring the initial setup string that knewc sends

I was thinking that I remembered an early problem where it was ignoring the setting requested and always sending the high quality. I was hoping that sub's fix made it respect the settings requested rather than just force it to always use the lower quality. But my (very limited) testing this morning seemed to indicate otherwise.

I'll try to remember to ping sub about it once he's back at home.

[sub]

I'll try to remember to ping sub about it once he's back at home.

Yep, do that. I though this was fixed a while back, but I'll need to recheck.

[BrettB]

I'll try to remember to ping sub about it once he's back at home.

Yep, do that. I though this was fixed a while back, but I'll need to recheck.

Sub: no rush, but now that you're back, when you get a chance can you take at look at honoring the screen quality requests from the knewc Remote UI clients?

[BrettB]

I'll try to remember to ping sub about it once he's back at home.

Yep, do that. I though this was fixed a while back, but I'll need to recheck.

Bump.