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

Playground not working on iOS 9.3.1 #173

Closed
hamoid opened this Issue Apr 14, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@hamoid
Copy link

hamoid commented Apr 14, 2016

I have tried on an iPad and the playground is silent.

I haven't checked the code, so I may be wrong, but sound should be enabled on "touchend".
It seems to work by add this:

document.addEventListener("touchend", startMySound, false);

and in startMySound I both .init() and .start() Flocking.

@colinbdclark

This comment has been minimized.

Copy link
Owner

colinbdclark commented Apr 14, 2016

Yes, you're right. This definitely seems to be a regression in iOS at some point. Thanks for noting the workaround. I'll take a look!

@colinbdclark

This comment has been minimized.

Copy link
Owner

colinbdclark commented May 2, 2016

This appears to be due to two issues:

  1. Apple seems to have removed the stop() method from AudioBufferSourceNode, yet Flocking's iOS initialization strategy uses it.
  2. In the master branch (version 0.1.x is unaffected), an Infusion IoC reference to Flocking's ScriptProcessorNode instance is incorrect, causing it to be undefined when initializing on iOS.
@colinbdclark

This comment has been minimized.

Copy link
Owner

colinbdclark commented May 2, 2016

Fixes for this issue have been pushed to master and the 0.1.x branch. I've cut a minor 0.1.6 maintenance release from the 0.1.x branch. Upgrading should resolve the issue causing Flocking not to work on iOS.

colinbdclark added a commit that referenced this issue May 4, 2016

Merge branch 'master' into midi-improvements
* master:
  gh-173: Fixes initialization strategy for recent versions of iOS.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment