Digital mixer QC should verify identity and version, visual assembly, every input and output, controls, display, processing, recording, networking, power behavior, extended operation, accessories, packaging and traceable test records.
Identity and visual inspection
Confirm model, serial or batch, firmware, hardware revision, voltage, labeling and approved artwork. Inspect enclosure fit, faders, knobs, connectors, screen, fasteners and printing.
Visual inspection is not cosmetic only. Misalignment can indicate assembly stress; loose connectors can become intermittent faults after transport.
Functional signal test
Inject a known signal into every input and verify gain, phantom power where applicable, routing, mute, solo, EQ, dynamics and metering. Test every physical and digital output under load.
Check scene save and recall, effects, USB functions, Bluetooth if included, remote control and control-system interfaces. A partial demonstration is not an all-channel test.
Stress and recovery tests
Operate the console for an extended period, monitor temperature and repeat power cycles. Disconnect and reconnect network control, attach several clients where supported and verify local operation remains available.
Test abnormal but realistic events: interrupted recording media, router restart, accidental scene change and restoration from a known file.
Packaging and shipment release
Verify accessories, power cable, manual, protective materials, carton marks and drop-protection design. Scan a sample of cartons and confirm the product inside matches the label.
The inspection report should record quantities, sample size, failures, corrective action and approval status. Keep the report with the purchase order and golden-sample record.
Frequently asked questions
Digital Mixer Quality-Control Checklist FAQ
Should every mixer be function-tested?
Critical functions should be tested on every unit when the process and risk justify it; broader performance sampling can supplement 100-percent basic testing.
What is a golden sample?
It is the signed, approved reference unit used to judge production appearance, function and configuration.
Why record firmware during inspection?
A firmware difference can change control behavior, compatibility and features even when the model name is unchanged.