[keynet]

Is the only fix for the log issue an upgrade the VDR 2.1.6?
I have a lot of other plugins that might be affected...
Also the messages are at "error" level for syslog which seems wrong.
Thanks

[FernetMenta]

Is the only fix for the log issue an upgrade the VDR 2.1.6?

Upgrade to 2.1.7 is ok as well

The messages are info-level. If you have an idea how to cope with this for buggy vdr 2.0.x please let me know. I have no clue why it fires the state changed event that often.

[smallint]

FernetMenta, this time on another stage

I have the same issue with VDR 2.0.6/2.0.7. I tracked that down until cVNSIClient::processRECORDINGS_GetCount() which is triggered every 10 seconds and this methods triggers Recordings.Load() which in turns reloads the entire recording list. At the current state I don't know if that is an issue of the client running in Kodi to trigger that request too often or of the vnsiserver plugin which forces vdr to reload the recordings. Uncommenting vnsiclient.c:1677 helps but is obviously not a correct fix. Maybe checking if StateChanged would be a better approach? But you know much better than myself.

[FernetMenta]

@smallint vdr 2.0.x is buggy in this regard. it is vdr what triggers the update. this is fixed with 2.1.x

[smallint]

OK, then I stop investigating and upgrade. Thanks.

[FernetMenta]

actually fixed in 2.1.3 http://projects.vdr-developer.org/git/vd...dde801cdf4
cRecordings::Refresh does not longer change the state