Project

General

Profile

Bug #612

Autodetect muxes seems to lead to mux entries without satconf value

Added by Rob vh over 13 years ago. Updated over 12 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-07-22
Due date:
% Done:

0%

Estimated time:
Found in version:
git-9d775da pulled 20jul11
Affected Versions:

Description

I have one adapter with Autodetect muxes. On the dvbmuxes directory for this adapter, there are entries without a satconfig part to their filename:

_dev_dvb_adapter0_STV090x_Multistandard12725000_V_satconf_6
_dev_dvb_adapter0_STV090x_Multistandard12728500_V_satconf_1
_dev_dvb_adapter0_STV090x_Multistandard130000000_H
_dev_dvb_adapter0_STV090x_Multistandard330000000_H
_dev_dvb_adapter0_STV090x_Multistandard338000000_H
_dev_dvb_adapter0_STV090x_Multistandard346000000_H
_dev_dvb_adapter0_STV090x_Multistandard354000000_H
_dev_dvb_adapter0_STV090x_Multistandard362000000_H
_dev_dvb_adapter0_STV090x_Multistandard370000000_H
_dev_dvb_adapter0_STV090x_Multistandard378000000_H
_dev_dvb_adapter0_STV090x_Multistandard386000000_H
_dev_dvb_adapter0_STV090x_Multistandard394000000_H
_dev_dvb_adapter0_STV090x_Multistandard402000000_H
_dev_dvb_adapter0_STV090x_Multistandard410000000_H
_dev_dvb_adapter0_STV090x_Multistandard426000000_H
_dev_dvb_adapter0_STV090x_Multistandard434000000_H
_dev_dvb_adapter0_STV090x_Multistandard442000000_H
_dev_dvb_adapter0_STV090x_Multistandard450000000_H
_dev_dvb_adapter0_STV090x_Multistandard458000000_H
_dev_dvb_adapter0_STV090x_Multistandard466000000_H
_dev_dvb_adapter0_STV090x_Multistandard522000000_H
_dev_dvb_adapter0_STV090x_Multistandard530000000_H
_dev_dvb_adapter0_STV090x_Multistandard538000000_H
_dev_dvb_adapter0_STV090x_Multistandard610000000_H
_dev_dvb_adapter0_STV090x_Multistandard618000000_H
_dev_dvb_adapter0_STV090x_Multistandard626000000_H
_dev_dvb_adapter0_STV090x_Multistandard8000000_H
_dev_dvb_adapter0_STV090x_Multistandard99999980_V_satconf_5
_dev_dvb_adapter0_STV090x_Multistandard99999990_H_satconf_5

These, and the 2 with invalid frequency, remain in "awaiting initial scan" state.

Contents of one of those files:

_Multistandard610000000_H {
"quality": 100,
"enabled": 1,
"status": "Unknown",
"transportstreamid": 10021,
"frequency": 610000000,
"symbol_rate": 6900000,
"fec": "3/5",
"polarisation": "Horizontal",
"modulation": "QPSK",
"delivery_system": "SYS_UNDEFINED",
"rolloff": "ROLLOFF_35"
}

History

#1

Updated by Adam Sutton over 12 years ago

  • Status changed from New to Rejected

Very old, if its still a problem please re-submit.

Also available in: Atom PDF