When a simple DaVinci Resolve export suddenly slows, check its selected audio devices and macOS device formats, then repeat the same short render. This controlled comparison can show whether the audio setup deserves further investigation before you change the edit.

This guide is for a Mac editor whose familiar timeline has become unexpectedly slow to export, especially after changing an interface, headphones or audio preferences. The Resolve controls below follow Blackmagic Design’s September 2026 DaVinci Resolve 21.1 Reference Manual. Earlier releases may use different labels. Apple’s guide includes a macOS version selector; choose the version installed on your Mac when following its instructions.

Establish a repeatable render before changing settings

Save the project and record the current settings. Choose a short timeline range that exhibits the slowdown—30 seconds is a practical illustrative choice—and use that exact range for every comparison. Keep the video codec, resolution, frame rate, audio export settings, destination drive and cache options unchanged.

Record elapsed completion time rather than relying only on the initial time estimate. Also note whether the slowdown persists throughout the range or begins at a particular clip. The procedure below is a diagnostic comparison derived from the documented controls; it is not a benchmark or a documented guarantee of faster rendering.

First check for an intentional export limit. Resolve documents a Render speed control that can throttle rendering, with Maximum as the ordinary default. If someone reduced that setting, restore the intended value before testing audio devices. Its documented purpose includes limiting bandwidth use on shared storage. DaVinci Resolve 21.1 Reference Manual, “Rendering Media,” page 4127.

Use a small record like this. The times are deliberately blank because they must come from your own project.

Test Change from the baseline What to record
A None Selected devices, buffer setting and elapsed time
B Change only the output device Same range’s elapsed time and whether playback works
C Restore A, then change only an unexpected device format Format before and after, plus elapsed time
D Restore A, then test another playback buffer setting Buffer before and after, plus elapsed time

If a change appears to help, repeat the comparison. A single faster run is a lead; a repeatable difference provides a stronger reason to keep investigating that setting.

Check which audio hardware Resolve is actually using

Open Resolve’s Preferences, select System, then open Video & Audio I/O. Record the I/O Engine, Input Device, Output Device and Playback processing buffer size before changing anything. In Resolve 21.1, the input, output and buffer controls described here are exposed by the System Audio engine. DaVinci Resolve 21.1 Reference Manual, pages 100–101.

For an ordinary desktop setup using the Mac’s own output or a compatible audio interface, inspect System Audio. Blackmagic documents support for onboard audio and Core Audio compatible third-party interfaces. Desktop Video and Fairlight Audio Accelerator are separate hardware paths; use them when that is your intended configuration. The manual explicitly limits ASIO to Windows, so selecting ASIO is not a Mac troubleshooting step. DaVinci Resolve 21.1 Reference Manual, pages 100–101.

Test one straightforward output

Check whether Output Device names the device you expect. If an external interface or combined device is selected, test the Mac’s built-in output where available. Leave the input selection and other settings unchanged for this first comparison. Save the preferences, follow any restart prompt, confirm that timeline audio plays, then render the same test range.

This is an isolation test: it asks whether the result changes when the monitoring device changes. Apple documents selecting the Mac’s speakers as a supported way to return to standard macOS audio drivers when a third-party driver is incompatible. That guidance concerns audio applications stopping working; it does not establish that an external interface causes slow Resolve exports. Apple: If your audio apps stop working while using Audio MIDI Setup on Mac.

Also inspect Automatic speaker configuration. Blackmagic describes this option as using the workstation’s built-in audio output; disabling it exposes controls for a custom speaker setup. Record its state and avoid changing speaker routing during the initial device comparison. If you need custom routing, verify that it still matches your actual speakers afterward. DaVinci Resolve 21.1 Reference Manual, page 101.

Check the selected device in macOS Audio MIDI Setup

Resolve’s device selection and the device’s macOS configuration are two separate checkpoints. Apple’s Audio MIDI Setup utility exposes device formats, including sample rate and bit depth, with available options depending on the hardware. Open the utility and choose Window > Show Audio Devices if its device window is hidden. Apple: Audio Devices window of Audio MIDI Setup on Mac.

  1. Select the output device used in the Resolve test.
  2. Record the sample rate and bit depth shown under Format.
  3. Inspect the input device separately if Resolve uses a different one.
  4. If the format differs from your intended setup, choose an appropriate supported format, then repeat the unchanged render test.
  5. To change the system output, Control-click the device and choose Use This Device For Sound Output. Recheck Resolve’s own output selection afterward.

Apple documents those format and device-role controls in its setup instructions. Its guidance is to use settings appropriate for the device, so choose from the supported options rather than assuming every interface offers the same formats. Apple: Set up audio devices in Audio MIDI Setup on Mac.

For example, suppose your intended workflow uses 48 kHz and the selected interface unexpectedly shows 96 kHz. If the device supports 48 kHz, testing that intended setting is reasonable. These numbers illustrate a configuration check; they do not imply that 96 kHz causes slow exports or that switching to 48 kHz will halve render time. Keep the project and exported audio requirements unchanged while testing the hardware setting.

If you use an aggregate device

An aggregate device combines multiple audio devices. If one is selected, inspect its members and synchronization settings before treating it as equivalent to a single output.

Apple recommends matching member sample rates where possible to minimize resampling. Its current guide uses Sync Source, Sample Rate and Sync controls, and explains when synchronization or drift correction is required. Labels can differ across macOS versions, so use the guide’s version selector. Apple: Set aggregate device settings in Audio MIDI Setup on Mac.

For the render comparison, temporarily selecting a single output is easier to interpret than rebuilding the aggregate device. Keep a record of the aggregate configuration so you can return to it if your normal monitoring or recording task requires it.

Test the playback buffer without assuming it controls export speed

Resolve 21.1 provides separate Playback processing buffer size and Record buffer size controls, each with an approximate latency display. They are distinct settings; changing the record buffer is not the same test as changing the playback processing buffer. DaVinci Resolve 21.1 Reference Manual, page 101.

After restoring the baseline device setup, test one other available playback buffer value. Keep everything else fixed, confirm playback, and render the same range. Record both the old and new values so the change is reversible.

The useful distinction is between responsiveness and render throughput. Audacity’s current documentation explains the general buffer tradeoff: larger buffers favor stability, while smaller buffers respond faster during overdubbing. That is guidance about Audacity’s audio operation, not evidence that a particular buffer value accelerates Resolve exports. Avoid transferring a recommended number from another application without testing it in your own setup. Audacity Manual: Audio settings.

If playback improves but export time remains similar, record those as separate outcomes. Keep the buffer value that serves your playback task, and continue investigating the render slowdown elsewhere.

Interpret the results and choose the next step

Use the comparison to narrow the next action rather than changing several more preferences at once.

Repeatable observation Reasonable next step
Built-in output is faster than the external output Recheck the interface’s supported formats and manufacturer driver compatibility; repeat the comparison after correcting a specific issue.
Correcting an unexpected device format helps Retain the intended supported format and test a longer range with the required export settings.
Buffer changes affect playback but not export time Treat playback responsiveness and render throughput as separate findings.
Device and format changes make no consistent difference Restore your preferred audio configuration and investigate the timeline, effects, media, export settings and destination.
The slowdown repeatedly begins at the same timeline position Test a short range around that position before changing more global preferences.

If a third-party driver is implicated, Apple recommends obtaining current drivers from the manufacturer and using standard macOS audio drivers when compatible third-party drivers are unavailable. Make that a targeted follow-up to the device comparison. Apple: If your audio apps stop working while using Audio MIDI Setup on Mac.

Keep Fusion preview controls separate from final delivery

If your simple edit includes a Fusion title or composition, use the correct render workflow. Blackmagic documents the integrated Fusion page as feeding the timeline through MediaOut, with the Resolve Deliver page handling final timeline output. Standalone Fusion Studio uses Saver nodes for rendering. Fusion 21.1 Reference Manual, page 90.

The Fusion manual also says its viewer quality and proxy controls improve interaction while final output renders at the highest quality regardless of those preview settings. A faster Fusion preview therefore does not establish that the final export workload has become lighter. If the slowdown follows a particular composition, inspect that composition as a separate branch of the investigation. Fusion 21.1 Reference Manual, page 27.

Once a change produces a repeatable improvement, render a longer representative section with the required audio included. Check the completed file for the expected duration, audible channels and synchronization before committing to the full export. Keep a short note of the device, format and buffer settings that worked so you have a useful baseline if the slowdown returns.

Sources