Stop scrolling: find any packet by name or content in VTCLab Media Analyzer
Open a real bitstream and the Packets panel fills up fast. The demo file atsc3.mpegts - an ATSC 3.0 transport stream carrying HEVC - holds 1,065 packets across two streams, and almost all of them are repetitive slice segments: TRAIL_N, TSA_N, RASL_N, IDR_N_LP, on and on. The handful you actually care about - the VPS/SPS/PPS configuration, the PMT program map, the first keyframe, or whatever packet carries one specific header value - are buried somewhere in that wall. Scrolling to find them is hopeless.
This is exactly what the Find Packet command is for. Type what you are looking for, press Enter, and the list jumps straight to it. Let's walk through it.
Quick start
First, make the Packets panel active by clicking any packet in it. Find Packet is only available when at least one packet is visible, so a single click to focus the panel is the price of entry.
Then open the command. The fastest way is Ctrl+F, which is bound to Find Packet whenever the Packets panel is active. If you prefer the menu, open the command palette with Ctrl/Cmd+Shift+P and type "Find Packet" (it lives under the SEARCH category).
The prompt walks you through three steps.
Step [1/3] - pattern. Type your search text into the field (placeholder "Enter search text"). This is required and cannot be empty. Press Enter to continue.
Step [2/3] - caseSensitive. A Yes/No choice, defaulting to No. Leave it on No unless a short token is over-matching (more on that below). Press Enter.
Step [3/3] - searchContent. Another Yes/No, defaulting to No. No means search packet names only; Yes also searches inside decoded content. Press Enter to run the search.
The overlay footer reminds you of the controls: "Up/Down to navigate. Home/End to jump. Enter to continue. Esc to go back."
Once the search runs, walk through the matches with F3 for the next hit and Shift+F3 for the previous one (or click the ‹ › chevrons in the status bar). Press Esc to clear the search when you are done.
Two search modes: names vs content
The searchContent toggle is the heart of Find Packet, so it is worth understanding what each mode looks at.
By default you are in NAMES mode. It matches the packet name or label only - strings like "HEVC Video Parameter Set (VPS)" or "Program Map Table (PMT)". It is fast, and it is exactly what you want when the goal is "jump to the SPS / VPS / PMT / first IDR slice".
Turn searchContent to Yes and you switch to CONTENT mode. Now the search also looks inside the full decoded content of each packet - every parsed field name and its interpreted value: a PID, an aspect_ratio_idc, a profile_idc, and so on. This mode is slower because it has to decode each packet's details, but it is the only way to find a value that never appears in any title. Use it for questions like "which packet has aspect_ratio_idc = 5" or "find the packet whose PID is 0x100".
Both modes use plain case-insensitive substring matching by default - no regular expressions, no field filters, just "does this text appear anywhere in the searched scope". Setting caseSensitive to Yes makes the match exact-case.
Here is the same idea as a table:
| Aspect | NAMES mode (default) | CONTENT mode (searchContent = Yes) |
|---|---|---|
| What it searches | Packet name / label only | Name plus every decoded field name and value |
| Speed | Fast | Slower (decodes each packet) |
Finds VPS, SPS, PMT, IDR | Yes | Yes |
Finds aspect_ratio_idc, a PID, a profile_idc value | No | Yes |
| Best for | "Jump to the SPS / VPS / PMT / first keyframe" | "Which packet has this buried header value" |
A gallery of searches
Most of your day-to-day lookups fall into a few patterns. Each recipe is a goal, the text to type, and the mode to use.
- Jump to the video parameter set - type
VPS, names mode. Inatsc3.mpegtsthis lands on "HEVC Video Parameter Set (VPS)" at offset0xF37B. - Jump to the sequence parameter set - type
SPS, names mode. Once you land there you can read thesequence_parameter_setfields directly; see Checking the AVC sequence parameter set (opens in new tab) for what those fields mean. - Jump to the picture parameter set - type
PPS, names mode. - Find the program map - type
PMT, names mode. - Land on the first keyframe - type
IDR, names mode. This matches "HEVC Slice Segment (IDR_N_LP)". - Find a packet by a header field name - type
aspect_ratio_idc, content mode. A field name like this never shows up in a packet title, so names mode would miss it. For what that value actually controls, see Aspect ratio: PAR, SAR, and DAR explained (opens in new tab). - Find a packet by a specific value - type something like
general_profile_idc, or a PID number, content mode. - Disambiguate an over-matching short token - enable
caseSensitiveso a small string stops matching things you did not mean.
The pattern to internalize: try names first because it is fast, and reach for content mode the moment you are hunting for a value rather than a kind of packet.
Reading the result
When a search finds something, the list scrolls to the first match and a status bar at the bottom of the Packets panel reports "Found at 0x<HEX>" - for example "Found at 0xF37B". That hex number is the packet's byte position in the file, which makes it easy to correlate the match with the Hex View panel. The ‹ › chevrons next to it step you to the previous or next hit, the same as Shift+F3 and F3.
Two more status messages are worth knowing. Searches wrap around: when you pass the last match, the next step continues from the start (and stepping backwards past the first wraps to the end), with the status showing "Wrapped to beginning" or "Wrapped to end". And if nothing in scope matches your text, the status simply reads "Not found" - your cue to loosen the pattern or, if you were in names mode, re-run with searchContent = Yes.
What it searches
Find Packet searches the visible packets only. If you enable or disable streams in the left panel, you change the set of packets the search runs over. That is useful - disable the streams you do not care about to narrow the search - but it also means a packet hidden by a disabled stream will not be found until you re-enable it.
Tips and gotchas
- Search names first; it is fast. If nothing matches, re-run with
searchContent= Yes. - Matching is case-insensitive by default. Enable
caseSensitiveonly when a short token over-matches. - "Found at
0x…" is the file offset - line it up with the Hex View panel to inspect the raw bytes. - Large files stay responsive and you can cancel a long scan.
- Scope is the visible packets. Toggling streams on or off changes what gets searched.
评论