Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
- 7.8K All Categories
- 11 Help with translations
- 4.2K General questions
- 107 Roadmap
- 358 Game & application design
- 316 Plugins
- 70 User experience
- 75 Marketplace
- 291 Code snippets
- 34 Building a team?
- 269 Suggestions & requests
- 352 Announce your apps made with Gideros.
- 90 Step by step tutorials
- 668 Bugs and issues
- 195 Introduce yourself
- 239 Announcements
- 106 Forum talk
- 404 Relax cafe
In this Discussion
Sound (wav) playback latency on Android (mainly Samsung devices)...
MobAmuse
Member
The following refers to apps built for Android with Gideros SDK only:
I've written a test drum pad app that triggers sound .wav's when multitouch drumpads are hit.
The multitouch is working 100% on Android and iOS, but there is approx 100ms+ of delay before you here a sound after triggering it from 'touches begin' on Android?
This issue mainly presents itself on Samsung devices and not so much HTC for example and also happens on Icecream Sandwich enabled devices i.e. really odd this!
I've tried using wav samples from 44Khz -16bit all the way down to 8Khz - 8bit and the result is the same. In fact I've tried the audio example 1,2,3 demo that comes with Guideros and it does the same thing. I've even noticed many Android apps on Google Play that are not of course written with Gideros do the same thing on a range of Android devices so I'm not sure it it's Gideros SDK or an Android device hardware/firmware problem.
100ms+ of audio delay is not so noticeable in a game of course but it is big problem in a music based app.
All works great on iOS just not on Android without the 100ms+ latency/delay.
My own Android test device is a Samsung Galaxy Tab S 5.0 wifi (i.e. not a phone) which is running Frodo 2.2.
I played a random free platform demo on just now that had a jump button and the sound triggers instantly! (meh?), so this is why I now think there is something wrong with the Gideros sound API/Layer/Interface perhaps.
I've tried everything pretty much :P
Anyone?
I've written a test drum pad app that triggers sound .wav's when multitouch drumpads are hit.
The multitouch is working 100% on Android and iOS, but there is approx 100ms+ of delay before you here a sound after triggering it from 'touches begin' on Android?
This issue mainly presents itself on Samsung devices and not so much HTC for example and also happens on Icecream Sandwich enabled devices i.e. really odd this!
I've tried using wav samples from 44Khz -16bit all the way down to 8Khz - 8bit and the result is the same. In fact I've tried the audio example 1,2,3 demo that comes with Guideros and it does the same thing. I've even noticed many Android apps on Google Play that are not of course written with Gideros do the same thing on a range of Android devices so I'm not sure it it's Gideros SDK or an Android device hardware/firmware problem.
100ms+ of audio delay is not so noticeable in a game of course but it is big problem in a music based app.
All works great on iOS just not on Android without the 100ms+ latency/delay.
My own Android test device is a Samsung Galaxy Tab S 5.0 wifi (i.e. not a phone) which is running Frodo 2.2.
I played a random free platform demo on just now that had a jump button and the sound triggers instantly! (meh?), so this is why I now think there is something wrong with the Gideros sound API/Layer/Interface perhaps.
I've tried everything pretty much :P
Anyone?
Comments
Likes: MobAmuse
https://deluxepixel.com