ffmpeg's decoder error [libaribcaption @ 0000025ee70e1e00]
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- audio-video-rtc
Research direction
No source file, test, or reproducible input is named. Start by reproducing the ffmpeg decoder output and trace how libaribcaption handles the unrecognized DRCS patterns identified by the two MD5 values; done should establish the expected handling and verify that the repeated warnings no longer indicate lost caption characters.
Written by the indexing model from the issue text.
Description
I got the following error in the decoder process inside ffmpeg.
[libaribcaption @ 0000025ee70e1e00] DecoderImpl: Cannot convert unrecognized DRCS pattern with MD5 a368b4ce2212ef80e2bf3d68559f5151 to Unicode
[libaribcaption @ 0000025ee70e1e00] DecoderImpl: Cannot convert unrecognized DRCS pattern with MD5 33d4c5243a45503d43fbb858a728664d to Unicode
[libaribcaption @ 0000025ee70e1e00] DecoderImpl: Cannot convert unrecognized DRCS pattern with MD5 33d4c5243a45503d43fbb858a728664d to Unicode
[libaribcaption @ 0000025ee70e1e00] DecoderImpl: Cannot convert unrecognized DRCS pattern with MD5 33d4c5243a45503d43fbb858a728664d to Unicode
Last message repeated 2 times
[libaribcaption @ 0000025ee70e1e00] DecoderImpl: Cannot convert unrecognized DRCS pattern with MD5 33d4c5243a45503d43fbb858a728664d to Unicode
Last message repeated 3 times
[libaribcaption @ 0000025ee70e1e00] DecoderImpl: Cannot convert unrecognized DRCS pattern with MD5 33d4c5243a45503d43fbb858a728664d to Unicode
Last message repeated 5 times
[libaribcaption @ 0000025ee70e1e00] DecoderImpl: Cannot convert unrecognized DRCS pattern with MD5 a368b4ce2212ef80e2bf3d68559f5151 to Unicode
[libaribcaption @ 0000025ee70e1e00] DecoderImpl: Cannot convert unrecognized DRCS pattern with MD5 33d4c5243a45503d43fbb858a728664d to Unicode
Last message repeated 5 times
[libaribcaption @ 0000025ee70e1e00] DecoderImpl: Cannot convert unrecognized DRCS pattern with MD5 33d4c5243a45503d43fbb858a728664d to Unicode
Last message repeated 1 times
[libaribcaption @ 0000025ee70e1e00] DecoderImpl: Cannot convert unrecognized DRCS pattern with MD5 33d4c5243a45503d43fbb858a728664d to Unicode
Last message repeated 1 times
[libaribcaption @ 0000025ee70e1e00] DecoderImpl: Cannot convert unrecognized DRCS pattern with MD5 33d4c5243a45503d43fbb858a728664d to Unicode
[libaribcaption @ 0000025ee70e1e00] DecoderImpl: Cannot convert unrecognized DRCS pattern with MD5 33d4c5243a45503d43fbb858a728664d to Unicode
Last message repeated 2 times
[libaribcaption @ 0000025ee70e1e00] DecoderImpl: Cannot convert unrecognized DRCS pattern with MD5 33d4c5243a45503d43fbb858a728664d to Unicode
Last message repeated 2 times
[libaribcaption @ 0000025ee70e1e00] DecoderImpl: Cannot convert unrecognized DRCS pattern with MD5 33d4c5243a45503d43fbb858a728664d to Unicode
[libaribcaption @ 0000025ee70e1e00] DecoderImpl: Cannot convert unrecognized DRCS pattern with MD5 33d4c5243a45503d43fbb858a728664d to Unicode
[libaribcaption @ 0000025ee70e1e00] DecoderImpl: Cannot convert unrecognized DRCS pattern with MD5 a368b4ce2212ef80e2bf3d68559f5151 to Unicode
I presume that there is a character string that has not been converted, but how should I deal with it?
- Dominant language
- C++
- Stars
- 129
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from xqq/libaribcaption
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
xqq/libaribcaption#17 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 32/100
xqq/libaribcaption#15 · 1 reaction ·
All issues in xqq/libaribcaption
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·