[mythtv-users] New tuners don't auto-switch the DVBT2 - do I need 0.28?

[John Pilkington]

On 08/04/15 16:34, Tim Draper wrote:
>
>
> ---- On Wed, 08 Apr 2015 14:29:31 +0100 Ian Oliver<lists at foxhill.co.uk> wrote ----
>   > In article <55251EB7.5030102 at prolingua.co.uk>, David Matthews wrote:
>   > > I've been running that version successfully for several months.  Of
>   > > course, that doesn't mean there isn't a bug!  It's possible that one of
>   > > the other fixes from the fixes-0.27 branch is causing a problem.
>   >
>   > It's far more likely that, 1) I've built it wrong, 2) I'm running it
>   > wrong, 3) both.
>   >
>   > > If
>   > > you've got time it might be worth trying a version of myth without my
>   > > patch, then apply the patch to it and see whether that is what is
>   > > causing the error.
>   >
>   > Yes, that's a good idea. I'll give it a whirl.
>   >
>   > My driver patch is working fine with stock 0.27, so I'm going to have to
>   > make an effort. If I don't, who knows whether 0.28 will do what I need?
>   >
>   >
>
> As nice as the dvb-s2 patch is, i don't feel comfortable applying out-of-box/tainted code (compared to official repo/git code) - all down to non-standard config rather than trust. i cant believe it's not already in 0.27/fixes. after being told (and buying) a 292e dvb-t2 tuner recently due to various recommended reasons, not once did the lack of easy dvb-t2 tuning on the 292e come up. I've seen various work arounds and hacks in this thread but non i feel would be a long-term easy solution.
> I might as well of stuck with my old dvb-t usb tuner.
>
> Good work on the patch and that there is a solution, but I'm personally living with lack of dvb-t2 scanning support and wait for 0.28 in the hope its merged for that release.
>

As a non-dev, I'd point out that patches need reports of testing before 
they will be committed, and testing for a new device generally requires 
that the dev team has access to that device in a relevant environment - 
and feels the need.  If yours is no good to you....