Submitted by The Quixonic Team on Wed, 11/10/2010 - 01:06.
Thanks SalsAlx,
In the almost two years since we've launched the app, this error hasn't ever been reported before. Not even in our own testing did this rear its ugly head. This error would only show up if the app could not write the peak file out to the application directory for some reason. Perhaps some questions can help us determine why:
What type of device do you have and what version of iOS?
Are you playing a file from the iOS library or the app's internal directory?
If from the app's internal directory, how were the files transferred? Via ftp/http/iTunes app sync?
Does it happen with every file or just with some files?
What is the name and format of the file?
If you attempt to play the file again, do you get the error again?
After closing out of the error, does the file show the BPM?
We've just finished some bug fixes and were getting to submit to the app store, but if we can narrow down this bug soon enough, we'll add it to the next release.
Thanks SalsAlx,
In the almost two years since we've launched the app, this error hasn't ever been reported before. Not even in our own testing did this rear its ugly head. This error would only show up if the app could not write the peak file out to the application directory for some reason. Perhaps some questions can help us determine why:
We've just finished some bug fixes and were getting to submit to the app store, but if we can narrow down this bug soon enough, we'll add it to the next release.
Thanks for your help.
- The Quixonic Team