Reply to thread

Message

<blockquote data-quote="misterd" data-source="post: 382007" data-attributes="member: 19503"><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" /> for testingCurrently I can't see any errors in the log that are caused by the changes:1. It is normal that you have two new cards. The latest version is looking for a different component of the HDPVR now, which has a different device path. But the benefit of this is that during graph building we can start directly with this component and don't need to search it. Therefor TvServer thinks that it is a new card.2. Most of the time for starting timeshift is spent with waiting for the PMT. The TvServer waits ~10 seconds for this.3. Probably this is also the reason why it doesn't work on the client. I will look at the code again.I will post a new version, when I found something.MisterD</blockquote>

[QUOTE="misterd, post: 382007, member: 19503"] :thx: for testing Currently I can't see any errors in the log that are caused by the changes: 1. It is normal that you have two new cards. The latest version is looking for a different component of the HDPVR now, which has a different device path. But the benefit of this is that during graph building we can start directly with this component and don't need to search it. Therefor TvServer thinks that it is a new card. 2. Most of the time for starting timeshift is spent with waiting for the PMT. The TvServer waits ~10 seconds for this. 3. Probably this is also the reason why it doesn't work on the client. I will look at the code again. I will post a new version, when I found something. MisterD [/QUOTE]

Verification