Reply to thread

Message

<blockquote data-quote="doveman" data-source="post: 1013442" data-attributes="member: 67412">You've probably got the right approach mm <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />&nbsp;I'm probably more obsessed with this at the moment than I should be, because this is a system I'm building for my brother (note that my other thread was about a different system) and once I've sent it to him, it's going to be next to impossible to check things like latency over the Net using TeamViewer. In some ways, it's perhaps easier to check for and eliminate latency issues (in theory anyway) than to test every possible scenario to see if there's any audio/video glitches and if I've ensured there are no latency issues and my brother reports that he's experiencing glitches, at least I'll know it's not that and can look at settings/codecs, etc.&nbsp;I'm not sure at the moment whether LatencyMon is just showing phantom readings though. If not, it would seem to suggest that DPC Latency Checker is pretty useless as it's not showing any of the latency spikes that LatencyMon is, so anyone just using that would think there is no latency problem and any issues they're having must be due to something else. On the other hand, if LatencyMon is only meant to be used with nothing else running, as the author initially suggested, then it's not much use for establishing whether any programs/activity are triggering latency spikes and DPC Latency Checker is probably more useful if there's no such restrictions with it.</blockquote>

[QUOTE="doveman, post: 1013442, member: 67412"] You've probably got the right approach mm ;) I'm probably more obsessed with this at the moment than I should be, because this is a system I'm building for my brother (note that my other thread was about a different system) and once I've sent it to him, it's going to be next to impossible to check things like latency over the Net using TeamViewer. In some ways, it's perhaps easier to check for and eliminate latency issues (in theory anyway) than to test every possible scenario to see if there's any audio/video glitches and if I've ensured there are no latency issues and my brother reports that he's experiencing glitches, at least I'll know it's not that and can look at settings/codecs, etc. I'm not sure at the moment whether LatencyMon is just showing phantom readings though. If not, it would seem to suggest that DPC Latency Checker is pretty useless as it's not showing any of the latency spikes that LatencyMon is, so anyone just using that would think there is no latency problem and any issues they're having must be due to something else. On the other hand, if LatencyMon is only meant to be used with nothing else running, as the author initially suggested, then it's not much use for establishing whether any programs/activity are triggering latency spikes and DPC Latency Checker is probably more useful if there's no such restrictions with it. [/QUOTE]

Verification