Fix missing MAME sound samples on Android without replacing ROMs
Use the exact MAME revision's `-listsamples shortname` output first. If it lists samples, run `-verifysamples shortname`, inspect the configured samplepath, and restore the matching authorized sample archive without renaming ROMs. If no samples are listed, move to machine emulation, performance, and Android audio routing instead.
Do this in order
- 01
Record the Android port and MAME revision, machine short name, missing sound effect, and whether all audio or only specific effects are absent.
- 02
With the matching MAME build, run `mame shortname -listsamples` and save the exact referenced sample names.
- 03
If samples are listed, run `mame shortname -verifysamples` and record missing, incorrect, or good results separately from the ROM audit.
- 04
Inspect the active samplepath in the target frontend; confirm the authorized sample archive or directory is reachable and named for that driver.
- 05
Relaunch with default machine audio and test the exact effect; do not replace game, parent, BIOS, or CHD files when only the sample audit fails.
- 06
If no samples are referenced or verification passes, compare another audited game and diagnose emulation speed, Android media output, mute, and audio focus.
Decision and diagnostic table
| Evidence | Likely boundary | Next action |
|---|---|---|
| `-listsamples` names effects | Driver references external samples | Run the sample-specific audit |
| `-verifysamples` reports missing | Sample archive or samplepath | Restore the exact authorized set and path |
| Samples verify; a few effects still fail | Driver behavior, version, or per-machine configuration | Retest defaults and inspect the target log |
| All games are silent | Global Android or frontend audio path | Check speed, media route, mute, and focus |
Samples are not a universal MAME sound pack
Some MAME drivers reference external recorded samples for particular effects, while many machines emulate their sound hardware without any sample archive. The target build's `-listsamples` output is the deciding evidence.
Adding a large sample collection cannot repair a machine that does not request samples. It also makes provenance and version drift harder to audit.
ROM and sample audits answer different questions
`-verifyroms` checks required ROM images, while `-verifysamples` checks sample files found through samplepath. Keep the outputs separate so a passing game audit does not hide a missing effect and a sample failure does not trigger ROM replacement.
Android ports may expose samplepath only through a directory setting. Record the actual configured path rather than assuming a desktop default is shared.
Use the symptom to exit the sample branch
Missing one named effect is consistent with a sample problem. Crackling, slow pitch, or silence across unrelated games more often points to performance, synchronization, mute, or Android output routing.
After samples verify, return to default audio settings and compare one authorized known-good machine. Change one layer at a time and keep the result tied to the exact build and device.
Audio samples may be copyrighted recordings. Obtain them only from your own lawful source or a release that authorizes your intended use; do not download a mystery sample pack or redistribute an archive because MAME references it.