Open Bug 1268891 Opened 9 years ago Updated 4 months ago

Sound plays as robotic when playbackRate decreased

Categories

(Core :: Audio/Video: Playback, defect, P3)

46 Branch
defect

Tracking

()

People

(Reporter: i.kholikov, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.87 Safari/537.36 Steps to reproduce: Here is an example to reproduce issue http://jsbin.com/jakixi/edit?html,output Open jsbin and try to decrease playbackRate and listen how sound is playing as a robotic. If you change playbackRate to 0.4 sound will not play at all.
OS: Unspecified → All
Hardware: Unspecified → All
Version: 45 Branch → 46 Branch
Component: Untriaged → Audio/Video: Playback
Product: Firefox → Core
I'm not 100% sure if that is how the song is supposed to sound slowed down or not.
It sounds the same on Chrome. So I guess Firefox is doing fine.
Mass change P2 -> P3
Priority: P2 → P3

I'd like to bump this issue, and note that Chrome? & Safari smooth (resamples?) audio at low playback rates while FF (71.0b9) does not. What can we do on our end to help move a resolution forward?

(In reply to John Bartos from comment #4)

I'd like to bump this issue, and note that Chrome? & Safari smooth (resamples?) audio at low playback rates while FF (71.0b9) does not. What can we do on our end to help move a resolution forward?

Test link: https://www.twitch.tv/moonmoon/clip/ExcitedToughSoymilkBrokeBack (voice is especially noticeable)

I can repro on Linux.

Status: UNCONFIRMED → NEW
Ever confirmed: true

(In reply to Alex Chronopoulos [:achronop] from comment #6)

I can repro on Linux.

Thanks, to be clear I reproduced on MacOS Mojave 10.14.6 (18G1012)

Reproduced on Windows 10 18363.657, it started happening with the 73.0 Firefox update, I have an older version (portable) that's one Version behind on my USB And this doesn't have the same issue on the same computer, Tried the basic troubleshooting steps refresh profile and such and reinstall, anything I found so far that could be it is bug 1427267 being fixed, Since that went out in 73.0.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.