[Webkit-unassigned] [Bug 122560] New: scriptProcessor Node not working on iOS (Safari/Chrome)
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Oct 9 10:51:44 PDT 2013
https://bugs.webkit.org/show_bug.cgi?id=122560
Summary: scriptProcessor Node not working on iOS
(Safari/Chrome)
Product: WebKit
Version: 528+ (Nightly build)
Platform: Other
OS/Version: Unspecified
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Web Audio
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: leolib2004 at gmail.com
CC: crogers at google.com, leolib2004 at gmail.com
Created an attachment (id=213792)
--> (https://bugs.webkit.org/attachment.cgi?id=213792&action=review)
Code of my app where scriptProcessor Node is not working on iOS
I have created an app in HTML 5 that generates white noise on its own using a ScriptProcessorNode (Google Chrome) or a JavaScriptNode (Safari).
All is working fine for Google Chrome/Safari on my Mac and also in my Android phone but it is not working in Safari/Chrome on my iPod Touch 5th/iPad 4th on iOS 6.1.2.
Browsers checked:
iOS:
Mob Safari 6.0 (Not working) (536.26 WebKit)
Chrome Mob iOS 30.0.1.1599 (Not working) (536.26 WebKit)
Mob Safari 7.0 (Not working)
MAC:
Desktop Chrome 30.0.1599 on MAC (Working) (537.36 WebKit)
Desktop Safari 6.0.5 on Mac (Working) (536.30.1 WebKit)
Android:
Chrome 29.0.1547.59 1547059 (Working) (WebKit 537.36)
I have a button on the screen that when it is touched the gainNode is connected to context.destination or it's disconnected. I can see that onaudioprocess event is not triggered on my iPod (iOS 6.1.2 Safari and Chrome)...
I am attaching the code of my simple app.
What am I doing wrong? Is something different from Safari/Chrome on iOS than for MAC that I am not considering?
I need to create sound samples on the fly... If this work I would add a filter node to filter the white noise for generating other sounds as the user wants.
Thanks!
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list