0

HiFIBerryOS DAC+DSP Spotify Connect Audio Comparison

Matt

May 09, 2020 08:03

None

Follow

Hi,

 

I did some A B comparison test between Hifiberry DAC+ DSP running HiFiBerryOS and my Yamaha RX-V585. 

Setup:

- Spotify Connect > Hifiberry DAC+ DSP (DSP and EQ Off) > Optical Out > Yamaha RX-V585 (DSP Off)

 

- Spotify Connect > Yamaha EX-V585 (DSP Off)

 

What I hear is that the Yamaha play its spotify audio less muddy, less distorted more bright. It's almost comparable to Tidal CD quality > Roon > HiFiBerry.

How can this possible? Is the HiFiBerry DAC involved even with optical output? Could be that the Yamaha is upsampling the audio from its Spotify Connect? 

 

 

 

 

• Facebook
• Twitter
• LinkedIn

22 comments

• 0
  
  Matt May 09, 2020 16:52

  Ok spent the day learning ALSA and found the conf file asound.conf.dmix_softvol already in place. I did modify rate, format and samplerate_medium.

  Edited by Matt May 09, 2020 16:53
• 0
  
  HiFiBerry team May 09, 2020 17:36

  This file isn't used since several releases. What version of HiFiBerryOS are you using?

• 0
  
  Matt May 09, 2020 17:51

  My berry is a DAC+ DSP. In the last file used is ok to put format and rate like this?

   

  pcm.hifiberry {

    type hw

    card 0

    device 0

    format S24_LE

    rate 88200

  }

   

• 0
  
  HiFiBerry team May 09, 2020 17:53

  You should not try to use your own asound.conf on HiFiBerryOS. HiFiBerryOS is designed to manage this file.
  The original file should be perfectly fine and using another asound.conf might break things.

• 0
  
  Matt May 09, 2020 17:56

  I understand this but there's no way to change the samplerate algo, rate and format via GUI on HifiBerryOS.

• 0
  
  HiFiBerry team May 09, 2020 17:58

  It doesn't support this as you don't need it. HiFiBerryOS doesn't resample on the Pi. Sample rate conversion is handled directly by the DSP anyway (and it doesn't matter what resampling you use on the Pi).

  If you want to experiment with things like this, I recommend rather using a standard Raspbian than HiFiBerryOS.

• 0
  
  Matt May 09, 2020 18:02

  "Sample rate conversion is handled directly by the DSP anyway (and it doesn't matter what resampling you use on the Pi"

  Can you tell me more about this? does resample at 24bit/192Khz? 

   

• 0
  
  HiFiBerry team May 09, 2020 18:06

  The DSP always runs with it's own clock domain. Therefore, all inputs to the DAC are re-sampled using high-quality asynchronous sample rate converters. This is completely transparent to the application sending data and happens automatically.
  Our profiles use 48kHz sample rate as this allows us to use longer delays and more filtering than it would be possible with 192kHz. If you want the DSP to run at 192kHz internally, you have to create your own DSP profile using SigmaStudio:
  https://github.com/hifiberry/hifiberry-dsp/blob/master/doc/dspprofiles.md

• 0
  
  Matt May 09, 2020 18:08

  Thank you!

• 0
  
  Matt May 09, 2020 18:38

  Last question :)

  are the generic96 and generic192 profiles on github exactly what I need for?

• 0
  
  Matt May 09, 2020 18:51

  OK, installed Generic 96K and it works. However my AVR still says 48K input.

• 0
  
  HiFiBerry team May 10, 2020 05:19

  I don't know what you "need", but I don't see any reason to upsample Spotify sources to 192kHz. Almost any DAC offers best performance at 44.1 and 48kHz as filtering out-of-band noise is much easier to do in this case.

  If you still want to upsample to 192kHz, you should create you own DSP profile with SigmaStudio.

• 0
  
  Matt May 10, 2020 11:40

  I did with generic96 profile. I had to make some adjustments now my AVR see 96Khz input. 

  Is the DAC+ DSP Universal dspproj available anywhere? I can't find it on Github.

• 0
  
  HiFiBerry team May 10, 2020 15:51

  https://github.com/bang-olufsen/create/blob/master/BeocreateUniversal-v10.dspproj

• 0
  
  Matt May 10, 2020 19:24

  Sorry, the link you posted is for the Beocreate, I need the one for DAC+ DSP.

• 0
  
  HiFiBerry team May 11, 2020 04:30

  We're using one project for both - only difference is the MUTE function that needs to be inverted. There is no separate project.

• 0
  
  Matt May 11, 2020 08:45

  Oh nice, thank you. I'm taking a look at the project right now. Is the MUTE function into the Hardware MUTE tab? Should I change the GPIO?

   

• 0
  
  Matt May 11, 2020 15:38

  Ok, I got it working (the Mute was ok, problem was one of the volume at -20db) but I can't control the volume now. from within the web gui I can see the controller going up and down like crazy.

  How can i fix that?

• 0
  
  Matt May 11, 2020 16:20

  Ok, volume is ok. But now I all the DSP filters are not working. If I click on them sounds mute. Also SPDIF input is greyed out.

• 0
  
  HiFiBerry team May 11, 2020 16:23

  You can't simply upload a program from SigmaStudio. You need to convert it to a DSP profile if HiFiBerryOS should be able to control things in this profile. HiFiBerryOS and requires the metadata for all control in this profile. 

  https://github.com/hifiberry/hifiberry-dsp/blob/master/doc/dspprofiles.md

  Check the metadata of the original XML file and make sure all of these are mapped correctly with your updated profile. As this is quite some work, I recommend to do this when the profile is really ready.

• 0
  
  Matt May 11, 2020 17:05

  metadata sampleRate had a typo

• 0
  
  Matt May 11, 2020 17:33

  OK, everything works! 

  Edited by Matt May 11, 2020 21:17