WAV vs SND for the MPC 2000XL

What do WAV and SND mean here?

WAV is the audio container used by many desktop tools. SND here means an Akai MPC sound file. Changing a filename from .WAV to .SND does not convert its audio or its header; use an actual exporter.

Akai’s operator’s manual lists both .SND and .WAV on the LOAD screen, printed page 164 (PDF; mirror). Its technical specifications, printed page 193 (PDF; mirror) describe 16-bit linear sampling at 44.1 kHz. Those specifications give context for the export target; they are not a test of every WAV encoding or storage device.

The Akai documentation and the fixture evidence below answer different questions. The manual describes the machine’s loading workflow. The fixtures show the bytes written by the inspected EZMPC export path. Neither establishes that a particular Mac-to-MPC storage setup has been tested.

What does EZMPC export?

The settings panel calls this option Default Sample Format. The program exporter also checks whether each sample is marked mono. For WAV inputs, the checked source makes this choice:

SND selected does not mean every exported file will be SND. The stereo branch chooses WAV. This is EZMPC’s implementation choice; it is not evidence that the MPC 2000XL only supports mono SND files.

Use WAV when you want the exported WAV inputs in a format you can inspect with common desktop audio tools. Use SND when you want EZMPC’s mono SND output while keeping stereo samples as WAV. Check the sample’s mono state before exporting, especially if you have used a mono conversion option.

The exporter requests 16-bit, 44.1 kHz conversion. This check used untrimmed WAV inputs with known channel metadata. Existing SND imports, trimming, loops, and other editing branches were not exercised. The results also do not establish a loading-speed advantage for either format.

Two original fixtures, inspectable outputs

We generated one mono tone and one stereo tone with different left and right signals. Both inputs are original 24-bit, 48 kHz WAV files, each 6,000 frames long (0.125 seconds), with no third-party samples. The same inputs were exported with SND selected and with WAV selected.

The run calls the source’s program exporter and native converter through a local harness. The file-system and settings bridges are supplied by the harness; the format decision and conversion code come from the inspected production source. WAV headers and the SND header/payload are independently read back from the exported files; SND’s 16-bit encoding is established by the writer and payload length because its header has no bit-depth field.

All four outputs contain 5,513 frames at 44,100 Hz. The stereo files retain different left and right PCM data. Inspect the input and output metadata with SHA-256 hashes, or download the original mono input and original stereo input. File headers, sample counts, and channel checks provide evidence beyond the filename extension.

Check a small kit before moving a library

A valid-looking export is one part of the workflow. Your MPC operating system, drive or emulator, and transfer method still need their own check. Use copies of your working files and a new test folder.

For an individual sound, the manual describes selecting the SND or WAV file on LOAD and pressing DO IT [F6], then using PLAY [F3] to preview and KEEP [F5] to retain it. Follow the sound’s note/pad assignment prompts. Loading sounds, printed pages 165–166 (PDF; mirror).

1. Choose two familiar sounds. Include one mono hit and one stereo sound with an obvious left/right difference. Keep stereo enabled if that difference matters.
2. Record the format setting. Export a small program. With SND selected, expect the mono WAV input to produce SND and the stereo WAV input to produce WAV in this checked implementation.
3. Inspect the actual files. Check the container, channels, bit depth, and sample rate with a tool that understands the format. An unfamiliar SND file failing to open in a desktop player alone does not prove it is corrupt.
4. Transfer through your normal setup. Keep the program and its sample files together. Record your MPC OS version and the storage device used.
5. Load, listen, save, and reload on the MPC. Check pad assignments, both stereo channels, sample starts and ends, and any settings your kit depends on. Resolve missing or incorrect sounds before exporting a large library.

If something fails, report the original input format, mono/stereo state, selected export format, output metadata, MPC OS version, and transfer device. Those details help distinguish an export problem from a program or storage problem. Contact EZMPC with your example.

Sources and what this check proves

Documentation evidence

Akai MPC2000XL Operator’s Manual (Platinum Audio Lab mirror): printed pages 164–166 cover file types and loading sounds; page 193 gives the sampling specifications. These correspond to PDF pages 175–177 and 204. This is Akai-authored documentation hosted by a third party. Consult the instructions for your own OS and media setup.

Source and fixture evidence

The local EZMPC source was checked at commit 4e4b54c8d888ab4a77194f564e6959c496039de6. The settings UI, program-export decision, and native conversion path were inspected. The evidence record identifies the source files, generated inputs, invocation, and output metadata.

This establishes the observed behavior of that source path with these fixtures. It does not certify every input, reproduce the full app UI or sandbox, verify the current App Store binary, or demonstrate loading or playback on physical hardware. No loading times were measured.