E1DA Cosmos ADC

[johny_2000]

Cosmos ADC works without Comtrue driver, if you need to install the Comtrue driver you probably want to reflash some FW. I don't know.

Thank you! I'll check/compare this with your screenshot of the driver name/version when I get back to my workstation. Maybe tomorrow.

Simply put, I don't care whether I work with or without a Comtrue driver, as long as it works properly.
Now (without the ComTru driver) I am having difficulty switching the device to Stereo mode from the default Mono mode using the Windows volume slider.
REW has two modes of working with the device - Direct or Exclusive mode. I've tried both options. In an Exclusive mode, the device remains in Mono mode (and I need Stereo for measurements), except when I launch the Tweak app and manually move the slider to the 2CH position (maximum to the left). In direct mode, I tried to change the volume manually, and at first glance, switching to Stereo mode occurs at volume values less than 18, but the output data from the ADC is somehow strange. The noise level is elevated (approximately -40-45 dB floor), and the measured signal values are +2...+3 dB from the actual one.

 

[phofman]

REW has two modes of working with the device - Direct or Exclusive mode

The "direct" mode as you call it is standard windows audio through the windows mixer. The mixer does all sorts of changes to your stream. That's why you get different results compared to the Wasapi Exclusive mode which talks directly with the soundcard driver.

 

[pma]

REW in “Java direct” mode works with only 16 bit resolution. It is usable for speaker measurements, but unusable for amplifier measurements.

 

[staticV3]

If we ignore the iAP device (note: I don't like it when any device on my computer has driver problems), then which device name do I need to select to install the driver manually?

You do not need to select any device name to install the driver.

The driver is downloaded as an .exe package.

Double-click the .exe and it'll guide you through the install process.

After the installation is complete, the Cosmos ADC will automatically switch to this driver, without you having to select any device name.

 

[johny_2000]

REW in “Java direct” mode works with only 16 bit resolution. It is usable for speaker measurements, but unusable for amplifier measurements.

Good to know. Thank you! Then I will only use Exclusive mode for my measurements.

 

[johny_2000]

You do not need to select any device name to install the driver.

The driver is downloaded as an .exe package.

Double-click the .exe and it'll guide you through the install process.

After the installation is complete, the Cosmos ADC will automatically switch to this driver, without you having to select any device name.

Thanks, staticV3. I did this yesterday and here are the results:

Pretty much the same results that charliecola described in his posts. Therefore, the only way to switch the operating mode (Mono <> Stereo) of the ADC is to use the Tweak app on the side of REW. And it will not remember the settings after turning off / restarting the computer.

 

[staticV3]

Pretty much the same results that @charliecola described in his posts. Therefore, the only way to switch the operating mode (Mono <> Stereo) of the ADC is to use the Tweak app on the side of REW. And it will not remember the settings after turning off / restarting the computer.

On two of my PCs, I can change between Mono, Stereo, and RIAA using the volume slider in the Sound Control Panel.

If I set the Cosmos to Stereo by setting the volume to <50, say 10, then the next time I turn on the PC, Windows will automatically restore the Cosmos volume to 10, putting it into Stereo mode.

 

[johny_2000]

On two of my PCs, I can change between Mono, Stereo, and RIAA using the volume slider in the Sound Control Panel.

If I set the Cosmos to Stereo by setting the volume to <50, say 10, then the next time I turn on the PC, Windows will automatically restore the Cosmos volume to 10, putting it into Stereo mode.

It's right. This is what I was looking for, but unfortunately I can't reproduce it on my two Win 10/11 computers. With the driver it is locked, the volume is set to zero 'decibels'. REW also reports this error. I may have to uninstall the Comtrue driver because without it the Win Volume slider works. The only thing that doesn't work is the firmware flashing tool, which I don't need right now.

It's possible that Comtrue drivers are not properly made or WHQL signed and are being blocked by the latest Windows updates. My computer systems are online and have the latest updates/patches.

 

[johny_2000]

I would happily run without the driver but then I don't get 32 bit throughput with the audio application.

I also wonder if this is true. I won't have 32-bit operations without ADC drivers?

 

[johny_2000]

Sure, I've described that here https://e1dashz.wixsite.com/index/cosmos-adc
I can make a special FW with fixed STEREO/MONO mode but why don't you reduce the volume of ADC instead?

Okay, this is a good idea in my opinion. I always prefer the default Stereo mode at power up. On rare occasions, I can reflash it to Mono mode as needed.

 

[johny_2000]

I checked, and the same driver SXW_setup_WHQL_20210429 works properly under Windows 7. Apparently, the ComTrue driver is not fully compatible with the latest versions of Windows 10/11 in terms of the volume slider, which is locked at 0.00 dB.

 

[staticV3]

I checked, and the same driver SXW_setup_WHQL_20210429 works properly under Windows 7. Apparently, the ComTrue driver is not fully compatible with the latest versions of Windows 10/11 in terms of the volume slider, which is locked at 0.00 dB.

Is ASIO4All installed on your system by any chance?

IIRC, there were cases where it bricked the volume control of USB devices and uninstalling it fixed the issue.

Maybe @IVX can recall more specific information.

 

[IVX]

I checked, and the same driver SXW_setup_WHQL_20210429 works properly under Windows 7. Apparently, the ComTrue driver is not fully compatible with the latest versions of Windows 10/11 in terms of the volume slider, which is locked at 0.00 dB.

please, make sure that the SXW_setup_WHQL_20210429 is installed, and Windows restarted. People use W10/W11, and the slider isn't blocked.

 

[johny_2000]

Is ASIO4All installed on your system by any chance?

That's a good point .

I don't have ASIO4All installed, but I have VB-Audio ASIO Bridge installed on both Win 10/11 computers. It does the same.

I have try to uninstall it, restart computer, install the ComTrue driver and restart again. I'll do it tomorrow. Thanks for idea!

 

[Grooved]

I don't have ASIO4All installed, but I have VB-Audio ASIO Bridge installed on both Win 10/11 computers. It does the same.

It does not do the same, it does the exact opposite

With ASIO4ALL, ASIO is used between software and ASIO4ALL (and WDM between ASIO4ALL and the audio interface)
With ASIO Bridge, ASIO is used between ASIO Bridge and the audio interface (and WDM between software and ASIO Bridge)

 

[johny_2000]

With ASIO4ALL, ASIO is used between software and ASIO4ALL (and WDM between ASIO4ALL and the audio interface)
With ASIO Bridge, ASIO is used between ASIO Bridge and the audio interface (and WDM between software and ASIO Bridge)

Thanks for clarifying. I haven't checked yet, but this is the only software that wasn't installed on the Win 7 machine, and I hope it was the one that did something weird with the volume control that staticV3 mentioned. It's worth trying to remove it and reinstall the driver.

 

[johny_2000]

Nope, uninstalling VB-Audio ASIO Bridge (and rebooting) didn't change anything. Volume with driver is locked at 0.0 dB. I'll keep looking. The reason is hidden somewhere in the features of Win 10. I saw similar questions from people with other sound recording devices.

Hint: Windows 10/11 Security may be involved in this issue.

SXW_setup_WHQL_20210429.exe Hybrid Analysis Spyware: Found a string that may be used as part of an injection method.

Risk Assessment:
Spyware:
- Found a string that may be used as part of an injection method
Persistence:
- Spawns a lot of processes
- Writes data to a remote process
Fingerprint:
- Queries kernel debugger information
- Queries the display settings of system associated file extensions
- Reads the active computer name
- Reads the cryptographic machine GUID
- Reads the windows installation language
Evasive:
- Marks file for deletion
This report has 19 indicators that were mapped to 13 attack techniques and 6 tactics.

 

[johny_2000]

After fiddling with the driver so much, I suddenly installed it correctly under Windows 10.

The only difference I did this time was that I right-clicked on the file "SXW_setup_WHQL_20210429.exe" and selected "Run as administrator", after which the OS gave me a message saying that the system has an old version installed driver and must be uninstalled first. I don't know why it decided this, but anyway I continue with the suggested uninstall process, then it required a reboot. After rebooting I right clicked on the file "SXW_setup_WHQL_20210429.exe" and again select "Run as administrator" and this time it just installed the driver and rebooted again.

After this, to my surprise, the driver installed correctly and the Windows volume slider works! with the ComTrue driver installed. And no more dB units, only 1...100.
Hope this helps other users solve this problem.

 

[danadam]

Does anyone has the USB cable with screw for ADCiso? I bought one but it looks like the hole in the case is too big and the screw just passes through.

 

[restorer-john]

I bought one but it looks like the hole in the case is too big and the screw just passes through.

Maybe you need to glue a nut on the back (inside)?