Invalid data found when processing input is an FFmpeg error code, not a diagnosis. When relaying radio to YouTube, first find out whether FFmpeg rejects the radio station’s input, fails while decoding it, or encounters a problem at YouTube’s output. Probe the station’s direct stream URL and inspect the surrounding log before changing codecs or bitrates.
What the FFmpeg invalid-data error means
FFmpeg documents AVERROR_INVALIDDATA as “Invalid data found when processing input.” That message says data could not be processed; by itself, it does not identify why. The cause could involve an unexpected response from the radio URL, an unrecognized format, a connection or access issue, or another input-processing step. The precise cause has to be established from the command and log.
For a radio relay, keep the two ends of the workflow separate: the radio station is FFmpeg’s input, and YouTube is its output. A YouTube URL or stream-key problem does not prove that the station’s audio is malformed.
Start by locating the failing stage
Read the complete FFmpeg command and the lines immediately around the error. Note the first preceding warning as well as the final error. Determine whether the failure occurs while opening the radio URL, reading or decoding its media, or connecting to and writing the YouTube output. The generic error string alone cannot distinguish these cases.
#1 Best Overall
- Includes Raspberry Pi 4 4GB Model B with 1.5GHz 64-bit quad-core CPU (4GB RAM)
- Includes Pre-Loaded 32GB EVO+ Micro SD Card (Class 10), USB MicroSD Card Reader
- CanaKit Premium High-Gloss Raspberry Pi 4 Case with Integrated Fan Mount, CanaKit Low Noise Bearing System Fan
- CanaKit 3.5A USB-C Raspberry Pi 4 Power Supply (US Plug) with Noise Filter, Set of Heat Sinks, Display Cable - 6 foot (Supports up to 4K60p)
- CanaKit USB-C PiSwitch (On/Off Power Switch for Raspberry Pi 4)
- Failure before FFmpeg identifies an input format or audio stream: investigate the radio URL, its response, any redirect or access requirement, and whether the installed FFmpeg build supports the protocol and format.
- Input is identified but decoding fails: examine the reported format, stream details, and nearby warnings. Do not assume a YouTube setting can fix an input-side decoding problem.
- Input works but output fails: check the YouTube server URL, stream key, chosen RTMP or RTMPS protocol, and output configuration.
Probe the radio stream URL on its own
Use the station’s actual listening-stream address—not just its website or a station-directory page—with ffprobe:
ffprobe -hide_banner -loglevel debug "RADIO_STREAM_URL"Replace RADIO_STREAM_URL with the direct stream URL. This is an inspection step, not a guaranteed repair. If FFmpeg identifies a format and audio stream, record those details before editing the relay command. If it does not, use the debug output and the server response to narrow down what is happening.
Rank #2
- Broadcom BCM2711, quad-core Cortex-A72 (ARM v8) 64-bit SoC @ 1. 5GHz
- 2. 4 GHz and 5. 0 GHz IEEE 802. 11b/g/n/ac wireless LAN, Bluetooth 5. 0, BLE
- 2 × USB 3. 0 ports, 2 x USB 2. 0 Ports
- 2 × micro HDMI ports supproting up to 4Kp60 video resolution
- Micro SD card slot for loading operating system and data storage
Check what the URL actually returns
- Confirm that the address is the station’s direct audio endpoint. A station page or directory listing may be HTML rather than a playable stream.
- Check whether the address returns a playlist that needs to be parsed to reach the actual audio endpoint.
- Look for evidence of a redirect, authentication requirement, temporary outage, or an HTTP error response. A login page, 404 document, or other text response is not audio; changing audio codec options will not turn it into a stream.
- Check whether the endpoint needs a signed query string or another access detail, but keep tokens and credentials private when sharing commands or logs.
These are possibilities to test, not conclusions implied by the error message. FFmpeg’s protocol documentation covers network protocols and options, but the address and server response determine what a particular station provides.
Check protocol and format support
Compare the URL scheme and the detected stream format with the protocols and formats available in your installed FFmpeg build. A station’s listening URL is an input endpoint. Do not confuse it with FFmpeg’s Icecast publishing syntax: documentation about publishing to Icecast does not establish that a station’s listener URL uses that same syntax. Avoid forcing a format such as MP3 unless the actual response supports that choice; first establish what data the endpoint returns.
Rank #3
- Broadcom BCM2711, Quad core Cortex-A72 (ARM v8) 64-bit SoC @ 1.5GHz
- 1GB, 2GB, 4GB or 8GB LPDDR4-3200 SDRAM (depending on model)
- 2.4 GHz and 5.0 GHz IEEE 802.11ac wireless, Bluetooth 5.0, BLE Gigabit Ethernet
- 2 USB 3.0 ports; 2 USB 2.0 ports.
- Raspberry Pi standard 40 pin GPIO header (fully backwards compatible with previous boards)
Check YouTube only after the input works
YouTube’s encoder workflow uses a server URL and a stream key obtained through YouTube Studio’s Live Control Room. YouTube’s setup instructions say: “To start streaming, enter your YouTube Live server URL and stream key into your encoder.” Copy the current values from the channel’s live setup and keep the key private.
Match the output protocol and audio settings
YouTube’s current encoder-settings page lists RTMP/RTMPS and recommends RTMPS, which encrypts data in transit to Google’s servers. Select the protocol that matches the destination and use the current server URL and key. YouTube lists AAC or MP3 as audio codec options; for stereo audio, its published settings specify 44.1 kHz and 128 Kbps. These are YouTube output settings, not a claim about the radio station’s source bitrate.
Rank #4
- Vilros Complete Starter Kit for Pi 4 Includes Raspberry Pi 4 Model B Board and all the accessories you need to get started.
- 9-PART KIT WILL HAVE YOU READY TO GET UP AND RUNNING: Kit Includes 1. Raspberry Pi 4 Model B Board 2. Case With Easy to connect Built-in fan 3. 64GB Micro SD card Preloaded with RP OS 4. Vilros Pi 4 Compatible Power Supply with Inline on/off switch (power supply color may vary white/black) 5. Micro HDMI to Standard HDMI cable (5ft) 6. Micro SD to USB adapter to reflash card if desired 7. Neoprene Storage Bag to store all parts when not in use 8. Set of 4 Heatsinks 9. Vilros QuickStart Guide instruction booklet for Pi 4
- PASSIVE & ACTIVE COOLING: The included case is well-vented and the kit also includes a set of heatsinks with thermal stickers for easy application and a pre-installed fan to keep the board cool in any use.
- CONVENIENT ACCESSORIES: The power supply features an inline on/off switch neoprene bag that holds and protects all the parts when not in use and the QuickStart guide is updated and written for Raspberry Pi 4.
- IMPORTANT: Kit does NOT include Keyboard, Mouse or Monitor
FFmpeg documents RTMP as a streaming protocol and shows FLV as the general output format for that workflow. Confirm that the command’s output format and destination are appropriate for the selected YouTube ingest protocol; do not use an output-side error as evidence that the input URL is invalid.
Consider whether the live presentation needs video
A radio stream supplies audio. YouTube’s encoder settings also cover video output, but those settings alone do not establish that every audio-only FFmpeg command will be accepted or rejected. If your intended live presentation needs a visual component, configure a legitimate still image or visual loop as a video input. That addresses presentation, not a malformed radio URL.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Best Value
- Includes Raspberry Pi 4 4GB Model B with 1.5GHz 64-bit quad-core CPU (4GB RAM)
- CanaKit 3.5A USB-C Power Supply with Noise Filter (UL Listed) specially designed for the Raspberry Pi 4 (5-foot cable)
- CanaKit USB-C PiSwitch (On/Off Power Switch)
- Set of 3 Aluminum Heat Sinks for the Raspberry Pi 4
Retest one change at a time
- Confirm that the radio URL can be probed or played and note the detected format and audio stream.
- Once the input works, make a short private or unlisted test with the current YouTube server URL, stream key, and matching protocol.
- Change one input or output setting at a time so you can tell which change affects the result.
- Keep a copy of the last working command and compare its log with the failing run.
Results depend on the station endpoint, operating system, FFmpeg build, command, and YouTube channel. The checks above are a diagnostic sequence, not a guarantee that one option will repair every station-specific failure.
Common symptoms and what to check
| Symptom | What to investigate | Next step |
|---|---|---|
ffprobe fails before showing a format or audio stream |
The URL, returned content, redirects, access requirements, temporary availability, or protocol/build support | Probe the direct listening endpoint and inspect the debug log and response before changing codecs. |
| The returned content appears to be HTML or text | A station webpage, login page, error document, or playlist may have been used instead of the audio endpoint | Find the actual stream URL or resolve the playlist to its audio endpoint. |
| The radio input probes, but YouTube does not receive the stream | The output-side server URL, stream key, selected RTMP/RTMPS protocol, or output configuration | Verify the current values in YouTube Studio and test the destination separately from the radio input. |
| The stream connects but its audio settings do not match the intended output | The YouTube encoder audio codec, sample rate, or bitrate settings | Check YouTube’s published settings: AAC or MP3, and for stereo, 44.1 kHz and 128 Kbps. |
| A command works briefly but not as an unattended relay | Whether the computer or hosted environment, network connection, and source endpoint remain available | First resolve any URL or format error. A VPS is an optional way to host a continuous process, not a repair for invalid input data. |
Running a continuous radio relay
For a short diagnostic test, run FFmpeg locally and observe its output. A continuous relay also depends on the process remaining active and on the radio source and YouTube destination staying reachable. You can run the process on a local computer or choose a hosted VPS; that is a hosting decision, not a fix for a malformed URL, unexpected response, or unsupported format. Whichever you use, protect the YouTube stream key and any private or signed radio URL.
Or let it run in the cloud
If the goal is a continuous YouTube stream from uploaded audio or video rather than diagnosing this particular FFmpeg error, StreamNeo is a cloud option. Upload a recording or build a playlist, add your YouTube stream key, and go live. Nothing has to stay on at home; it plays uploaded videos rather than broadcasting from a camera. It supports any uploaded quality up to 4K 60fps at one price per slot, with no re-encode or quality tiers, and can automatically recover if YouTube drops the stream. The first day is free with no card.
StreamNeo is for YouTube only, and it does not fix a radio URL or FFmpeg input error. See StreamNeo for service details, or view plans. The first day is free with no card, and the monthly plan is $9.99 per month. Start your free day with StreamNeo.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
