Rainer Hochecker

> But then still everything is synced over to Kodi, right? No, vnsiserver only syncs channels that passes the filter. I am talking about VNSI channel filter, not Kodi's channel...

vnsi channel filters also sort channels.conf. wanted channels are first, then unwanted ones.

I don't see any problem in the log. It switches modes. What do you think it's wrong?

I think the problem is your wrong interpretation of the codec screen. Your log states that it has switched to mode 0x4e: XRANDR: /usr/lib/xbmc/xbmc-xrandr --output HDMI2 --mode 0x4e which is...

When did you run xbmc-xrandr? After the switch?

I have added a debug log to print out info right after xrandr event: fb207824a93002eaecc6302b07f28677ec892e64 Can you post a new log when you have this change available?

The change was not supposed to be a fix, just more info to track this down. So xbmc requests mode 0x4e and right after the xrandr wrapper detects 0x4b. You...

Does this problem still exist? Maybe this helps: 1dc0e424ae66dcfdfc8c0efaa39e01bed323be89

> What shall I do? you have those options: 1) upgrade to vdr 2.4 2) stay with vnsiserver 1.6 3) patch sources of vdr 2.2 vdr should not define functions...

> vnsiserver 1.6 is the last compatible version to vdr 2.2.0? no, just for the time being. master is a development branch that can break. I am grateful for posts...