Closed Bug 934100 Opened 12 years ago Closed 11 years ago

createMediaElementSource audio progress bar

Categories

(Core :: Web Audio, defect, P2)

25 Branch
x86_64
Windows 7
defect

Tracking

()

RESOLVED DUPLICATE of bug 938022

People

(Reporter: nov_fr, Unassigned)

References

Details

(Whiteboard: [bugday-20131106])

Attachments

(1 file)

10.33 KB, application/empty
Details
Attached file webaudioapi.js
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release) Build ID: 20131025151332 Steps to reproduce: I use createMediaElementSource on an audio tag to create visual analysers: _this.analyser = window.myAudioContext.createAnalyser(); _this.source = window.myAudioContext.createMediaElementSource($(audio).get(0)); _this.source.connect(_this.analyser); _this.analyser.connect(window.myAudioContext.destination); (see attachment for more details) Actual results: The progress bar of the audio tag doesn't move. You can see the problem here: http://www.arnaudcompo.fr/Music/8/Routes-Numeriques.html (it works in Chrome 30.0.1599.101 m) The remaining time is not updated too (audio.currentTime always equal to 0)
Same with 2013-11-06-03-02-00-mozilla-central-firefox-28.0a1.en-US.linux-x86_64.
Component: Untriaged → Web Audio
Product: Firefox → Core
Whiteboard: [bugday-20131106]
"The HTMLMediaElement must behave in an identical fashion after the MediaElementAudioSourceNode has been created, except that the rendered audio will no longer be heard directly, but instead will be heard as a consequence of the MediaElementAudioSourceNode being connected through the routing graph. Thus pausing, seeking, volume, .src attribute changes, and other aspects of the HTMLMediaElement must behave as they normally would if not used with a MediaElementAudioSourceNode." I wonder whether that is meant to be the same with mozCaptureStream. I haven't found documentation of mozCaptureStream.
Blocks: 855568
Priority: -- → P2
Just to inform you that the site http://www.arnaudcompo.fr/ is no longer available. However, the problem is solved in Firefox Nightly (29.0a1)
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: