Hi I’ve been battling to find ways round the audio latency issues with Android and whenever you add an improvement to try help the issue. A recent test i made where the audio was always on ( never triggered on and off) but was able to change pitch on different keys still had a delay so I created a really basic test. I had one touch event which played a sound at the same time as blinking a square and a timer event which triggered a similar event, not the same one and blinked a different square. what I see is the latency comes from the touch event. When the touch event is triggered, the corresponding square blinks instantly and then the delayed audio sound. With the timer event, the square blinks at the same time as the audio event … it seems so there isnt a delay on the audio when triggered by a timer. Unless im going crazy?
[import]uid: 124886 topic_id: 34842 reply_id: 334842[/import]
Interesting. I would like to see improvements on reducing the audio latency issues on Android as well. I tend to notice more latency on a touch event as well. However… my sense is it has more to do with extra processing, and less to do with touch specifically. I still experience audio latency in other situations where no touch-events are being triggered. [import]uid: 10818 topic_id: 34842 reply_id: 138505[/import]
Hopefully someone at Corona can explain the delay in touch events and why its quite big compared to being triggered by a timer event (as in my experiment above). Why does it happen and is it to do with the touch event library having some kind of bottle neck or just an android thing? [import]uid: 124886 topic_id: 34842 reply_id: 138789[/import]
Interesting. I would like to see improvements on reducing the audio latency issues on Android as well. I tend to notice more latency on a touch event as well. However… my sense is it has more to do with extra processing, and less to do with touch specifically. I still experience audio latency in other situations where no touch-events are being triggered. [import]uid: 10818 topic_id: 34842 reply_id: 138505[/import]
Hopefully someone at Corona can explain the delay in touch events and why its quite big compared to being triggered by a timer event (as in my experiment above). Why does it happen and is it to do with the touch event library having some kind of bottle neck or just an android thing? [import]uid: 124886 topic_id: 34842 reply_id: 138789[/import]