Okto dac8 stereo DAC Review

[Mike Rubin]

From what firmware version are you updating?
What part is not working out for you?

*Did you succced to flash the usb with mint?
*Did you succeed to boot your computer with mint?
-Or did it fail in terminal mode, not finding your dac?

I had some problems typing the commands in terminal mode since the keys was not coresponding to the right symbols/letters but once i figured that out it worked.
Also the first time I typed the commands it failed because I did not chose the right usb input on the Okto dac, so it was not recognized when searching usb-ports for Okto product.
Also I had to use an old computer with more than one USB-A ports, since I had the USB-stick i booted from in one and hooked up the dac I was going to flash in the other one.
Well if you don't succeed I hope you get the flash tool from Okto soon.
I wish you luck!

Here is what I posted at the time, in response to TaxTime:

“I had no success with it, trying to update from 1.11.

“Using the Windows update method and file, I can update the driver but the firmware itself won't update.

“Using the USB update method and software, which Okto recommends after an update failure, I couldn't even get Terminal to run in the recommended Linux Mint OS. Clicking on it just brings up the equivalent of the hourglass and then... nothing. (Google discloses that others have had an issue getting Terminal to run in Mint.)”

I later added:

“According to the instructions for the USB method, I should have been able to bring up a Terminal option by right-clicking in the white space on the Mint Desktop. That didn't work so I clicked on Terminal in the application menu. Unfortunately, that only brought up the Linux equivalent of the hourglass, which spun and spun until I was dropped back to the desktop again.

“I gave up after the third or fourth USB stick installation.

“Emailed Pavel, but he's never been quick about responding, so I await a response a few days after.”

I eventually got an email from Okto Customer Service that promised that I eventually get the update tool that was going to circulate among users. That was several months ago.

My unit operates pretty reliably and I don’t even know what 1.2 accomplishes that 1.11 doesn’t, so I am not sweating this too much.

 

[Zooqu1ko]

[...]

“Using the USB update method and software, which Okto recommends after an update failure, I couldn't even get Terminal to run in the recommended Linux Mint OS. Clicking on it just brings up the equivalent of the hourglass and then... nothing. (Google discloses that others have had an issue getting Terminal to run in Mint.)”

I later added:

“According to the instructions for the USB method, I should have been able to bring up a Terminal option by right-clicking in the white space on the Mint Desktop. That didn't work so I clicked on Terminal in the application menu. Unfortunately, that only brought up the Linux equivalent of the hourglass, which spun and spun until I was dropped back to the desktop again.

“I gave up after the third or fourth USB stick installation.
[...]

I'd recommend using a different USB stick, if possible a fast USB 3 device made by a reputable vendor. If that doesn't help, try other Linux distributions. I'd start with Ubuntu, possibly Fedora, and if that fails, GRML. Try writing the USB stick on a different computer, even a Mac is OK for that. If all that doesn't work, the problem may be your computer. Borrow an old laptop, or rescue one from the trash. Anything made in the last 15 years should be good enough.

 

[Mike Rubin]

I'd recommend using a different USB stick, if possible a fast USB 3 device made by a reputable vendor. If that doesn't help, try other Linux distributions. I'd start with Ubuntu, possibly Fedora, and if that fails, GRML. Try writing the USB stick on a different computer, even a Mac is OK for that. If all that doesn't work, the problem may be your computer. Borrow an old laptop, or rescue one from the trash. Anything made in the last 15 years should be good enough.

Thank you. I will try this again, using a different computer. (I did try using several USB sticks when I did this initially.). Okto confirmed that some of the DAC 8's simply won't update, hence the circulating tool, but it is couldn't hurt to try to again with my laptop.

 

[Kal Rubinson]

Thank you. I will try this again, using a different computer. (I did try using several USB sticks when I did this initially.). Okto confirmed that some of the DAC 8's simply won't update, hence the circulating tool, but it is couldn't hurt to try to again with my laptop.

Some will not update with the hardware kit because their circuit board lacks a header which the user needs to obtain.

 

[Mike Rubin]

Some will not update with the hardware kit because their circuit board lacks a header which the user needs to obtain.

Oh, great.

 

[Kal Rubinson]

Oh, great.

Sure. But it is doable.

 

[Mike Rubin]

Sure. But it is doable.

I guess I will have to cross that bridge if I come to it.

 

[Mike Rubin]

I'd recommend using a different USB stick, if possible a fast USB 3 device made by a reputable vendor. If that doesn't help, try other Linux distributions. I'd start with Ubuntu, possibly Fedora, and if that fails, GRML. Try writing the USB stick on a different computer, even a Mac is OK for that. If all that doesn't work, the problem may be your computer. Borrow an old laptop, or rescue one from the trash. Anything made in the last 15 years should be good enough.

Thank you, Zooqu1ko. I used a different computer, brand new 3.1 USB stick, and a different USB cable. The Windows executable didn’t work because it couldn’t find an attached DAC, so I tried Mint again and this time was able to update, at least according to the screen display. I had to reprogram my remote and revert my settings, so I guess that means the update indeed took.

I appreciate the guidance.

 

[Mike Rubin]

And now, after installing 1.2, I am having major issues when playing DSD. Whenever I start or stop DSD, to play or advance to the next DSD track on a playlist, I get a loud pop through the system. Since I usually listen at DSD256 on HQPlayer, this is a problem that renders the DAC almost unusable. I have the same issue, however, with DLNA players like JPlay for iOS, JRiver or Audirvana and with Roon when playing DSD. It’s 100 percent repeatable.

This happens whether I am using my Signature SE or my Pi4 with Volumio. I therefore blame the DAC

Any suggestions other than avoiding DSD? I have a lot of money invested in DSd files!

 

[Zooqu1ko]

[...]

Any suggestions other than avoiding DSD? I have a lot of money invested in DSd files!

I have no better suggestions than to contact Pavel, since he's planning to roll out a bug fix release for the DSD issue described just one page earlier. In the meantime, as a workaround, convert to 96 or 192kHz PCM.

 

[Mike Rubin]

I have no better suggestions than to contact Pavel, since he's planning to roll out a bug fix release for the DSD issue described just one page earlier. In the meantime, as a workaround, convert to 96 or 192kHz PCM.

Thank you. I emailed Pavel a few days ago, before posting here, but haven't yet heard from him.

When I read about the DSD issues on the previous page, I thought that Pavel was addressing issues that occurred only with Aurender products and popping that came up randomly throughout playback. My problems seem slightly different, which is why I posted.

Mine have occurred with both a Sonore renderer and the onboard Pi / Volumio server. They arise occur when I start or end DSD playback or when advancing tracks in a DSD album or playlist.

My workaround, similar to what you suggested, has been to convert files, including dsf, to PCM 384 in HQPlayer and to avoid dsf selections altogether in DLNA and Roon servers.

 

[Mike Rubin]

Secondary issue after firmware update: I frequently have to remove the power cord and reinsert it to enable handshake between my Sonore Rendu and the DAC and, also, when switching between the internal Pi4 and the Sonore unit. Since upgrading to 1.2, that loses the settings that the DAC previously stored. That means that I need to reprogram the remote, reselect the inputs, and restore the volume to 0db fixed. In the entire time that I have owned the DAC before the update, I never had to reprogram the remote and settings, ever, despite removing and reinserting the power cord frequently. The upgrade instructions warn that I would have to re-enable the remote and prior settings after a successful update, but it didn’t say I would have to do so every time the unit is removed from power. Has this happened to any of you?

 

[AudioJester]

And now, after installing 1.2, I am having major issues when playing DSD. Whenever I start or stop DSD, to play or advance to the next DSD track on a playlist, I get a loud pop through the system. Since I usually listen at DSD256 on HQPlayer, this is a problem that renders the DAC almost unusable. I have the same issue, however, with DLNA players like JPlay for iOS, JRiver or Audirvana and with Roon when playing DSD. It’s 100 percent repeatable.

This happens whether I am using my Signature SE or my Pi4 with Volumio. I therefore blame the DAC

Any suggestions other than avoiding DSD? I have a lot of money invested in DSd files!

I have the same issue with my okto8pro and multichannel dsd with convolution filters in hqp. Happens with an ultrarendu or computer straight into dac via usb. Also since latest firmware.

 

[Mike Rubin]

I have the same issue with my okto8pro and multichannel dsd with convolution filters in hqp. Happens with an ultrarendu or computer straight into dac via usb. Also since latest firmware.

I feel your pain. (FWIW, I am not using any convolution in HQPlayer.)

 

[AudioJester]

I feel your pain. (FWIW, I am not using any convolution in HQPlayer.)

I will have to try again to confirm, but i dont think it happens with Roon upscaling/convolution engine.
Maybe a hqp-okto specific issue?

 

[Mike Rubin]

I will have to try again to confirm, but i dont think it happens with Roon upscaling/convolution engine.
Maybe a hqp-okto specific issue?

I don't think that is the issue. I have the same problem on the Sonore rendu with dsf files in JRiver and Audirvana DLNA and both dsf and upsampled DSD files in Roon with RAAT. I also have the problem with native DSD files using the built-in Raspberry Pi 4 streamer.

I should mention that all playback is over USB. I don't even know if the other digital inputs support DSD and the only device I own with an optical output doesn't play DSD so I can't test.

 

[AudioJester]

I don't think that is the issue. I have the same problem on the Sonore rendu with dsf files in JRiver and Audirvana DLNA and both dsf and upsampled DSD files in Roon with RAAT. I also have the problem with native DSD files using the built-in Raspberry Pi 4 streamer.

I should mention that all playback is over USB. I don't even know if the other digital inputs support DSD and the only device I own with an optical output doesn't play DSD so I can't test.

Can confirm - no pops with Roon outputing dsd. Wonder what Roon does differently?

 

[TaxTime]

Secondary issue after firmware update: I frequently have to remove the power cord and reinsert it to enable handshake between my Sonore Rendu and the DAC and, also, when switching between the internal Pi4 and the Sonore unit. Since upgrading to 1.2, that loses the settings that the DAC previously stored. That means that I need to reprogram the remote, reselect the inputs, and restore the volume to 0db fixed. In the entire time that I have owned the DAC before the update, I never had to reprogram the remote and settings, ever, despite removing and reinserting the power cord frequently. The upgrade instructions warn that I would have to re-enable the remote and prior settings after a successful update, but it didn’t say I would have to do so every time the unit is removed from power. Has this happened to any of you?

Hmmm...I am currently on 1.2, and have no issues after power is disconnected. In fact, we had a full power outage just today due to the weather, and when it came back up, all settings were still there, including custom remote programming (I mapped existing buttons on the remote for my preamp).

 

[Mike Rubin]

Hmmm...I am currently on 1.2, and have no issues after power is disconnected. In fact, we had a full power outage just today due to the weather, and when it came back up, all settings were still there, including custom remote programming (I mapped existing buttons on the remote for my preamp).

That's the weirdest thing to me. I gather many DACs pop with DSD, but this is new and unprecedented behavior that I haven't seen elsewhere.

Unfortunately, no one from Okto has responded to the two emails I sent more than a week ago and the note I left on the Okto site several days later.

 

[TaxTime]

That's the weirdest thing to me. I gather many DACs pop with DSD, but this is new and unprecedented behavior that I haven't seen elsewhere.

Unfortunately, no one from Okto has responded to the two emails I sent more than a week ago and the note I left on the Okto site several days later.

I recall that when I emailed Okto for ideas because of multiple failures of the update, it took Pavel a couple of weeks to get back to me, which didn't bother me at the time because it was operating fine otherwise on the older firmware.

Have you tried reinstalling the firmware? Perhaps there is a fault/glitch in your initial update.