02-24-2012 09:36 AM - edited 02-24-2012 09:38 AM
you may be using a single audio element that is over-writing itself when you call the second sound to be played. i think you just need to create two different audio elements (if you're using the HTML5 audio)...
var firstSound = document.createElement('audio');
var secondSound = document.createElement('audio');
in your script:
both should play at the same time.
if that doesn't work or you need help with how to structure in your app, let me know. i just tested it in my app and it worked with no issues.
02-24-2012 02:23 PM
good call @drony... i just ran it through the firefox browser and it worked. i am on the 18.104.22.168 sdk and the playbook hardware with 2.0 OS. i will try the same test when i get home this afternoon and confirm or deny my outrageous () claim. i am pretty sure the actual playbook would play multiple sounds because i had that problem a few times when i only wanted it to play 1 at a time - but i will confirm later.
02-24-2012 09:11 PM
correct - chrome will allow my two elements to play simultaneously, but the second sound overrides the first in the app. i jumped the gun, but at least using the HTML5 audio element (unless i'm missing something), it doesn't look like it will allow 2 simultaneous sounds.
03-05-2012 07:48 AM - edited 03-05-2012 07:58 AM
this is not possible mobile webkit engine.
All mobile browsers appear to have this limitation. They will only play 1 piece of media at a time through their HTML5 native audio/video.
This affect: iOS, Android, BB PlayBook.
and apple dev source