Wetek Play 2 vs Sundtek tuner

I use Wetek Play 2 with CE 8.95.6 now and record DVB-T2 with Tvheadend. I’ve got also one Sundtek DVB‑C/T/T2 tuner that did not work until a trouble with its driver was fixed in November.

Now it works but with so many continuity errors that its recordings are unusable. Sundtek recommends to switch to isochronous mode in such case:

 mediaclient --transfermode=iso -d /dev/dvb/adapter0/frontend0

see https://discourse.coreelec.org/t/sundtek-skytv-ultimate-dtv-clear-failed-e-success/2280/26

Unfortunately it didn’t help me because setting ‘transfermode=iso’ resulted in ‘No input detected’. I have discussed it broadly with Sundtek and Markus Rechberger tried to help me, but eventually his conclusion was this:

“it’s clear your system does not support USB well enough. There are some system hick-ups which interrupt the usb stream and cause a buffer overflow on the USB Stick. The second bad thing is that isochronous is not supported on that system (otherwise transfermode=iso would have worked). Better use a raspberry PI and you will see the difference the hick-ups will be gone and even isochronous works with it.”

As many people obviously use the Sundtek on different amlogic boxes, e.g. @trex_daemon, who opened the thread mentioned above, it seems that the wrong part of my system might be the Wetek itself. If is there anybody using WP2 with Sundtek tuner, please, let me know. It’s hard for me to believe that so excellent tuner cannot be used with WP2.

Are you sure you are using the right device ?
Run mediaclient -e and check where your device is mounted in the dev tree, and use that one when changing the mode.

@trex_daemon - Thank you for your reply. But I believe it is the right device. This is the change to ISO mode:

CoreELEC (official): 8.95.6 (S905.arm)
CoreELEC:~ # mediaclient -e

**** List of Media Hardware Devices ****
device 0: [MediaTV Digital Home III (EU)]  DVB-C, DVB-T, DVB-T2, REMOTE-CONTROL
. . .
  [DVB-C,DVB-T,DVB-T2]:
     FRONTEND: /dev/dvb/adapter2/frontend0
     DVR: /dev/dvb/adapter2/dvr0
     DMX: /dev/dvb/adapter2/demux0

CoreELEC:~ # mediaclient --transfermode=iso -d /dev/dvb/adapter2/frontend0
Setting transfermode to Isochronous
Please reconnect your device in order to activate the transfer mode change
CoreELEC:~ #kodi

And this is the Tvheadend log saying No input source available:

2019-02-14 12:38:47.093 linuxdvb: adapter removed /dev/dvb/adapter2
2019-02-14 12:38:55.666 linuxdvb: adapter added /dev/dvb/adapter2
2019-02-14 12:38:56.001 linuxdvb: adapter 2 setting exclusive flag
2019-02-14 12:39:16.933 dvr: entry 03e257c7091752d8460f4729fc36cb39 "Twister" on "NOVA CINEMA | T2" starting at 2019-02-14 11:02:30, scheduled for recording by "10.0.0.32"
2019-02-14 12:39:16.933 dvr: "Twister" on "NOVA CINEMA | T2" recorder starting
2019-02-14 12:39:16.934 mpegts: 554MHz in DVB-T2 přechod - tuning on Sundtek DVB-C (III) #2 : DVB-T #0
2019-02-14 12:39:17.070 subscription: 0018: "DVR: Twister" subscribing on channel "NOVA CINEMA | T2", weight: 300, adapter: "Sundtek DVB-C (III) #2 : DVB-T #0", network: "DVB-T2 přechod", mux: "554MHz", provider: "CESKE RADIOKOMUNIKACE", service: "NOVA CINEMA | T2", profile="pass"
2019-02-14 12:39:17.627 linuxdvb: Sundtek DVB-C (III) #2 : DVB-T #0 - failed to open /dev/dvb/adapter2/dvr0
2019-02-14 12:39:17.628 linuxdvb: Unable to provide UNC value.
2019-02-14 12:39:23.046 subscription: 0018: service instance is bad, reason: No input detected
2019-02-14 12:39:25.046 subscription: 0018: No input source available for subscription "DVR: Twister" to channel "NOVA CINEMA | T2"
2019-02-14 12:39:25.046 dvr: Recording unable to start: "Twister": No input detected
2019-02-14 12:39:27.046 subscription: 0018: No input source available for subscription "DVR: Twister" to channel "NOVA CINEMA | T2"
2019-02-14 12:39:29.046 subscription: 0018: No input source available for subscription "DVR: Twister" to channel "NOVA CINEMA | T2"
2019-02-14 12:39:31.046 subscription: 0018: No input source available for subscription "DVR: Twister" to channel "NOVA CINEMA | T2"

and so on and so on. Nothing is recorded until the BULK mode is resumed.

yes, I’ve observed this as well. With recent updates my sundtek stopped working in this mode until Ive switched back to bulk mode. It could be that something has been changed in the usb driver