Tvheadend

I have not seen these errors in 3.9.1743, but after my new git pull last weekend I have been having bad tunes again.
they may be linked with having a streaming connection active, when a recording starts. here is one from last night:

23:20:17 I start a streaming connection, tuned to NPO2, using adapter 3.
23:49:30 a recording start on Channel, using adapter 2.
25:59:30 another recording starts for Net5 HD, on adapter 4. This one fails with

2014-10-17 23:59:31.341 [ DEBUG]:linuxdvb: STV090x Multistandard : DVB-S #4 - status BAD (SIGNAL | CARRIER)
2014-10-17 23:59:37.073 [ DEBUG]:linuxdvb: STV090x Multistandard : DVB-S #4 - status NONE ()
2014-10-17 23:59:37.545 [ DEBUG]:linuxdvb: STV090x Multistandard : DVB-S #4 - status BAD (SIGNAL | CARRIER)
2014-10-17 23:59:40.303 [ DEBUG]:service: 23.5E/12187H/NET5 HD: Status changed to [Graceperiod expired] [Data timeout]
2014-10-17 23:59:40.616 [ DEBUG]:capmt: oscam, CA_SET_DESCR adapter 3 par 0 idx 0 fe227292a5b8fc59
2014-10-17 23:59:42.299 [ DEBUG]:mpegts: 12187H in 23.5E - stopping mux
2014-10-17 23:59:42.299 [ DEBUG]:linuxdvb: STV090x Multistandard : DVB-S #4 - stopping 12187H in 23.5E
2014-10-17 23:59:42.299 [ DEBUG]:epggrab: grab done for 12187H in 23.5E (stolen)

Adapter 4 is definitely not bad or lazy, other recordings for Net5 HD start perfectly on adapter4.

So after tvh discarded adapter 4, he tries adapter 5, and gets continuity errors.