Opened 16 months ago
#11603 new defect
error handling of CBS
| Reported by: | quinkblack | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | undetermined |
| Version: | unspecified | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description
When use CBS to parse bitstream, it can check invalid synatax/data in the bitstream, and report error. How to handle these error is a problem.
For example, when there are error in SEI, it can break the decoding/transcoding process.
./ffmpeg -bsf:v h264_metadata -i ~/Movies/bean.mp4 -an -f null - [h264_metadata @ 0x60000392c0f0] Invalid SEI user data unregistered payload. [h264_metadata @ 0x60000392c0f0] Failed to read unit 0 (type 6). [h264_metadata @ 0x60000392c0f0] Failed to read access unit from packet. [vist#0:0/h264 @ 0x14c704ba0] Error applying bitstream filters to a packet: Invalid data found when processing input [in#0/mov,mp4,m4a,3gp,3g2,mj2 @ 0x14c6062c0] Task finished with error code: -1094995529 (Invalid data found when processing input) [in#0/mov,mp4,m4a,3gp,3g2,mj2 @ 0x14c6062c0] Terminating thread with return code -1094995529 (Invalid data found when processing input)
We can ignore some error like invalid data.
It would be better with the context that the error happens only with SEI, so it isn't fatal.
Attachments (1)
Note:
See TracTickets
for help on using tickets.



video with broken SEI