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="Woody[UK]" data-source="post: 1123356" data-attributes="member: 151367"><p>Hi,</p><p>I did check latency last week with Thesycon DPC Latency Checker. I found that Intel LAN driver v19.5 caused high latency spikes every few seconds, dropping back to driver v19.1 fixed this.</p><p></p><p>Temperatures for the CPU, Motherboard, HDD and SSD are all around 20 'C at idle. The CPU goes up to 50 'C under load with OCCT power supply test (70 watts at the wall).</p><p></p><p>Having previously discovered disabling 'Cool and Quiet' on the AMD PC improved recording with Argus TV. I disabled EIST (speedstep) and fixed the CPU multiplier to x16 on the Intel PC, this did not help.</p><p></p><p>I also…</p><p>Checked the aerial and cable connections.</p><p>Check digitaluk.co.uk for engineering work.</p><p>Checked signal strength with a digital TV signal meter.</p><p>Used the USB tuner in powered usb hub to ensure correct volts.</p><p>Updated the Intel/Asus P8Z77-I BIOS to the newest v1201.</p><p>Reset BIOS to defaults.</p><p>Toggled HPET on/off in BIOS.</p><p>Tested with Thesycon DPC Latency Checker.</p><p>Disabled Wifi in BIOS.</p><p>Disabled Bluetooth in BIOS.</p><p>Disabled Asmedia USB3 controller in BIOS.</p><p>Disabled Intel xHCi mode (usb3 mode) in BIOS.</p><p>Disabled Intel LAN controller in BIOS.</p><p>Disabled Spread Spectrum in BIOS.</p><p>Uninstalled Asus Ai Suite 2 with cleaner.</p><p>Reformatted the HDD.</p><p>Reinstalled Windows 7 sp0.</p><p>Installed Intel RST driver only (not the driver install.exe).</p><p>Installed newest Intel Management Engine driver v10.0.30.1054.</p><p>Flashed IME firmware to v8.1.52.1496.</p><p>Flashed BIOS v1203 updated with UBU v1.9.</p><p></p><p>Installing the older Intel LAN v19.1 driver helped as previous to this even TV Scheduler Pro failed to record on the Intel PC.</p><p></p><p>As I own two PCTV 290e USB tuners and now have two PCs I am able to run more tests. Using a Labgear FBS402/S 2 way splitter I connect both my AMD and Intel PCs to the same aerial. All of the tests were performed using the Intel PC, which was powered off between each test. I used PCTV 290e driver v5.2013.1206.0 from the Empia folder in the PCTVSystems TVCenter download (same driver as the PCTV 292e). All of the recordings are of the same channel on the same mux (ITV2 SD). The AMD PC was set to continuously record the same channel on the same mux (ITV2 SD). Each recording was scanned for errors using 'MPEG-2 Transport Stream packet analyser'. Power consumption was measured at the wall with a Belkin Conserve Insight Energy Use Monitor. System monitoring was performed using 'xperf' from the 'Windows Performance Toolkit' part of the 'Windows ADK for Windows 8.1 Update'.</p><p>[SPOILER="xperf usage notes"]</p><p></p><p>======================================================</p><p></p><p>set trace_name=FileName</p><p></p><p>======================================================</p><p></p><p>start log DiagEasy (PROC_THREAD +LOADER +DISK_IO+ HARD_FAULTS+ DPC+INTERRUPT +CSWITCH +PERF_COUNTER)</p><p>------------------</p><p>Xperf –on DiagEasy</p><p></p><p>======================================================</p><p></p><p>start log latency (PROC_THREAD +LOADER +DISK_IO +HARD_FAULTS +DPC +INTERRUPT +CSWITCH +PROFILE)</p><p>---------------------</p><p>xperf -on latency -stackwalk profile</p><p></p><p>======================================================</p><p></p><p>start log custom</p><p>---------------------</p><p>xperf -on PROC_THREAD+LOADER+DPC+INTERRUPT+PROFILE+DRIVERS -stackwalk Profile -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 1024 -FileMode Circular</p><p></p><p>======================================================</p><p></p><p>start log custom+hdd</p><p>---------------------------</p><p>xperf -on PROC_THREAD+LOADER+DPC+INTERRUPT+PROFILE+DRIVERS+DISK_IO+HARD_FAULTS -stackwalk Profile -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 1024 -FileMode Circular</p><p></p><p>======================================================</p><p></p><p>stop and save to file</p><p>---------------------------</p><p>xperf -stop -d R:\temp\%trace_name%.etl</p><p>======================================================</p><p></p><p>filter to txt file</p><p>------------------</p><p>xperf -I R:\temp\%trace_name%.etl -a dpcisr > R:\temp\%trace_name%_dpc.txt</p><p></p><p>======================================================</p><p></p><p>list driver versions</p><p>------------------------</p><p>xperf -I R:\temp\%trace_name%.etl -a fileversion > R:\temp\%trace_name%_driver_versions.txt</p><p></p><p>======================================================</p><p></p><p>xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7)</p><p>The error message is misleading and has nothing to do with a file that already exists. It happens when a different tool already started a NT Kernel Logger to capture ETW data</p><p></p><p>======================================================</p><p></p><p>Latency Graphs</p><p>---------------------</p><p>DPC/ISR - DPC Duration by Module, Function</p><p>DPC/ISR - ISR Duration by Module, Function</p><p>DPC/ISR - DPC/ISR Duration by Module, Function</p><p></p><p>[/SPOILER]</p><p></p><p>Test Results.</p><p>[ATTACH=full]161028[/ATTACH]</p><p></p><p>None of the recordings created with TV Scheduler Pro on the AMD PC had errors.</p><p></p><p>The Intel/Asus P8Z77-I BIOS has two sub-menus named 'CPU Power Management'. Accessed in different places, both contain SpeedStep but one menu has Duration Power Limits and the other has C state settings. Finding the C State settings helped a lot, as disabling 'CPU C6 Report' made a huge difference to the amount of errors produced by TV Server.</p><p></p><p>When comparing 'TV Scheduler Pro C6 on' and 'TV Server C6 on' xperf traces, I cannot see anything obvious. In 'DPC/ISR Duration by Module', USBPORT.SYS and ndis.sys Duration Max are under 0.2ms and all Module Duration Ave are under 0.025ms.</p><p></p><p>With the amount of errors TV Server (and Argus TV) vs. TV Scheduler Pro I would have thought the cause would be obvious, or maybe it is.. I'm just not seeing it… does this pattern help?</p><p></p><p>Thank you</p></blockquote><p></p>
[QUOTE="Woody[UK], post: 1123356, member: 151367"] Hi, I did check latency last week with Thesycon DPC Latency Checker. I found that Intel LAN driver v19.5 caused high latency spikes every few seconds, dropping back to driver v19.1 fixed this. Temperatures for the CPU, Motherboard, HDD and SSD are all around 20 'C at idle. The CPU goes up to 50 'C under load with OCCT power supply test (70 watts at the wall). Having previously discovered disabling 'Cool and Quiet' on the AMD PC improved recording with Argus TV. I disabled EIST (speedstep) and fixed the CPU multiplier to x16 on the Intel PC, this did not help. I also… Checked the aerial and cable connections. Check digitaluk.co.uk for engineering work. Checked signal strength with a digital TV signal meter. Used the USB tuner in powered usb hub to ensure correct volts. Updated the Intel/Asus P8Z77-I BIOS to the newest v1201. Reset BIOS to defaults. Toggled HPET on/off in BIOS. Tested with Thesycon DPC Latency Checker. Disabled Wifi in BIOS. Disabled Bluetooth in BIOS. Disabled Asmedia USB3 controller in BIOS. Disabled Intel xHCi mode (usb3 mode) in BIOS. Disabled Intel LAN controller in BIOS. Disabled Spread Spectrum in BIOS. Uninstalled Asus Ai Suite 2 with cleaner. Reformatted the HDD. Reinstalled Windows 7 sp0. Installed Intel RST driver only (not the driver install.exe). Installed newest Intel Management Engine driver v10.0.30.1054. Flashed IME firmware to v8.1.52.1496. Flashed BIOS v1203 updated with UBU v1.9. Installing the older Intel LAN v19.1 driver helped as previous to this even TV Scheduler Pro failed to record on the Intel PC. As I own two PCTV 290e USB tuners and now have two PCs I am able to run more tests. Using a Labgear FBS402/S 2 way splitter I connect both my AMD and Intel PCs to the same aerial. All of the tests were performed using the Intel PC, which was powered off between each test. I used PCTV 290e driver v5.2013.1206.0 from the Empia folder in the PCTVSystems TVCenter download (same driver as the PCTV 292e). All of the recordings are of the same channel on the same mux (ITV2 SD). The AMD PC was set to continuously record the same channel on the same mux (ITV2 SD). Each recording was scanned for errors using 'MPEG-2 Transport Stream packet analyser'. Power consumption was measured at the wall with a Belkin Conserve Insight Energy Use Monitor. System monitoring was performed using 'xperf' from the 'Windows Performance Toolkit' part of the 'Windows ADK for Windows 8.1 Update'. [SPOILER="xperf usage notes"] ====================================================== set trace_name=FileName ====================================================== start log DiagEasy (PROC_THREAD +LOADER +DISK_IO+ HARD_FAULTS+ DPC+INTERRUPT +CSWITCH +PERF_COUNTER) ------------------ Xperf –on DiagEasy ====================================================== start log latency (PROC_THREAD +LOADER +DISK_IO +HARD_FAULTS +DPC +INTERRUPT +CSWITCH +PROFILE) --------------------- xperf -on latency -stackwalk profile ====================================================== start log custom --------------------- xperf -on PROC_THREAD+LOADER+DPC+INTERRUPT+PROFILE+DRIVERS -stackwalk Profile -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 1024 -FileMode Circular ====================================================== start log custom+hdd --------------------------- xperf -on PROC_THREAD+LOADER+DPC+INTERRUPT+PROFILE+DRIVERS+DISK_IO+HARD_FAULTS -stackwalk Profile -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 1024 -FileMode Circular ====================================================== stop and save to file --------------------------- xperf -stop -d R:\temp\%trace_name%.etl ====================================================== filter to txt file ------------------ xperf -I R:\temp\%trace_name%.etl -a dpcisr > R:\temp\%trace_name%_dpc.txt ====================================================== list driver versions ------------------------ xperf -I R:\temp\%trace_name%.etl -a fileversion > R:\temp\%trace_name%_driver_versions.txt ====================================================== xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7) The error message is misleading and has nothing to do with a file that already exists. It happens when a different tool already started a NT Kernel Logger to capture ETW data ====================================================== Latency Graphs --------------------- DPC/ISR - DPC Duration by Module, Function DPC/ISR - ISR Duration by Module, Function DPC/ISR - DPC/ISR Duration by Module, Function [/SPOILER] Test Results. [ATTACH=full]161028[/ATTACH] None of the recordings created with TV Scheduler Pro on the AMD PC had errors. The Intel/Asus P8Z77-I BIOS has two sub-menus named 'CPU Power Management'. Accessed in different places, both contain SpeedStep but one menu has Duration Power Limits and the other has C state settings. Finding the C State settings helped a lot, as disabling 'CPU C6 Report' made a huge difference to the amount of errors produced by TV Server. When comparing 'TV Scheduler Pro C6 on' and 'TV Server C6 on' xperf traces, I cannot see anything obvious. In 'DPC/ISR Duration by Module', USBPORT.SYS and ndis.sys Duration Max are under 0.2ms and all Module Duration Ave are under 0.025ms. With the amount of errors TV Server (and Argus TV) vs. TV Scheduler Pro I would have thought the cause would be obvious, or maybe it is.. I'm just not seeing it… does this pattern help? Thank you [/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
