The OpenSL ES and Java layers provides only the API, the top interfaces that are exposed to the application developer. They both sit on top of AudioTrack, AudioFlinger, and the audio effects implementation.
If you want to replace an existing audio effect, you can mostly ignore the OpenSL ES layer, as long as you're using the right GUID for the effect. The OpenSL ES API does not currently support custom effects. Custom effects are exposed by the Java API -- see http://developer.android.com/reference/android/media/audiofx/AudioEffect.html#queryEffects%28%29 On Feb 28, 10:40 pm, SM <[email protected]> wrote: > My aim is to plugin the audio Effect Lib via the OpenSL ES. I went > through the code > at frameworks/base/media/libeffects. It contains implementations of > Audio Effects by vendors. > For eg, There is an AudioEffect Library, Dynamic Bass Boost by NXP > Software Ltd. > Does this make use of OpenSL ES? > > On Feb 25, 8:54 pm, Glenn Kasten <[email protected]> wrote: > > > The primary documentation for integrating audio effects is frameworks/ > > base/include/media/EffectApi.h. Also study the default effects code in > > frameworks/base/media/libeffects, and AudioFlinger. For Java APIs, > > frameworks/base/media/java/android/media/audiofx and frameworks/base/ > > media/jni/audioeffect may also be helpful. For the native audio APIs > > based on OpenSL ES, see system/media. > > > On Feb 24, 11:10 pm, SM <[email protected]> wrote: > > > > I have an IP which is an audio enhancement codec. OpenSL specifies > > > interfaces for certain effects such as bass boost, preset > > > reverberation, stereo widening etc. Through which interface of > > > Android(OpenSL) do i need to plugin my IP. -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
