Open
Bug 1731813
Opened 3 years ago
Updated 3 years ago
Playback of .mp3 file as a MediaElementAudioSource hiccups at start
Categories
(Core :: Audio/Video: Playback, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox-esr91 | --- | affected |
firefox93 | --- | wontfix |
firefox94 | --- | wontfix |
firefox95 | --- | wontfix |
People
(Reporter: jujjyl, Assigned: alwu)
References
(Regression)
Details
(Keywords: regression)
STR:
- Visit http://clb.confined.space/audio_test_suite/8bit_detective/8bit_detective.html (or git clone the site down for local examination from https://github.com/juj/audio_test_suite )
- Click the last button on the page '8bit_detective_8000hz_mono_lame3.99.mp3'.
Expected:
The page should play back a seamlessly looping audio file as a MediaElementAudioSource with loop: true.
Observed:
The audio starts playing, but then immediately after ~1/3 seconds, has a hiccup/glitch, and then resumes to play normally. (Compare against the other audio formats for reference)
Updated•3 years ago
|
Assignee: nobody → padenot
Comment 2•3 years ago
|
||
Alastor, this is a regression from https://bugzilla.mozilla.org/show_bug.cgi?id=1712598 it seems like, I just used mozregression to make sure. I can reproduce easily by following the instructions.
Flags: needinfo?(alwu)
Assignee | ||
Comment 3•3 years ago
|
||
Thanks for checking, I will take a look later.
Assignee: padenot → alwu
Component: Web Audio → Audio/Video: Playback
Flags: needinfo?(alwu)
OS: Windows 10 → All
Priority: -- → P3
Regressed by: 1712598
Hardware: x86_64 → Unspecified
Updated•3 years ago
|
Has Regression Range: --- → yes
Updated•3 years ago
|
Keywords: regression
Comment 4•3 years ago
|
||
Set release status flags based on info from the regressing bug 1712598
status-firefox93:
--- → affected
status-firefox94:
--- → affected
status-firefox95:
--- → affected
status-firefox-esr78:
--- → unaffected
status-firefox-esr91:
--- → affected
Updated•3 years ago
|
Updated•3 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•