https://bugs.kde.org/show_bug.cgi?id=364298
Mauro Carvalho Chehab <mchehab+...@kernel.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |CONFIRMED
--- Comment #27 from Mauro Carvalho Chehab <mchehab+...@kernel.org> ---
(In reply to lev.cohan from comment #25)
> (In reply to Mauro Carvalho Chehab from comment #24)
> > Ok. It would be good later send me what's happening there, for me to fix
> > the bug at the tool as well.
> How should I report it? Via E-Mail?
Yes. Send an e-mail to linux-me...@vger.kernel.org.
> Kaffeine built from commit f03047d and patched finds 514 channels.
> That's pretty good.
Good! From the logs, the other NIT tables pointed to 83 transponders. 26 ones
failed to tune. I suspect that such transponders are available on other
cities/states/countries where this cable operator provides services.
> Do you have any script to export the channels form the sqlite.db?
No, but it shouldn't be hard to get the channels from there using the command
line. It should be almost identical to what dvbscan found. I suspect that the
other channels got by dvbscan are the data only channels.
> I attached the gzipped log file for the scan in which you can see that for
> every transponder it adds all 83 transponders multiple times.
Every time it gets a new transponder, it will parse the NIT tables provided
there, as NIT table(s) may be different. Btw, where I live, different channels
provide different NIT tables.
> > So, for a final patch, it is likely interesting to add some options to avoid
> > the user the need of scanning transponders that will never be available for
> > him, e. g. allowing them to completely disable other NIT or to filter just
> > one (or a few?) other NITs. Doing an easy to use GUI interface for it could
> > be tricky, though.
>
> How about adding a network-id entry to the DVBv5 file format for the
> dtv-scan-tables?
It could, but I don't see any advantage. It will still need to parse the other
NIT tables, as other places using the same scan file could be using different
transponders.
> Adding a text-field to the device tab would also be a possibility.
The problem is that the screen is already too crowd on devices that support
multiple delivery systems, like this one:
https://mchehab.fedorapeople.org/kaffeine_screenshots/tmp/kaffeine-terrestrial-cable.png
The problem is that the usage of other NIT tables should happen per delivery
system type. So, a frontend that support 3 different delivery systems (like the
one shown on the above image) would need 3 extra lines for a button to enable
"all other network tables" or 6 lines if we also add text input field for the
network ID(s) that will be used. To make it even worse,, the Kernel currently
maps as two frontends single devices that support both Satellite and Cable (or
Terrestrial) delivery systems. We'll eventually fix this bug. So, a single
device could support up to 8 different delivery systems (right now, there are
devices with 6 different delivery systems on the same frontend).
As some people use Kaffeine with 21:9 monitors, adding those extra lines could
be a problem.
So, I'm actually thinking that I to add an extra button (and eventually a combo
box) at the channel scan window that would make it parse the other NIT tables.
That would avoid polluting the channel configuration tabs.
--
You are receiving this mail because:
You are watching all bug changes.
