You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be helpful to provide a way to enable debug mode from within the browser. e.g. Add a "try to play anyway" button to the toast message or enable the debug mode state to be specified in the URL.
The information regarding mobile browser support is currently fragmented and confusing. The main source seems to be #2 which specifies:
Chrome for Android M51 does not support the multichannel audio decoding in MediaElement yet. However, the 4-channel audio stream can be decoded properly with the UnifiedMediaPipeline flag enabled.
Chrome for Android M53 (which is the dev channel ATM) supports the multichannel audio decoding by default, thus Omnitone can be used there without fiddling flags.
The Beta is currently M52 and the only reference to Unified Media Pipeline is a flag confusingly named "Disable Unified Media Pipeline" (with the option available to "enable" the disabling).
But after attaching a desktop debugger I was able to manually change the value of the player debug value to 'true' and the Resonance demo played successfully. (Highlight for me: following the sound of the clucking chickens. :) )
The text was updated successfully, but these errors were encountered:
It would be helpful to provide a way to enable debug mode from within the browser. e.g. Add a "try to play anyway" button to the toast message or enable the debug mode state to be specified in the URL.
The information regarding mobile browser support is currently fragmented and confusing. The main source seems to be #2 which specifies:
The Beta is currently M52 and the only reference to Unified Media Pipeline is a flag confusingly named "Disable Unified Media Pipeline" (with the option available to "enable" the disabling).
But after attaching a desktop debugger I was able to manually change the value of the player
debug
value to 'true' and the Resonance demo played successfully. (Highlight for me: following the sound of the clucking chickens. :) )The text was updated successfully, but these errors were encountered: