ADBTuner has been working great for quite some time for me but lately I've been seeing recordings failed. It seemed intermittent but now I saw what was going on.
Here is my configuration:
2 Mecool devices
1 Chromecast
1 Onn
Provider is YTTV
I thought my second Mecool device was the source of the problem so I used the excellent feature of setting the tuner priority to that device to 4 so that it would pick that tuner last. That seemed to fix this issue at least until I had to record 4 channels at the same time (something I don't think I've ever done IRL). Well, I had a failed recording but this time on the Chromecast device.
After trying recording on each device individually while watching the tuning happening by viewing the video output of the encoder, I noticed that Channels gave up on the channel tuning if the ADB device took too long to tune. In the failed recording case, the YTTV app displayed two different YTTV logo screens before it successfully tuned to the selected channel. This delay in tuning caused Channels to give up waiting for a stream and responds with:
In a normal working tuning case I do not see those two YTTV logo screens before the video streams starts. The extra delay of the YTTV app displaying those logos is causing Channles to abort the tuning.
ADBTuner has been a game changer now that TVE has gone the way is has. Any ideas of how to get around this issue?
EDIT: I now see that long tuning with the two YTTV logos before streaming starts (but Channels tuning timeout) happens the first tuning after a device reboot. Then every other tuning on that device is fast and Channels does not timeout.