MP4 Containers created by MP4Box fail to parse having 'meta' atom set
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 28/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- rust
- Domain
- audio-video-rtc
Research direction
Reproduce the MP4Box command from the issue using the ffmpeg conversion steps, then call mp4parse::read_mp4 on the resulting file. Compare parsing with and without the meta atom and trace where CheckParserStateErr is returned. Done means the reported MP4 parses successfully or the unsupported structure is reported explicitly; the related GPAC issue may provide context.
Written by the indexing model from the issue text.
Description
Hello there,
I have issues when I'm trying to convert Original Sony ILCE-7M4 movies to HEVC with a lower bitrate, and adding a META box / atom via MP4Box.
I do the following steps:
First I CONVert the ORIGinal File
ffmpeg -i "${ORIGFILE}" -preset faster -c:v libx265 -crf 17 -c:a aac_at -b:a 192k -movflags use_metadata_tags+faststart -map_metadata 0 -tag:v hvc1 "${CONVFILE}"
Then I add a meta box to a new PROCessed file (previously I added XML data to the meta, but this does not make any difference)
MP4Box -add "${CONVFILE}#1" -add "${CONVFILE}#2" -set-meta meta:tk=1 -new "${PROCFILE}"
When I then try to parse the file via mp4parse::read_mp4(&mut file).unwrap() I get thread 'main' panicked at 'called Result::unwrap()on anErr value: InvalidData(CheckParserStateErr)'
Can you please have a look at this? In the gpac area I already tried to investigate what happens, but I have to confess that I'm not an expert obviously ;). -> https://github.com/gpac/gpac/issues/2603
Thank you very much,
Joachim
- Dominant language
- Rust
- Stars
- 448
- Forks
- 72
- Avg merge
- 20d 3h
- Merged PRs (30d)
- 1
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 mozilla/mp4parse-rust
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
mozilla/mp4parse-rust#444 · 5 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
mozilla/mp4parse-rust#441 ·
-
senc box Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
mozilla/mp4parse-rust#415 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
mozilla/mp4parse-rust#412 · 2 comments ·
-
Difficulty 2/5 Half a day Newbie friendliness 35/100
mozilla/mp4parse-rust#411 · 1 comment ·
All issues in mozilla/mp4parse-rust
Similar issues
-
bug CLI custom-model
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
rust-bitcoin/rust-bitcoin#6930 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fulcrumgenomics/ferro-hgvs#2251 ·
-
A-allocators A-docs C-enhancement T-libs
Difficulty 2/5 1-3 hours Newbie friendliness 75/100