Choose the right input and tool source
Use a file you are authorised to inspect and a legitimate FFmpeg distribution for your operating system. This page does not verify a downloaded binary. Work with a local reference file rather than pasting a private streaming URL into a command or public support post.
Keep the original unchanged. ffprobe inspects input; the example below is not a transcoding command and specifies no output media file.
Request a limited structured report
The official documentation provides stream selection and structured output. For a local file named sample.mp4, an example is: ffprobe -v error -show_entries stream=index,codec_type,codec_name,profile,width,height,pix_fmt -of json "sample.mp4".
Use the literal local filename appropriate to your own environment and understand shell quoting before entering paths. Do not copy an untrusted filename into command syntax or add account-bearing addresses to make the example resemble a live service.
Read the stream entries
Inspect each reported stream separately. An audio stream has a different role from video or subtitles. Codec name and profile describe the detected track; dimensions describe the video stream rather than the television's current HDMI output.
Unknown or absent fields remain unknown. Do not infer HDR, complete compatibility or a source bitrate from an unrelated displayed value. The tool documentation is the reference for the exact fields your version reports.
Limit what you share
For a support question, extract only the relevant non-secret fields and include the ffprobe version. Full reports can contain local paths, tags or other metadata unrelated to the fault. A developer may need a specific sample later, but metadata alone often helps identify the next question.
Do not treat a clean report as a safety scan. It neither authenticates the file nor establishes that every decoder will handle it.
Test playback separately when appropriate
Use the actual supported app and device to check the task. Record opening, picture, sound, subtitle and seek results individually. A format inspector can identify a requirement while a physical test establishes observed behaviour under stated conditions.
No command or media test was executed here. This page supplies a scoped example and interpretation workflow, not an IPTV Canada compatibility result or a licence to redistribute media.
Check the tool version with the report
Field availability and interpretation can change across tool releases. Keep the installed ffprobe version with the selected output, and consult its matching documentation where necessary. Do not add a large unrestricted report simply to compensate for an unfamiliar field. Ask which property the developer needs and retain the narrow local-file scope of the example.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- FFmpeg ffprobe documentation — Official current tool documentation excerpt: stream selection and structured inspection. Example command is proposed for an authorised local file, not executed here.
- Android supported media formats — Official current documentation excerpts: container/codec and profile qualifications. No device-wide or IPTV player guarantee inferred from a framework table.
