If Larix Broadcaster audio is missing on YouTube Live, trace it from Android’s microphone controls through Larix’s selected input and into YouTube’s incoming stream. A silent stream can have more than one cause, so treat each check as evidence about one part of the path, not proof that the whole setup works.
First identify what audio you expect: sound from the phone’s microphone, an external microphone or mixer, or playback from another app. Then compare what Larix captures with what YouTube receives and what a separate viewer device can play. The phone model, Android version and microphone are not known here, so menu labels and available capture paths may differ.
Find where the audio disappears
Think of the route as a series of hand-offs: Android permits an audio source, Larix selects and captures it, the encoder sends it, YouTube receives it, and a viewer’s playback device plays it. A failure at one stage can look much like a failure at another. Listening only to your own phone while setting up the stream does not tell you what a remote viewer receives.
Before changing settings, note what is actually silent. Is a person speaking near the phone inaudible, or is music playing in another Android app missing? Are both missing? Is the incoming preview in YouTube Live Control Room silent, or do you only hear silence on one viewer device? Keep those observations separate; microphone recording and capture of audio from other apps are not the same Android function.
Make one short, controlled test and change one thing at a time. For example, say a few words into the built-in microphone while Larix is active, then listen to any available local capture and check the YouTube preview. Record which step has sound before adjusting a permission or changing input. This makes a useful comparison; it does not establish a universal diagnosis.
If you are trying to keep a recorded video running continuously rather than capture a live phone microphone, the problem may be a different kind of stream. The guide to streaming recorded Marathi church sermons from a Windows PC covers a file-based route, which has a different audio path from Larix on Android.
Check Android microphone permission and privacy
Android’s permission for an individual app and the device-wide microphone privacy control are separate. Check both. Google’s Android app-permission instructions describe microphone permission as what allows an app to record audio, but the exact settings labels can vary between Android releases and manufacturers.
On many phones, the app-level route is Settings, Apps, Larix Broadcaster, Permissions, Microphone. If Microphone is denied, allow it for the app while it is in use, if that choice is offered. Return to Larix and repeat a brief test rather than assuming the setting has taken effect across every audio mode.
Next look for the phone-wide microphone access control. It may be under Privacy controls or a similar privacy section in Android Settings, and some versions expose a microphone toggle in the quick settings panel. If system-wide access is off, granting Larix permission alone may not make the microphone available. Turn it on for the test, then check Larix again.
If permission already appears allowed and device-wide access is on, do not keep toggling them without a reason. Move to the selected source, then revisit permissions if a system prompt appears or the behaviour changes. A visible permission setting is evidence that access is allowed at that level; it is not proof that Larix is receiving the particular microphone or that YouTube is receiving the encoded audio.
Verify Larix’s selected audio input
Open Larix’s audio settings and inspect Audio source. The built-in microphone, a wired or USB microphone, and a mixer feed are different inputs. Choose the source that matches what is connected and what you intend to capture. A connector fitting into the phone does not establish that the phone recognises the signal or that Larix has selected it.
If you are using the built-in microphone, disconnect external audio equipment for one test and speak near the phone. If that works, reconnect the external device and test again. If you are using an external microphone or mixer, connect it before checking the source and confirm that the phone recognises it. Re-select or test the intended input in Larix after connection; do not assume the app changes source automatically.
Larix’s Google Play listing includes developer guidance to try Settings > Audio > Audio source when an input is not detected. It also suggests that some external devices may need a higher sample rate, with 48000 given as an example. Treat that as a setting to test for a relevant external input, not a universal requirement or a fix for denied permission, an unsupported accessory, or a YouTube-side issue. Change one setting, make a short test, and note whether the result changes.
For a headset, USB microphone or mixer, check the whole connection: the accessory, any adapter, the phone’s port, and the selected Larix source. If a line-level feed is involved, its signal and connector may not behave like a microphone input. The Larix listing includes an individual user report about a Pixel 3a not always detecting a headphone-jack line feed; that is one person’s report, not evidence that all Pixel phones or headphone connections have the same problem.
Separate microphone capture from app audio
A common source of confusion is expecting Larix to capture music or sound that is playing inside another Android app. That is not the same as recording a person speaking into the phone’s microphone. A microphone permission check alone cannot settle whether Android permits another app’s playback to be captured.
Softvelum’s Larix FAQ says that Android 9 and earlier restrict capture of audio from other apps. It says Android 10 supports media capture only from apps that allow external recording. For the supported path, the FAQ points to Larix Audio > Sound settings > Media sounds. The Android version and the app playing the sound matter, so do not infer that a silent music source proves the phone’s microphone is unavailable.
If the missing sound is music inside another app, check whether that app supports external recording and whether Larix’s Media sounds option is available and enabled. If the sound is someone speaking near the phone, instead investigate microphone permission, system-wide access and Larix’s selected input. Keeping these two questions separate prevents you from changing microphone settings to solve an app-audio restriction.
Use local capture as a clue, not a verdict
If Larix offers an audio activity indicator or you have a local recording available, use it to ask a narrow question: does sound appear to be captured on the phone? Speak or play the intended source during a short test and listen back if a recording exists. A silent local capture points you back towards Android access, the selected Larix input, the accessory connection or the specific capture path.
Sound in a local recording is useful evidence that audio was captured somewhere on the device. It does not guarantee that the same sound is routed into the live encoder, sent to YouTube, or audible to viewers. Local capture and live-stream output are separate checks. The audio can be present locally while the stream’s input or output configuration is wrong.
Use the results as a branching diagnostic, not a pass/fail certificate:
| Test result | What it suggests | Next check |
|---|---|---|
| Local capture is silent | The intended source may not be reaching Larix | Recheck Android access, Audio source and accessory recognition |
| Local capture has sound, YouTube preview is silent | Capture may work, but the live hand-off needs checking | Review Larix’s stream setup and YouTube’s incoming preview |
| YouTube preview has sound, separate playback is silent | The incoming stream may contain audio, but playback needs checking | Test another device, browser or playback route |
| Results differ between built-in and external input | The source or connection may be involved | Compare the input selection and connection one change at a time |
The table narrows the next place to look; it does not identify a cause on its own. A local recording can use a different route from the live stream, and a single viewer device can have its own muted or misrouted playback. If the results conflict, repeat the same short test with the same source and check from a second playback device where practical.
Check the encoder hand-off and YouTube playback
When local capture contains the intended sound but the YouTube stream appears silent, check the live hand-off rather than repeatedly changing Android permissions. Confirm that Larix is sending to the intended YouTube broadcast and that its stream connection settings are the ones for that broadcast. YouTube’s encoder setup guide explains entering the YouTube Live server URL and stream key in an encoder, and recommends connecting and setting up microphones with the encoder.
Open the incoming preview in YouTube Live Control Room and listen there if possible. Then check the stream from a separate device, not only the phone running Larix. These comparisons help distinguish a silent incoming stream from a playback problem on one device. YouTube’s encoder instructions do not provide a Larix-specific audio meter diagnosis, so treat this as a practical isolation sequence rather than an official Larix troubleshooting guarantee.
If the Control Room preview has sound but one remote device does not, check that device’s volume, mute state and playback route, then try another browser or device. If both preview and separate playback are silent while local capture has sound, return to Larix’s encoder and stream settings. If neither local capture nor the incoming preview has sound, stay nearer the phone and input checks. Each result narrows the path, but none guarantees what every viewer hears.
A stream can also be mistaken for an audio fault when the live connection itself is unstable or the wrong broadcast is being watched. Confirm that you are monitoring the intended live event and allow the preview to settle before comparing. Avoid changing several settings at once: if the sound returns, you otherwise will not know whether a source selection, connection correction or playback change mattered.
Test for the phone and microphone you actually have
Because the handset and microphone are unspecified, use comparisons rather than instructions tied to one manufacturer’s menu. First test the phone’s built-in microphone with external devices disconnected. Then reconnect one accessory at a time: a wired headset, USB microphone or mixer feed, for example. Keep the same speaking or playback test so that the source is the only deliberate change.
For each source, note four things: whether Android grants the relevant access, whether Larix shows or selects that source, whether local capture contains sound, and whether YouTube’s incoming preview contains sound. A compact record prevents guesswork when menu names differ:
| Source being tested | Android access or recognition | Larix source selected | Local result | YouTube preview |
|---|---|---|---|---|
| Built-in microphone | Note what the phone permits | Note the selected built-in source | Record what you hear | Record what you hear |
| Wired or USB microphone | Note whether the phone recognises it | Confirm the external source | Record what you hear | Record what you hear |
| Mixer or line feed | Note the connection and signal | Confirm the intended input | Record what you hear | Record what you hear |
| Sound from another app | Check OS and app capture support | Check Media sounds if offered | Record what you hear | Record what you hear |
This comparison is especially useful when a physical connection appears to fit but the signal is not recognised. If the built-in microphone works while an external source does not, check the adapter, input type and Larix source before buying different equipment. A compatible USB-C lavalier microphone can be an alternative if you have established that the current microphone or connection is the problem; check compatibility with your phone and intended use before purchase. New hardware cannot resolve an app permission denial or a YouTube stream configuration fault.
If you are setting up an always-on channel, a phone microphone is a different operating choice from sending a prepared video file. The guide to managing a 24/7 YouTube stream from your phone without a PC helps frame that distinction. For file-based approaches, compare how audio is routed in OBS and FFmpeg for pre-recorded streams; neither changes what Android allows Larix to capture from a phone microphone.
Keep a repeatable test for the next stream
Once you have a result that works, write down the source, relevant Android permission state, Larix Audio source and any external connection used. Keep a short test clip or note what you said and when, so that a later check can use the same source. This is not a guarantee that a future broadcast will carry sound, but it gives you a baseline to compare after an app, OS or accessory change.
Before a longer broadcast, check the incoming YouTube preview and listen from another device. If the stream is intended to run unattended, a quick check at launch is more useful than discovering silence after the audience has already asked about it. The separate article on monitoring an FFmpeg stream and restarting it when it fails covers a different PC-based setup, but the underlying habit of checking the actual outgoing stream is relevant.
Where a phone-based setup keeps requiring hands-on checks, a prepared video broadcast may be a better fit than capturing live audio continuously. StreamNeo can remove the need to leave a computer running by turning an uploaded video into a YouTube live stream, which is useful when the source is a finished file rather than a microphone feed. It is YouTube-only, so it is not a solution for diagnosing or capturing live Android microphone audio.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Why is Larix silent on YouTube but my phone recording has sound?
A local recording suggests the phone captured audio, but it does not prove the same audio is being sent through Larix’s live encoder. Check Larix’s stream connection settings, the YouTube incoming preview and playback from a separate device to locate the difference.
Does microphone permission allow Larix to capture music from another app?
Not necessarily. Microphone permission concerns microphone access, while Android’s support for capturing other apps’ playback depends on Android version and whether the source app allows external recording. Larix’s Media sounds setting applies to that separate capture path where it is supported.
Should I set Larix’s sample rate to 48000?
Larix’s Google Play listing mentions a higher sample rate such as 48000 as a possible test for some external devices. It is not a universal setting or a guaranteed fix. Try it only when relevant to the input, change one setting at a time and compare the result.
What if the YouTube preview has sound but viewers still cannot hear it?
Check the stream on a separate device and confirm that the playback is not muted or routed elsewhere. One device’s silence does not show that every viewer is receiving a silent stream, and a preview with sound does not guarantee every playback path works.