DAWs

Configure ASIO4ALL inputs and outputs in Cubase

Changing the ASIO driver in Cubase can leave a project’s existing buses pointing to ports from the previous device. Configure ASIO4ALL in Studio Setup and then verify the bus assignments in Audio Connections. With both in place, Cubase can send playback to your headphones and record from the intended input.

Composition studio with MIDI piano keyboard, laptop showing blurred horizontal multitrack recording lanes and headphones
In this guide

How to set up ASIO4ALL in Cubase

To use ASIO4ALL in Cubase, open Studio › Studio Setup › Audio System, choose ASIO4ALL v2 as the ASIO driver and enable your input and output in the ASIO4ALL control panel. Then press F4 to open Audio Connections and point the project's stereo output bus and any input buses at the real device ports. Finish with a short playback and recording test before you start a real session.

The driver selection and the bus routing are two separate jobs. Cubase remembers bus assignments per project, so switching drivers can leave an older project pointing at ports that no longer exist. Most "Cubase is silent with ASIO4ALL" reports come down to that second step rather than the driver itself.

What you need before you start

  • Cubase installed on Windows 10 or Windows 11. ASIO4ALL is Windows only.
  • ASIO4ALL v2 installed from the official installer, currently ASIO4ALL_2_22.exe from asio4all.org.
  • Headphones or speakers connected to a device that already plays sound in Windows.
  • Optionally, a microphone or instrument input you want to record from.

Tip: Save your project before switching drivers. The available port names and channel count can change as soon as you select a different driver, and you want an easy way back.

How ASIO4ALL fits into Cubase

Cubase talks to audio hardware through ASIO drivers. Many built-in laptop sound chips, USB microphones and budget USB headsets do not ship with an ASIO driver of their own. ASIO4ALL is a universal ASIO driver that sits on top of the existing Windows WDM drivers and presents those devices to Cubase as one ASIO device.

Inside Cubase it appears as ASIO4ALL v2. Whatever inputs and outputs you enable in its control panel become the device ports Cubase can see. If a port is not enabled in ASIO4ALL, Cubase cannot route to it, no matter how you configure the project.

Three layers to keep in mind

  • Windows: the physical device must work and must not be held exclusively by another app.
  • ASIO4ALL: the right inputs and outputs must be enabled, with a sensible buffer size.
  • Cubase: buses in Audio Connections must map to the ports ASIO4ALL exposes, and tracks must use those buses.

Working through these layers in order is the fastest way to a working setup and the fastest way to troubleshoot later.

Select ASIO4ALL in Cubase Studio Setup

The Audio System page in current Cubase versions is where you select the driver. Older versions may label the page VST Audio System. The steps below follow the current layout described in the Cubase Pro 15 manual for setting up audio hardware.

  1. Save the current project, or start with an empty one.
  2. In Cubase for Windows, open Studio › Studio Setup and choose Audio System in the Devices list.
  3. Select ASIO4ALL v2 in the ASIO Driver menu. Confirm the switch if Cubase asks.
  4. Choose the driver entry that now appears below Audio System in the Devices list and click Control Panel.
  5. In the ASIO4ALL panel, enable your playback output and any input you plan to record. Start with one audio device if it has both connections.
  6. Close the panel, click Apply and then OK in Studio Setup.

Choosing devices in the ASIO4ALL panel

The panel lists the WDM devices Windows exposes. Each device has a power button style toggle. In advanced mode you can expand a device and enable individual inputs or outputs, which is useful when a laptop offers several capture sources but you only want one.

Keeping both input and output on one device is the most reliable choice. Combining a USB microphone with laptop headphones is possible, but the two devices run on separate clocks. The device aggregation guide covers when that is worth doing and what to watch for.

The ASIO4ALL manual on connecting a DAW explains that the control panel is opened from the host. Open it from Cubase rather than looking for a separate standalone app.

Assign the actual ports to project buses

Press F4 to open Audio Connections using the default shortcut. This window has separate tabs for Inputs and Outputs, and each bus has a Device Port column showing which ASIO4ALL channel it uses. The Cubase Pro 15 manual for assigning input and output buses describes the window in detail.

Outputs

Under Outputs, look at the Device Port entries for your stereo bus. Assign the left and right channels to the playback pair that reaches your speakers or headphones. With a typical laptop or headset there is only one stereo pair, so this is usually ports 1 and 2 of the enabled output.

Inputs

Under Inputs, add a mono bus for one microphone if the project needs it and select its matching device port. A voice or instrument microphone is a single channel, so a mono bus avoids recording an empty second channel. Add a stereo input bus only if you are capturing a genuinely stereo source.

Typical Cubase bus layout for common ASIO4ALL setups
SetupOutput busInput bus
Laptop speakers or headphone jackStereo Out to the laptop output pairNone, or mono from the built-in mic for quick tests
USB microphone with headphone jackStereo Out to the microphone's playback pairMono In to the microphone's capture channel
USB mic plus laptop headphonesStereo Out to the laptop output pairMono In to the USB mic channel
Small USB interface without its own ASIO driverStereo Out to outputs 1 and 2Mono In per microphone or instrument input

Existing projects after a driver switch

In an existing project, inspect buses marked Not Connected after the driver switch. Reassign each one to a valid ASIO4ALL port or remove buses you no longer need. Save an updated bus preset if you expect to reuse the same hardware configuration, so the next project can load the correct routing in one click.

Verify playback and recording with a simple project

Test with a nearly empty project first. If something fails here, the cause is in the driver or routing rather than in plug-ins or a heavy session.

  1. Create an empty project and import a short audio clip you know plays correctly elsewhere.
  2. Make sure the clip's track outputs to the Stereo Out bus, then press play and listen.
  3. Add a mono audio track and choose your mono input bus in the track's input routing.
  4. Arm the track and speak or play. Confirm that its meter responds.
  5. Record ten seconds, stop, disarm the track and play the recording back.

Play a known clip through the stereo output to check playback separately from recording. If the clip plays but the recording is silent, the problem is on the input side. If the recording meter moved and the file contains audio but you hear nothing, the problem is on the output side.

Tip: Turn off the track's monitor button after the test. Monitoring through ASIO4ALL adds the buffer delay to what you hear, which can feel like an echo when you speak into the mic.

Fix routing before adjusting latency

When the track meter moves and there is silence, first check the track's output bus, the stereo bus's device ports and the physical headphone or speaker connection. If your edition uses Control Room to monitor, verify the monitor port in Audio Connections as part of the same check. A Control Room assigned to a port that no longer exists can mute everything you hear even though the Stereo Out meter is moving.

Quick silence checklist

  • Is the output enabled and active in the ASIO4ALL panel?
  • Does the Stereo Out bus show real device ports, not Not Connected?
  • Is the track routed to Stereo Out, and is nothing muted?
  • Is another application, such as a browser or video call, still holding the device?
  • Are the headphones plugged into the device you actually enabled?

If these all check out and you still hear nothing, the no sound troubleshooting guide walks through device states such as unavailable outputs in more depth.

Matching the sample rate

Cubase sets the sample rate per project in Project › Project Setup. If the project rate differs from what the device supports or what Windows has configured, you may hear silence, wrong pitch or errors on playback. Keep the project at a rate the device supports, usually 44.1 kHz or 48 kHz. The sample rate guide explains how ASIO4ALL handles rate changes.

Tune the ASIO4ALL buffer in Cubase

Once a short recording plays back cleanly, use the ASIO4ALL panel to tune the buffer. Open it from Studio › Studio Setup via the driver's Control Panel button. Smaller buffers lower latency but give the computer less time to process each block of audio. Larger buffers are more stable but add delay.

The delay for one buffer is samples divided by sample rate, multiplied by 1000. Cubase also displays the reported input and output latency on the driver page, which is a useful cross-check.

Buffer size and one-way buffer latency at common sample rates
Buffer (samples)At 44.1 kHzAt 48 kHzTypical use in Cubase
128about 2.9 msabout 2.7 msTracking with live monitoring on a light project
256about 5.8 msabout 5.3 msGeneral recording and editing
512about 11.6 msabout 10.7 msMixing dense sessions with many plug-ins
1024about 23.2 msabout 21.3 msFinal mixdown when dropouts persist

Try a larger setting for dense sessions with dropouts. Cubase's Audio Performance meter, opened with F12 by default, helps you see whether the session is hitting its real-time limit. The ASIO4ALL buffer size guide covers the trade-offs in more detail.

Watch out: Cubase holds the ASIO device while it is open. If you want to play audio from another application at the same time, check the option on the Audio System page that releases the driver when Cubase is in the background, or close Cubase first.

When a vendor driver is the better choice

If an interface manufacturer supplies a current ASIO driver for your model, check that driver when the session needs more hardware inputs or vendor-specific routing. Native drivers often expose features such as direct monitoring mixers that ASIO4ALL cannot reach. The ASIO4ALL vs native ASIO comparison explains how to decide.

Frequently asked questions

Make sure ASIO4ALL is installed and restart Cubase after installation so it rescans drivers. On Windows on Arm, version 2.22 adds native ARM64 and ARM64EC support, so use the current installer from asio4all.org rather than an old copy.

Yes. ASIO4ALL is free for end users, including commercial audio work. The publisher restricts resale and bundling, which affects distributors rather than people using it to make music or podcasts.

The project still expects the port names of the previous driver. Open Audio Connections with F4, assign each bus to an enabled ASIO4ALL port and save a bus preset so future projects load the correct routing.

Start at 256 samples, which is about 5.3 ms at 48 kHz. Drop to 128 for tracking if playback stays clean, and raise it to 512 or higher when mixing a heavy session that crackles or drops out.

Sources and further reading

ASIO4ALL Editorial Team

We write expert, hands-on guides for Windows musicians, podcasters and producers. Driver facts are checked against the publisher's manual and release notes; DAW steps against each vendor's documentation.