Skip to main content

Troubleshooting

If iD2 does not behave as expected, work through the relevant checks below in order. Begin with the physical connections and the selected input or output before changing advanced settings. For further help, visit https://support.audient.com.

iD2 does not power on​

  1. Check that the USB-C cable is securely connected to the COMPUTER port on iD2 and to a working USB port on the computer.
  2. If the interface remains unresponsive, disconnect and reconnect its USB connection and allow it to initialise.
  3. Try a different known-good USB cable or computer USB port if available. For testing, connect the interface directly rather than through a hub or dock.
  4. If the computer's USB connection cannot provide sufficient power, use the ALT POWER USB-C port for supplementary power. ALT POWER carries power only, not audio or control data.
  5. If the interface still does not initialise, contact Audient Support.

iD2 is not recognised by the computer or iD Control​

  1. Check that the cable is connected to the COMPUTER port, not the ALT POWER port.
  2. Open iD Control and confirm that the correct interface is connected. Complete installation of the Audient Control Software Installer from your registered product in ARC if required.
  3. Close and reopen iD Control. If the interface remains unavailable, restart the computer and try again.
  4. In your DAW's audio preferences, select iD2 as the input and output device. On Windows, use the Audient ASIO driver; on macOS, select iD2 as the Core Audio device.
  5. Try a direct USB connection and a known-good cable to rule out a connection issue.

A microphone or instrument is not reaching the DAW​

  1. Check the cable and the intended physical input. The two Mic/Line sockets record on Inputs 1–2. Connecting an instrument to the JFET socket takes the place of Mic/Line Input 1.
  2. For a microphone that requires phantom power, select its Mic/Line channel and enable +48 V. Check the microphone manufacturer's requirements before switching phantom power on.
  3. Set Input Gain manually or use Smartgain, and check that the relevant input meter shows activity. Raising the monitor mix fader will not increase the level recorded by the DAW.
  4. In the DAW, select the correct iD2 hardware input on a mono audio track, enable recording and check the track's input meter.
  5. If the iD Control input meter shows signal but the DAW does not, check the DAW's audio-device selection, track input assignment and recording settings.

No sound from the speakers or headphones​

  1. Start with the output level turned down and check that the speakers or headphones are connected to the intended sockets. Raise the listening level gradually.
  2. Check Global Mute, individual output Mute states and the selected Main/ALT speaker destination in iD Control.
  3. Both headphone sockets share the HP1 path. Select HP1 and check its volume, source selection and Mute state in iD Control.
  4. In iD Control, check that the required input or computer playback channel reaches the selected monitor mix and is not muted or turned down.
  5. If using ALT speakers or an Independent Mix, check that the correct output or headphone source is selected and that the mix is receiving audio.

DAW playback cannot be heard​

  1. In the DAW, select iD2 as the playback device and check the stereo output assignment of the track or master bus.
  2. Start playback and confirm that the relevant computer-playback or Virtual channels in the iD Control Mixer show a signal.
  3. Check their faders, Mute states and the selected listening mix. The DAW may be playing correctly even if that playback is not included in the monitor mix.
  4. Check the active monitor or headphone output level and its destination. If you have selected an Independent Mix or direct Host playback for a headphone output, check that source independently.

Monitoring sounds doubled or delayed​

  1. Check whether the live input is being heard both through the iD Control Mixer and through software monitoring in the DAW.
  2. For low-latency monitoring through iD Control, disable the DAW's input-monitoring path for that track while leaving recording armed.
  3. If you intentionally need to hear DAW plug-ins while performing, monitor through the DAW instead and use an appropriately low, stable audio buffer size.

The signal clips, distorts or produces clicks​

  1. If an input is clipping, lower its Input Gain or repeat Smartgain while performing at the loudest expected level. Reducing the monitor fader will not repair an already clipped recording.
  2. If playback clicks or drops out during a demanding DAW session, increase the audio buffer size and test again.
  3. If the source uses optical digital audio, make sure that iD2 and the connected equipment have a compatible digital format, matching sample rates and one clock master. Check Digital I/O & Clocking.
  4. Check audio cables and monitor levels, and test the problem with a simple DAW session before adding plug-ins or extra equipment.

Smartgain does not produce the expected result​

  1. Select the intended analogue input channels before starting the measurement. Smartgain does not set the gain of computer-playback or Loopback channels or optical digital inputs.
  2. Allow the countdown to finish and perform at the loudest level you expect during recording.
  3. Check whether the result reports a successful or unsuccessful measurement. If necessary, use Retry Failed or repeat the measurement with a longer duration or a more suitable target level.
  4. If the input remains silent, check the physical input connection and microphone power before trying Smartgain again.

Loopback is silent or contains the wrong audio​

  1. In the DAW or streaming application, choose the stereo Loopback input: Inputs 11+12.
  2. Open Settings > Routing > Loopback Source in iD Control and choose the source you intend to record.
  3. If Main Mix is selected, remember that monitor level, Mute, Dim, Mono and RoomTune correction affect the Loopback feed. A muted Main Mix can therefore also produce silent Loopback.
  4. If Virtual Thru is selected, confirm that the computer application is playing to the Virtual Outputs selected as the Loopback source. Virtual Thru bypasses the iD Control Mixer.
  5. Do not send the live Loopback recording track back into the same source mix: this can create an audio feedback loop.

RoomTune cannot complete a measurement​

  1. Use the Audient RM1 measurement microphone and check the microphone setup and serial-number confirmation shown in RoomTune. The RM1 is sold separately from iD2.
  2. During automatic level setup, allow RoomTune to establish its 75 dB SPL measurement level. Do not change the hardware volume or input gain during the process.
  3. Follow the displayed microphone positions and hold the RM1 still while RoomTune measures. A complete measurement contains 26 positions.
  4. If the measurement is interrupted, use the available pause/resume instructions in RoomTune and complete the remaining positions before exporting the correction profile.

Optical digital inputs are silent or click​

  1. Check that the TOSLINK cable runs from the external device's digital output to iD2's optical input.
  2. Set the digital input to ADAT or optical S/PDIF to match the connected device, and use the same sample rate on both devices.
  3. Choose a single clock master. Because iD2 has an optical input but no digital or word-clock output, the external device must provide the clock signal. Set the external device to its internal clock and select Digital 1 in iD Control so that iD2 follows the incoming optical signal.
  4. If fewer ADAT channels appear than expected, check the sample rate. At 88.2/96 kHz the optical input supports up to four ADAT channels; at 176.4/192 kHz, up to two.
  5. Check that the DAW is using the correct digital input channel.

If the issue remains after these checks, contact Audient Support at https://support.audient.com with the interface model, computer operating system, iD Control version, DAW, connections used and a description of what you have already tried.