Originally Posted by RobJ
The brevity of this post belies its importance, may have caused it to be overlooked. I would like to thank QueOnda for this suggestion, and emphasize the usefulness of the DPC Latency Checker in monitoring a strong source of stream disruption and dropouts. The web page has helpful info too, in understanding media dropouts.
The use of a number higher than 100% seems consistent with increased irritation and decreased objectivity. May I respectfully suggest that your overemphasis and phraseology may not be characterizing their position correctly? All they can go on is what the built-in info sensors and error detection has detected and logged or reported, from both their own software and the numerous sub-systems that are involved. Their reputation is very good, and from all reports are nearly as interested as you in resolving your issues. When a user reports an issue, but all systems are reporting nominal, there is nothing they can fix, without further research. Typically, the fastest way to a resolution is for both you and the support individuals to maintain objectivity, and work together as a team. Be open to ANY plausible idea, whether it agrees with your suspicions or not.
Just a technicality, but I wanted to suggest care in referring to SageTV as a monolithic entity. When I am eating with others and a dish containing apple components is offered, it is easiest for me to say "I am allergic to apples". But an apple contains thousands of compounds, most of which are quite common to other edible items, to which I am not allergic. So technically, if I wanted to take the time (and be annoying to others!), I should say "I experience symptoms consistent with a certain form of allergic response when I consume an unknown compound found within apples or associated with their processing." The advantage of this longer expression though, is that it does suggest more avenues of research, to isolate the true source of the issue. All to say that it helps to remember that SageTV is actually a huge system consisting of numerous sub-systems, many of which are written and maintained by the SageTV developers, but many of which are not (Java, many codecs, renderers, and drivers, etc). As an example (but probably not related to *your* dropouts), I have had numerous problems in the past with the Java garbage collector (on an old and slow computer), as well as with other background processes that disrupted smooth recording. That's why I do think that the suggested latency monitor may be useful, to isolate the source of your issues.
|
11-09-2010, 04:58 PM
Similar Threads
Linear Mode
