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
Support
Installation, configuration support
Poor quality recordings, PCTV 290e DVB-T/DVB-T2.
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: 1123370" data-attributes="member: 82144"><p>Wow, that's some serious analysis... and honestly, a fair amount of it goes over my head. I haven't updated my knowledge of BIOS settings, CPU power state etc. since I assembled my current PC - which is a first gen Intel Core 2 + 975X chipset - and I've never used Xperf either. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p></p><p>Some questions:</p><ol> <li data-xf-list-type="ol">When you test with TV Server, are you simply recording... or also timeshifting? I wasn't 100% sure given the content of the "rec to" column. Obviously it wouldn't be a fair comparison if you were only recording with TVS Pro, and timeshifting + recording with TV Server. So, I guess you're only recording... but I'd like to be certain.</li> <li data-xf-list-type="ol">When you tested the signal strength:<ol> <li data-xf-list-type="ol">What was the reading?</li> <li data-xf-list-type="ol">Did you have the powered splitter connected?</li> </ol></li> <li data-xf-list-type="ol">During all this testing, were you able to observe temporal patterns? I mean, did you have TV Server manual control open to check the discontinuity counter... and check whether that correlated with any of the other metrics you were monitoring?</li> </ol><p></p><p></p><p>The cause is certainly not obvious to me.</p><p></p><p>The Xperf data is very detailed, but from my perspective it isn't that helpful. The key thing it doesn't show is correlation with continuity errors. When you're looking at an intermittent temporal (time-based) problem like continuity errors, it's critical to have correlation between the errors and the other metrics you're monitoring. That way you could say (for example): "ahhh, the errors are correlated with high power use..." (or whatever).</p><p></p><p>Intellectually I know that USB device interaction with the CPU can be troublesome. For tuners this <em>should </em>be user-land (software) independent. In other words, as long as the same CPU settings, USB chipset driver and tuner driver are used, the performance of the CPU+USB+tuner subsystem should be roughly the same in TVS Pro and TV Server. In saying this I'm assuming that TVS Pro isn't fiddling with eMPIA or PCTV proprietary settings... because TV Server doesn't have any code targeted at eMPIA or PCTV tuners.</p><p></p><p>The storage subsystem is a different story. File management (write chunk size, sync/async etc.) could make a difference... but I have no idea how TVS operates. Never used it.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1123370, member: 82144"] Wow, that's some serious analysis... and honestly, a fair amount of it goes over my head. I haven't updated my knowledge of BIOS settings, CPU power state etc. since I assembled my current PC - which is a first gen Intel Core 2 + 975X chipset - and I've never used Xperf either. ;) Some questions: [LIST=1] [*]When you test with TV Server, are you simply recording... or also timeshifting? I wasn't 100% sure given the content of the "rec to" column. Obviously it wouldn't be a fair comparison if you were only recording with TVS Pro, and timeshifting + recording with TV Server. So, I guess you're only recording... but I'd like to be certain. [*]When you tested the signal strength: [LIST=1] [*]What was the reading? [*]Did you have the powered splitter connected? [/LIST] [*]During all this testing, were you able to observe temporal patterns? I mean, did you have TV Server manual control open to check the discontinuity counter... and check whether that correlated with any of the other metrics you were monitoring? [/LIST] The cause is certainly not obvious to me. The Xperf data is very detailed, but from my perspective it isn't that helpful. The key thing it doesn't show is correlation with continuity errors. When you're looking at an intermittent temporal (time-based) problem like continuity errors, it's critical to have correlation between the errors and the other metrics you're monitoring. That way you could say (for example): "ahhh, the errors are correlated with high power use..." (or whatever). Intellectually I know that USB device interaction with the CPU can be troublesome. For tuners this [I]should [/I]be user-land (software) independent. In other words, as long as the same CPU settings, USB chipset driver and tuner driver are used, the performance of the CPU+USB+tuner subsystem should be roughly the same in TVS Pro and TV Server. In saying this I'm assuming that TVS Pro isn't fiddling with eMPIA or PCTV proprietary settings... because TV Server doesn't have any code targeted at eMPIA or PCTV tuners. The storage subsystem is a different story. File management (write chunk size, sync/async etc.) could make a difference... but I have no idea how TVS operates. Never used it. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Installation, configuration support
Poor quality recordings, PCTV 290e DVB-T/DVB-T2.
Contact us
RSS
Top
Bottom