Identify the microphone that should be recorded
A computer can expose several audio inputs: a built-in microphone, a headset, a webcam microphone or a virtual device. Begin by naming the intended input and checking it through the operating system’s supported sound controls. The presence of a device in a menu does not establish that it is receiving the voice you expect.
Use your own short test phrase in a quiet place and avoid capturing another person’s conversation. Keep a note of the physical microphone and connection. For an original example, say the device name followed by a brief count; the resulting file then contains a recognizable check that it came from the intended test.
Choose the platform’s documented capture source
VideoLAN’s desktop recording guide gives DirectShow through Open Capture Device for Windows, and an Input devices route with Audio selected for the documented macOS interface. Use the applicable route for the installed build. Do not copy a Windows device-selection screenshot into a Mac procedure.
Select the actual audio device and inspect whether the operating system requires access permission for the application. Keep other capture sources unchanged. If the expected device is absent, investigate system recognition and the current application’s supported capture route before changing output codecs.
Record to a new destination and stop normally
The guide proceeds through Convert, an audio profile, a save location and Start. Choose a clearly named new file in a writable folder. Keep the source device and profile in the test notes so an unreadable output can be distinguished from a silent input.
Record the short phrase, then stop through the normal VLC control. Let the output complete before playing it. Avoid choosing the same destination for repeated tests until you know whether the application replaces or otherwise handles the existing file in the intended way.
Listen back through a known working output
Open the finished sample and listen using a known working speaker or headset route. Confirm the expected phrase is present, intelligible and not clipped. A moving timeline alone does not prove the microphone was captured. If the sample is silent, compare the selected input, permission and output playback separately.
Once the sample is satisfactory, preserve the chosen device and settings for the longer recording. Retain the original voice file until any conversion or editing is checked independently. The expected outcome is a verified recording from the intended input; it does not establish a live broadcast route or guarantee that desktop video and microphone capture are automatically combined.
Questions answered
Why can a recording file exist but contain silence?
The output process can run while the selected input is silent, unavailable or not the intended microphone. Verify the device and listen to the completed sample.
Should I use the same capture-device instructions on Windows and macOS?
No. VideoLAN documents platform-specific input routes. Follow the controls for the installed operating system and build.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.