Reply to thread

Message: <blockquote data-quote="mm1352000" data-source="post: 1214462" data-attributes="member: 82144">Thanks for the update Andy_2639Nothing has changed with 1.16 PR. As explained in my previous reply, Windows chooses TV Server's I/O priority. The fact that Windows chooses "background" is not considered a bug/problem. In other words: don't expect TV Server's I/O priority to change.You've set the TV Server log level to "warning":[2017-02-26 12:51:26,739] [Log    ] [4        ] [INFO ] - Set loglevel to: WarningThat means we get almost nothing in the log files, and so it's hard to say anything about the error. I can only guess that the account you were trying to use doesn't have permission to write to c:\ProgramData\Team MediaPortal\MediaPortal TV Server....but why are you trying to use a different account in the first place? The default is recommended and shouldn't be changed unless you have good reason to do so.Are you basing this conclusion on the tuner's signal strength/quality readings?If yes, please be aware that tuner readings tend not to show temporal issues (short/intermittent glitches/jitter).Your "dropouts" are temporal issues so you shouldn't necessarily trust your tuner's signal readings.If the artefacts correlated with I/O, shouldn't we have expected almost continuous artefacts during your test?The system specifications in your forum profile say that you're using Windows 10. If that's the case these results should be disregarded. As it says on the DPC Latency Checker home/download page:If you want to check DPC latency on W8 or newer, you need to use another program such as <a href="http://www.resplendence.com/latencymon" target="_blank">LatencyMon</a>.Have you considered that resmon might be reporting incorrect details?If you insist that the system is to be used for multi-tasking and you're convinced the problem is I/O-related, maybe you need to seriously consider an additional/new HDD/SSD as previously suggested. That 5400 rpm HDD imposes real constraints. You have to be realistic about what you can achieve within those constraints.This is exactly why I said that I didn't think setting I/O priority would be a reliable solution. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink    ;)" loading="lazy" data-shortname=";)" />I can only repeat: if you're convinced the problem is I/O-related (I'm not yet) and you care about drop-outs in recordings, in my opinion your focus on I/O priority is misplaced.Note that RAM drive drivers can affect DPC latency.</blockquote>

Verification