9000h

did the check in case of a retune make sense here? https://github.com/rofafor/vdr-plugin-satip/blob/826dea4ba84d8054a5302879c147c55dcb808d81/tuner.c#L224-L227

there is another issue in tsSet the UpdatePids is not needed here as it's done later on in tsLocked https://github.com/rofafor/vdr-plugin-satip/blob/826dea4ba84d8054a5302879c147c55dcb808d81/tuner.c#L126 https://github.com/rofafor/vdr-plugin-satip/blob/826dea4ba84d8054a5302879c147c55dcb808d81/tuner.c#L156

I see one of the issues come from the latest commit, so may @REELcoder can explain how this makes sense in case of re-tune as it did not work here...

if I comment this part out all is fine, as it's happen with minisatip and digibit r1 it should be also happen on a octonet. Can you please try as...

I do only notice this with invalid channels, and with multiple sat pos. and VDR you have every time some in the channels.conf. I may heart also the background eit/epg...

thanks, still testing but looks like without it's still better

unfortunately not, on the last switch to chan 1 there is no picture sorry was the wrong log before [syslog.txt](https://github.com/rofafor/vdr-plugin-satip/files/4227738/syslog.txt)

it a matter of time here, if you switch with in vdr with key 0 you should be able to reproduce it.

I like to bring this up again as with vdr-2.5.1 and git from today the issue is still happen here I do have to comment out the "return true" to...

will do