Du verwendest einen veralteten Browser. Es ist möglich, dass diese oder andere Websites nicht korrekt angezeigt werden. Du solltest ein Upgrade durchführen oder einen alternativen Browser verwenden.
Heftige Tonaussetzer (Knacker) bei Musikproduktion trotz 16 gb Ram
wie im Titel gesagt habe ich starke Knacker und Tonaussetzer beim produzieren. Diese Knackser sind ein häufig bekanntes Problem und habe mir deshalb extra ein neues Notebook geholt mit 16 gb Ram. Ich kann mir nicht vorstellen dass es etwas mit meinem Arbeitsspeicher zu tun hat. Vielleicht kann mir ja jemand helfen ob es sich um ein versteckten Hintergrundprozess oder sonstiges handelt.
Hier ein Screenshot während diese Aussetzer auftreten:
Zudem habe ich unzählige Prozesse laufen und ich weiß überhaupt nicht wo die alle her kommen. Ich hoffe ich bin im richtigen Unterforum gelandet und mir kann jemand helfen. Ist echt frustieren zumahl ich mir das Notebook extra dafür gekauft habe um das zu vermeiden.
ok, das saffire ist bus-powered...
hast du verschiedene usb-anschlüsse probiert sofern vorhanden?
also auch bei akkubetrieb immer noch dieselben störgeräusche?
verschiedene geräte im gerätemanager zu deaktivieren, wie dpc latency vorschlägt, wäre vielleicht nicht falsch.
du hast wahrscheinlich den neuesten Treiber fürs saffire installiert. wenn nicht - direkt von focusrite online beziehen.
hast du monitorboxen am gerät angeschlossen?
wenn ja, sind die geräusche auch im kopfhörer?
...im grunde blöde frage, dpc latency zeigt ja, dass da intern was nicht stimmt...
...also vergiss die zwei ersten zeilen hier... der prozessor sollte entlastet werden denke ich...
dazu könntest du im gerätemanager einige geräte deaktivieren... wlan-adapter zb
oder deinen autostart aufräumen, nicht benötigte programme deinstallieren usw
habe schon alles deaktiviert aber das kann ja nicht die lösung sein der rechner sollte damit doch kein problem haben. dann muss das problem ja an der externen soundkarte liegen wenn ichs richtig verstanden habe?
Es ist schon ein besserer Virenscanner bei Windows 8 onboard, da braucht es diesen nicht mehr.
Ich nehme auch teilweise Musik auf, und deaktiviere meinen Virenscanner, bzw. versetze ihn in den Gamingmodus.
Wenn der nämlich während der Aufnahme anspringt, kommt es schnell zu Störgeräuschen!
Es kann auch durchaus an der externen Soundkarte liegen, gerade USB Soundkarten sollen recht empfindlich sein, da sie über den USB Port ja den Strom bekommen (logisch).
Es ist schon ein besserer Virenscanner bei Windows 8 onboard, da braucht es diesen nicht mehr.
Ich nehme auch teilweise Musik auf, und deaktiviere meinen Virenscanner, bzw. versetze ihn in den Gamingmodus.
Wenn der nämlich während der Aufnahme anspringt, kommt es schnell zu Störgeräuschen!
Es kann auch durchaus an der externen Soundkarte liegen, gerade USB Soundkarten sollen recht empfindlich sein, da sie über den USB Port ja den Strom bekommen (logisch).
Heutige PCs haben absolut NULL Probleme mehr, was Stromversorgung über den USB-Port angeht. Und bei der Stromversorgung ist es sch**** egal, ob da nen Virenscanner läuft oder nicht!
Diese Störgeräusche entstehen weil es zu Verzögerungen zwischen den einzelnen Prozessen kommt. Dadurch wird kurzzeitig der Audiotransfer unterbrochen. Diese fehlenden Daten führen zu Störgeräuschen.
Ich habe mein Antivir bereits installiert und es wimmelte nur so von malware auf meinem laptop. Ist also keine option für mich.
ABer wie gesagt selbst den Suchlauf im Hintergrund sollte das notebook doch ohne Probleme wegstecken - ich verstehs nicht
Ergänzung ()
Ich hab mal den Latency Mon laufen lassen mit folgendem Ergebnis - vielleicht wird jemand daraus schlau?
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system seems to have difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:01:27 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: MG
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: 20354, LENOVO, Lancer 5A5
CPU: GenuineIntel Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz
Logical processors: 4
Processor groups: 1
RAM: 16276 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2594,0 MHz
Measured CPU speed: 2900,0 MHz (approx.)
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): 1523,763206
Average measured interrupt to process latency (µs): 4,610997
Highest measured interrupt to DPC latency (µs): 1502,051554
Average measured interrupt to DPC latency (µs): 1,220896
_________________________________________________________________________________________________________
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): 706,351581
Driver with highest ISR routine execution time: USBPORT.SYS - USB 1.1 & 2.0-Porttreiber, Microsoft Corporation
Highest reported total ISR routine time (%): 0,403350
Driver with highest ISR total time: USBPORT.SYS - USB 1.1 & 2.0-Porttreiber, Microsoft Corporation
Total time spent in ISRs (%) 0,410408
ISR count (execution time <250 µs): 163905
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 39
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µ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): 1498,516962
Driver with highest DPC routine execution time: USBPORT.SYS - USB 1.1 & 2.0-Porttreiber, Microsoft Corporation
Highest reported total DPC routine time (%): 1,194040
Driver with highest DPC total execution time: USBPORT.SYS - USB 1.1 & 2.0-Porttreiber, Microsoft Corporation
Total time spent in DPCs (%) 1,978037
DPC count (execution time <250 µs): 627284
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 91
DPC count (execution time 1000-1999 µs): 6
DPC count (execution time 2000-3999 µ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: fl64.exe
Total number of hard pagefaults 820
Hard pagefault count of hardest hit process: 685
Highest hard pagefault resolution time (µs): 6578,501928
Total time spent in hard pagefaults (%): 0,285525
Number of processes hit: 4
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 5,662324
CPU 0 ISR highest execution time (µs): 706,351581
CPU 0 ISR total execution time (s): 0,678101
CPU 0 ISR count: 101636
CPU 0 DPC highest execution time (µs): 1473,484194
CPU 0 DPC total execution time (s): 4,082311
CPU 0 DPC count: 456580
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 2,862113
CPU 1 ISR highest execution time (µs): 364,449113
CPU 1 ISR total execution time (s): 0,471574
CPU 1 ISR count: 38149
CPU 1 DPC highest execution time (µs): 1498,516962
CPU 1 DPC total execution time (s): 1,731839
CPU 1 DPC count: 96984
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 1,169480
CPU 2 ISR highest execution time (µs): 366,154973
CPU 2 ISR total execution time (s): 0,063560
CPU 2 ISR count: 7477
CPU 2 DPC highest execution time (µs): 1090,772938
CPU 2 DPC total execution time (s): 0,377109
CPU 2 DPC count: 28194
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 1,507569
CPU 3 ISR highest execution time (µs): 349,981496
CPU 3 ISR total execution time (s): 0,215756
CPU 3 ISR count: 16682
CPU 3 DPC highest execution time (µs): 1085,971087
CPU 3 DPC total execution time (s): 0,696028
CPU 3 DPC count: 45623
_________________________________________________________________________________________________________
Ergänzung ()
Ich hab den W-Lan adapter jetzt ausgeschaltet - nochmal latency laufen lassen und diesmal habe ich wieder die selben probleme also audio dropouts aber latency sagt das alles ok ist.
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
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:13 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: MG
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: 20354, LENOVO, Lancer 5A5
CPU: GenuineIntel Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz
Logical processors: 4
Processor groups: 1
RAM: 16276 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2594,0 MHz
Measured CPU speed: 2904,0 MHz (approx.)
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): 310,674001
Average measured interrupt to process latency (µs): 3,929887
Highest measured interrupt to DPC latency (µs): 277,119630
Average measured interrupt to DPC latency (µs): 1,027428
_________________________________________________________________________________________________________
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): 140,933308
Driver with highest ISR routine execution time: USBPORT.SYS - USB 1.1 & 2.0-Porttreiber, Microsoft Corporation
Highest reported total ISR routine time (%): 0,344673
Driver with highest ISR total time: USBPORT.SYS - USB 1.1 & 2.0-Porttreiber, Microsoft Corporation
Total time spent in ISRs (%) 0,353906
ISR count (execution time <250 µs): 132164
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µ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): 224,888975
Driver with highest DPC routine execution time: USBPORT.SYS - USB 1.1 & 2.0-Porttreiber, Microsoft Corporation
Highest reported total DPC routine time (%): 1,121953
Driver with highest DPC total execution time: USBPORT.SYS - USB 1.1 & 2.0-Porttreiber, Microsoft Corporation
Total time spent in DPCs (%) 1,836461
DPC count (execution time <250 µs): 509763
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µ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: fl64.exe
Total number of hard pagefaults 200
Hard pagefault count of hardest hit process: 110
Highest hard pagefault resolution time (µs): 4272,729761
Total time spent in hard pagefaults (%): 0,058940
Number of processes hit: 3
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 5,012597
CPU 0 ISR highest execution time (µs): 137,973786
CPU 0 ISR total execution time (s): 0,600219
CPU 0 ISR count: 92534
CPU 0 DPC highest execution time (µs): 157,939476
CPU 0 DPC total execution time (s): 3,659726
CPU 0 DPC count: 398679
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 1,710158
CPU 1 ISR highest execution time (µs): 140,933308
CPU 1 ISR total execution time (s): 0,284654
CPU 1 ISR count: 24815
CPU 1 DPC highest execution time (µs): 224,888975
CPU 1 DPC total execution time (s): 1,053073
CPU 1 DPC count: 62571
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,786030
CPU 2 ISR highest execution time (µs): 43,079414
CPU 2 ISR total execution time (s): 0,039926
CPU 2 ISR count: 5042
CPU 2 DPC highest execution time (µs): 165,716268
CPU 2 DPC total execution time (s): 0,243710
CPU 2 DPC count: 20047
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,867817
CPU 3 ISR highest execution time (µs): 59,068234
CPU 3 ISR total execution time (s): 0,108832
CPU 3 ISR count: 9773
CPU 3 DPC highest execution time (µs): 170,665767
CPU 3 DPC total execution time (s): 0,407133
CPU 3 DPC count: 28466
_________________________________________________________________________________________________________
Für den Anschluss der USB-Soundkarte mal ein geschirmtes USB-Kabel verwenden. USB-Treiber aktuell?
Mein DVB-T-Stick hatte auch Probleme (Bildaussetzer bei der TV-Wiedergabe), bis ich ihn mit einem geschirmten USB-Kabel an den PC angeschlossen habe. Danach waren die Fehler verschwunden.
