alostpacket
Over Macho Grande?
Converting to wav is slow and must use a lot of memory. Using the same hardware I created a similar app on Windows mobile which can easily pitch shift 2 mp3s and use the device at the same time without any glitches. Maybe android api's have more restrictions making this not so easy.
Android has no API for sound manipulation. Well at least not before 2.3.
It's a bit of a developer minefield tbh.
So how did you pitch shift the mp3s though, through an API call? Were they pitch shifted after decoding by the system? I'm pretty sure all MP3s are decoded before being sent to the DSP too, so if decoding to wav is so slow...then how can it work on the fly? And if everything is decoded on the fly, then the idea is to free up processor cycles and to not have to decode so you have more room for sound manipulation (graphic eq, pitch shift, etc).
But I guess when you way memory and disk I/O vs the cpu of decoding on the fly plus any processing, maybe decoding on the fly wins out depending on how much processing you do. Mostly because phones are so memory strapped and disk IO is expensivley slow.
Anyways thanks for the post, curious to learn more about your app.
