Home › Forums › Breakaway Professional Products – [discontinued] › Dropouts, crackles & pops only audible whilst BBP running
- This topic has 2 replies, 2 voices, and was last updated 9 years, 6 months ago by producerlawson.
-
AuthorPosts
-
May 9, 2015 at 2:02 pm #2942producerlawsonMember
So I really like Breakaway Broadcast.. however I was missing that clunk/impact feeling that I was trying to emulate, anyway last night I came across the DSP's that Leif made and it's sealed the deal (only took me a couple of years to realise those plugins were there).
So I downloaded the demo again to trial it out on my new server. I setup numerous net stations as a kid and now that I have been working in the industry with a better vat of experience, I felt ready to make a much more superior station. However after around 12 hours of running it I hit the crackling, pops and huge dropouts (up to 10 seconds sometimes).
I understand there's already a thread about how some people have managed to deal with them, however having tried them all with no prevail I'm slumped again. All I have open is RadioDJ, Oddcast and Breakaway – I have been through driver settings, making sure my power management is at the highest possible and I'm still getting a bad sound. Worryingly virtual audio cables gives off a much better performance in-comparison to the pipelines included.. so much so that the included pipelines make the music inaudible.
I took it up on myself to investigate this much deeper and ran LatencyMon – here are the results (the visual version look horrifying).
quote :_________________________________________________________________________________________________________
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 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:23:45 (h:mm:ss) on all processors._________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: WIN-B223U69G8OD
OS version: Windows Server 2008 R2 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: ASUSTeK COMPUTER INC., P8H77-M PRO
CPU: GenuineIntel Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
Logical processors: 8
Processor groups: 1
RAM: 16069 MB total_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3400.0 MHz
Measured CPU speed: 2354.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): 2346.445742
Average measured interrupt to process latency (µs): 3.188614Highest measured interrupt to DPC latency (µs): 61.439473
Average measured interrupt to DPC latency (µs): 0.774268_________________________________________________________________________________________________________
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): 91.614412
Driver with highest ISR routine execution time: ataport.SYS – ATAPI Driver Extension, Microsoft CorporationHighest reported total ISR routine time (%): 0.014250
Driver with highest ISR total time: hal.dll – Hardware Abstraction Layer DLL, Microsoft CorporationTotal time spent in ISRs (%) 0.016709
ISR count (execution time <250 µs): 1450203
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): 201.394706
Driver with highest DPC routine execution time: NDIS.SYS – NDIS 6.20 driver, Microsoft CorporationHighest reported total DPC routine time (%): 0.054330
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.141256
DPC count (execution time <250 µs): 9875211
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: breakawaybroadcast.exe
Total number of hard pagefaults 1912
Hard pagefault count of hardest hit process: 476
Highest hard pagefault resolution time (µs): 165416.042059
Total time spent in hard pagefaults (%): 0.055389
Number of processes hit: 18_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 27.467930
CPU 0 ISR highest execution time (µs): 91.614412
CPU 0 ISR total execution time (s): 1.905390
CPU 0 ISR count: 1450203
CPU 0 DPC highest execution time (µs): 164.412941
CPU 0 DPC total execution time (s): 9.895359
CPU 0 DPC count: 8364367
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 42.472024
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): 188.270294
CPU 1 DPC total execution time (s): 0.090592
CPU 1 DPC count: 29871
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 37.100041
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): 201.394706
CPU 2 DPC total execution time (s): 0.565654
CPU 2 DPC count: 118502
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 36.975090
CPU 3 ISR highest execution time (µs): 0.0
CPU 3 ISR total execution time (s): 0.0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 115.380
CPU 3 DPC total execution time (s): 2.018437
CPU 3 DPC count: 746540
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 34.655957
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): 149.584118
CPU 4 DPC total execution time (s): 1.610242
CPU 4 DPC count: 180848
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 31.903159
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): 184.412941
CPU 5 DPC total execution time (s): 0.592526
CPU 5 DPC count: 216717
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 27.110517
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): 189.078235
CPU 6 DPC total execution time (s): 0.807045
CPU 6 DPC count: 77007
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 23.478180
CPU 7 ISR highest execution time (µs): 0.0
CPU 7 ISR total execution time (s): 0.0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 89.113824
CPU 7 DPC total execution time (s): 0.527826
CPU 7 DPC count: 141359
_________________________________________________________________________________________________________The server is hosted by Hetzner in Germany, so I have no real access to it unfortunately. I have ran Stereo Tool with the same setup on another machine (exact same spec) and it was perfect, no dropouts or pops/crackles for over 6 months – which is why it's really hitting me hard because I've suddenly fallen even more so in love with this product!
Any more possible advice? Could the ASIO version be of any help or is this likely to delay the dropouts (etc) for a little bit?
Thank you.
May 10, 2015 at 2:21 pm #14112timmywaParticipantTry replacing the Pipelines with Virtual Audio Cable 4.14.
May 10, 2015 at 8:00 pm #14113producerlawsonMemberYeah that seems to have smoothed it out a little – it's been going 12 hours without any issues so far, however it was stuttering with VAC before during the test; switching the stream buffers to auto seems to have done the trick for now.. everywhere seems nice and slick again http://media-ice.musicrad.io/oxygen
-
AuthorPosts
- The forum ‘Breakaway Professional Products – [discontinued]’ is closed to new topics and replies.