-
Notifications
You must be signed in to change notification settings - Fork 22.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with "Web Audio playbackRate explained": (Note: pitch of the audio track does not change, for video only) #3783
Comments
I can update this 👍 |
It's possible that this is dependent on the audio format of the video file, but I'm not sure. |
I think this is not correct. The spec is clear that the I think what's happening with the example quoted: https://mdn.github.io/webaudio-examples/decode-audio-data/ is that this example isn't using the If I use the same audio file in an One real issue is that https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement/playbackRate says:
It looks like Maybe we should file a separate issue for that though? |
It turns out that we have BCD for |
I filed #14183 to add this. |
MDN URL: https://developer.mozilla.org/en-US/docs/Web/Guide/Audio_and_video_delivery/WebAudio_playbackRate_explained
What information was incorrect, unhelpful, or incomplete?
One of the notes says "The pitch of the audio track does not change when playBackRate is altered." This is true for video elements, like the example provided. However, it's not true for audio elements, like this example.
Ideally, links to examples of both types would be provided, along with a more detailed note.
Specific section or headline?
Notes
What did you expect to see?
The pitch of the audio track changes when playBackRate is altered for audio elements, but not for video elements.
Did you test this? If so, how?
I compared the relationship between pitch and playback rate with these two examples:
MDN Content page report details
en-us/web/guide/audio_and_video_delivery/webaudio_playbackrate_explained
The text was updated successfully, but these errors were encountered: