Klaus Schmidinger wrote:

Lauri Tischler wrote:

...

Found in log..

Sep 13 15:55:37 vdr2 vdr[16360]: changing pids of channel 1 from 512+128:650=eng,652=dut:2321 to 512+128:650=fin:2321 Sep 13 15:55:37 vdr2 vdr[16360]: retuning due to modification of channel 1 Sep 13 15:55:37 vdr2 vdr[16360]: switching to channel 1 Sep 13 15:55:37 vdr2 vdr[16360]: transfer thread ended (pid=16360, tid=-1289061456) Sep 13 15:55:37 vdr2 vdr[16360]: cTS2PES got 3 TS errors, 4 TS continuity errors Sep 13 15:55:37 vdr2 vdr[16360]: cTS2PES got 0 TS errors, 4 TS continuity errors Sep 13 15:55:37 vdr2 vdr[16360]: cTS2PES got 0 TS errors, 4 TS continuity errors Sep 13 15:55:37 vdr2 vdr[16360]: buffer stats: 89488 (4%) used Sep 13 15:55:37 vdr2 vdr[16360]: transfer thread started (pid=16360, tid=-1289061456) Sep 13 15:55:37 vdr2 vdr[16360]: buffer stats: 11092 (5%) used Sep 13 15:55:39 vdr2 vdr[16360]: setting audio track to 1 (0)

---

I seem to remember that change in apid should not require retuning. Maybe I'm wrong. ps. vdr patched with subtitles and livebuffer.

Only a change in the language definitions doesn't trigger a retune. An actual PID change does require a retune.

Can we make it check for a retune if necessary before attempting to record?

Regards.