Does anyone know if Octo is shipping anything? It's been 29 weeks since I ordered and still no box at my door.
https://www.audiosciencereview.com/forum/index.php?threads/okto-8-owner’s-thread.13899/post-867589
Does anyone know if Octo is shipping anything? It's been 29 weeks since I ordered and still no box at my door.
YesSince Okto does not respond to my question by mail, I would like to know if anyone happen to know the follwoing about the Okto DAC8:
Can I assign the same input channel to in the routing submenu multiple times?
Example:
Out1 source: CH1
Out2 source: CH2
Out3 source: CH1
Out4 source: CH2
....
(aim: can feed the stereo input signal from USB to multiple amplifiers at the same time)
Many thanks! Hope the DAC8 will be available once again for order.
Based on my understanding of the manual (I’ve pasted the key sections below) if you use USB/AES input mode of the DAC8 Pro you could still use DSP.
So I think it would be possible to connect your source to the AES inputs , and a computer (with DSP processing with low enough latency ) to the usb. In USB/AES mode the signal flow would be
source => DAC8 AES/EBU input => DAC8 USB host => computer DSP => DAC8 USB host => DAC8 D/A converter => analog outs
Hopefully @Okto Research can chime in here.
Yes, that is exactly what we had in mind when implementing the AES/EBU to USB functionality. The planned Owner's manual update is going to bring some examples of usage.
@Okto Research @Ozymandias
Please can you point me toward the examples in the manual. I'm trying to get this to work with hqplayerd on ubuntu. Thanks for your help,
Matt
Michael,I am using mine in USB/AES mode (with a RPi4 running Ubuntu 21.04 64 bit but not HQ Player). The only issue that I have encountered is that as explained in the manual you need to have your USB source set to run at the same sample rate as your AES source. My AES source has a ASRC so I convert everything to 96 kHz and then leave my CamillaDSP setup on the RPi set at 96 kHz.
Michael
What does you signal routing look like? Do you have a single AES source or multiple? What are you trying to do with HQ Player?Michael,
Thanks - that all makes sense, I'll persevere. I've managed to get rid of the ls mismatch error on the dac and the hqplayer log says its playing but no sound. I'm not to familiar with CamillaDSP (although had a quick look through) - but do you need to set the DAC up as a separate input and output?
Matt
---
devices:
samplerate: 96000
chunksize: 2048
silence_threshold: -100
silence_timeout: 5.0
capture:
type: Alsa
channels: 8
device: "hw:DAC8PRO"
format: S32LE
playback:
type: Alsa
channels: 8
device: "hw:DAC8PRO"
format: S32LE
Thank you so much I'm working through.What does you signal routing look like? Do you have a single AES source or multiple? What are you trying to do with HQ Player?
I would probably try to see if you can get the DAC to work in Pure USB mode (playing a file from your computer) as that eliminates the complications with the AES routing and then work from there.
I assume you are not using CamillaDSP? In CamillaDSP an AES/USB setup will specify the DAC8 as the capture and playback device, for reference this is the start of my CamillaDSP configuration file. Maybe one thing to look out for is that at least in my setup which only has 2 input channels (and 8 output channels) I need to specify that 8 input channels are available or it does not work (I setup my CamillaDSP mixer so that I router channels 1/2 where they need to go).
Code:--- devices: samplerate: 96000 chunksize: 2048 silence_threshold: -100 silence_timeout: 5.0 capture: type: Alsa channels: 8 device: "hw:DAC8PRO" format: S32LE playback: type: Alsa channels: 8 device: "hw:DAC8PRO" format: S32LE
Michael
Thanks again and sorry for the radio silence. It may be the firmware (given posts from @dualazmak, @Zooqu1ko and @Burki) - it doesn't look like I'm getting any digital output either from AES or USB which is a pain.Thank you so much I'm working through.
Still no plan for a firmware update ?Although I assume all of you are well aware of, let me remind you of this;
https://www.audiosciencereview.com/forum/index.php?threads/okto-8-owner’s-thread.13899/post-914295
saying;
Apparently, there's a bug in some firmware revisions that causes the AES/EBU out to transmit only zeroes. It'll be fixed in future firmware versions, and he says he'll "attempt to release an update for the existing units".
Fortunately, my DAC8PRO (firmware ver. 1.32) works perfectly for AES/EBU digital output (intact digital out of through CH1+CH2) in Pure USB Mode as shared here in my thread.
2 years later, still no firmware update for existing owners.What firmware are you on? What does your signal routing look like? I haven’t heard of anyone having issues with USB or AES input, just AES output.
Michael
Still no plan for a firmware update ?
...
2 years later, still no firmware update for existing owners.
Very sad.
I'd say there are plans, but the practical execution isn't there yet. It's probably not trivial to implement a firmware update process that can be safely recovered in case of failure, especially if the bootloader of the units out in the field does not yet provide such a mechanism, and there's no "consumer" interface that could be used for a simple recovery process (except, of course the AES inputs - playing back audio to upgrade or recover the firmware would be interesting, extra points if it's steganographically hidden in a piece of music)Still no plan for a firmware update ?
2 years later, still no firmware update for existing owners.
Very sad.
Most manufacturers seem happy to use the XMOS example code for firmware updates. More details in an earlier postI'd say there are plans, but the practical execution isn't there yet. It's probably not trivial to implement a firmware update process that can be safely recovered in case of failure, especially if the bootloader of the units out in the field does not yet provide such a mechanism, and there's no "consumer" interface that could be used for a simple recovery process (except, of course the AES inputs - playing back audio to upgrade or recover the firmware would be interesting, extra points if it's steganographically hidden in a piece of music)
I also updated my firmware as well using a tool Pavel sent me.Didn’t @Burning Sounds mention that he updated his firmware earlier in this thread? Or maybe he got a new unit with new firmware?
Michael