Skip to content

Troubles with "Start TS Packet No:" after "Parse data" #51

@lars18th

Description

@lars18th

Hi @EricBerendsen ,

The problem is that after doing "Parse data" with the right mouse button in a pid with PES Data (video, audio, substitles), when checking the "Start TS Packet No:" numbers the values seems to be incorrect. My assumption is that this value indicates the TS PACKET where the PES packet starts. However, if I go to the Transport packets, the "index" doesn't exists.

But this is not a bug. The value is correct. The problem is that the value "Start TS Packet No:" references the TS packet of the total packets. And the list "Transport packets" is indexed with the PID list order (aka the packets of this pids). So here is the root cause of the confusion. Therefore, my suggestion is to print the two values: the "global" TS packet and the "local" TS packet. Then it will be more easy to find the packet, independent of the list that you're using. Example: Start TS Packet No: 0xBD0D (48397) [28], where [28] is the 28th packet of this pid when you search in the "Transport packet" tree. Take note that after you full expand the Transport packet tree you will se the (48397) packet number, but not when you're expanding it.

Do you agree with this simple improvement?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions