[mythtv-commits] Ticket #12499: Diseqc LNB 2 can no longer be configured for use in mythtv-setup
MythTV
noreply at mythtv.org
Wed Dec 2 22:48:39 UTC 2015
#12499: Diseqc LNB 2 can no longer be configured for use in mythtv-setup
-------------------------------------------------+-------------------------
Reporter: Ian Richardson | Owner: gigem
<grandmastermarclar@…> | Status:
Type: Bug Report - General | infoneeded
Priority: major | Milestone: unknown
Component: MythTV - Mythtv-setup | Version: Master
| Head
Severity: high | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------------------+-------------------------
Comment (by dani@…):
Hi,
I am wondering if anything is going to be done to restore the 'killer'
feature in MythTV where multiple LNBs can be used on a DiSEqC switch as
well as cascading if necessary. In previous versions the additional LNB
inputs branch under the DVB-S/S2 adapter separately making it very easy to
configure from within mythtv-setup with multiple populated 4-port DiSEqC
switches.
Part of the dump from a past working setup is the following:
{{{
--
-- Dumping data for table `cardinput`
--
INSERT INTO `cardinput` (`cardinputid`, `cardid`, `sourceid`, `inputname`,
`externalcommand`, `changer_device`, `changer_model`, `tunechan`,
`startchan`, `displayname`, `dishnet_eit`, `recpriority`, `quicktune`,
`schedorder`, `livetvorder`) VALUES
(1, 1, 1, 'Composite 1', NULL, NULL, NULL, NULL, 'Please add',
'Bulsatcom', 0, 0, 0, 1, 1),
(2, 2, 1, 'Composite 1', NULL, NULL, NULL, NULL, 'Please add',
'Bulsatcom', 0, 0, 0, 2, 2),
(3, 3, 1, 'Composite 1', NULL, NULL, NULL, NULL, 'Please add',
'Bulsatcom', 0, 0, 0, 3, 3),
(4, 4, 2, 'DVBInput #1', NULL, NULL, NULL, NULL, 'Please add', 'Hotbird
#1', 0, 0, 0, 4, 4),
(5, 5, 2, 'DVBInput #1', NULL, NULL, NULL, NULL, 'Please add', 'Hotbird
#1', 0, 0, 0, 4, 4),
(6, 4, 3, 'DVBInput #2', NULL, NULL, NULL, NULL, 'Please add', 'Astra
19.2E #1', 0, 0, 0, 4, 4),
(7, 5, 3, 'DVBInput #2', NULL, NULL, NULL, NULL, 'Please add', 'Astra
19.2E #1', 0, 0, 0, 4, 4),
(8, 4, 4, 'DVBInput #3', NULL, NULL, NULL, NULL, 'Please add', 'Freesat -
Sky #1', 0, 0, 0, 4, 4),
(9, 5, 4, 'DVBInput #3', NULL, NULL, NULL, NULL, 'Please add', 'Freesat -
Sky #1', 0, 0, 0, 4, 4),
(10, 4, 5, 'DVBInput #4', NULL, NULL, NULL, NULL, 'Please add', 'Türksat
#1', 0, 0, 0, 4, 4),
(11, 5, 5, 'DVBInput #4', NULL, NULL, NULL, NULL, 'Please add', 'Türksat
#1', 0, 0, 0, 4, 4),
(12, 6, 2, 'DVBInput #1', NULL, NULL, NULL, NULL, 'Please add', 'Hotbird
#2', 0, 0, 0, 6, 6),
(13, 7, 2, 'DVBInput #1', NULL, NULL, NULL, NULL, 'Please add', 'Hotbird
#2', 0, 0, 0, 6, 6),
(14, 6, 3, 'DVBInput #2', NULL, NULL, NULL, NULL, 'Please add', 'Astra
19.2E #2', 0, 0, 0, 6, 6),
(15, 7, 3, 'DVBInput #2', NULL, NULL, NULL, NULL, 'Please add', 'Astra
19.2E #2', 0, 0, 0, 6, 6),
(16, 6, 4, 'DVBInput #3', NULL, NULL, NULL, NULL, 'Please add', 'Freesat -
Sky #2', 0, 0, 0, 6, 6),
(17, 7, 4, 'DVBInput #3', NULL, NULL, NULL, NULL, 'Please add', 'Freesat -
Sky #2', 0, 0, 0, 6, 6),
(18, 6, 5, 'DVBInput #4', NULL, NULL, NULL, NULL, 'Please add', 'Türksat
#2', 0, 0, 0, 6, 6),
(19, 7, 5, 'DVBInput #4', NULL, NULL, NULL, NULL, 'Please add', 'Türksat
#2', 0, 0, 0, 6, 6),
(20, 8, 2, 'DVBInput #1', NULL, NULL, NULL, NULL, 'Please add', 'Hotbird
#3', 0, 0, 0, 8, 8),
(21, 9, 2, 'DVBInput #1', NULL, NULL, NULL, NULL, 'Please add', 'Hotbird
#3', 0, 0, 0, 8, 8),
(22, 8, 3, 'DVBInput #2', NULL, NULL, NULL, NULL, 'Please add', 'Astra
19.2E #3', 0, 0, 0, 8, 8),
(23, 9, 3, 'DVBInput #2', NULL, NULL, NULL, NULL, 'Please add', 'Astra
19.2E #3', 0, 0, 0, 8, 8),
(24, 8, 4, 'DVBInput #3', NULL, NULL, NULL, NULL, 'Please add', 'Freesat
-Sky #3', 0, 0, 0, 8, 8),
(25, 9, 4, 'DVBInput #3', NULL, NULL, NULL, NULL, 'Please add', 'Freesat
-Sky #3', 0, 0, 0, 8, 8),
(26, 8, 5, 'DVBInput #4', NULL, NULL, NULL, NULL, 'Please add', 'Türksat
#3', 0, 0, 0, 8, 8),
(27, 9, 5, 'DVBInput #4', NULL, NULL, NULL, NULL, 'Please add', 'Türksat
#3', 0, 0, 0, 8, 8);
}}}
Merging card input with the capturecard table might represent an
optimisation from a development standpoint but it is horrific for the end
user. The strength of MythTV is its felixibility and ability to mix
analogue and digital devices as allowing the end user to use it set it up
to meet all his requirements. Few other systems can match that especially
from a backend standpoint. I am not able to set up separate DVB device for
each LNB as they show up as 'already used.' What can I do to solve this
problem as I am stuck with setting up the backend as a result?
--
Ticket URL: <https://code.mythtv.org/trac/ticket/12499#comment:29>
MythTV <http://www.mythtv.org>
MythTV Media Center
More information about the mythtv-commits
mailing list