Hi,
can anyone specify a rough 'guide' or give 'instructions' on how to configure the combo384 for a shorter word length compared to the default of 32 bits? I downloaded the OEMtool 1.17 (which seems to be the latest). I don't know my firmware version will permit me to use my combo384 with the OEMtool. The board came shipped with the Rev F datasheet (4/09/2013). Thank you in advance to anyone who can advise!
can anyone specify a rough 'guide' or give 'instructions' on how to configure the combo384 for a shorter word length compared to the default of 32 bits? I downloaded the OEMtool 1.17 (which seems to be the latest). I don't know my firmware version will permit me to use my combo384 with the OEMtool. The board came shipped with the Rev F datasheet (4/09/2013). Thank you in advance to anyone who can advise!
Hi everyone,
I also have a problem configuring the Combo384. On the OEMtool 1.15, in the configuration bits panel, I select 24Bit as word lenght as well as DSD channel swap function and then press "write flash". A confirmation message appears saying "Flash Updated!" but as I connect the Combo384 back to my MacMini the interface is still recognized as 32Bit.
I also tried selecting the the 24Bit option before doing a complete refresh of both CPU and CPLD firmwares but I get the same thing. Another user from this forum had the same problem as well as Mikeg88.. I might just write Domenico, hopefully he would know the way around it.
Cheers,
Alex
can we do to the value of F0 .. F3 feet set in oemtools check buttons, much like in this picture:
http://www.7image.ru/pics/0714/452732684.png
It is desirable also for the input bit depth make a choice (16/24/32 bit) ....
I have a DAC and there ad1853 mode selection DF done with 2 jumpers - it would be very convenient to use ....
http://www.7image.ru/pics/0714/452732684.png
It is desirable also for the input bit depth make a choice (16/24/32 bit) ....
I have a DAC and there ad1853 mode selection DF done with 2 jumpers - it would be very convenient to use ....
can we do to the value of F0 .. F3 feet set in oemtools check buttons, much like in this picture:
http://www.7image.ru/pics/0714/452732684.png
It is desirable also for the input bit depth make a choice (16/24/32 bit) ....
I have a DAC and there ad1853 mode selection DF done with 2 jumpers - it would be very convenient to use ....
http://www.7image.ru/pics/0714/452732684.png
It is desirable also for the input bit depth make a choice (16/24/32 bit) ....
I have a DAC and there ad1853 mode selection DF done with 2 jumpers - it would be very convenient to use ....
One option is removing L1 and inset 5V DC, another option is removering U2 and insert 3.3V DC.
If You have a 3.3V power supply there are better than the onboard ADP151 regulator use that.
http://amanero.com/USB_E.pdf
If You have a 3.3V power supply there are better than the onboard ADP151 regulator use that.
http://amanero.com/USB_E.pdf
Need more info... photos maybe ...
Did you check outputs on Amanero or Buffalo III?
Sync or async(with default onboard 100 MHz)?
Ok, I think I have an answer for you, Alex. I PM'ed ACKO and he pointed out that even when you set the configuration bit for '24 bits' in the OEM tool, the combo384 appends 8 zeros to the word length. 24+8=32...so you have 24-bit audio samples, 'contained' in 32-bits (this is also evidenced by the '64fs' text adjacent to the selector for 24-bits in the configuration panel).
I think that's then explanation for why your combo384's output is recognized as 32 bit. So if you're like me, and your other audio system components (DAC, SRC, etc.) can't take 32 bits, then you're screwed and you need to abandon the combo384 and find an alternative.
One other work-around would be to use the combo384 in 16bit output mode, but I think that's not really any good - it wouldn't permit me to play my higher-res audio material, and there are much cheaper alternatives to the combo384 if all you need is 16 bits anyways.
I'm considering the audio widget from QNKTC (a.k.a. Borge Strand-Bergesen), or the XMOS-based board from DIYINHK.
I had a similar problem, to me it was a software problem.
Are You using the latest firmware for CPLD , CPU and Device Drivers.
Is the problem with WASAPI and/or ASIO.
Have You tried another audio player instead of foobar.
Thanks for the suggestions!
I have flashed the latest firmware.
I have done a fresh install on another PC.
I have tried different music players, WASAPI/KS/DS/ASIO, and still nothing - the player either becomes unresponsive, or "plays" the entire song in 2 seconds.
I will try to contact the guys at Amanero Tech...
I have flashed the latest firmware.
I have done a fresh install on another PC.
I have tried different music players, WASAPI/KS/DS/ASIO, and still nothing - the player either becomes unresponsive, or "plays" the entire song in 2 seconds.
I will try to contact the guys at Amanero Tech...
Thanks for the suggestions!
I have flashed the latest firmware.
I have done a fresh install on another PC.
I have tried different music players, WASAPI/KS/DS/ASIO, and still nothing - the player either becomes unresponsive, or "plays" the entire song in 2 seconds.
I will try to contact the guys at Amanero Tech...
Can you check 3.3V power supply?
I've had similar experience when I used synchronous mode with Acko's boards. CPLD_for_1080 and CPU firmware_1080 is the only combination of firmwares that should be used with BIII. Right after the flashing, amanero should be in the default mode of using it's onboard oscillators. Don't touch anything else in the ConfigTool. If you flashed some CPLD slave firmware the default is slave mode and selecting or deselecting slave check box is irrelevant.
If you were, maybe, carried away with configuration bits, namely slave mode, then amanero expects external clock, which should be enabled by providing corresponding pin clock selector signal to the oscillators on Acko's (or similar) board which you don't have (connected).
When fiddling with configuration bits please do reconnect USB cable.
Last edited: