Un tampon fini d'un joueur audio OpenSL ES doit-il être libéré?

Question

juste pour la confirmation.Lorsqu'un lecteur audio, créé via OpenSl ES pour Android, finit la lecture d'un tampon, est-ce que la mémoire tampon est automatiquement libérée par le collecteur des ordures?Ou dois-je avoir besoin de libérer le tampon moi-même?

Si c'est ce dernier, je pourrais utiliser une certaine aide.Mais comme pour l'instant, je n'établirai aucun code avant d'avoir dit que j'ai besoin de le faire moi-même ...

Answer 1

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.

Answer 2

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.