3

Just for confirmation. When an audio player, created via OpenSL ES for Android, finishes playing a buffer, is that buffer automatically freed by the Garbage collector? Or do I need to free the buffer myself?

If it is the latter, I could use some help. But as for now, I won't post any code until I get told that I need to do it myself...

zxcat
  • 2,054
  • 3
  • 26
  • 40
ThaMe90
  • 4,196
  • 5
  • 39
  • 64

2 Answers2

5

The buffer queue doesn't actually allocate buffer memory itself (or need to free it), you pass in pointers to memory you have allocated via the 'enqueue' function. You will need to free the memory you allocated when you're finished playing buffers.

As OpenSL ES is a native library in C++, it knows nothing of garbage collection, any memory you allocate for the API must be freed by you, and objects you create must have 'destroy' called on them to clean up internal memory.

Mathew Block
  • 1,613
  • 1
  • 10
  • 9
  • Yeah I figured as much, and I already implemented a clean up routine. Still, thank you for confirming my suspicions. – ThaMe90 May 19 '11 at 06:27
3

As the previous poster said, you call Enqueue with a buffer you have created previously. I'd point out, however, that unless you're playing only one audio event once in your app, you should probably keep re-using your audio buffers to avoid GC altogether - the beauty of C!

Also check out the Android OpenSL ES doc concerning Destroying your interfaces once your done with them, that has to be done manually.

Marc Lindahl
  • 161
  • 1
  • 6
  • Though what you say is true, I have already found that out, and implemented it. Like my comment on the previous poster, I already have a clean-up routine, and already am re-using the buffers. Nevertheless, thank you for your time and comment. :> – ThaMe90 Sep 15 '11 at 12:27