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
I think I implemented this in one of the decoders (for debugging?) but this should be everywhere.
I may have put it in a different high level library
Will error if you then start providing data with frames other than 0
Need to be careful about un-timed SPS/PPS/Headers
Frame numbers dictated by output rather than input
We should never ever output a frame with a duplicated frame number unless it IS the same frame (eg. double decode keyframe - or some kinda meta frame - though that should be in the peek meta)
The text was updated successfully, but these errors were encountered:
SoylentGraham
changed the title
When pushing packets with no frame/timestamp, we should auto generate frames
When pushing packets with no frame/timestamp, we should auto generate frame numbers
Feb 10, 2024
I think I implemented this in one of the decoders (for debugging?) but this should be everywhere.
The text was updated successfully, but these errors were encountered: