• Welcome to ASR. There are many reviews of audio hardware and expert members to help answer your questions. Click here to have your audio equipment measured for free!

Okto DAC8 update with DSP

Hi Dualazmak,
As far as I m aware, the question of supporting multiple USB Audio device with the Thesycon Asio driver was raised to them and they have no plan to make this happen. So the only solution is to use a MAC Os. may be something on linux exists which I m not aware of. Therefore I cannot answer all your subsequent questions.

One technical solution which I have been thinking some time ago was to configure a master dac8pro in 16 channel (max 96k) and extract 8 of them to send them to a slave dac8pro over the xmos Xlink channel which is available on the cpu board inside dac8pro. But that requires some code and some hardware connection between them. Also the length of the cable would be critical and then we never really worked on this scenario, but that would be possible (but limited to 96k). Recently XMOS delivered a new version of their USB Stack able to support 16channels at 192k but this requires the new chips version and a 800mhz clock, so not compatible with dac8pro.
Here we are

Thank you for your kind responses, even though I am now quite disappointed hearing those since I am Windows guy all the way... :facepalm:
One of the major drawbacks of OKTO would be its total dependence on Thesycon for ASIO driver developments, I Assume.

Now, I would like to share again my dream and asking Pavel's serious attention on possible development of DAC16PRO(?) which I have already described several times on ASR including here and here.
In my post here #2,145, I wrote;
I just posted my wish for possible DAC16PRO(?) in my post here;
WS003999.JPG


Edit: I wrote there;
USB 16-Ch ASIO input (by one or two USB 2.0 cable from PC) and 16-Ch balanced analog out should be just enough for me. Therefore, my simple wish for 16-Ch Sync Pro DAC, (OKTO?) DAC16PRO(?) with two (or three?) of ES9028PRO or ES9038PRO (or new AKM DAC chips?) in it; 8-Ch AES/EBU digital stereo inputs would be welcome for future possible use, and for those who in pro field...
Of course, the dedicated ASIO driver in PC should recognize all of the 16-Ch of this gear; quite easy to be achieved, I believe.

I do hope Pavel of OKTO would look here.

Edit: If this would become reality in the near future, I will be more than happy to be a beta tester since I fully utilize DAC8PRO in my multichannel multi-amplifier project. My latest system setup can be found here
here.
 
In other words no 16 channels with current model without a change in hardware? So if you need more channels for Atmos it is either a 16 channel AES interface and 2 Oktos in Pure AES mode or any other 16 channel dac like Audient Oria?
 
I've changed both cables for much better quality ones nevertheless. We'll see!

It does seem that both they are actually helping, with no skips so far. I shall keep monitoring.

Thanks again Guys!

And have a great weekend.
 
I've mentioned the PipeWire capability for keeping different clock domains in sync similar to MacOS in another thread.
Thanks for the hint, I dint know, that seems a good way (on Linux only) to demux a single audio peripheral to multiple USB Audio device, we should investigate that.
Still we would need an AES connection between 2 dac8pro (one being in USB/AES) to guarantee the perfect sync of the 2 audio streams.

In other words no 16 channels with current model without a change in hardware? So if you need more channels for Atmos it is either a 16 channel AES interface and 2 Oktos in Pure AES mode or any other 16 channel dac like Audient Oria?
I d say differently, any DAC with an internal XMOS device (216 or 316) not running at 800mhz will not be able to process a 16ch at 192k (or 8ch 384k/DSD256) in a raw.
Coupling device is possible to some extend, when the host computer includes mechanisms to send audio on multiple USB device (like MacOS or Linux-PipeWire). In that case, Okto dac8pro is the only one able to render the stream without time correction (or arsc) by synching 2 devices over AES and using the USB/AES mode on one of them.

I m very fond of this topic and this is definitely an area for development , let see
 
Last edited:
Still we would need an AES connection between 2 dac8pro (one being in USB/AES) to guarantee the perfect sync of the 2 audio streams.
If you've got hardware clock sync via AES connection (so shared clock domain) you can use an ordinary alsa composite device which has been around for years - handy for pro audio devices sharing a master clock signal. The bit PipeWire added is the ASRC so that devices with separate clock domains (like ordinary USB DACs, or USB and I2S) don't drift out of sync, so they can be combined into a virtual device too. If you want to use PipeWire with hardware sync between multiple USB devices then don't forget to set the clock.name property the same on each device - this tells it about the shared clock and stops it doing unnecessary ASRC.
 
Last edited:
Hi there!

MO, thanks for your test so this is not a problem of SPDIF/AES LOCK but a problem of sensitivity of the Sabre ES9028 to a jittered I2S signal.
I have no turnkey solution for this At The Moment but will discuss this with Pavel shortly. No promise for a solution.

Hi @fabriceo! Hope you're well. Any news on this??

With both cables changed for (supposedly much) better quality ones, still skipping... little less I'd want to say... but still.

I'm about to try a new power supply: https://www.silentpower.tech/products/ipower2 for the Hosa ODL-312 adapter... but at this point, I'm not that willing to keep spending money just to "trial and error" my solution.

Hopefully you can give me a better hint.

Thanks much in advance.

Cheers!
 
Good morning Guys!

It seems that the improvements I've made to the system chain have actually contributed to decreasing the occurrence of the skips. It is now only happening with Spotify playing on the Samsung SmartTV. No skips in any other application so far.

I have deleted and reinstalled Spotify just in case, and nothing changed.

Even Qobuz, which is supposed to be more bandwidth demanding, plays nicely, now.

Any other ideas on what this could be with this new information..??

Thanks and regards!!
 
Good morning Guys!

Any other ideas on what this could be with this new information..??
Hi, another idea comes to my mind reading this some month after :)
if the lock status of the AKM is OK then maybe it is just the Spotify app running in the TV which does not deliver samples correctly to the toslink...
you can test this by using the mode USB/AES of the DAC8PRO and use a software like Audacity to capture the stream and see what sort of hole we have here.
The sample rate on the host computer must be set equal to the Toslink spdif rate.
It might be possible to play a 1khz sine reference by listening some specific Audio test CD (please search in Spotify, I got this idea from Gemini...)

if we have a "clean" hole in audacity then this has nothing to do with the ES9028 and as the AK4118 seems to be locked then it would come from the streaming app!

hope we'll progress
 
There is also Minidsp Tide 16 for $3500
 
I was told in an email from Okto that they are working on a new firmware that will allow for fully clock and sample synchronized operation of multiple dac8s in a parallel USB configuration. my hope is that you could run camilladsp on a rpi 5 as a full DSP solution, run multiple USB synced Oktos for D/A, and you could have a world beating 16, 24, or 32 channel home theater DSP system for $5k. I think you'd want the DSP centralized on one device, so I'm not sure using onboard DSP would make sense at that point.

related question about DSP: I'm reading the AVDSP github and it says this at the bottom:

The firmware V1.61 is enabled up to 192Khz sampling rate but this is a challenging limit for this processor. In short at 192k it is possible to apply 6 biquads and 1 delay line on 8 channels. At 96k we have a more comfortable 20 biquads capabilities for 8 channels. version 1.62 provides twice this performance and even a bit more when using overclocking

does this mean under 1.62 we have around 40 biquads per channel?
 
Hi all,

Hope this is the right thread to post this ?plea for a feature?.. ask for help?.. I dunno, I've been trying to solve this puzzle for a while now, and just can't.

The problem: Native DSD playback to Okto DAC8Pro. Specifically, the dsf 5.0 files. More specifically, under Linux (Ubuntu, so Debian-ish).
JRMC is the player.
2.0 and 5.1 files more or less work. 5.0 I managed to play only as DoP.

I don't have a deep technical understanding of how the signal chain is made; the digging I was able to do (with help of AI) shows that DAC8Pro presents to ALSA 3 altsets for the DSD playback: 6, 8, and 2 channels, and ALSA baulks at the channel mismatch when 5.0 dsf file is presented.

Under Windows, everything just works, and my limited understanding is that Okto's ASIO driver is to thank for that -- so this is my current solution, but would be nice to solve this for Linux.

Does anyone have suggestions on how to fix this problem? Would @fabriceo kindly consider sparing some time and maybe bake a 5.0 altset into Okto's firmware?

Thanks all,

Alex

PS. No, I don't want to alter the files. No, I don't want to just play them as PCM.
 
Hi all,

Hope this is the right thread to post this ?plea for a feature?.. ask for help?.. I dunno, I've been trying to solve this puzzle for a while now, and just can't.

The problem: Native DSD playback to Okto DAC8Pro. Specifically, the dsf 5.0 files. More specifically, under Linux (Ubuntu, so Debian-ish).
JRMC is the player.
2.0 and 5.1 files more or less work. 5.0 I managed to play only as DoP.

I don't have a deep technical understanding of how the signal chain is made; the digging I was able to do (with help of AI) shows that DAC8Pro presents to ALSA 3 altsets for the DSD playback: 6, 8, and 2 channels, and ALSA baulks at the channel mismatch when 5.0 dsf file is presented.

Under Windows, everything just works, and my limited understanding is that Okto's ASIO driver is to thank for that -- so this is my current solution, but would be nice to solve this for Linux.

Does anyone have suggestions on how to fix this problem? Would @fabriceo kindly consider sparing some time and maybe bake a 5.0 altset into Okto's firmware?

Thanks all,

Alex

PS. No, I don't want to alter the files. No, I don't want to just play them as PCM.
Sounds like a JRiver problem to me. I'd expect them to be able to play back 5.0 files as 5.1 with a silent LFE channel.
 
Sounds like a JRiver problem to me. I'd expect them to be able to play back 5.0 files as 5.1 with a silent LFE channel.
methinks this less likely, since mpd-based solutions (Volumio, for example), or even aplay -D run into the same ALSA wall. In theory, JRMC devs _could_ conceivably put their brilliant brains together and solve this at the player level... but I'm sure they will not, since a) this is a bit of an edge case, and b) JRMC already has a functional workaround in a form of DoP...

It would be so very nice to have it solved either at the firmware level, or at the "driver of sorts" level! but I'm not nearly knowledgeable enough to undertake such a project.
 
methinks this less likely, since mpd-based solutions (Volumio, for example), or even aplay -D run into the same ALSA wall. In theory, JRMC devs _could_ conceivably put their brilliant brains together and solve this at the player level... but I'm sure they will not, since a) this is a bit of an edge case, and b) JRMC already has a functional workaround in a form of DoP...

It would be so very nice to have it solved either at the firmware level, or at the "driver of sorts" level! but I'm not nearly knowledgeable enough to undertake such a project.
Are there any disadvantages of DoP, since that seems to work for you?
 
Are there any disadvantages of DoP, since that seems to work for you?
yes, slight, with a couple of possible workarounds (that I haven't tested... yet):

on Okto, DoP is limited to DSD64, which is fine for the 5.0, 5.1, and the _majority_ of 2.0 dsf files I own... but for the couple of albums in 2.0 DSD128, DoP chokes.

one workaround is creating a "Native DSD-specific" Zone in JRMC (or, possibly, the other way around, "DoP-specific") and then create a rule sending a file to such zone based on number of channels or DSD resolution -- I could conceivably do this;

another is to "downsample" DSD128 to DSD64... -- nope, not going there.

yet another one is to use Roon Bridge... -- but I hear rumours that Roon deals with this problem by converting dsf to PCM, inserting a silent LFE channel, and converting back to dsf... and I'd like to avoid any conversion whatsoever at any stage of the soundchain.

(insert a whinny voice here): but on Windows it just works!.. no workarounds required.
 
PS. No, I don't want to alter the files. No, I don't want to just play them as PCM.
OK, I can well understand your above preference. ;)

On the other hand...
Just for your possible reference and interest, at least in my PC-DSP-based multichannel multi-SP-driver multi-amplifier full active audio system (details can be found in #931, #1,009, #1,022 on my project thread), and as far as "my present ears and brain" concern, "on-the-fly (real-time)" conversion (over-sampling, down-sampling) of all the digital tracks into 88.2 kHz or 96 kHz PCM by JRiver MC is more than enough, and it is even needed.

You can find the "historic sequences", background, reasons and rationales in my post #532 on my project thread.
_
 
Last edited:
Back
Top Bottom