You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a simple TS with one video es and one audio es, having the pcr_pid set equal to the video pid, led to a file that has some packet with random_access_filed = 1 but no pcr.
According to ISO/IEC 13818-1 "In the PCR_PID the random_access_indicator may only be set to '1' in Transport Stream packet containing the PCR fields."
I saw that the random access field is triggered in the multiplexer by the presence of the random field in the uref currently passing in the multiplexer, and that this field is set by the framer when it founds an IDR (I am using a h264 video stream).
A small and ugly patch in upipe_ts_encaps just where the tsaf_set_randomaccess is called can fix this (avoiding to set the random access field if there is no pcr), but I am not able to find and information related to the pcr_pid within the encapsulator, so maybe I am not getting the point of where it is managed.
Is this the point where the thing should be managed so I can write my own patch to propagate the pcr_pid information to the encapsulator and use it beside the tsaf_set_randomaccess or should it be addressed in a different way?
The text was updated successfully, but these errors were encountered:
In a simple TS with one video es and one audio es, having the pcr_pid set equal to the video pid, led to a file that has some packet with random_access_filed = 1 but no pcr.
According to ISO/IEC 13818-1 "In the PCR_PID the random_access_indicator may only be set to '1' in Transport Stream packet containing the PCR fields."
I saw that the random access field is triggered in the multiplexer by the presence of the random field in the uref currently passing in the multiplexer, and that this field is set by the framer when it founds an IDR (I am using a h264 video stream).
A small and ugly patch in upipe_ts_encaps just where the tsaf_set_randomaccess is called can fix this (avoiding to set the random access field if there is no pcr), but I am not able to find and information related to the pcr_pid within the encapsulator, so maybe I am not getting the point of where it is managed.
Is this the point where the thing should be managed so I can write my own patch to propagate the pcr_pid information to the encapsulator and use it beside the tsaf_set_randomaccess or should it be addressed in a different way?
The text was updated successfully, but these errors were encountered: