Marc

Here is from Vu+ an linux kernel patch [patch](http://code.vuplus.com/repository/openvuplus_3.0.git/commit/?id=e79f10463a103a1e9e27e74d084082053d140fb3) that defines it as 21 ``` From e79f10463a103a1e9e27e74d084082053d140fb3 Mon Sep 17 00:00:00 2001 From: hschang Date: Wed, 28 Feb 2018 16:04:44...

Hi @nikolauzi11 Yes, you too have a great new year, So the commit before this was beter? or is this stiil as #181

Hi @nikolauzi11 Thanks for your support! it is appreciated. Could you try for testing, to modify Filter.h in: https://github.com/Barracuda09/SATPI/blob/410b47f5d9aaed43d41976b7ea6c345f171397e1/src/mpegts/Filter.h#L205-L215 And change Line 211 to: ``` _mutex.unlock(); const bool done =...

Hi @nikolauzi11 That is nice, thanks for trying this. Then we found a permanent solution for this problem. The problem is (probably) the combination of VDR, Sundtek tuner and this...

Hi @aurelmarius and @Saentist It seems that in the screen shots there is in the `Monitor Info` section the `Signal Strength`but No `snr` So maybe something else is wrong too?

@Saentist and @aurelmarius I think your solution is when TVH is retrieving the signal status from the drivers. But I believe this signal is send by SatPI via RTP. The...

So disabling `Check tuner-number in signal-status messages` does not work? Strange here it does, which version of TVH are you using?

So there are bars, so the data is RTCP data is send to TVH. But is not correct so it seems.

I think @Saentist had a point with: > Driver module is not capable to send DVBAPI 5.x information use 3.x SatPI is probably using 5.x and only falls back to...

@aurelmarius Did you change something in between? Because the first screen shot was 221: ***  *** And second 65534: ***