HomeiOS Developmentavaudioplayer - IOS App - scores of quick sound information vs. just...

avaudioplayer – IOS App – scores of quick sound information vs. just a few bigger information


I’ve an IOS app the place I’ll find yourself with a number of hundred quick very quick sounds- most are voiced phrases, although there shall be some sound results as effectively.

If I’ve one file per sound, I solely must retailer the file identify per sound identify. If I’ve a number of sounds in a file, I must retailer the file identify, start line and length for every sound identify.

Whereas recording the narrator reads a number of phrases with pauses in between and information into one file (I would like to interrupt this up into a number of information if wanted).

The information are usually not bundled with the app – primarily based on person preferences, the information are downloaded and saved on the machine. Consider it as person chooses a sport degree, and all of the sound and picture information related are downloaded.

My query is in regard to dimension and efficiency of the app. Is a technique higher than the opposite – say 600 sound information or 30 information with 20 sounds every – and why is a technique higher than the opposite?

I can go along with one file for every sound or have giant sound file and play from a particular time within the file for the size of the sound. I’ve examined code each methods and it produced the sound appropriately.

I perceive the trade-offs throughout coding and making ready the audio information. However I wouldn’t have a really feel for app dimension, efficiency and so forth. I might recognize any enter.

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments