Improve mp3 trimming
Categories
(Core :: Audio/Video: Playback, defect, P1)
Tracking
()
People
(Reporter: padenot, Assigned: padenot)
References
(Blocks 1 open bug)
Details
Attachments
(1 file, 4 obsolete files)
In bug 1566389, mp3 decoding was made almost correct. It's not correct if the end trimming spans two packets, like it is in this file: https://github.com/juj/audio_test_suite/blob/master/8bit_detective/8bit_detective_8000hz_8kbs_mono_lame3.99.mp3, that has a duration of 28.65675s, but Firefox reports 28.6618820861678s, it's missing 41 frames at the end, after having trimmed the last packet, it should have trimmed the previous one.
| Assignee | ||
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
| Assignee | ||
Comment 2•5 years ago
|
||
We can't handle this at the decoder level, because the decoder doesn't know that
a particular packet it's seeing is the second to last packet and it should start
trimming the end of this packet because the encoder padding spans multiple
packet.
| Assignee | ||
Comment 3•5 years ago
|
||
Depends on D94469
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
| Assignee | ||
Comment 4•5 years ago
|
||
jya, can you r+ the patches here and then we can land? It's your patch and my test, fixed.
Updated•5 years ago
|
Comment 6•5 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/d5cbc458d318
https://hg.mozilla.org/mozilla-central/rev/863ecb9b15d5
Comment 7•5 years ago
|
||
Backed out for crashing in mozilla::MP3TrackDemuxer::GetNextFrame: https://hg.mozilla.org/mozilla-central/rev/d7d7fd7434a6f8945394e304b21bb23c727bd04b
Comment 8•5 years ago
|
||
For crashes like bp-d2311904-dee6-4e6c-9ea5-8fcd50201106 - [@ mozilla::MP3TrackDemuxer::GetNextFrame]
Comment 9•5 years ago
|
||
Backed out changeset 863ecb9b15d5 (bug 1669503)
Backed out changeset d5cbc458d318 (bug 1669503)
Updated•5 years ago
|
| Assignee | ||
Comment 10•5 years ago
|
||
Updated•3 years ago
|
Updated•3 years ago
|
| Assignee | ||
Comment 11•3 years ago
|
||
Fixed by the big patch series in bug 1817997 and others.
Description
•