I'm working on an audio related project and i discovered that the Ti.Media.AudioPlayer API for android is very quite limited in its usage for any advanced audio streaming related application.
The most useful features like -
- ability to seek a song to a particular position
- get the duration of the song etc.
are missing.
But the Ti.Media.Sound API has got all that.
Will it creates any problem if I go with Ti.Media.Sound API instead of Ti.Media.AudioPlayer for my project?
No remote URL streaming but everything will be streamed locally.
How does the former differs with the later?
For instance, the wiki page states that
Keep in mind though that with the Sound object, the entire sound file is loaded into memory before it's played. This increases memory use in your app. It also creates a delay before the sound can be played the first time (while the file is being read into memory).
With regard to the memory, I think I can call the release method to deallocate the memory occupied by the sound file.
But will this Sound object be capable of playing file size as large as 50-100MB?
Does not the Ti.Media.AudioPlayer API loads the sound file into the memory as well when the sound is playing on?
Thank you for any help.