Reply to thread

Message

<blockquote data-quote="jonesdb" data-source="post: 490789" data-attributes="member: 64597">I actually believe that there are at least two problems that show similar symptoms.&nbsp; (At least for me, this seems to be the case)First, I'm on cable using clear QAM, so the situation maybe somewhat different for satellite.&nbsp; First Problem.&nbsp; The cable company does change the PID number associated with a particular PAT program number (ServiceID or cable program channel ...i.e. History channel) at seemingly random points in time, though these don't change often (every few months).&nbsp; When it does occur, MP won't tune that particular ServiceID (program channel) any longer as the PMT PID no longer exists.&nbsp; MP keeps track of the expected PMT PID in the tuning details table along with the ServiceID (PAT program number).&nbsp; The result when such a change takes place is a PMT timeout error and no recording or live TV.&nbsp; &nbsp; If I update the tuning details to reflect the new PMT PID for that particular ServiceID everything is back to normal.&nbsp;&nbsp; (I have a Sony DVR that doesn't have any problem with such changes, as it just looks up the new PID for that PAT program number.)&nbsp; I believe that storing the ServiceID and the associated PMT PID this was done to produce a quick response when changing channels (programs).&nbsp; It would be a great help if MP would update the PMT PID in the tuningDetails table for that particular ServiceID when the PMT PID is not found during the tuning process.Second problem.Sometimes the PMT PID search just does a timeout.&nbsp; I have found no reason for this.&nbsp; I have tired extending the search time with no improvement.&nbsp; I have checked for existence of the PMT PID with TSReaderLite right after a PMT PID timeout and the PMT PID exists.&nbsp; I have had MP tune to a PMT PID and record the program, wait an hour and try to retune the same PMT PID and timeout, wait another hour and try to tune the same PMT PID again and be successful.The second problem is more bothersome to me as the result is that MP seems to randomly not record some of my scheduled programs.&nbsp; I have not been able to identify anything in the logs that is different during these incidents.</blockquote>

[QUOTE="jonesdb, post: 490789, member: 64597"] I actually believe that there are at least two problems that show similar symptoms. (At least for me, this seems to be the case) First, I'm on cable using clear QAM, so the situation maybe somewhat different for satellite. First Problem. The cable company does change the PID number associated with a particular PAT program number (ServiceID or cable program channel ...i.e. History channel) at seemingly random points in time, though these don't change often (every few months). When it does occur, MP won't tune that particular ServiceID (program channel) any longer as the PMT PID no longer exists. MP keeps track of the expected PMT PID in the tuning details table along with the ServiceID (PAT program number). The result when such a change takes place is a PMT timeout error and no recording or live TV. If I update the tuning details to reflect the new PMT PID for that particular ServiceID everything is back to normal. (I have a Sony DVR that doesn't have any problem with such changes, as it just looks up the new PID for that PAT program number.) I believe that storing the ServiceID and the associated PMT PID this was done to produce a quick response when changing channels (programs). It would be a great help if MP would update the PMT PID in the tuningDetails table for that particular ServiceID when the PMT PID is not found during the tuning process. Second problem. Sometimes the PMT PID search just does a timeout. I have found no reason for this. I have tired extending the search time with no improvement. I have checked for existence of the PMT PID with TSReaderLite right after a PMT PID timeout and the PMT PID exists. I have had MP tune to a PMT PID and record the program, wait an hour and try to retune the same PMT PID and timeout, wait another hour and try to tune the same PMT PID again and be successful. The second problem is more bothersome to me as the result is that MP seems to randomly not record some of my scheduled programs. I have not been able to identify anything in the logs that is different during these incidents. [/QUOTE]

Verification