Thread Focusrite Saffire Pro 40 audio dropout after few seconds
- 4 replies
- 2 participants
- 2,579 views
- 2 followers
kmaenpaa
5
New AFfiliate
Member 10 years ago
Topic Posted on 07/16/2014 at 09:29:21Focusrite Saffire Pro 40 audio dropout after few seconds
Hello,
I just got my Focusrite today in order to track some drums. The problem is, that using the ASIO driver, audio drops out after about 5 seconds.
I can sort of reset the driver by changing the sample rate in the mix app to 48Khz and then start playback again, to no avail.
I also have problems with my Presonus FS Mobile, mainly some stuttering - maybe my TI firewire chip is going bad? I've tried all drivers from TI to legacy, tried different versions of Focusrite drivers, etc. Nothing helps. I only get a moment of audio from my Genelec monitors.
Everything seems proper - sync is OK, lights are green.
Running Windows 7 on an Abit IP35 motherboard.
I just got my Focusrite today in order to track some drums. The problem is, that using the ASIO driver, audio drops out after about 5 seconds.
I can sort of reset the driver by changing the sample rate in the mix app to 48Khz and then start playback again, to no avail.
I also have problems with my Presonus FS Mobile, mainly some stuttering - maybe my TI firewire chip is going bad? I've tried all drivers from TI to legacy, tried different versions of Focusrite drivers, etc. Nothing helps. I only get a moment of audio from my Genelec monitors.
Everything seems proper - sync is OK, lights are green.
Running Windows 7 on an Abit IP35 motherboard.
kmaenpaa
5
New AFfiliate
Member 10 years ago
2 Posted on 07/16/2014 at 13:30:14
OHCI report :
Looking for OHCI 1394 Host Controllers...
1:
Vendor : (104C) Texas Instruments
Chipset: (8023) TSB43AB22A
Revision: 00
Max 1394 Speed Capability: S400
Support: Compatible, no known issues.
Done.
Looking for OHCI 1394 Host Controllers...
1:
Vendor : (104C) Texas Instruments
Chipset: (8023) TSB43AB22A
Revision: 00
Max 1394 Speed Capability: S400
Support: Compatible, no known issues.
Done.
kmaenpaa
5
New AFfiliate
Member 10 years ago
3 Posted on 07/16/2014 at 13:32:47
LatencyMon :
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. Also one or more ISR 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:04:43 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: MAINFRAME
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: . , http://www.abit.com.tw/, IP35 (Intel P35+ICH9R)
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz
Logical processors: 4
Processor groups: 1
RAM: 6142 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3000,0 MHz
Measured CPU speed: 1809,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): 7603,808697
Average measured interrupt to process latency (µs): 4,454490
Highest measured interrupt to DPC latency (µs): 7587,766186
Average measured interrupt to DPC latency (µs): 1,256055
_________________________________________________________________________________________________________
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): 2972,563333
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,606088
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in ISRs (%) 0,884194
ISR count (execution time <250 µs): 2767306
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 202
ISR count (execution time 1000-1999 µs): 78
ISR count (execution time 2000-3999 µs): 32
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): 9326,543333
Driver with highest DPC routine execution time: ndis.sys - NDIS 6.20 driver, Microsoft Corporation
Highest reported total DPC routine time (%): 2,131169
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in DPCs (%) 2,461352
DPC count (execution time <250 µs): 3306239
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 873
DPC count (execution time 1000-1999 µs): 36
DPC count (execution time 2000-3999 µs): 18
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: svchost.exe
Total number of hard pagefaults 2119
Hard pagefault count of hardest hit process: 943
Highest hard pagefault resolution time (µs): 989355,673333
Total time spent in hard pagefaults (%): 4,555217
Number of processes hit: 19
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 12,745822
CPU 0 ISR highest execution time (µs): 2972,563333
CPU 0 ISR total execution time (s): 3,304533
CPU 0 ISR count: 909019
CPU 0 DPC highest execution time (µs): 7502,70
CPU 0 DPC total execution time (s): 7,929524
CPU 0 DPC count: 1397218
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 10,363401
CPU 1 ISR highest execution time (µs): 2647,620
CPU 1 ISR total execution time (s): 2,110756
CPU 1 ISR count: 618859
CPU 1 DPC highest execution time (µs): 2768,850
CPU 1 DPC total execution time (s): 6,325913
CPU 1 DPC count: 630861
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 11,154621
CPU 2 ISR highest execution time (µs): 2773,043333
CPU 2 ISR total execution time (s): 2,421202
CPU 2 ISR count: 619601
CPU 2 DPC highest execution time (µs): 7291,846667
CPU 2 DPC total execution time (s): 6,991836
CPU 2 DPC count: 640131
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 10,503801
CPU 3 ISR highest execution time (µs): 2622,493333
CPU 3 ISR total execution time (s): 2,173713
CPU 3 ISR count: 620139
CPU 3 DPC highest execution time (µs): 9326,543333
CPU 3 DPC total execution time (s): 6,618385
CPU 3 DPC count: 638970
_________________________________________________________________________________________________________
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. Also one or more ISR 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:04:43 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: MAINFRAME
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: . , http://www.abit.com.tw/, IP35 (Intel P35+ICH9R)
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz
Logical processors: 4
Processor groups: 1
RAM: 6142 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3000,0 MHz
Measured CPU speed: 1809,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): 7603,808697
Average measured interrupt to process latency (µs): 4,454490
Highest measured interrupt to DPC latency (µs): 7587,766186
Average measured interrupt to DPC latency (µs): 1,256055
_________________________________________________________________________________________________________
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): 2972,563333
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,606088
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in ISRs (%) 0,884194
ISR count (execution time <250 µs): 2767306
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 202
ISR count (execution time 1000-1999 µs): 78
ISR count (execution time 2000-3999 µs): 32
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): 9326,543333
Driver with highest DPC routine execution time: ndis.sys - NDIS 6.20 driver, Microsoft Corporation
Highest reported total DPC routine time (%): 2,131169
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in DPCs (%) 2,461352
DPC count (execution time <250 µs): 3306239
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 873
DPC count (execution time 1000-1999 µs): 36
DPC count (execution time 2000-3999 µs): 18
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: svchost.exe
Total number of hard pagefaults 2119
Hard pagefault count of hardest hit process: 943
Highest hard pagefault resolution time (µs): 989355,673333
Total time spent in hard pagefaults (%): 4,555217
Number of processes hit: 19
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 12,745822
CPU 0 ISR highest execution time (µs): 2972,563333
CPU 0 ISR total execution time (s): 3,304533
CPU 0 ISR count: 909019
CPU 0 DPC highest execution time (µs): 7502,70
CPU 0 DPC total execution time (s): 7,929524
CPU 0 DPC count: 1397218
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 10,363401
CPU 1 ISR highest execution time (µs): 2647,620
CPU 1 ISR total execution time (s): 2,110756
CPU 1 ISR count: 618859
CPU 1 DPC highest execution time (µs): 2768,850
CPU 1 DPC total execution time (s): 6,325913
CPU 1 DPC count: 630861
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 11,154621
CPU 2 ISR highest execution time (µs): 2773,043333
CPU 2 ISR total execution time (s): 2,421202
CPU 2 ISR count: 619601
CPU 2 DPC highest execution time (µs): 7291,846667
CPU 2 DPC total execution time (s): 6,991836
CPU 2 DPC count: 640131
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 10,503801
CPU 3 ISR highest execution time (µs): 2622,493333
CPU 3 ISR total execution time (s): 2,173713
CPU 3 ISR count: 620139
CPU 3 DPC highest execution time (µs): 9326,543333
CPU 3 DPC total execution time (s): 6,618385
CPU 3 DPC count: 638970
_________________________________________________________________________________________________________
David_Focusrite
65
AFfable Poster
Member 10 years ago
4 Posted on 07/17/2014 at 09:10:54
Hi kmaenpaa,
Sorry to hear that you are having trouble with the audio dropping out on your Saffire Pro 40, maybe I can offer some assistance!
Can you try disabling the following in your device manager:
- All network adapters
- All other sound devices
- Bluetooth
- Any card reader
- Modem
- Any other unnecessary device you might have
Then restart your computer.
Also we recommend Optimizing your PC for audio. The steps to do this can be found here : https://us.focusrite.com/answerbase/optimising-your-pc-for-audio-on-windows-7
The driver you would need for your Saffire Pro 40 can be found here : http://d3se566zfvnmhf.cloudfront.net/sites/default/files/focusrite/downloads/20454/saffire-mixcontrol-3.4.exe
If the problem still persists after attempting these steps, I would recommend contacting a PC tech, or your PC manufacturer to help with your system hardware configurations.
If you should have any further issues pertaining to your Saffire Pro 40 please feel free to contact us directly! Phone support is available at (310) 322-5500, Monday - Friday, 8am - 6pm Pacific Time.
Sorry to hear that you are having trouble with the audio dropping out on your Saffire Pro 40, maybe I can offer some assistance!
Can you try disabling the following in your device manager:
- All network adapters
- All other sound devices
- Bluetooth
- Any card reader
- Modem
- Any other unnecessary device you might have
Then restart your computer.
Also we recommend Optimizing your PC for audio. The steps to do this can be found here : https://us.focusrite.com/answerbase/optimising-your-pc-for-audio-on-windows-7
The driver you would need for your Saffire Pro 40 can be found here : http://d3se566zfvnmhf.cloudfront.net/sites/default/files/focusrite/downloads/20454/saffire-mixcontrol-3.4.exe
If the problem still persists after attempting these steps, I would recommend contacting a PC tech, or your PC manufacturer to help with your system hardware configurations.
If you should have any further issues pertaining to your Saffire Pro 40 please feel free to contact us directly! Phone support is available at (310) 322-5500, Monday - Friday, 8am - 6pm Pacific Time.
kmaenpaa
5
New AFfiliate
Member 10 years ago
5 Posted on 07/21/2014 at 14:39:28
Hi all,
I ran DPC Latency checker and had spikes. I disabled everything and even without restarting the culprit is my TP Link WiFi PCI card. It completely blocks the Saffire Pro 40 from working properly.. a 15 euro part is messing with a 400 euro part. Very annoying. I'll have to try out USB WiFi tomorrow and see if I can get both sound and the Internet on this computer.
I ran DPC Latency checker and had spikes. I disabled everything and even without restarting the culprit is my TP Link WiFi PCI card. It completely blocks the Saffire Pro 40 from working properly.. a 15 euro part is messing with a 400 euro part. Very annoying. I'll have to try out USB WiFi tomorrow and see if I can get both sound and the Internet on this computer.
- < Thread list
- Rules