Bug #611
invalid satconf value in dvbmuxes filename after "copy to other adapter" button used
| Status: | Rejected | Start date: | 07/22/2011 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - | |||
| Found in version: | git-9d775da pulled 20jul11 | Affected Versions: |
Description
I have 4 identical adapters, connected to 4 quattro LNBs via a 17x8 switch.
So I configured each adapter with identical Satellite configs:
Name Switchport LNB Type
Astra 1 0
Astra 2 1
Astra 3 2
I have not assigned Switchport 3 yet.
Then I scan with adapter 1. After scan I use "copy to other adapter" button from Muxes list. This copies OK, so I copy to all 3 other adapters.
Now checking the .hts directory structure.
dvbsatconf/_dev_dvb_adapter0_STV090x_Multistandard:
1 5 6
dvbsatconf/_dev_dvb_adapter1_STV090x_Multistandard:
2 7 8
dvbsatconf/_dev_dvb_adapter2_STV090x_Multistandard:
10 3 9
dvbsatconf/_dev_dvb_adapter3_STV090x_Multistandard:
11 12 4
OK, so 1 satconfig is created when the adapter is found (1 .. 4) and the others were manually added.
In dvbmuxes for adapter 0 we see the satconf numbers assigned from the list under adapter 0:
_dev_dvb_adapter0_STV090x_Multistandard12685000_H_satconf_6
_dev_dvb_adapter0_STV090x_Multistandard12685000_V_satconf_6
_dev_dvb_adapter0_STV090x_Multistandard12692000_V_satconf_5
_dev_dvb_adapter0_STV090x_Multistandard12692250_H_satconf_1
_dev_dvb_adapter0_STV090x_Multistandard12696000_H_satconf_6
The "copy to other adapter" button copies these files to the other adapters, e.g. in adapter 1 directory:
_dev_dvb_adapter1_STV090x_Multistandard12636000_V_satconf_6
_dev_dvb_adapter1_STV090x_Multistandard12640000_V_satconf_1
_dev_dvb_adapter1_STV090x_Multistandard12641000_H_satconf_6
_dev_dvb_adapter1_STV090x_Multistandard12643350_H_satconf_5
_dev_dvb_adapter1_STV090x_Multistandard12643350_V_satconf_5
_dev_dvb_adapter1_STV090x_Multistandard12644000_H_satconf_6
_dev_dvb_adapter1_STV090x_Multistandard12645000_H_satconf_6
but note that the satconf_1, 5 and 6 refer to satconfs that exist under adapter 0.
Of course, the files themselves also refer to the same satconf number (that is in another adapter).
So this assumes that the adapter that will do the tuning (adapter 1) must have the same diseqc connections as the adapter that did the scan.
And definitions made via the GUI (satellite config on the Adapter definition) are redundant/ignored for all but the adapter that did the scan.
This leads to internal inconsistencies in the filename/directory name structure but does not seem to cause tuning issues.
History
#1
Updated by Adam Sutton 11 months ago
- Status changed from New to Rejected
If this problem still exists with latest code can you please re-submit.