6.2 Audio and Computer Maintenance

Preventive rather than reactive

Maintenance occurs on a schedule, not only after failure. Create an inventory with device identifiers, location, firmware or approved configuration, purchase or service information, battery dates, known issues, and assigned spares. Follow manufacturer and organization guidance. A component can pass power-on yet fail under movement, sustained recording, or battery load, so functional exercise matters.

Audio equipment

Inspect microphones for damaged grilles, capsules, goosenecks, clips, switches, and connectors. Keep them dry and clean using approved methods; liquids or compressed air can damage some capsules. Test each microphone at normal cable length and move the cable gently to reveal intermittence.

Inspect cables end to end for cuts, crushed sections, exposed shielding, bent pins, loose latches, and poor strain relief. Label tested cables without wrapping adhesive where it damages the jacket. Retire unreliable cables rather than marking them “sometimes works.” Check mixers and interfaces for noisy controls, loose jacks, overheating, clock or driver errors, and stable connection under realistic multichannel load.

Track rechargeable batteries by age and performance. A battery that shows full but collapses quickly under load is not a dependable spare. Store and charge according to manufacturer safety instructions; inspect for swelling, leakage, heat, or physical damage and remove unsafe batteries from service.

Computer and storage maintenance

Maintain:

• approved operating-system and security updates;
• recording application, drivers, firmware, licenses, and platform compatibility;
• sufficient local storage and healthy backup destinations;
• endpoint protection and account controls required by policy;
• clean ventilation, fans, ports, and stable power;
• accurate date and time configuration; and
• tested restore media, configuration notes, and support contacts.

Do not use free space as the only storage-health measure. Monitor system warnings and organizational health tools. Preserve records before maintenance and follow authorized disposition; clearing a drive is not a substitute for a retention decision.

Update discipline

Updates can repair vulnerabilities and compatibility problems, but they can also change permissions, device names, drivers, or audio routing. Use a controlled sequence:

1. Review release and compatibility information.
2. Confirm authorization and backup current configuration or data.
3. Update a noncritical or test system first when possible.
4. Reboot and test every input, channel, annotation, file-write, playback, export, backup, and remote function.
5. Record the tested versions and result.
6. Keep a documented recovery or escalation path.

Avoid optional updates immediately before a proceeding. Deferring an urgent security update may also be unacceptable; follow the administrator's decision and use a tested alternate system if necessary.

Cleaning and environment

Dust blocks cooling and damages connectors. Store equipment in protective cases, control moisture and temperature, and avoid leaving devices in hot or freezing vehicles. Keep food and liquids away. Secure small adapters so they do not disappear between jobs. Coil cables without sharp bends and separate known-good, untested, and failed items.

Maintenance testing

Periodically run a duration test approximating a real proceeding: record all channels, annotate, monitor, switch to backup power if authorized, close files, replay isolated tracks, and restore a backup. A backup that has never been restored is unverified. Test alert volume and visibility; warning sounds are useless if monitoring settings suppress them.

Records and replacement

Log date, technician or reporter, inspection, version changes, faults, corrective action, and final test. Repeated dropouts on the same port or cable indicate replacement or professional service. Do not return a failed device to the ready kit without a verified repair.

The exam distinguishes maintenance from live troubleshooting. Maintenance reduces risk before the job; troubleshooting isolates a present symptom. Both end with recorded verification, not assumption.

Exam application

A maintenance log shows three intermittent dropouts from the same USB port over two months. Passing a short test today does not erase that pattern. Remove the unreliable path from ready service, arrange authorized repair or replacement, and test the replacement under sustained multichannel load. In contrast, a damaged cable clearly isolated and replaced with a known-good tested spare may need no system-wide rebuild. Maintenance questions reward trend recognition, documented disposition, and verification—not the hope that a recurring fault will wait until after the next job.

Review checkpoint

Keep failed equipment physically separated from ready equipment and label its status. A future reporter should not be able to select an intermittent cable merely because it was returned to the same case.