Microphone Troubleshooting: How to Diagnose and Fix Any Mic Problem

Microphone Troubleshooting: How to Diagnose and Fix Any Mic Problem

Microphone issues usually get easier to solve once you sort them by type. In most cases, the problem is either a missing device or no sound, even though it shows up. Likewise, weak audio quality, unstable wireless connection, or an app that cannot access the mic could be the reasons. This guide breaks each situation into clear fixes for Windows, macOS, iOS, Android, and widely used recording and calling apps.

Start Here — Quick Diagnostic Checklist

Work through this list before opening Device Manager or reinstalling anything. Most microphone failures are resolved at one of these steps.

1. Check the physical connection: For USB mics, unplug and replug firmly. For XLR mics, confirm both ends of the cable are locked in. For 3.5mm headset mics, confirm the plug is seated in a headset combo jack, not a headphone-only port.

2. Confirm the mic is not muted: Check the physical mute button or switch on the mic body. On wireless transmitters, look at the LED indicator. A red or flashing LED on the transmitter typically signals a muted state — not a pairing failure.

3. Verify it is the selected default input: On Windows, right-click the speaker icon in the system tray and select Sound Settings, then check the Input dropdown. On macOS, go to System Settings > Sound > Input and confirm the correct device is selected.

4. Check app-level microphone permissions: On Windows 11, go to Settings > Privacy and Security > Microphone. On macOS, go to System Settings > Privacy and Security > Microphone. Confirm both system access and per-app access are enabled. This step is missed frequently after OS upgrades.

5. Inspect the OS input volume slider: The mic may be the selected device, but have its level slider set to zero. Open Sound Settings and confirm the input level is at 60% or above before testing.

6. Test in a second application: Open Voice Recorder on Windows or QuickTime Player on macOS and attempt a recording. If the mic works there but not in your primary app, the issue is app-specific, not system-wide.

7. Look for driver warnings in Device Manager (Windows): Press Win + X and select Device Manager. Expand “Sound, video and game controllers.” A yellow exclamation mark next to a device means the driver needs attention.

8. Restart the Windows Audio service: Press Win + R, type services.msc, locate “Windows Audio,” right-click, and select Restart. This clears many unexplained audio glitches without a full system reboot.

If none of these resolved the issue, continue to the section that matches your specific symptom.

Microphone Not Detected by Your Computer

When the microphone does not appear in your system’s audio input list at all, the cause is typically a driver issue, a privacy setting blocking access, or a hardware or port problem. The fix process differs between operating systems.

Fix on Windows 10 / 11

1. Open Sound Settings and check the Input dropdown. Right-click the taskbar speaker icon and select Sound Settings. If your mic does not appear in the Input device list, continue below.

1. Check Device Manager for driver issues. Press Win + X and select Device Manager. Expand “Sound, video and game controllers.” If the microphone appears with a yellow warning triangle, right-click it and select Update driver > Search automatically for drivers.

2. Reveal hidden or disabled devices. In Sound Settings, click “More sound settings” to open the classic Sound panel. Go to the Recording tab, right-click in the blank area, and enable “Show Disabled Devices” and “Show Disconnected Devices.” If your mic appears grayed out, right-click it and select Enable.

3. Enable the microphone access privacy toggle. Go to Settings > Privacy and Security > Microphone. Confirm “Microphone access” is on and that “Let apps access your microphone” is also toggled on. This setting, introduced in Windows 10 and carried into Windows 11, silently blocks all mic input when it is off.

4. Reinstall the audio driver. In Device Manager, right-click the audio device, select Uninstall device, check the option to delete the driver file, and restart Windows. The system reinstalls a default driver on reboot. For USB microphones, check the manufacturer’s website for a dedicated driver.

5. Switch to a different USB port. Front-panel USB ports on desktop computers are sometimes underpowered or not fully wired internally. Move the mic cable to a rear USB port on the motherboard.

Fix on macOS

1. Go to System Settings > Sound > Input. Confirm the microphone appears in the input device list. If it does not appear, unplug and reconnect the mic, then check again.

1. Check per-app microphone permissions. Go to System Settings > Privacy and Security > Microphone. Enable access for any app you want to use the mic with. Apps that are not yet listed need to request access by being launched first.

1. Restart Core Audio. Open Terminal and run sudo killall coreaudiod. Enter your administrator password when prompted. This restarts macOS’s audio engine and resolves many phantom detection failures without a system reboot.

2. Inspect Audio MIDI Setup. Open Audio MIDI Setup from /Applications/Utilities/. Confirm the microphone appears in the left-side device list. If it is listed but shows no input activity, select it, click the gear icon, and choose “Use This Device for Sound Input.”

3. Quit background audio apps. Virtual audio routing tools such as Loopback or Blackhole can intercept audio device registration and make the mic invisible to other apps. Close background audio utilities and retest.

USB Microphone Not Showing Up

• Connect directly to the computer, not a hub. Passive USB hubs and some powered hubs cause enumeration failures with USB microphones. Plug the mic directly into a port on the machine.

• Try a different cable. USB cables can fail while appearing undamaged. Swap the cable and retest before troubleshooting anything else.

• Inspect both USB ports for debris or bent pins. Physical damage inside the port prevents a proper electrical connection.

• Test on a second computer. If the mic is not detected on any computer, the unit may be defective.

Microphone Detected but No Sound or Very Low Volume

The mic shows up in device settings, the input meter is visible, but it barely moves or stays flat. The problem is almost always in the gain chain — the series of volume controls between the microphone capsule and the app recording the audio.

Check Input Levels in Windows and macOS

On Windows: Right-click the speaker icon, select Sound Settings, and click the arrow next to your input device to open its properties. Go to the Levels tab and confirm the input slider is not near zero. A starting point of 60 to 80 percent works for most USB microphones. Also, check your app’s own volume controls. Zoom, OBS, Discord, and Teams each have independent input level sliders that operate separately from the OS settings.

On macOS: Go to System Settings > Sound > Input. The “Input Volume” slider at the bottom of the panel controls system-level gain. Speak into the mic and watch the input level meter. If the meter does not move at any slider position, the problem is upstream of the OS, at the microphone connection, or the device itself.

Disable Exclusive Mode (Windows)

Windows Exclusive Mode allows a single application to take full control of an audio device and block access by all other apps. When enabled, apps outside the controlling program see the mic as unavailable or receive zero audio.

To disable Exclusive Mode: 

1. Right-click the speaker icon and select Sound Settings. 

2. Click “More sound settings” to open the classic Sound panel. 

3. Go to the Recording tab, right-click your microphone, and select Properties. 

4. Click the Advanced tab. 

5. Uncheck “Allow applications to take exclusive control of this device” and “Give exclusive mode applications priority.” 

6. Click OK and retest in the affected app.

Note: Professional audio software that uses ASIO drivers (such as Ableton Live or Reaper) may require Exclusive Mode to function correctly. Re-enable it if audio performance in those apps degrades after this change.

Adjust Gain at Each Stage of the Signal Chain

Audio passes through multiple gain stages between the microphone and a recording. Setting any single stage to zero silences the entire chain.

1. Preamp or interface gain knob: This is the physical dial on an audio interface (e.g., Focusrite Scarlett) or mixer. Turn it up until speech peaks clearly on the input meter without hitting the red zone. This is the most important gain stage for XLR microphones.

1. OS input level: The Windows or macOS input slider. Set it to approximately 70 percent as a baseline.

2. App input level: Zoom, OBS, Discord, and Teams each have their own mic gain or input volume slider inside the app’s audio settings. Set this to 100 percent and adjust the interface or OS gain to correct the overall level.

Pro Tip: Always increase gain starting at the source and work downstream. Boosting OS or app gain on a weak signal amplifies noise just as much as it amplifies the voice. Get the signal strong at the capsule or interface first.

Poor Audio Quality — Echo, Background Noise, and Distortion

The mic is working, but what it records is not usable. These three sub-problems have distinct causes and require different fixes.

How to Fix Microphone Echo

Echo during a call or recording is almost always caused by speaker output looping back into the microphone, or a software monitoring setting playing the mic input through speakers in real time.

• Use headphones: This is the most effective fix. If a speaker is playing audio in the same room as an open microphone, the mic will capture it. Switching to headphones eliminates speaker-to-mic bleed completely.

• Disable “Listen to this device” on Windows: Go to Sound Settings > Recording tab > right-click your mic > Properties > Listen tab. Uncheck “Listen to this device.” This setting, when active, plays the mic input through your speakers continuously and is a common source of feedback loops.

• Disable software monitoring in recording apps. OBS, Audacity, and DAWs include a monitoring or listen-back feature. If speakers are active, disable monitoring during recording.

• Confirm echo cancellation is active in conferencing apps. Zoom, Teams, and Meet all include built-in acoustic echo cancellation. If you are experiencing echo in those apps specifically, check the audio settings panel to confirm it is enabled.

Reducing Background Noise and Hiss

Persistent noise, such as HVAC hum, keyboard clicks, room ambience, or electronic hiss, degrades recordings and transmission quality.

• Reduce input gain first: High gain captures everything in the room. Lowering gain reduces the noise floor; compensate by moving the mic closer to the source rather than boosting volume downstream.

• Improve mic placement: Position the mic 6 to 12 inches from the speaker’s mouth, directed away from fans, open windows, and mechanical keyboards.

• Apply software noise suppression: Third-party tools include NVIDIA RTX Voice (for RTX GPU users), Krisp, and NVIDIA Broadcast. These apply AI-based suppression at the driver level and work across all apps simultaneously.

• Use a noise gate in OBS or a DAW: A noise gate silences the microphone input whenever the level drops below a defined threshold, preventing continuous room noise from being broadcast between spoken words.

Fixing Microphone Distortion and Clipping

Distortion, crackling, and a harsh, saturated sound are caused by clipping: the audio signal exceeds the maximum level a gain stage can handle.

• Reduce gain at the source: Turn down the interface gain knob or the transmitter gain setting. Lowering OS or app volume after clipping has occurred does not remove the distortion. The damage happens before that stage.

• Increase distance from the mic: Speaking directly into a sensitive microphone at high gain clips on loud consonants and peaks. Pull back to 6 to 12 inches and add a pop filter for vocal work.

• Check for stacked audio processing: Multiple noise suppression filters, EQ plugins, or enhancement tools applied simultaneously can push the signal into distortion. Disable processing layers one at a time to find the source.

• Match sample rates: A mismatch between the microphone’s sample rate and the app or project settings (e.g., mic at 48 kHz, project expecting 44.1 kHz) causes warbling and digital distortion. In Windows Sound Settings > input device Properties > Advanced, confirm the sample rate matches your recording software’s project settings.

Wireless Microphone Troubleshooting

Wireless microphones can fail in ways that wired and USB mics do not. Knowing the basic setup helps you find issues faster. A wireless lavalier system like the Hollyland LARK MAX 2 uses a transmitter worn by the speaker and a receiver connected to a device. The transmitter captures sound and sends it through a 2.4 GHz signal to the receiver. Any break in that connection causes audio loss on the receiving end.

This section uses the Hollyland LARK MAX 2 and Hollyland LARK M2 as reference points. Their LED indicators and app controls help show a clear system status during troubleshooting.

Wireless Mic Won’t Pair or Connect

When the TX and RX fail to establish a connection, the RX typically shows a flashing LED and produces no output signal.

Pairing reset for the LARK MAX 2:

1. Place the TX transmitter back into the LARK MAX 2 charging case. 

2. Close the lid completely and wait 5 seconds. 

3. Reopen the lid. This triggers the LARK MAX 2’s auto-pair sequence: the TX and RX negotiate a fresh handshake automatically. 

4. Watch the RX receiver LED. A solid blue LED confirms a successful pairing and active link. A flashing blue means the RX is still searching. 

5. If the LED does not go solid blue within 15 seconds, repeat the case lid close-and-reopen cycle.

If auto-pair does not restore the connection:

• Press and hold the TX button for 3 seconds to manually enter pairing mode. The TX LED will flash rapidly to indicate it is broadcasting a pairing signal. The RX should detect and lock on. 

• Keep TX and RX within 1 meter of each other during the pairing process. Distance pairing is unreliable even on systems with long rated ranges.

LARK M2 pairing: Press and hold the button on the M2 TX unit until the LED flashes, indicating pairing mode. Once the RX locks on, the TX LED transitions to a solid blue. Keep both units close during the initial connection sequence.

Note: The LARK MAX 2 charging case lid mechanic simplifies re-pairing. If a case-lid reset does not restore the link, confirm both TX and RX units have sufficient battery before attempting again — low battery prevents stable pairing on all wireless systems.

Audio Dropouts and Interference

A paired wireless mic that cuts out intermittently during recording almost always has an RF interference problem in the 2.4 GHz band.

Identifying the cause:

• If your recording has audio with silent gaps at regular or irregular intervals, the wireless link is dropping. If the entire recording is silent, check that the input device was correctly selected and the file was saved. 

• Crowded venues with many Wi-Fi routers, smartphones, and Bluetooth devices all share the 2.4 GHz band and create interference that does not exist in a home environment.

Fix steps:

• Pair the TX with the camera RX. On the display, check whether both mics have a full signal strength. A weak signal display during setup predicts dropout during recording. 

• Power the LARK MAX 2 system off and back on to trigger a fresh automatic channel scan. The system selects the least congested available 2.4 GHz channel on each startup. 

• Maintain line-of-sight between the TX transmitter and RX receiver wherever possible. Human bodies, walls, and metal surfaces absorb 2.4 GHz signals significantly. 

• Stay within the rated operational range. The LARK MAX 2 supports up to 340 meters in open conditions; expect a meaningfully shorter range in indoor or RF-dense environments. 

• Move away from Wi-Fi routers, smartphones, and other 2.4 GHz devices. Even 2 to 3 meters of separation from interference sources makes a measurable difference in signal stability.

Using 32-bit Float backup recording on LARK MAX 2: The LARK MAX 2 TX transmitter records audio locally in 32-bit Float format at all times. All you need to do is press the REC button to begin and save the recording internally. To ensure its recording, the LED indicator will turn red. This is a super helpful feature because if the wireless link drops mid-recording, you can use the TX unit to record audio.  

Once done, you can retrieve the backup file from the TX by connecting the unit directly via USB-C. This is the most reliable failsafe against silent recording loss in professional field recording situations.

The same goes for Hollyland LARK M2 users. A strong connection will show a solid blue TX and RX LED indicators. Whereas flashing blue LED indicators after the session has started signal that the connection between the two units is either lost or weak. Note the timestamp, check that portion of your recorded file, and adjust transmitter position or reduce interference sources before the next take.

Low Signal Level from Wireless Transmitter

The mic is paired, the link is active, but audio arriving at the camera or computer is too quiet to use, even with OS input levels raised.

The cause is almost always insufficient TX gain. Increasing the OS or app input level on a weak wireless signal amplifies noise as much as it amplifies speech. Gain must be corrected at the transmitter.

LARK MAX 2 via the HollyAudio (LarkSound) app:

1. Open the HollyAudio app and connect to your LARK MAX 2 system. 

2. Navigate to the TX gain settings. You can set Dynamic Gain to High, Medium, or Low. Contrarily, you can set custom gain for each connected TX/mic by adjusting the levels from the Set gain to section.

3. Speak at normal conversational volume and monitor the level meter in the app. Target peaks in the -12 to -6 dBFS range. 

4. Check the AI Noise Cancellation setting in the app. At aggressive suppression levels, the filter can attenuate quiet speech alongside background noise. If the voice sounds thin, clipped, or intermittent at low gain, reduce the noise cancellation intensity.

LARK M2 gain adjustment: Like the Hollyland LARK MAX 2, the Hollyland LARK M2 does not adjust volume from the transmitter. On the mobile version, gain changes are made through the LarkSound app. For the camera version, use the receiver knob to adjust output volume. Turn it right to increase volume and left to lower it. The three LEDs below the knob indicate the current volume level.

Wireless Mic Muted Unexpectedly

A working wireless setup can suddenly produce no sound due to a muted transmitter. This often happens when the TX unit gets switched off by mistake. The clothing movement can press the mute control without notice. This issue appears frequently during real-world recording situations.

LARK MAX 2 TX: The mute button sits on the transmitter body. When muted, the TX LED displays red.. Double-pressing the multi-function button on the TX mutes or unmutes the mic.

LARK M2: The Hollyland LARK M2 transmitter does not include a dedicated mute button. The standard M2 model has no on-mic mute function available. To stop audio capture, press and hold the yellow button for three seconds to turn it off. You can also remove the transmitter from your clothing when needed.

LARK A1: The Hollyland LARK A1 comes with a built-in mute option. You can turn mute on or off from the transmitter or receiver. On the TX, press the button twice to switch mute status. On the RX, double-press the multi-function button for Mic 1. And press it three times to mute or unmute Mic 2.

Battery and Power Issues Causing Wireless Failure

Wireless audio systems often start performing poorly before the battery fully runs out. You may notice unstable connections, brief dropouts, or flickering LED alerts. These signs usually appear during the final low-power stage before the device turns off.

LARK MAX 2:

• The TX LED flashes red when the battery reaches the low threshold. Do not continue recording after this warning appears; signal quality will be unstable before the unit powers off. 

• Charge TX units via the charging case using the case’s USB-C port. The TX LED displays a solid or slowly blinking pattern during active charging and changes to a steady indicator when fully charged. 

• During multi-take shoots, return TX units to the case between setups to top up battery charge and reconfirm the paired state for the next take.

LARK M2:

• The LARK M2 charging case charges TX units via USB-C. The case displays its own battery level via a 4-dot LED bar on its exterior. Each illuminated dot represents approximately 25% of the remaining case capacity. 

• The LARK M2 system supports up to 40 hours of total battery life across the case’s full charge capacity, meaning the case can fully recharge the TX units multiple times before the case itself needs recharging. Plan charge cycles accordingly for full-day or multi-day productions.

Platform-Specific Microphone Fixes

If the microphone works in system sound settings, the hardware is fine. When the input meter moves while speaking, the device is detecting sound correctly. If one app still has no audio, the problem is inside that app. Each application controls its own microphone settings separately from the system. You may need to check input selection, gain, and permissions inside that app.

Zoom Microphone Not Working

• Open Zoom Settings: click your profile picture > Settings > Audio.

• In the Microphone dropdown, explicitly select your device. 

• Check the Input Level slider in Zoom’s audio panel. If it reads zero, no audio will transmit regardless of OS settings.

• Click “Test Microphone” to confirm audio is reaching Zoom before joining a call.

• If your mic does not appear in the dropdown, quit Zoom entirely, ensure the mic is connected, then relaunch.

• On macOS, confirm Zoom has microphone permission under System Settings > Privacy and Security > Microphone.

OBS Studio Not Picking Up Mic

• Go to Settings > Audio in OBS. Confirm “Mic/Auxiliary Audio” is set to your specific device and not set to Disabled.

• In the Audio Mixer on the main OBS screen, confirm the mic fader is not at zero and the channel is not muted (the speaker icon should be active, not crossed out).

• Right-click the mic source in the Audio Mixer and open Advanced Audio Settings. Confirm the track is enabled and monitoring is set to your preferred mode.

• If the OBS input meter does not respond while the OS meter does, the device selected in OBS is pointing to a different input. Re-select the correct device in Settings > Audio.

Discord Mic Issues

• Open User Settings (gear icon) > Voice and Video.

• Under Input Device, select your microphone explicitly from the dropdown.

• Turn off “Automatically determine input sensitivity” and set the threshold manually so normal speech consistently activates the input indicator.

• If using Push-to-Talk, confirm the keybind is assigned and that you are pressing it when speaking.

• On Windows and macOS, confirm Discord has microphone permission in Privacy and Security settings.

Microsoft Teams Microphone Fix

• In Teams, open Settings > Devices. Under Microphone, select your input device from the dropdown and run “Make a test call” to verify audio reaches Teams.

• Confirm Teams has microphone permission at the OS level.

• If audio quality is poor in Teams, go to Settings > Devices and adjust the Noise Suppression setting. Cycling through Auto, Low, and High can reveal whether the suppression algorithm is over-attenuating your voice.

• After major Windows updates, Teams sometimes loses its audio device reference. Reinstalling the Teams desktop client clears cached device states that are occasionally corrupt.

Mobile Microphone Troubleshooting (iOS and Android)

iPhone Microphone Not Working

• Go to Settings > Privacy and Security > Microphone. Confirm the toggle is on for the specific app you are using. Apps do not appear in this list until they have requested mic access at least once — launch the app and attempt to use the mic to trigger the permission prompt.

• If the mic works in the Phone app but not a third-party app, the problem is app-specific permissions, not a hardware fault.

• Check that a phone case is not covering the microphone grille. The primary iPhone mic is at the bottom edge and can be blocked by full-coverage cases or debris.

• For users connecting the Hollyland LARK A1 wireless receiver via Lightning or USB-C: the LARK A1 is plug-and-play and requires no driver or app installation. If the iPhone does not automatically route audio from the receiver, open the recording app’s audio input settings and manually select the external input. If audio from the LARK A1 sounds noisy, press the noise cancellation button on the dongle receiver to cycle through its three suppression levels until the result suits your environment.

Android Microphone Not Working

• Go to Settings > Apps > select the app > Permissions > Microphone and confirm access is granted. The path varies by Android version and device manufacturer.

• Test with a second app (Google Recorder or the native Voice Memos equivalent) to confirm whether the problem is app-specific or hardware-level.

• Check for physical obstruction at the mic port. Android microphone grilles are typically located at the bottom of the device and can be blocked by full-coverage cases.

• For users connecting the Hollyland LARK A1 USB-C receiver: some Android apps default to the internal microphone regardless of what is connected externally. Go into the app’s audio settings and manually select USB Audio as the input device. If audio quality on the LARK A1 sounds noisy in the field, cycle the noise cancellation button on the receiver dongle to the appropriate suppression level.

Hardware Checks — When Software Fixes Aren’t Enough

If all software steps have been completed and the mic still fails, the problem may be physical.

• Inspect cables for damage: Flex XLR and TRS cables near the connector ends while monitoring audio. Internal breaks near connectors are common and only appear as intermittent drops when the cable is flexed.

• Test on a second device: Connecting the mic to a different computer, phone, or interface immediately separates a device problem from a mic problem.

• Confirm phantom power for condenser mics: Condenser microphones require 48V phantom power from the audio interface. Without it, they produce no output at all. Confirm the phantom power button on your interface is enabled.

• Clear the 3.5mm jack: Use compressed air to remove lint or debris from the port before testing a 3.5mm headset mic.

• Contact manufacturer support: If the mic fails on multiple devices after completing all steps above, the unit is likely defective. Check the manufacturer’s warranty terms and reach out to their support team.

Frequently Asked Questions

Why is my microphone not working even though it’s plugged in?

The most common causes are a blocked app permission, the mic not being set as the default input device, or a driver issue. Start with the Quick Diagnostic Checklist at the top of this guide. In most cases, the fix is found in system permissions and audio settings. Check the microphone privacy options in Windows 11 or macOS first. Then select the correct default input device for recording. Also, confirm that browsers and chat apps can access the microphone.

How do I fix a microphone that’s detected but produces no sound?

First, make sure the operating system input volume is not muted. Then check the microphone permissions in system settings carefully. Confirm apps are allowed to access the microphone correctly. After that, review volume and gain at every stage. Check hardware controls, operating system settings, and app audio levels. A zero setting at any point can mute everything.

Why does my wireless mic keep cutting out?

The most common causes are RF interference from nearby 2.4 GHz devices, a low transmitter battery, or the TX unit moving beyond the effective range. For LARK MAX 2 users, the TX unit stores a 32-bit Float backup recording locally throughout every session. If the wireless link drops, that file is intact and recoverable after the shoot.

Why does my mic work in one app but not another?

Apps let you choose a specific microphone from their own settings. They still depend on operating system permissions to access it. So, confirm that microphone access is allowed in privacy settings. Then open the app’s audio settings and choose your microphone manually. This can fix problems caused by the wrong default device being selected.

Why does my mic sound muffled or distant?

The most likely causes are the mic positioned too far from the source, the gain set too low, or an aggressive noise suppression filter cutting the wanted signal. For wireless TX users, check the transmitter gain setting via the HollyAudio app or the RX volume knob, and reduce the noise cancellation level if voice sounds thin or intermittent.

How do I reset a wireless microphone that won’t pair?

Place the TX transmitter back into the charging case, close the lid, wait 5 seconds, and reopen. On the Hollyland LARK MAX 2, this triggers an automatic re-pair sequence. If the link does not restore, press and hold the TX button to manually enter pairing mode. As a last resort, perform a factory reset using the button-hold sequence described in the device manual.

Conclusion

The quickest way to fix mic issues is to find the cause first. Check whether the problem involves detection, volume, sound quality, wireless connection, or a specific app. Verify each change using the operating system input meter. Do this before assuming the microphone hardware is faulty. For wireless recording, the Hollyland LARK MAX 2 includes 32-bit float backup recording. This helps prevent silent recording loss that cannot be fixed later with software. 

Facts Index