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
Describe the bug
The h264 bitstream to save sps and pps data, currently parses only if the bitstream if buffer starts with sps information. But for some h264 bitstreams sei information prepended before sps data hence the parser fails to save the sps and pps data.
To Reproduce
Create a pipeline connecting rtspCam module to mp4Writer.
Expected behavior
The parses should also look if sei data is prepended before sps . If yes, then it should also save the sei information along with sps and pps data.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: [e.g. iOS]
Version [e.g. chrome, safari]
Cuda Version [e.g. 22]
Architecture [e.g. x86_64, arm64]
Additional context
Add any other context about the problem here.
Would you like to work on the issue?
Please state if this issue should be assigned to you or who you think could help to solve this issue.
The text was updated successfully, but these errors were encountered:
Describe the bug
The h264 bitstream to save sps and pps data, currently parses only if the bitstream if buffer starts with sps information. But for some h264 bitstreams sei information prepended before sps data hence the parser fails to save the sps and pps data.
To Reproduce
Create a pipeline connecting rtspCam module to mp4Writer.
Expected behavior
The parses should also look if sei data is prepended before sps . If yes, then it should also save the sei information along with sps and pps data.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
Would you like to work on the issue?
Please state if this issue should be assigned to you or who you think could help to solve this issue.
The text was updated successfully, but these errors were encountered: