Review and Measurements of Okto DAC8 8Ch DAC & Amp

[somebodyelse]

I'll dig thru my emails and see if I documented what I did - though it had to have been a either a full reset, or simply unplugging and leaving it that way for a while before plugging it back in and powering up.

That's conceivable - if the display driver has got into some odd state it may need an extended power down for the supply lines to drop low enough to fully reset everything, rather than a quick off then on, especially if 'off' isn't really off for all parts. I've had something similar with a phone - the battery had to go into protective cutoff before it would do anything other than bootloop after it overheated on a dashboard.

Oh, and a Venu360 I'd used for years was completely killed dead by a storm event of some kind...so it can happen.

It can indeed - sometimes enough to kill it entirely, and sometimes enough to damage but not render completely inoperable. The latter can lead to some very odd behaviour that's very difficult to diagnose the cause of.

 

[dziemian]

I've turned the Okto off for 12 hours and reinstalled 1.6 firmware. The problem still persists. I have reported it to the Okto Research.

 

[Neddy]

I've turned the Okto off for 12 hours and reinstalled 1.6 firmware. The problem still persists. I have reported it to the Okto Research.

Sorry to hear that.
Did you unplug it, or just power off via menu? I do recall that unplugging it made a difference.
I dug thru my old emails to Pavel, and didn't find any mention of the display glitches.
Either I never mentioned it, or I can't find the email that covered it.
He was extraordinarily helpful, however, so I would encourage contacting him directly.
IRCC, it was as weird as what you showed.

 

[dziemian]

Yes, I unplugged it for 12 hours. Didnt make a diffrence.

 

[wineds]

Yes, I unplugged it for 12 hours. Didnt make a diffrence.

Try to reflash the firmware.

 

[dziemian]

I have. I have also got a reply from Okto. According to them it's a burn-in. A small shift between lines is being caused by a change in firmware. I can order a new display for 50 euro plus shipping and set auto-dim and auto-off next time which I recommend to everyone.

 

[somebodyelse]

I have. I have also got a reply from Okto. According to them it's a burn-in. A small shift between lines is being caused by a change in firmware. I can order a new display for 50 euro plus shipping and set auto-dim and auto-off next time which I recommend to everyone.

People speculated about whether burn-in would be a problem early in this thread, and Okto included the auto dim/off settings before any burn-in had appeared. It's unfortunate that you get to confirm it's a real issue, but now we know for sure.

 

[dualazmak]

Yesterday and today, we @fabriceo and myself, had an important (but finally disappointing) discussion on the possibility of two DAC8PRO sync aggregation using its ASIO driver on a Windows PC in "pure USB" configuration.

Please refer to our posts #95, #100 and #101 on the thread "Okto DAC8 update with DSP".

 

[dziemian]

You can use an older Lynx AES16e or RME HDSPe AES AES/EBU PCI Express card with 32-channels and 2 or more Okto DAC8 Pro in Pure AES mode. I have seen Lynx AES16e on ebay for around $300 lately.

 

[dualazmak]

You can use an older Lynx AES16e or RME HDSPe AES AES/EBU PCI Express card with 32-channels and 2 or more Okto DAC8 Pro in Pure AES mode. I have seen Lynx AES16e on ebay for around $300 lately.

Looks, sounds, interesting!
You would please let me (us) know, if you would find any article and/or post describing the details of such actual "Pure AES mode" sync aggregation of two DAC8PRO on a Windows PC, hopefully with evidence and validation of strict synchronization.

At least in my case, at present, my DSP "EKIO" or VB-AUDIO MATRIX (as system-wide ASIO/VASIO/VAIO routing center) needs to recognize the 16-Ch (you say 32-Ch) through ASIO driver of Lynx AES16e or RME HDSPe AES/EBU PCI Express card.

 

[dziemian]

I guess you need to write to either Lynx or RME support and ask these questions directly. RME has its own ASIO driver and the RME HDSPe AES supports both AES and Word Clock synchronization.

 

[Neddy]

I have. I have also got a reply from Okto. According to them it's a burn-in. A small shift between lines is being caused by a change in firmware. I can order a new display for 50 euro plus shipping and set auto-dim and auto-off next time which I recommend to everyone.

Thanks for the update!
As soon as the display options were added, I implemented them, and have had no OLED problems since (other than the weird glitching early on, mentioned earlier.)
At least the box is pretty easy to get into, and the cost is not outrageous.

 

[welwynnick]

You can use an older Lynx AES16e or RME HDSPe AES AES/EBU PCI Express card with 32-channels and 2 or more Okto DAC8 Pro in Pure AES mode. I have seen Lynx AES16e on ebay for around $300 lately.

Be careful.
Some Lynx cards are PCI.
Some Lynx cards are PCIe.