home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Quality Assurance
Bugreports
Archive
Micro stutter on one particular channel during LIVE TV (Solved because: Probably hardware related)
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1168780" data-attributes="member: 82144"><p>Okay, let's go point by point... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p></p><p>Logs confirm - thanks.</p><p></p><p></p><p>This change was <strong>not </strong>successful. The log is saying:</p><p>[2016-01-02 13:26:46,984] [11dc02e0] [1aa4] - --- Buffering delay = 0 ms (default value, allowed range is 0 - 10000)</p><p></p><p>...which means that the default value is being used.</p><p>The problem is that you have specified the value as hexidecimal (base 16). As you can see in your screenshot, 0x5000 means 20480. 20480 is outside the allowed range (0 - 10000).</p><p>Please try this one again. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p></p><p>Logs confirm - thanks.</p><p></p><p></p><p>Sorry, that won't make any difference for this problem.</p><p></p><p></p><p>You could use Windows task manager -> resource monitor if you want to know which processes are using the HDD most.</p><p>It might also be a good idea to check DPC latency with <a href="http://www.resplendence.com/latencymon" target="_blank">LatencyMon</a>.</p><p></p><p>[edit: ...but to be clear, I think for now it's best to stay with the SSD if it's the only option that guarantees zero TsWriter continuity errors. Once the problem is solved then you could consider moving the TS folder to another location.]</p><p></p><p></p><p>In short: no.</p><p>In these logs I don't see any issues in the TsWriter log.</p><p>The TsReader log still contains:</p><ul> <li data-xf-list-type="ul">..."PES 0-0-1 fail" messages, but for now I'm not too fussed about them because they're only at the start of the timeshifting (therefore they could be normal).</li> <li data-xf-list-type="ul">...one "audio to render late" message, which should hopefully be solved when you increase the buffer size properly.</li> </ul><p>So for now the most important thing to try is the TsReader buffer setting.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1168780, member: 82144"] Okay, let's go point by point... :) Logs confirm - thanks. This change was [B]not [/B]successful. The log is saying: [2016-01-02 13:26:46,984] [11dc02e0] [1aa4] - --- Buffering delay = 0 ms (default value, allowed range is 0 - 10000) ...which means that the default value is being used. The problem is that you have specified the value as hexidecimal (base 16). As you can see in your screenshot, 0x5000 means 20480. 20480 is outside the allowed range (0 - 10000). Please try this one again. :) Logs confirm - thanks. Sorry, that won't make any difference for this problem. You could use Windows task manager -> resource monitor if you want to know which processes are using the HDD most. It might also be a good idea to check DPC latency with [URL='http://www.resplendence.com/latencymon']LatencyMon[/URL]. [edit: ...but to be clear, I think for now it's best to stay with the SSD if it's the only option that guarantees zero TsWriter continuity errors. Once the problem is solved then you could consider moving the TS folder to another location.] In short: no. In these logs I don't see any issues in the TsWriter log. The TsReader log still contains: [LIST] [*]..."PES 0-0-1 fail" messages, but for now I'm not too fussed about them because they're only at the start of the timeshifting (therefore they could be normal). [*]...one "audio to render late" message, which should hopefully be solved when you increase the buffer size properly. [/LIST] So for now the most important thing to try is the TsReader buffer setting. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Quality Assurance
Bugreports
Archive
Micro stutter on one particular channel during LIVE TV (Solved because: Probably hardware related)
Contact us
RSS
Top
Bottom