• WANTED: Happy members who like to discuss audio and other topics related to our interest. Desire to learn and share knowledge of science required. 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!

E1DA Cosmos ADC

Nice! A bit limited by the modulation at higher frequencies. Can we expect a future FW update to fix this? ;)
This is HW issue, Cosmos ADC utilizes CT7601C with 384k limit, I just did correct the source code to deceive the descriptor forming but the USB bridge is slower than it should be for 768k. To get Cosmos ADC to work at 768k better you need to replace the USB bridge IC CT7601CR to CT7601PR and use the FW I introduced today.
 
Guys, I have an interesting and I bet unexpecting update for the Cosmos ADC ;) I found that just by the new FW is possible to expand the sampling frequency up to 768kHz.
Add a little more and you're making it Oscilloscope. :) I wonder how much it'll cost a 32-bits @ 1 MHz scope...

Now seriously, great work @IVX, I'm sure more and more customers will appreciate your efforts and this very well designed ADC. Good finding @staticV3!
 
This is HW issue, Cosmos ADC utilizes CT7601C with 384k limit, I just did correct the source code to deceive the descriptor forming but the USB bridge is slower than it should be for 768k. To get Cosmos ADC to work at 768k better you need to replace the USB bridge IC CT7601CR to CT7601PR and use the FW I introduced today.
Since this great software tweak/upgrade is in place will you maybe consider to use the CT7601PR in future Cosmos ADC versions? I am right now thinking about a second ADC to buy but maybe i should be a bit patient (until u have used all your CT7601CR Stock) and then I could take advantage of a improved ADC version? This CT7601PR chip is also not a typical candidate to buy easily in a shop over here in Europe.

Is in Your opinion the CT7601CR a "lower grade" selected CT7601PR , which just not meeting the best spec (meaning they come form the same silicon wafer) or is it probably a completely different silicon? In the first case some of us might be lucky that the CR might almost perform like a PR?

many regards from germany!
 
https://e1dashz.wixsite.com/index/cosmos-adc contains the updated firmware too, for those trying to make use of the latest experimental firmware with RIAA and 768 KHz support.

Some issues I encountered in the past: https://www.audiosciencereview.com/forum/index.php?threads/e1da-cosmos-adc.27038/page-8#post-962327, although today I have no issues, see below snip:

E1DA_Cosmos-Firmware_V13_RIAA_768.png

@IVX, I guess the "Verifying Success" means that the latest fw has been applied, right? However, I can't see the 768 kHz in the Windows Sound system, so is there anything I need to perform?

Also, regarding the below screenshot, I guess the slider in the middle now, but not sure if this means RIAA is enabled...or is it?

E1DA_Cosmos_Tweak-TRLsSeetings.png
 

Attachments

  • E1DA_Cosmos-Firmware_V13_RIAA_768.png
    E1DA_Cosmos-Firmware_V13_RIAA_768.png
    27.6 KB · Views: 67
Last edited:
Last edited:
Last edited:
trl, better to use the Windows ADC Volume slider to control that because Windows will send UAC2 commands at every start of the PC, and the Tweak setting will be overridden.
audio1234, I can make the next batch of Cosmos ADC with CT7601PR but not sure if it's really needed. Look, CT7601CR makes some extra wide-band noise at 768k(FFT spikes at >200k will be the same, it is about ES9822 noise-shaper) but who needs to measure the noise level higher than 20k, or Ok, 100k? Harmonics look the same, whatever, 768 or 384k, so you can investigate THD at higher frequencies. CT7601PR is more expensive, actually, I don't know how much that is today but for my 9038D6K DAC I buying opamps for 5x prices i.e. the silicon crisis is still here. Hence, Cosmos ADC with CT7601PR would be more expensive but practically will not give you anything else.
phofman, I didn't try that REW version yet.
 
pkane, because of the Volume curves are different Win vs Mac. I did adjust that at Win10 45..55% of the slider.
BTW, people already asking me if they need to replace the USB bridge IC for the faster CT7601PR to get 768k operation?
The answer is No! You need the only reflash Cosmos ADC with the new FW, that's it. This is 100% FW solution and 100% free.
 
pkane, because of the Volume curves are different Win vs Mac. I did adjust that at Win10 45..55% of the slider.
BTW, people already asking me if they need to replace the USB bridge IC for the faster CT7601PR to get 768k operation?
The answer is No! You need the only reflash Cosmos ADC with the new FW, that's it. This is 100% FW solution and 100% free.

I haven't tested the new FW on Windows yet, maybe tomorrow :) I do see the 705.6k and 768k rates in the MIDI setup app.

RIAA EQ looks like this @192k:

1665278595303.png
 
  • Like
Reactions: trl
RIAA curves are correct from 44.1k to 384k, 705-768k RIAA is not implemented.
BTW, I did add there 20Hz 2ord HPF as a subsonic but on the fixed Fs=384k, i.e. at 192k the HPF cuts <10Hz, at 48k cuts <5Hz. I guess RIAA users will go with 384k
to ripping their LPs in most cases, so they will get a normal subsonic filter then. If they don't want that filter, just go 192K or 48K and HPF will cut lower than audio range freqs.
2022-10-09_09-33-48.jpg
 
Last edited:
@IVX and @pkane, I eas referring to the E1DA_Cosmos_Tweak slider, see the screenshot from few posts above. Slider is at -40 dB, is this OK to enable the RIAA curve?
 
  • Like
Reactions: pma
"Java" is REW's name for javasound API, part of OpenJDK, the main java distribution. The javasound API links to native libraries shipped in OpenJDK builds for various OSes - the native library in OSX OpenJDK build uses coreaudio devices https://github.com/openjdk/jdk/tree...e428/src/java.desktop/macosx/native/libjsound , in linux it uses alsa hw devices (no PCM devices) https://github.com/openjdk/jdk/tree...de428/src/java.desktop/linux/native/libjsound , in windows it uses DirectSound https://github.com/openjdk/jdk/tree...428/src/java.desktop/windows/native/libjsound .
Fortunately javasound can be extended with external SPI providers https://www.baeldung.com/java-spi implementing the javasound API which can link to custom native libraries. The latest REW is shipped with my CleanSine javasound provider https://github.com/pavhofman/csjsound-provider which on windows links to WASAPI exclusive native library (DLL) https://github.com/pavhofman/csjsound-wasapi (devices provided by that provider are prefixed with "EXCL:" in the REW device list). On amd64 linux it links to ALSA PCM native library (.so) https://github.com/pavhofman/csjsound-alsapcm (devices prefixed with "PCM:") which offers custom PCM devices defined in .asoundrc configs.

ASIO due to its duplex bufferSwitch callback is largely incompatible with the javasound API (which uses independent playback and capture devices), therefore the third-party java ASIO connector has its own java API https://github.com/mhroth/jasiohost . John Mulcahy, when incorporating this API into REW, had to add a selector for which java audio API to use, present only in the windows build of REW. Since the added WASAPI exclusive/ALSA PCM provider implements the stock javasound API, the devices discovered by wasapi exclusive/ALSA PCM are listed under the java API selector, named appropriately.
 
"Java" is REW's name for javasound API, part of OpenJDK, the main java distribution. The javasound API links to native libraries shipped in OpenJDK builds for various OSes - the native library in OSX OpenJDK build uses coreaudio devices https://github.com/openjdk/jdk/tree...e428/src/java.desktop/macosx/native/libjsound , in linux it uses alsa hw devices (no PCM devices) https://github.com/openjdk/jdk/tree...de428/src/java.desktop/linux/native/libjsound , in windows it uses DirectSound https://github.com/openjdk/jdk/tree...428/src/java.desktop/windows/native/libjsound .
Fortunately javasound can be extended with external SPI providers https://www.baeldung.com/java-spi implementing the javasound API which can link to custom native libraries. The latest REW is shipped with my CleanSine javasound provider https://github.com/pavhofman/csjsound-provider which on windows links to WASAPI exclusive native library (DLL) https://github.com/pavhofman/csjsound-wasapi (devices provided by that provider are prefixed with "EXCL:" in the REW device list). On amd64 linux it links to ALSA PCM native library (.so) https://github.com/pavhofman/csjsound-alsapcm (devices prefixed with "PCM:") which offers custom PCM devices defined in .asoundrc configs.

ASIO due to its duplex bufferSwitch callback is largely incompatible with the javasound API (which uses independent playback and capture devices), therefore the third-party java ASIO connector has its own java API https://github.com/mhroth/jasiohost . John Mulcahy, when incorporating this API into REW, had to add a selector for which java audio API to use, present only in the windows build of REW. Since the added WASAPI exclusive/ALSA PCM provider implements the stock javasound API, the devices discovered by wasapi exclusive/ALSA PCM are listed under the java API selector, named appropriately.

Is there any chance of supporting more than 192k under MacOS (@JohnPM)? I can see all the sample rates up to 768k in MIDI Setup app, but inside REW, I get only up to 192k:

1665332881920.png

1665333212014.png
 
Last edited:
Back
Top Bottom