WebFV
Local audio / Field guide

Set up ArtCraft SoundCraft and verify an audio export

Check a small WAV import, saved session and exported mix before recording important audio.

By WebFV Editorial · Checked October 23, 2026 · SoundCraft v0.12.1 · macOS CLI test

What the evidence coversImport, session save/reopen and WAV export tested with original audio. Hardware playback and recording were not tested.

Start with ArtCraft's SoundCraft

For the open-source audio editor, use storytold/soundcraft, linked from ArtCraft's SoundCraft page. This guide concerns that desktop application and its command line, not Soundcraft mixing-console hardware.

Start with a short WAV you own. Import it, save a session, export a mix, and reopen both files before trying an important recording. SoundCraft v0.12.1 completed that file workflow in our macOS CLI test. Hardware playback, microphone recording and other operating systems were not tested.

Choose the app or the command line

The official v0.12.1 release provides separate packages. Choose the desktop app if you want the Edit and Mix windows. Choose the CLI archive for the repeatable file test below.

Platform What to download
macOS, Apple Silicon or Intel Universal desktop .dmg, or the separate universal CLI .zip
Windows Installer or portable ZIP matching x64, arm64 or x86
Linux Package matching your distribution and processor; the release lists the available builds
FreeBSD The release's matching tarball
Browser The web build, which has a separate hosting/build path

On macOS, copy the desktop app from the disk image into Applications. The CLI ZIP instead expands into a folder containing soundcraft-cli. You can run that executable by its full path without installing it globally. On Windows, match the installer to your system's architecture before running it. The platform packages are upstream release assets, not a claim that we tested every build.

The project still labels itself pre-alpha. Preserve original audio and keep a working copy of sessions before updates. Source builds have additional Rust and platform dependencies; downloading a suitable release is the shorter route for this first check.

Select playback and recording devices separately

The current interface source places Playback Engine under Setup. Its window has separate Output device and Input device choices, plus sample-rate and buffer settings. Choose the output you intend to listen through; choose an input only when you need to record. Use Refresh devices after connecting hardware, then Apply to reopen the devices with the selected settings.

These labels were checked in the upstream interface source. We did not operate this hardware dialog. The displayed output can fall back to a silent clock when no real device is available, so a moving playhead alone does not prove that your speakers are receiving audio.

Keep monitoring volume low for the first playback. If you plan to record, check the operating system's microphone permission and the selected input before arming a track. The offline export test below does not require a microphone and cannot validate recording latency or an audio interface's driver.

Reproduce a small import and export

Our input is an original, generated two-second 440 Hz tone: mono, 48 kHz, 16-bit PCM. It contains no recording or copyrighted music. Download it into an empty test folder and name it tone.wav.

Download the test WAV

Run the following from that folder. Replace soundcraft-cli with the full path to your extracted executable if it is not on your PATH.

soundcraft-cli run \
  --cmd 'file.import_audio={"path":"tone.wav"}' \
  --cmd 'session.audio_health={}' \
  --save tone.scraft \
  --bounce mix.wav --start 0 --end 2 --inspect

This imports the WAV into a new session, checks loaded media, saves tone.scraft and exports the first two seconds to mix.wav. In the reproduced run, the import created one mono track with 96,000 frames. The exported mix was stereo, 48 kHz, 24-bit WAV with the same duration. Its measured peak was about −23.77 dB, so it contained a nonzero signal.

The output is available for comparison. Playback starts only when you press the control; turn the volume down first.

Download the exported mix

Reopen the session and inspect the exported file

Run a fresh command against each saved result:

soundcraft-cli info tone.scraft
soundcraft-cli info mix.wav
soundcraft-cli run --in tone.scraft \
  --cmd 'session.audio_health={}' --inspect

The reopened test session had one audio track and one clip, with the source stored under Audio Files/tone.wav. Keep that media folder with the session when moving the project. A session file and a finished audio export serve different purposes: one preserves editable work; the other is the mix you can play independently.

Our readback reported a two-second session, loaded source media and zero audio-health issues. The exported WAV's header also reported 96,000 frames at 48 kHz. This is a file and engine check on macOS 26.6.2 using the universal CLI, with preferences disabled for the test. It is not an assessment of sound quality, speaker playback or microphone recording.

Use the same checks in the desktop app

The command catalog identifies File, Import, Audio for adding audio and File, Bounce Mix for exporting a mix. Import your disposable WAV, confirm that its waveform appears, and press Space to start or stop playback. Listen through the output selected in Playback Engine. Save the session, bounce the intended time range, then open the exported WAV in another player.

If the waveform is visible but you hear nothing, check the actual output device and track routing rather than repeatedly importing the file. If the exported mix is silent, check the selected range, track mute state and output routing. A successful session.audio_health result checks loaded audio and clip bounds; it explicitly does not test signal levels, plugins or routing.

If a session reopens with missing media, restore its companion audio files before doing further edits. Do not overwrite your only good session while investigating. Record the app version and the smallest failing example when reporting an issue upstream.

For a separate local-document task, the GenOffice download guide uses the same save-and-readback approach with a small DOCX. The test here remains limited to SoundCraft's audio workflow.