0

Cracks ans pops / dac+dsp / 20201213 hifiberryos

Domenico Guerra

January 09, 2021 23:18

None

Follow

 

Describe the bug two loud crack on startup / with DSP-V10 NO CRACKS loud pop on stop playing / only if Spdif is active and newer played / same behaviour with DSP-V10 HiFiBerryOS version 20201213 “DAC+ DSP Universal Version 12” HiFiBerry sound card DAC+DSP Raspberry PI 4 Expected behaviour No cracks and pops

• Facebook
• Twitter
• LinkedIn

4 comments

• 0
  
  Lu Greco March 10, 2021 17:58

  hi domenico,

  i saw the dacdasp v11 and v12 in the directory but i can not choose in hifiberryOS. why?

  thanks

• 0
  
  Gjcourt September 16, 2022 05:04

  I’m running into a similar issue. From a cold start i consistently hear two loud pops and one smaller one. I’m running software version 20220826 and DSP program version 12. I have REW filters loaded via dsptoolkit. Additionally I’ve noticed that the audio channels appear to be swapped when using the toslink output to my external DAC, which is frustrating.

  Another issue I’ve noticed that if dsptoolkit is used to load REW filters with an amplifier connected, there will be loud pops and noises emitted via the analog outputs (have not tested digital for fear of ruining speakers).

  I love the product but these issues make the Dac+ Dsp very hard to use and require disconnecting from the amplifier for nearly any changes for fear of destroying speakers.

• 0
  
  HiFiBerry team September 16, 2022 14:13

  It's normal that you hear pops when you load filters. 
  
  Also small pops during startup are normal as the DSP is resetted. But we don't hear "loud" pops here. Do you use analog or digital output?

• 0
  
  Gjcourt September 17, 2022 07:44

  I disagree, the job of any audio device is to only allow through signal that is purposeful audio material. If I were setting a North Star for an audio company, that would be it. From this perspective, any snap, crackle, or pop that is allowed to pass on through to the speakers is a bug.

   

  This is why most amplifier implementations include soft-start and quick disconnect functionality. Ultimately I don’t want my $75 raspberry pi hat to be the cause of the destruction of my multi-thousand speaker system. Active muting should be the modus operadi anytime an operation is performed that might send spurious signals barreling down the audio output, in my opinion anything other than the users’ intended program material falls into this category.

   

  What’s worse, I’m fairly sure that the signals being sent down the outputs while filters are being loaded contain significant DC components because I’ve observed the cones on my drivers move dramatically in one direction or the other during this operation. Again, I’m a user and love the product, but this is an obvious defect.