When an Owncast-related YouTube stream has no audio, find the point where sound disappears before changing settings at random. Check the broadcaster’s source and meters first, then test Owncast playback and YouTube’s encoder ingest as separate paths.
The word “Owncast” does not establish how your YouTube output is connected. Owncast documents how to broadcast into an Owncast server, while YouTube documents its own encoder ingest; your YouTube feed might be sent directly by the encoder or arrive by another route. Confirm your actual setup before drawing conclusions.
Quick triage: find where sound disappears
Listen to the source you intend to broadcast: a microphone, desktop audio, music player, or video file. Then listen to the broadcaster’s preview or a short local recording made with the same scene and audio routing. If that recording is silent, the fault is upstream of the platforms: source selection, track assignment, or the encoder’s audio output needs attention.
If the recording has sound, listen to the Owncast playback in a supported player, if Owncast is one of your destinations. Separately inspect YouTube’s Live Control Room for the stream’s audio status and, where possible, listen to the live preview. Sound in Owncast but not YouTube suggests checking the output that feeds YouTube; sound on YouTube but not Owncast points you towards the Owncast-bound output or playback path.
Make a simple record of each result before you change anything: source heard, encoder meter moving, local recording audible, Owncast playback audible, and YouTube audio present. Mark tests you cannot perform as unknown rather than treating them as failures. This gives you a way to compare the paths without assuming that one platform forwards to the other.
For continuous channels, avoid rebuilding the scene during the first checks. A music or video source may be quiet or paused while the microphone remains routed correctly, or the reverse. The OBS audio-level guide for a Hindi audiobook stream is useful when you need to distinguish a moving meter from audio that is actually audible in the final mix.
Check the audio source and broadcaster meters
In OBS or your encoder, identify which source is supposed to provide sound. Check that it is active, not muted, and assigned to the scene you are streaming. For a microphone, speak near it; for desktop audio, play a known sound; for a media source, start a segment that definitely contains audio. Watch the relevant meter while each test sound is present.
A meter that does not move narrows the problem to the selected device, source configuration, mute state, or the scene’s audio routing. Confirm the correct microphone or playback device is selected in the operating system and in the broadcaster. If you recently unplugged a headset, changed a USB port, or switched scenes, the application may still refer to a device that is no longer active.
A moving meter is evidence that the broadcaster sees a signal, but not proof that the signal reaches the output track. Check the audio mixer, track assignment, and monitoring configuration. Listen through the broadcaster’s monitor function if available, taking care not to create an echo by monitoring the same microphone through speakers. A local recording is a stronger check of what the chosen scene and output routing actually produced.
Make that recording with the same scene, sources, and audio tracks used for the live output. Play it in an ordinary media player, not only inside OBS. If it is silent, or if it contains the wrong source, fix the mixer or source routing and record again. If it is audible locally, preserve the recording as a known-good reference while you test each platform path.
YouTube’s own guidance starts with the encoder’s sound, routed sources, encoder errors, and local archive; when the encoder output is healthy, it recommends looking at the outbound connection. See YouTube’s live streaming troubleshooting guidance. That order matters: changing an ingest setting cannot restore a sound that the encoder never included.
Confirm the encoder’s audio settings
Once the source and local output are audible, inspect the audio settings for each destination. If your encoder offers multiple outputs, do not assume they use the same source, track, codec, or bitrate. Check each output’s audio-enable option, source or track routing, number of audio streams, codec, sample rate, and bitrate. A profile copied from another job can leave the video configured correctly while its audio track is absent or routed elsewhere.
For an Owncast-bound stream, Owncast recommends H.264 video and AAC audio for compatibility. Its broadcasting documentation describes the supported workflow, and its OBS setup instructions explain configuring a custom RTMP service with the Owncast endpoint and matching stream key. These instructions explain sending a stream into Owncast; they do not establish how your separate YouTube output is routed.
Owncast’s FFmpeg example specifies AAC at 128 kbps and 44.1 kHz. Treat those as documented example settings, not a guarantee that every encoder or output should use the same profile. The relevant comparison is whether the output sent to Owncast uses a compatible audio configuration and whether the selected source is actually included.
For YouTube RTMP or RTMPS ingest, YouTube accepts AAC or MP3. Its published stereo recommendation is 44.1 kHz and 128 kbps; consult the current YouTube live encoder settings rather than relying on a saved preset. YouTube’s error guidance also flags multiple audio streams and unsupported settings, so check that the output has one intended audio stream and that the dashboard recognises its format.
Change one setting at a time and repeat the local recording or destination test. If you change codec, sample rate, track assignment, and output profile all at once, a successful result will not tell you which change mattered. Keep a note of the original profile so you can restore it if a change makes the picture or sound worse.
Test the Owncast ingest and playback path
If Owncast is a destination, confirm the encoder is using the Owncast endpoint and the corresponding stream key. Owncast’s getting-started configuration guide covers initial stream setup. A connected video picture alone does not confirm that audio arrived: use the Owncast playback page and a supported player to listen, and check whether the problem is consistent across players.
Owncast says it passes audio through untouched by default. As a result, missing or unsuitable audio at the input can remain missing or unsuitable in a served output that uses passthrough. Owncast also documents that when passthrough is disabled for an output variant, that variant’s audio is re-encoded to AAC. This is useful context when diagnosing Owncast playback, but it does not show that a YouTube output goes through Owncast.
If video plays on Owncast but sound does not, return to the local recording and compare it with the Owncast-served playback. If both are silent, the source or encoder output remains the likely place to investigate. If the recording is audible but Owncast playback is not, confirm the Owncast-bound output’s audio settings and inspect the player and stream diagnostics before changing the YouTube profile.
Owncast’s Stream Performance page reports playback metrics and errors for supported players; its hardware page gives CPU, memory, and disk context. Use these as observations about the Owncast-served path. They can help distinguish player or playback trouble from an upstream source problem, but they cannot by themselves establish what a separate YouTube ingest received.
Keep the test narrow. Try another supported player or browser, then compare the result with the original. If only one player is silent, note the player and its error rather than changing the encoder immediately. If every Owncast playback test is silent but a local recording is audible, capture the relevant Owncast error and move to the settings for the Owncast destination.
Check the separate YouTube output path
Now treat YouTube as its own destination. Identify what sends video and audio to YouTube: OBS directly, a second encoder output, or another process in your setup. Do not infer the path from the presence of Owncast. Check the actual output configuration and confirm that its audio-enable option is on, its intended source or track is selected, and exactly one audio stream is being sent.
If your encoder has separate output profiles, compare them side by side. A direct YouTube output can have a different track selection from an Owncast-bound output even when both use the same scene. Check whether the output is AAC or MP3, whether the sample rate and bitrate match YouTube’s published guidance, and whether the audio track is present in a local recording of that exact output where the encoder permits it.
Open YouTube Live Control Room while the stream is running and read the audio diagnostics, not just the video preview. A visible picture with no sound can mean the video portion reached YouTube while the audio stream did not. The status message can distinguish no audio from unsupported audio settings or multiple streams; use that clue to choose the next check rather than changing unrelated video settings.
For a channel that switches between playlist items or scenes, reproduce the transition with a short test. A source may have audio in one item and none in the next, or a scene change may alter track routing. The article on OBS switching between VLC playlist items and YouTube disconnects deals with a different symptom, but the same practical habit applies: test the transition itself instead of checking only a stationary scene.
If the YouTube output uses an intermediate process, inspect that process’s input and output separately. Verify that it receives audio from its source and includes audio in the stream it sends to YouTube. Avoid assuming that a successful Owncast playback proves that intermediate output is carrying the same audio; only a test at the YouTube-facing output can confirm that.
Use YouTube’s no-audio status message
YouTube’s error wording includes “Your encoder is sending no audio.” The live streaming error messages page associates this with a stream that has no audio and notes that some encoders let you turn audio on or off. Start by checking that the YouTube-bound encoder has audio enabled and that its output includes the intended source.
If the dashboard reports multiple audio streams, set the output to send one intended stream and retest. If it reports an unsupported audio codec or incorrect sample rate, adjust the YouTube-bound output to an accepted codec and the sample rate indicated by the dashboard or official guidance. Do not copy a setting from the Owncast output unless you have confirmed that both destinations share the same output configuration.
Read the whole status message and note when it appears. A warning that begins after a scene change or playlist transition may point to a source or track change at that moment. A persistent warning from the start of the stream is more consistent with an output configuration problem. These are clues, not proof, so compare them with a local recording and the encoder’s own error log.
After correcting one setting, allow the dashboard to update and confirm whether the same message remains. If YouTube still reports no audio while the exact YouTube-bound output is audible locally, check the outbound connection and any intermediate process between that output and YouTube. A local file confirms the encoder’s output at that test point; it does not prove that every downstream link delivered it.
Compare results and isolate the failing link
Use the test results together rather than treating “audio works” as a single yes-or-no answer. The pattern tells you which link deserves attention next. Keep the path labels literal: “Owncast playback” is not a synonym for “YouTube output”, and a healthy result on one does not prove the other is healthy.
| Test result | What it suggests | Next check |
|---|---|---|
| Source is audible, but the broadcaster meter does not move | The source may not be selected, active, or routed to the scene | Check the device, mute state, and scene mixer |
| Meter moves, but the local recording is silent | The signal may not be on the recorded or output track | Check track assignment and audio output settings |
| Local recording is audible, but Owncast playback is silent | The Owncast-bound output or its playback path needs investigation | Confirm destination settings, then inspect Owncast player diagnostics |
| Owncast playback is audible, but YouTube is silent | The YouTube-facing output or a link after it may be failing | Inspect YouTube audio status and the actual route into YouTube |
| YouTube is audible, but Owncast playback is silent | The issue is likely specific to the Owncast-bound output or playback | Compare its source, track, and audio settings with the working output |
| Both platform paths are silent, but local audio is present | A shared downstream step may be dropping audio, or the outputs may not match the local test | Test each destination-facing output independently |
The table narrows the search; it does not establish a cause on its own. For example, an audible local recording and silent YouTube preview could result from a different output profile, an intermediate process, or a connection problem. Confirm which component sends the YouTube stream, then test immediately before and after that component if your tools allow it.
For an always-on channel, keep a short record of the time, active scene or playlist item, encoder profile, local recording result, Owncast result, YouTube message, and any setting changed. That makes a recurring silent segment easier to compare with a known-good one. The guide to monitoring an always-on YouTube stream remotely may help you plan checks when you cannot stay beside the encoder.
Do not buy a new microphone or interface until a test points towards the physical source. If the meter moves and the local recording is clear, replacing the microphone is unlikely to solve a missing audio track on one destination. Likewise, do not rebuild the entire stream because YouTube’s dashboard identifies a specific codec or track problem.
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
Does Owncast automatically forward my stream to YouTube?
Do not assume that it does. Owncast’s published broadcasting guidance describes sending a stream into Owncast, and YouTube documents its own encoder ingest; those facts do not establish your setup’s routing. Check which encoder or process actually sends the YouTube output.
Why is the YouTube picture present when audio is missing?
Video and audio are separate parts of the output, so a destination can receive a picture even when the encoder has not included the intended audio stream. Check the YouTube-bound output’s audio option, source or track routing, stream count, and dashboard message.
What audio settings should I try for YouTube RTMP or RTMPS?
YouTube accepts AAC or MP3, and its published stereo guidance specifies 44.1 kHz and 128 kbps. Confirm current guidance and the Live Control Room error details before changing settings, and make sure the encoder sends one intended audio stream.
Can Owncast’s performance page prove that YouTube received audio?
No. Its playback metrics and errors describe supported players on the Owncast-served path, not necessarily the separate output sent to YouTube. Test and inspect the YouTube-facing output directly.