Hi Riksmith,Thanks for supplying the logging guys!
The previous post for now answers one question, and for the other two of you:
Your logs are somewhat different. Partly it is the same, but Jean-Christophe also has a lot of "PMT Timeout" errors.
The debug logging and all other logging does not suggest MP is doing something wrong. The driver does not report any errors to our commands.
Also looking in the code there does not seems to be any alternative to what we are sending now, although the SDK is poorly documented.
Since it has worked with the older driver and i can not find any indication of something we do wrong in MP i have to point at the driver. Specifically since the older driver works without any modification in MP code.
Even if it is NOT a driver problem, we will need help from the devs at TT to try and solve this. They know what is changed in their driver (so why it used to work and now not anymore) and how it should be coded. They can also check our code if they are willing to, to spot any issues.
So i think it is wise to contact TT support through the official channels and report them your problems. The fact that the older driver used to work (with BSOD's) and the newer does not any longer is very important to report.
You could try if it is working with for instance DVB viewer, not that i can solve it if it does work there, but it could indicate that we are doing something different.
thanks for looking into this, highly appreciated!
I just reverted back to driver 184.108.40.206 and first try gave me a 'channel scrambled' message. so the solution is not in the driver version.
@everybody owning a TT with (or without) this issue: how can we organize and unite to get somebody from TT to 'jump in' on this issue. How can we build a case for them to get interested?
I have no experience at all with TT and their support department (do they have one?)