Opened 9 years ago
Closed 5 years ago
Last modified 5 years ago
#12792 closed Bug Report - General (Duplicate)
default timeouts are to tight for channel scan with a HDHR3-4DC on DVB-C
Reported by: | Karl Egly | Owned by: | Klaas de Waal |
---|---|---|---|
Priority: | minor | Milestone: | 31.0 |
Component: | MythTV - HDHomeRun | Version: | Unspecified |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
Raise the timeouts, I get not a single transport/service with the defaults.
Change History (6)
comment:1 Changed 9 years ago by
comment:2 Changed 9 years ago by
I found that there is a settable option (Signal Timeout) in Capture Card Setup under Recording Options, but evidently it is not used when discovering channels.
comment:3 Changed 6 years ago by
This problem is possibly not a question of a timeout value.
The mythtv-setup code sees all the HDHomerun devices that support DVB-T, DVB-C or both, as DVB-T devices.
It can work with DVB-C devices such as the HDHR3-4DC because mythtv-setup generates an "auto" tuning command that is the same for both DVB-T and DVB-C devices.
For example, for the 474MHz frequency the command is "auto:474000000".
The HDHR3-4DC tries all the modulation values in parameter /sys/dvbc_modulation and if one of these is correct for the signal then tuning succeeds in one second or so. But if the modulation values are not correct or not present then tuning will never succeed.
The modulation values can be read and written with the hdhomerun_config utility which can be downloaded from the Silicon Dust website.
For example, this are the values for my test system:
[klaas@modu ~]$ hdhomerun_config 1410F45C get /sys/dvbc_modulation a8qam64-6875 a8qam256-6900 [klaas@modu ~]$ hdhomerun_config 1410F45C set /sys/dvbc_modulation "" [klaas@modu ~]$ hdhomerun_config 1410F45C get /sys/dvbc_modulation [klaas@modu ~]$ hdhomerun_config 1410F45C set /sys/dvbc_modulation "a8qam64-6875" [klaas@modu ~]$ hdhomerun_config 1410F45C get /sys/dvbc_modulation a8qam64-6875 [klaas@modu ~]$ hdhomerun_config 1410F45C get /sys/dvbc_modulation a8qam64-6875 [klaas@modu ~]$ hdhomerun_config 1410F45C set /sys/dvbc_modulation "a8qam64-6875 a8qam256-6900" [klaas@modu ~]$ hdhomerun_config 1410F45C get /sys/dvbc_modulation a8qam64-6875 a8qam256-6900 [klaas@modu ~]$
The modulation value is built as follows:
a is always present 8 bandwidth in MHz qam256 modulation 6900 symbol rate
Of course, the parameters have to be chosen for the local DVB-C signal.
It would be better if the MythTV did not depend on a configuration item; if the MythTV code would be changed to have explicit tuning commands, e.g. "a8qam64-6875:474000000", then the HDHR3-4DC would always work independent of the /sys/dvbc_modulation parameter configuration.
comment:5 Changed 5 years ago by
Milestone: | unknown → 31.0 |
---|---|
Resolution: | → Duplicate |
Status: | new → closed |
The default timeout values for the HDHR3-4DC are 1000 ms for the "Signal timeout" and 3000 ms for the "Tuning timeout". With these timeout values scanning is correct on the local DVB-C signal with today's pre-v31 master.
It is possible that the tuning problem described in this ticket is solved by the resolution of ticket #13371 which makes this ticket a duplicate.
Note that if the timeout values are too low for certain cable networks then the values can be changed in the mythtv-setup Capture Card configuration.
This ticket is now closed. If there is still a problem with scanning then please re-open this ticket or create a new ticket.
comment:6 Changed 5 years ago by
Owner: | changed from Karl Egly to Klaas de Waal |
---|
I have the same observation. Should this be a "minor" problem? For me, the severity is worse than medium, as no channels can be found at all (on HDHomeRun Dual). The signal is strong, my HDHomeRunView works fine (and the config-gui), as does EyeTV. From the experience with EyeTV, it may take quite a long time to detect the channels. How about making the timeout a configurable item?