Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 933537" data-attributes="member: 82144">@<a href="https://forum.team-mediaportal.com/members/ianc.63303/" target="_blank">ianc</a>To me it looks like your problem is HDD or CPU speed/stress. Everything is just generally sluggish without good cause. Check for real-time scanners and HDD free space.&nbsp;Generally speaking, aside from code efficiency and overall system capability these are the things that determine zap time:<ol>
<li data-xf-list-type="ol">Tuner driver.</li>
<li data-xf-list-type="ol">CAM/decryption solution.</li>
<li data-xf-list-type="ol">Server CPU load and HDD speed, load, free space and fragmentation.</li>
<li data-xf-list-type="ol">Network configuration - firewall, IPv6, wireless/wired, DNS.</li>
<li data-xf-list-type="ol">Codecs, GPU and HDD on the client side.</li>
<li data-xf-list-type="ol">Zap delay setting.</li>
</ol>You can monitor (1) by checking the tv.log. In particular, how long does it take to apply the tune request:&nbsp;...and how long does it take to start the graph:&nbsp;For (2), check how long it takes before audio/video is seen:&nbsp;For (3), look at overall &quot;sluggishness&quot; of the server. If the tuning process doesn't have any unusual delays but everything seems generally slower then this is almost a certain sign of real-time scanning causing problems for the HDD and/or CPU.&nbsp;For (4), attempt to correlate the MediaPortal.log and tv.log and look for reasonably significant delays that don't have any good justification. This takes a little familiarity with the code and/or tuning process.&nbsp;(5) is quite subjective. You're basically looking at how long it takes between when the light on the TV button [in the MP UI] turns on and when you start seeing video and hearing audio.&nbsp;(6) is a setting. If you find working with the remote slow but selecting a channel through the mini-guide fast then the zap delay is to blame.&nbsp;Of course there are always exceptions.&nbsp;mm</blockquote>

[QUOTE="mm1352000, post: 933537, member: 82144"] @[URL='https://forum.team-mediaportal.com/members/ianc.63303/']ianc[/URL] To me it looks like your problem is HDD or CPU speed/stress. Everything is just generally sluggish without good cause. Check for real-time scanners and HDD free space. Generally speaking, aside from code efficiency and overall system capability these are the things that determine zap time: [LIST=1] [*]Tuner driver. [*]CAM/decryption solution. [*]Server CPU load and HDD speed, load, free space and fragmentation. [*]Network configuration - firewall, IPv6, wireless/wired, DNS. [*]Codecs, GPU and HDD on the client side. [*]Zap delay setting. [/LIST] You can monitor (1) by checking the tv.log. In particular, how long does it take to apply the tune request: ...and how long does it take to start the graph: For (2), check how long it takes before audio/video is seen: For (3), look at overall "sluggishness" of the server. If the tuning process doesn't have any unusual delays but everything seems generally slower then this is almost a certain sign of real-time scanning causing problems for the HDD and/or CPU. For (4), attempt to correlate the MediaPortal.log and tv.log and look for reasonably significant delays that don't have any good justification. This takes a little familiarity with the code and/or tuning process. (5) is quite subjective. You're basically looking at how long it takes between when the light on the TV button [in the MP UI] turns on and when you start seeing video and hearing audio. (6) is a setting. If you find working with the remote slow but selecting a channel through the mini-guide fast then the zap delay is to blame. Of course there are always exceptions. mm [/QUOTE]

Verification