No nativ DSD in Debian ? only DOP?

Hello,
I can choose DOP 1 or 1.1 but no way to use the DAC TEAC UD-507 max upsample DSD capability, as with MacOS.

the app see 512 max and the TEAC is labelled as “play with”.

Am I missing something ?

Is it the same things on other distro ?

Do I need to install jack, pulseaudio or pipe wire ?

I’ve tried Ubuntu studio, but dependencies were missing to install Audirvana.

thank’s for your help :slight_smile:

I am curious… Does the modulation processing of PCM to DSD in Audirvāna (r8Brain or SoX) sound better than the native DSP processing to 1-bit 22.4MHz (DSD512) in the UD-507 from your experience?

:notes: :eye: :headphones: :eye: :notes:

Difficult question. I use R8B. The 1bit mode on the UD-507 is very different from the multibit. the snap of the stick on the metal of the snare drum is much sharper and faster in one bit. It’s my choice.

With this parameters I can compare
256 Audirvana made versus
512 teac made with 358/32 Audirvana as a source.

256 DSD open the space and the instruments are more behind the speakers. Very good for 80 players orchestras. Teac upsample has perhaps richer textures.

Interesting. I use two Ubuntu (Debian based) distros, and native DSD works just fine, as with my other two Linux distros (the driver would be the same).

What is your setup?

When you change the TEAC settings to modulate to DSD256 and make the comparison, how do they compare?

:notes: :eye: :headphones: :eye: :notes:

the DAC config 128, 256, or 512 Fs is the setting where I can choose the DSD upsample output ?

What is the prefered way of communication between ALSA and Audirvana ? pipewire ? Jack2 ? ubuntu studio Qapt cannot satisfy dependencyand instal Audirvana. I’ve tried to install avahi and zero conf, in vain. What kind of dependency could that be ?
What are the ubuntu distro do you use ? (I need a GUI)

ok that’s the settings. never try before ! it’s very close, I need hours to know. perhaps a sweet spot ! perhaps a good reason to go back to 3.5 and no upsample at all in Audirvana… the sound make me think at the PS audio directsream, another FPGA with DSD treatment, but that was not as good at the 503 to my ears. (that was a surprise for me and made me a lot of problems and obliged me to take the road to give it back).

You don’t make things more simple you know ? :grin: :rofl: :beers:

I have Xubuntu (GUI - XFCE) and Ubuntu Server 24.04 LTS (no GUI). Audirvana installs and runs on both without problems.

I believe I have pipewire installed on Xubuntu. I will have to check whether I have it installed on Ubuntu Server. I am reasonably sure I don’t have either pulse or jack installed on either one.

Do you know how to install packages from the terminal? If you try that it will have a good chance of telling you what dependencies you are missing. Here are the dependencies shown for Arch and Arch-based distros; they will probably be the same or very close to the same for Ubuntu or Debian:

  • alsa-lib
  • avahi
  • curl
  • gcc-libs
  • glibc
  • libxml2

So it doesn’t appear as if pipewire, jack, or pulse are needed.

If you don’t know how to install apps using the terminal, let me know and I’ll find a decent explanation and give you a link.

Just confirming I have neither pulseaudio nor pipewire nor jack installed on Ubuntu Server 24.04 LTS, and Studio installs and runs there without problems.

OK. Thank you for this informations. I’ve switch to ubuntu (not studio). same result. here are my hypothesis.

The DAC and Audirvana are communicating using ALSA
The DAC tells his abilities and Audirvana show corresponding choices
The DAC answer is not good, or ALSA transform the exchange, or the reading of the answer is not good.
Audirvana has a table with all the DACS abilities and this table is different in windows and linux for my dac.

If I find the file that describe the capabilities I can adjust to the hardware.

Is will check the ALSA instal to begin.

If you want to start over with clean settings there are two directories with settings you want to delete, and then some minimal file information you want to put back. I know where these are in Arch based distros but not off the top of my head in Ubuntu, and unfortunately I’ll be busy for the next couple of days and unable to look. I’ll let you know in a couple of days unless you’ve solved the issue before then.

don’t worry, have a good WE !
I’ve tried a fresh instal on Ubuntu and to folow this method : Native DSD On Linux via MPD: a mini guide - United & Co
as a result :slight_smile:
aplay --dump-hw-params -D hw:CARD=MODELNAME -f cd /dev/zero
Lecture données brutes ‘/dev/zero’ : Signed 16 bit Little Endian, Fréquence 44100 Hz, Stéréo
Params HW pour le périphérique “hw:CARD=MODELNAME” :


ACCESS: MMAP_INTERLEAVED RW_INTERLEAVED
FORMAT: S16_LE S32_LE S24_3LE
SUBFORMAT: STD MSBITS_MAX
SAMPLE_BITS: [16 32]
FRAME_BITS: [32 64]
CHANNELS: 2
RATE: [44100 1536000]
PERIOD_TIME: [125 1000000]
PERIOD_SIZE: [8 1536000]
PERIOD_BYTES: [64 12288000]
PERIODS: [2 1024]
BUFFER_TIME: (10 2000000]
BUFFER_SIZE: [16 3072000]
BUFFER_BYTES: [64 24576000]
TICK_TIME: ALL

I tried to instal HQ Player and no way to avoid DOP.
I will now start the search from the DAC

It’s OK with windows, I can try windows Atlas, but my previous test on windows Atlas have drive me back on MacOS.

I had a moment and another thought occurred to me. Usually a DAC capable of DSD512 will also be capable of 768kHz PCM. But your DAC’s specifications appear to me to say it is limited to 384kHz PCM. If this is correct, the DSD512 capability may be the result of a driver not available in Linux. Experiencing the same limitation with both Audirvāna and HQPlayer might be an indication this is the case.

Just a thought, perhaps correct, perhaps not.

I guess that comparing the PCM /DSD capacity has the max kb/s rate as a basis. But here the problem is that I cant get ride of DOP.
I’ve found a fix that seem’s to work for all 50X TEAC DAC USB.

this part in the right hand green corner let me hope

“TEAC devices with USB DAC functionality */
1373 if (is_teac_50X_dac(chip->usb_id)) {
1374 if (fp->altsetting == 3)
1375 return SNDRV_PCM_FMTBIT_DSD_U32_BE;
1376

But I don’t understand how to use the fix, It’s an SDK for engineer, it’s perhaps for Damien :slight_smile:

I will try the front USB-C card…

:roll_eyes:… The UD-507 is a proprietary ladder-DAC that upsamples/modulates everything to DSD and outputs the signal as either 1-bit DSD or Multi-bit DSD-Wide… This DAC does not support PCM sample-rates above 384kHz. There is zero reason to.

There are no recordings done at 768kHz, These are all iterations of lower PCM sample-rates up-sampled to 768kHz.

There are very few recordings produced using 1-bit 11.2MHz (DSD256) A/D… I think Octave Records (PS Audio) is beginning to build a catalog of content recorded at 22.4MHz.

There are zero 22.4MHz (DSD512) recordings. These are all iterations of lower sample-rate 1-bit recordings or up-sampled PCM recordings.

:notes: :eye: :headphones: :eye: :notes:

The UD-507 modulates all PCM signals to 1-bit DSD… The modulator frequency can be selected between DSD128, DSD256 and DSD512

Do you happen to know whether it has the DSD512 capability for Linux, or could this be limited to Windows? What about MacOS? (“Native” DSD is possible on MacOS with USB if a custom driver is used. Does the TEAC UD-507 have such a custom driver?)

As you probably know, the quirks file passes device capability information to the kernel, and I’m guessing someone better versed in Linux than I am might be able to tell you how to do this - it wouldn’t necessarily have to be Damien.

This may help to determine whether your Linux system currently recognizes your UD-507 as having “native” DSD capability:

First issue the command

aplay -l

to get the UD-507’s card and subdevice numbers.

Then issue the following command, substituting the UD-507’s card and subdevice numbers for X and Y, respectively:

aplay --dump-hw-params -D hw:X,Y -f cd /dev/zero

Can you copy and paste the result here?