Protocol scope and method
The scanner identifies byte offsets for common start codes and does not validate complete PES lengths or decode media.
Search for 000001 + streamId.
Diagnostic scenario
Apply the scanner to a redacted MPEG-PS byte range after RTP payload reconstruction. Locate pack, system, program-stream-map and PES start codes, then compare their byte offsets and declared lengths with a demultiplexer trace.
How to interpret the result
A start-code hit is a boundary clue, not proof of a complete pack or PES packet. Payload bytes can contain similar patterns, and truncated capture data can end before the declared section. Full validation requires length and syntax parsing.
Input reference
- PS/PES hex
- Example default: Sample input included
Common mistakes
- Using an unredacted production capture with vehicle, credential or network identifiers.
- Treating every 000001 pattern as a complete valid packet.
- Treating a successfully parsed sample as standards compliance or interoperability proof.
Before using the result
- Confirm the protocol edition, transport framing and vendor profile before interpreting fields.
- Check declared section and PES lengths around each candidate offset.
- Keep a redacted known-good and known-bad sample as a regression pair.
Questions to check during diagnosis
Does the MPEG-PS Start Code Scanner leave my browser?
No application upload is used. Avoid putting sensitive production data in shareable URLs.
Is this a standards compliance test?
No. Confirm the edition and vendor profile with licensed documents and your target platform.
Offline diagnostic aid. Verify fields, version and vendor extensions before production use.