Reply to thread

Message

<blockquote data-quote="jonesdb" data-source="post: 486864" data-attributes="member: 64597">Thanks for the feedback.I don't think the issue is with tuningParameters file though.&nbsp; As I understand the process the tuningParameters file is only used during the scan process.&nbsp; Once stations have been identified and written to the database, only the information in the database is used change the active channel.&nbsp; Thus, every time you select a channel the same data is being read from the database.&nbsp; I have a log file (applicable parts attached) that has recorded two shows one after the other on channel 59 and then tried to record a third show on that same channel after a one hour delay.&nbsp; TVServer was not used during the delay period.&nbsp; I should also let you know that I have disabled EPG gathering for the time being, so that should not interfere with the process.&nbsp; The third show failed to find the PMT and subsequently didn't record anything, even though the client showed a record light and TVServer setup showed a show being recorded.&nbsp; I have compared the log entries for each of the three shows and everything looks identical up to the point of not finding the PMT.&nbsp; I have had another log where three programs were scheduled for recording on the same channel.&nbsp; The first and third recorded fine, but the one in the middle didn't find the PMT and didn't record.&nbsp; Sorry, I didn't keep the log.&nbsp; The 1400 and 1500 logs are for the shows that found the PMT and the 1700 log is the show that failed.Given the above,&nbsp; I'm actually leaning toward believing it is a problem in the parsing of the transport signal for the PMT information.&nbsp; Any other thoughts?</blockquote>

[QUOTE="jonesdb, post: 486864, member: 64597"] Thanks for the feedback. I don't think the issue is with tuningParameters file though. As I understand the process the tuningParameters file is only used during the scan process. Once stations have been identified and written to the database, only the information in the database is used change the active channel. Thus, every time you select a channel the same data is being read from the database. I have a log file (applicable parts attached) that has recorded two shows one after the other on channel 59 and then tried to record a third show on that same channel after a one hour delay. TVServer was not used during the delay period. I should also let you know that I have disabled EPG gathering for the time being, so that should not interfere with the process. The third show failed to find the PMT and subsequently didn't record anything, even though the client showed a record light and TVServer setup showed a show being recorded. I have compared the log entries for each of the three shows and everything looks identical up to the point of not finding the PMT. I have had another log where three programs were scheduled for recording on the same channel. The first and third recorded fine, but the one in the middle didn't find the PMT and didn't record. Sorry, I didn't keep the log. The 1400 and 1500 logs are for the shows that found the PMT and the 1700 log is the show that failed. Given the above, I'm actually leaning toward believing it is a problem in the parsing of the transport signal for the PMT information. Any other thoughts? [/QUOTE]

Verification