Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1031689" data-attributes="member: 82144">Cool. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Yeah, the PMT wait in the patch is &quot;sub-optimal&quot; for the HD-PVR 2. When I created the patch I didn't know that HD-PVR 2 has a different PMT PID compared with HD-PVR 1 and Colossus. So one of the things that is making it so slow is that TV Server is waiting for PMT (video/audio stream info), not finding it after those 3 seconds, and then having to do an &quot;exhaustive search&quot; to find the actual PMT (which may take another second or two). Maybe that doesn't make a lot of sense; in short it just means keep that PMT timeout as low as you can because every second you add is a second more in channel switching delay.Yes. There is maybe a second of delay in TV Server's timeshifting mechanism, and probably another second in the HD-PVR's drivers and encoding.One of the problems I see is this:That is way longer than what I ever remember seeing for the HD-PVR 1 or Colossus. The above is on first tune (when the HD-PVR is loaded for the first time). On subsequent tunes:Basically your HD-PVR 2 seems to be slow to start up.To mitigate this I suggest you try changing &quot;when card enters idle state...&quot; to &quot;pause&quot; and enable &quot;allow this card to be preloaded&quot;.<a href="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/02_TV_Servers#Edit_Tuner_Settings" target="_blank">http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/02_TV_Servers#Edit_Tuner_Settings</a>That may improve things a little.No definitely not.The blasting happens as part of the IRSS TVE 3 blaster plugin. I have no control over what that does. All I know is that it blasts in parallel with the TV Server &quot;channel change&quot;. In technical terms: it happens asynchronously in a separate thread, not sequentially.</blockquote>

[QUOTE="mm1352000, post: 1031689, member: 82144"] Cool. :) Yeah, the PMT wait in the patch is "sub-optimal" for the HD-PVR 2. When I created the patch I didn't know that HD-PVR 2 has a different PMT PID compared with HD-PVR 1 and Colossus. So one of the things that is making it so slow is that TV Server is waiting for PMT (video/audio stream info), not finding it after those 3 seconds, and then having to do an "exhaustive search" to find the actual PMT (which may take another second or two). Maybe that doesn't make a lot of sense; in short it just means keep that PMT timeout as low as you can because every second you add is a second more in channel switching delay. Yes. There is maybe a second of delay in TV Server's timeshifting mechanism, and probably another second in the HD-PVR's drivers and encoding. One of the problems I see is this: That is way longer than what I ever remember seeing for the HD-PVR 1 or Colossus. The above is on first tune (when the HD-PVR is loaded for the first time). On subsequent tunes: Basically your HD-PVR 2 seems to be slow to start up. To mitigate this I suggest you try changing "when card enters idle state..." to "pause" and enable "allow this card to be preloaded". [url]http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/02_TV_Servers#Edit_Tuner_Settings[/url] That may improve things a little. No definitely not. The blasting happens as part of the IRSS TVE 3 blaster plugin. I have no control over what that does. All I know is that it blasts in parallel with the TV Server "channel change". In technical terms: it happens asynchronously in a separate thread, not sequentially. [/QUOTE]

Verification