Portisch

I have done a new test version: https://github.com/Portisch/RF-Bridge-EFM8BB1/blob/62d3cbd5411cb019492e808b5b4c9d31ebe60384/Keil%208051%20v9.53%20-%20Release/RF-Bridge-EFM8BB1.hex Please try this again with 0xA6. If no red LED on the bridge is flashing please report!

As this thread was inactive the branch didn't get updated. I will do tomorrow. Use the latest hex file from the master branch and do 0xB1 sniffing again please.

Please try the new binary with 0xA6 sniffing: https://github.com/Portisch/RF-Bridge-EFM8BB1/blob/25b90c9ff90ab09c973d1805381f108100b0e143/Keil%208051%20v9.53%20-%20Release/RF-Bridge-EFM8BB1.hex

@Paulchen-Panther is right and the Grabber can not detect the "black borders" on 4:3 as they aren't included in the video frames. I think this is done afterwards in Kodi...

@Paulchen-Panther is right and the Grabber can not detect the "black borders" on 4:3 as they aren't included in the video frames. I think this is done afterwards in Kodi...

fixed jenkins diff

Need to use `const RESOLUTION_INFO res = CServiceBroker::GetWinSystem()->GetGfxContext().GetResInfo()` to get real, current used display resolution. Filtered from kodi.log to see the timing: ```t 2024-12-04 09:59:14.836 T:1093 warning : CRenderManager::UpdateLatencyTweak(897) -...

I changed now `width` & `height` to only `resolution` and use display mode `height`. This is enough and not so "confusing" for users as its only like `1080` or `2160`...

Yes, these are Vesa modes? It's the question what want to have or if there is a diff latency need at all for same height but different width? I guess...

> changes for all configs in the conf/cards directory You really go to need to change all configs on earth?