[mythtv-users] PCTV 292e DVB-T2

[Mark Perkins]

> On 26 Nov 2014, at 4:06 am, "Mike Perkins" <mikep at randomtraveller.org.uk> wrote:
> 
>> On 25/11/14 15:46, David Matthews wrote:
>> I have a DVBSky T9580 which has the same SI2168 tuner chip as the PCTV 292e.
>> Myth worked with the closed-source driver on DVB-T and DVB-T2 but I found a
>> problem when I tried the open-source driver.  It would work only on DVB-T.
>> 
>> I'm testing some patches to support DVB-T2 and it now works for me.  I followed
>> the same approach as Myth currently uses to switch between DVB-S and DVB-S2.  If
>> the "mod_sys" field in the dtv_multiplex table contains "DVB-T2" the driver is
>> set to use DVB-T2 otherwise it is set to DVB-T.
>> 
>> I haven't submitted the patches yet for two reasons.  First, the only way to set
>> a multiplex to DVB-T2 is to manually enter the multiplex in the database.  I
>> haven't done anything yet about mythtv-setup.  It needs some way to set the
>> modulation to either DVB-T or DVB-T2 when entering a multiplex manually and also
>> a way to do a full scan with DVB-T2. Secondly, I'm using the fixes-0.27 branch
>> and I'd need to test with master before submitting the patches.  If anyone wants
>> to test what I've done so far or take it over and finish it please let me know.
> This sounds all very interesting, but the standard software seems to work with a PCTV-290e. I can tune both DVB-T and DVB-T2 multiplexes with one, so what is different?
> 
> -- 
> 
> Mike Perkins
> 
> _______________________________________________

Agreed. I'm not sure exactly what the state-of-play with DVB-T2 is supposed to be but there seem to be a number of threads around that claim MythTV can't tune DVB-T2 but the responses seem to indicate it should.

Don't think I've seen any log files from any of them yet though (not sure if log files would show anything but it's a good place to start). Particularly as it seems MythTV will tune DVB-T2 for some.

If there are bugs in external drivers (hypothetical - although in this case it appears one driver set works and the other doesn't, implying a driver bug) it seems to me the best approach (in the first instance) would be to push to get the bugs in the external drivers fixed rather than building workarounds into MythTV.