Opened 17 years ago
Closed 17 years ago
Last modified 17 years ago
#3011 closed defect (fixed)
importing channels.conf does not work since revision 11682
Reported by: | Owned by: | Janne Grunau | |
---|---|---|---|
Priority: | minor | Milestone: | 0.21 |
Component: | mythtv | Version: | head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description (last modified by )
Importing the channels.conf file generated by dvbscan tools does not work anymore. In the logging the message is listed that channels are imported, but none of them are stored in the database for some unclear reason. No error-message is given at all. Channels are just all ignored, not even 'skipped' mesages are displayed in the setup. After this error of importing automaticly the scanner is started, tuning for channels, but it cannot lock anything.
To me, it seems a different problem that ticket #2830. The channel.conf files are generated as is, by dvbscan tooling. And even if the format is invalid and this quirky behaviour is by design, the setup tool should mention what is incorrect in the channels.conf files, at least in the logfiles. But: before revision 11682 my channel.conf files, work, and from 11682 and on it they do not, so I do NOT believe the channel.conf files are wrong.
I use DVB-S, on the Astra 1, 2 and Hotbird satellites. I live in the Netherlands. (MPEG2)
Attached I have put my channels.conf files (generated by dvbscan) and a logfile of mythtv-setup.
Attachments (4)
Change History (11)
Changed 17 years ago by
Attachment: | myfiles.tgz added |
---|
comment:1 Changed 17 years ago by
Owner: | changed from Isaac Richards to danielk |
---|---|
Version: | 0.20 → head |
comment:2 Changed 17 years ago by
Uuh, it might be that I stopped the scan by hand in this logging... If I do not do that, the scanner is scanning for hours, only waiting for timeouts, and finally come up with no channels...
Because you say that the first error in the logging is a stop of tuning, do I understand it correctly that it is now by design that the tuner start scanning for channels it already has imported? If so, do I need to produce a logging of these timeouts?
comment:3 Changed 17 years ago by
Uhm, if you cancel the scan immediately no channels will be inserted.
Please try importing just one channel you know you should be able to get and let it scan without cancelling the import, attach the log & channel.conf from that.
The import just seeds the channel scanner. The timeout for DVB-S is by default very conservative, something like 40 seconds. This is why it takes so long. If you only scan one rotor position at a time you should be able decrease this to 1 second for the signal lock, and 4 seconds for the channel lock during the scan. Once we apply the patch in #2802 we can decrease the lock timeout and only use this timeout once the rotor has turned.
comment:4 Changed 17 years ago by
Hello Daniel,
Attached I have put the channels.conf, and a logfile of myth-setup where I try to import only 1 channel. I have chosen a channel that works, As sanity check I have tested it before and after importing this channel in MythTV.
BTW: Where can I find the option to decrease the time from 40 seconds to shorter? I have no rotor anywhere, I only have switches and a WaveFrontier? T90 with room for 16 LNB's... So, a few seconds is more than enough for me...
Remy
Changed 17 years ago by
Attachment: | channels.conf added |
---|
Changed 17 years ago by
Attachment: | channels.2.conf added |
---|
Changed 17 years ago by
Attachment: | mythsetup.log added |
---|
comment:5 Changed 17 years ago by
Description: | modified (diff) |
---|---|
Milestone: | unknown → 0.21 |
Owner: | changed from danielk to Janne Grunau |
comment:6 Changed 17 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Here's where things go awry:
For some reason the scan stops after looking at just one frequency. I will need to add some debugging statements to the code to figure out why this is failing.