diese soundeinstellungen sind ja derart verteilt, da ist es schwer durchzublicken. als ich ausdrücklich den monitor in den soundsettings aktiviert hatte, konnte ich dort via kopfhörer oder speaker ton bekommen. das macht aber keinen sinn, denn sobald ich dann im pc vorne kopfhörer einstecke, bleibt youtube für 10 sekunden stehen.
ich versuche nun
diese empfehlungen umzusetzen. im taskmanager die priority für fxsound hochzusetzen geht nicht, der zugriff wird verweigert, warum auch immer.
das sagt latencymon - wie interpretiert ihr das?
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:01:39 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: PC1
OS version: Windows 11, 10.0, version 2009, build: 26100 (x64)
Hardware: Z690 PG Riptide, ASRock
BIOS: 20.02
CPU: GenuineIntel 13th Gen Intel(R) Core(TM) i5-13400
Logical processors: 16
Processor groups: 1
Processor group size: 16
RAM: 32522 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 250 MHz
Reported CPU speed (registry): 2496 MHz
Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.
_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.
Highest measured interrupt to process latency (µs): 511,70
Average measured interrupt to process latency (µs): 14,586728
Highest measured interrupt to DPC latency (µs): 488,0
Average measured interrupt to DPC latency (µs): 4,074197
_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.
Highest ISR routine execution time (µs): 178,014423
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0,000777
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,001116
ISR count (execution time <250 µs): 2065
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0
_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.
Highest DPC routine execution time (µs): 690,418269
Driver with highest DPC routine execution time: netbt.sys - MBT Transport driver, Microsoft Corporation
Highest reported total DPC routine time (%): 0,005867
Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.
Total time spent in DPCs (%) 0,026077
DPC count (execution time <250 µs): 78555
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 17
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0
_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.
NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.
Process with highest pagefault count: msmpeng.exe
Total number of hard pagefaults 175
Hard pagefault count of hardest hit process: 136
Number of processes hit: 5
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 5,787871
CPU 0 ISR highest execution time (µs): 178,014423
CPU 0 ISR total execution time (s): 0,017310
CPU 0 ISR count: 2017
CPU 0 DPC highest execution time (µs): 278,146234
CPU 0 DPC total execution time (s): 0,240043
CPU 0 DPC count: 34033
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 4,629057
CPU 1 ISR highest execution time (µs): 0,0
CPU 1 ISR total execution time (s): 0,0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 0,0
CPU 1 DPC total execution time (s): 0,0
CPU 1 DPC count: 0
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 4,698058
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 292,005208
CPU 2 DPC total execution time (s): 0,044107
CPU 2 DPC count: 23915
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 4,658289
CPU 3 ISR highest execution time (µs): 26,891026
CPU 3 ISR total execution time (s): 0,000193
CPU 3 ISR count: 14
CPU 3 DPC highest execution time (µs): 156,149038
CPU 3 DPC total execution time (s): 0,001899
CPU 3 DPC count: 111
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 3,410285
CPU 4 ISR highest execution time (µs): 0,0
CPU 4 ISR total execution time (s): 0,0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 690,418269
CPU 4 DPC total execution time (s): 0,052526
CPU 4 DPC count: 5158
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 3,977862
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 137,343750
CPU 5 DPC total execution time (s): 0,000826
CPU 5 DPC count: 104
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 4,296391
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 152,712340
CPU 6 DPC total execution time (s): 0,010943
CPU 6 DPC count: 2506
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 4,356753
CPU 7 ISR highest execution time (µs): 30,862580
CPU 7 ISR total execution time (s): 0,000260
CPU 7 ISR count: 14
CPU 7 DPC highest execution time (µs): 278,844551
CPU 7 DPC total execution time (s): 0,018431
CPU 7 DPC count: 1478
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 3,944912
CPU 8 ISR highest execution time (µs): 0,0
CPU 8 ISR total execution time (s): 0,0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 215,93750
CPU 8 DPC total execution time (s): 0,010122
CPU 8 DPC count: 1181
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 3,891096
CPU 9 ISR highest execution time (µs): 4,124199
CPU 9 ISR total execution time (s): 0,000030
CPU 9 ISR count: 20
CPU 9 DPC highest execution time (µs): 226,909054
CPU 9 DPC total execution time (s): 0,007627
CPU 9 DPC count: 3703
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 4,592227
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 216,975561
CPU 10 DPC total execution time (s): 0,014571
CPU 10 DPC count: 4359
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 4,517497
CPU 11 ISR highest execution time (µs): 0,0
CPU 11 ISR total execution time (s): 0,0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 189,405849
CPU 11 DPC total execution time (s): 0,000954
CPU 11 DPC count: 412
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 1,889411
CPU 12 ISR highest execution time (µs): 0,0
CPU 12 ISR total execution time (s): 0,0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 203,326122
CPU 12 DPC total execution time (s): 0,002581
CPU 12 DPC count: 440
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 1,562122
CPU 13 ISR highest execution time (µs): 0,0
CPU 13 ISR total execution time (s): 0,0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 143,173478
CPU 13 DPC total execution time (s): 0,003923
CPU 13 DPC count: 319
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 1,476892
CPU 14 ISR highest execution time (µs): 0,0
CPU 14 ISR total execution time (s): 0,0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 177,277244
CPU 14 DPC total execution time (s): 0,003206
CPU 14 DPC count: 367
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 1,599284
CPU 15 ISR highest execution time (µs): 0,0
CPU 15 ISR total execution time (s): 0,0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 188,739984
CPU 15 DPC total execution time (s): 0,003908
CPU 15 DPC count: 486
_________________________________________________________________________________________________________
ich versuche auch die erwähnte realtek audio console zu starten. das endet aber so.
und zur info, im gerätemanager sieht es so aus: