Skip to main content
F
florianklan
Participant
March 15, 2021
質問

Rode AI-1 ASIO driver only works at a Sample Rate of 48000 Hz (in Audition 13.0.13, 14.0 and Betas)

  • March 15, 2021
  • 返信数 1.
  • 8920 ビュー

Hi there,

I've recently bought a Rode Complete Studio Kit that includes the AI-1 Interface. While it has excellent preamps and works well using MME and WASAPI drivers, on my fully updated Windows 10 (20H2) machine, Rode's ASIO drivers do only work at a Sample Rate of 48000 Hz in Audition. As soon as I change the Sample Rate to any other value, Audition tells me that the "device could not be opened".

The error occurs in Audition 13.0.13, 14.0 and the current Beta version – it occurs regardless of whether I check "Use machine-specific device defaults" and if I attempt to force the hardware to the document's Sample Rate, I end up with the driver running at 48000 Hz anyway (with no audio being recorded above 24 kHz, even though it should, had forcing the hardware actually succeded). The Sample Rate settings in Windows for input and playback devices do not affect the error at all. It's also worth noting that the exact same thing happens if I try the same settings in Adobe Premiere, which I assume is due to Premiere using the same audio engine?

Interestingly enough, the driver works at 96 kHz in Ableton Live 10 Lite that came with the Rode's kit, which basically rules out a hardware fault. I've also already tried different USB ports, cables, Windows user accounts, usb hubs, motherboard drivers and so on. So far, nothing has helped. 

I'm running a Ryzen 3900X build with a Gigabyte X570 Aorus Master motherboard and the latest chipset drivers.

Kind Regards

 

このトピックへの返信は締め切られました。

返信数 1

SteveG_AudioMasters_
Community Expert
SteveG_AudioMasters_Community Expert
Community Expert
March 15, 2021

First thing to try is putting a check in that box immediately above your warning message - the one about attempting to force the hardware to the document sample rate. That generally does it...

F
florianklan作成者
Participant
March 16, 2021

Thank you very much for your input, Steve! Unfortunately, putting a check in that box does only lead to a recording that does not contain any audio above 22 kHz (not even noise), meaning that it seems as if the interface merely records at a Sampling Rate of 44,1 or 48 kHz in a file that is set to 96 kHz. In addition to that, the setting does not persist, but has to be set every time I launch Audition. Reinstalling Audition also hasn't helped in that regard.

B
Bidhan Chandra5E15
Participant
October 23, 2021

Thanks again for your input, Steve! I've come to the conclusion that the ADC does in fact not run at 96 kHz if I put a checkbox in the "Attempt to force hardware to document sample rate" because of the following findings:
1.) If I record with my NT1 (using my AI-1 interface) at a sample rate of 96 kHz using Windows MME drivers, peaks reach up to 38 kHz (even though nobody is going to hear it, but Audition certainly can display it using the frequency plot)

[ Take a look at the right portion of the recording in the screenshot ]
2.) If I use the AI-1 ASIO driver with the checkbox, nothing is recorded, in the frequency range beyond 22 kHz... not even ADC noise. [ see the left portion of the recording in the screenshot ]

3.) If I run the AI-1 ASIO driver at 48000 kHz and record into a 96 kHz file, I get the exact same results as in 2.)

 

Due to Shannon-Nyquist-Limit and the design of the drivers, there cannot be anything above 22 to 24 kHz if the ADC does not run at a higher sampling rate. In addition to that, setting anything but 48 kHz in the device settings in Audition gives a "(not working)" message for the AI-1 ASIO driver.

 

 


Hello, my self bidhan from india, i also use adobe audition and rode NT1 and AI1 inerface, now when i select ASIO in device class and select RODE AI-1 ASIO in device and when i am changing sample rate 48000 to 44100 it says the device couldnt be opened. Now if I select MME in device class, then everything is working fine. It is my request to all the senior members please help if anyone knows regarding this issue. I am glad and lucky i found this community to ask question.

契約条件Accessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices