On Android Device Sound Library Delay Issues
GameSalad community,
I would like to take a moment to address the confusion surrounding Android devices and sound issues related to the Android sound library. We would like to clearly demonstrate the nature of this problem and where it originates. Also, we would like to clearly express our path toward resolution.
When launching the Android platform for GameSalad, our internal staff was compelled to chose which operating systems (and Android sound library) that our software would support. We ultimately made this decision based on the library that would allow access to MORE Android devices, rather than targeting fewer. Specifically, we aimed to provide access to the Nook Color (Android OS 2.2), which at the time our Android engine was built, was the top of the line for Nook devices.
Additionally, we wanted to support BOTH the Nook Color and Kindle Fire (Android OS 2.3). This meant choosing a sound library that supported Android OS 2.2 and earlier, as opposed to choosing to support Android OS 2.3, which would have dropped supported for Nook Color.
During our final launch stages, the new NOOK Tablet device was announced to the public on November 7th (less than a week before GameSalad launched Android publishing). The Nook Tablet, like the Kindle Fire, runs on a modified version of Android OS 2.3.
In Android OS 2.2 and earlier, the operating system is built with a software accelerated audio library system. Unfortunately, this has been known to contain inherent sound deficiencies, including performance lag on some devices. This deficiency between the library and software acceleration system results in a potential sound delay.
Currently, 35.3% of all Android devices support OS 2.2 and 50.6% of all Android devices support OS 2.3. (http://www.androidguys.com/2011/12/02/gingerbread-now-on-more-than-50-percent-of-android-devices/) So, our choices were between supporting 50% (OS 2.3 and up) and 85% (OS 2.2 and up) of the Android market. We chose the 85%, including the NOOK Color.
Operating system breakdown among top devices:
Nook Tablet: Android 2.3 with customized UI
Nook Color: Android 2.2 with customized UI
Kindle Fire: Android 2.3 with customized UI
Our core engine team is currently hard at work at some major architectural changes that should greatly improve this issue. In addition, those changes will also significantly improve performance and project file size.
We are also investigating the ability to support multiple libraries, thus allowing developers to choose a hardware-accelerated library in exchange for dropping support of older Android devices.
We truly understand the paramount nature of such problems for developers and we are diligently taking steps to remedy this concern for everyone in the community.
I would like to take a moment to address the confusion surrounding Android devices and sound issues related to the Android sound library. We would like to clearly demonstrate the nature of this problem and where it originates. Also, we would like to clearly express our path toward resolution.
When launching the Android platform for GameSalad, our internal staff was compelled to chose which operating systems (and Android sound library) that our software would support. We ultimately made this decision based on the library that would allow access to MORE Android devices, rather than targeting fewer. Specifically, we aimed to provide access to the Nook Color (Android OS 2.2), which at the time our Android engine was built, was the top of the line for Nook devices.
Additionally, we wanted to support BOTH the Nook Color and Kindle Fire (Android OS 2.3). This meant choosing a sound library that supported Android OS 2.2 and earlier, as opposed to choosing to support Android OS 2.3, which would have dropped supported for Nook Color.
During our final launch stages, the new NOOK Tablet device was announced to the public on November 7th (less than a week before GameSalad launched Android publishing). The Nook Tablet, like the Kindle Fire, runs on a modified version of Android OS 2.3.
In Android OS 2.2 and earlier, the operating system is built with a software accelerated audio library system. Unfortunately, this has been known to contain inherent sound deficiencies, including performance lag on some devices. This deficiency between the library and software acceleration system results in a potential sound delay.
Currently, 35.3% of all Android devices support OS 2.2 and 50.6% of all Android devices support OS 2.3. (http://www.androidguys.com/2011/12/02/gingerbread-now-on-more-than-50-percent-of-android-devices/) So, our choices were between supporting 50% (OS 2.3 and up) and 85% (OS 2.2 and up) of the Android market. We chose the 85%, including the NOOK Color.
Operating system breakdown among top devices:
Nook Tablet: Android 2.3 with customized UI
Nook Color: Android 2.2 with customized UI
Kindle Fire: Android 2.3 with customized UI
Our core engine team is currently hard at work at some major architectural changes that should greatly improve this issue. In addition, those changes will also significantly improve performance and project file size.
We are also investigating the ability to support multiple libraries, thus allowing developers to choose a hardware-accelerated library in exchange for dropping support of older Android devices.
We truly understand the paramount nature of such problems for developers and we are diligently taking steps to remedy this concern for everyone in the community.
Comments
and thank you much for the clarification. it's great.
Guru Video Channel | Lost Oasis Games | FRYING BACON STUDIOS
(just a peak into what some of us are doing while GS is smoothing out the Kinks) and this is being said knowing that they are working on the issue... if they are not i'll be furious as well.
Website ∞ Twitter ∞ My apps are available on: Apple iOS App Store ∞ Google Play App Store ∞ Amazon App Store
Sound stops on hitting Home button, lag is there but you can live with it.
Thanks GS! I can publish!
Would love to see this implemented. A little tired of sound delays on my KFire and NTablet.
From the post, it sounds like both Fire and Tablet operate on the same platform "The Nook Tablet, like the Kindle Fire, runs on a modified version of Android OS 2.3." Thus, 1 new publishing option would cover both very important devices. For monetary purposes, these two devices are arguably more important then all the other android phones combined (especially since we don't have ads options).
On the actual functionality of it, it sounds like GS already did the work, or knows how to do it, since they expressed the above post as a decision between two options. Why couldn't it be an option to support or not support older devices, such as we had with iOS publishing? It sounds like the only part of the code being affected is the sound library included.
The choice above was expressed as a decision to support new devices or more older devices. GS should be working to support the newer devices, since inevitably the older devices will no longer matter, such as Apple has stopped supporting the original iPhone.
As it stands, GS developers are limited in their publishing abilities, being unable to publish quality games (and yes, the sound delay does in fact affect quality. The slightest delay makes an app seem sloppy and unpolished. No amount of developer ingenuity can overcome that.) to Amazon, B+N, or MAC appstore. That's 3 out of the 5 major markets where GSers can't publish quality games.
Guru Video Channel | Lost Oasis Games | FRYING BACON STUDIOS
I did it as to directly reference the GS official position. This post was great to hear in December, but I thought we'd revisit it since it hasn't been addressed. They improved sound delays for older android devices, but have not addressed the issues with these two important markets.
I've just got mine running, but no sound FX at all. Only music.
Running on Desire HD.
That would be PRETTY AWESOME. :-[
I think OGG is the one that's compatible for both. You live and you learn.
That is just basic clear instructions!
Give the power to the user. Take the frustrating mysterious of game development out of the equation.
Rock.
- Murray
I know this is an old thread, but I still have lag on audio for my android nexus 7 device for some sounds. I converted to OGG but the lag remains. Does anyone else have thing problem still or is it just me on?