objective c - iPhone Music App: Playing from a Cache of Notes -
It will basically be a temporary wavetable synthesizer.
With the number of devices to use the Times,
Notes are stored as .wav files and cached in RAM to prevent overhead from hard drive retrieval Will go However, there is a major time-space business in terms of physical memory, since .wav files can be very large
Does anyone know how to caching them. Wave files are more space-efficient? Compression is a good choice, but can greatly reduce the quality. The interval or distorted frequencies on the fly will definitely be very low. If I am wrong then correct me, but with this implementation 200 bpm will play.
If you have experience with the music app, please share your advice.
No experience with the music app, per copy, but I have used audio with the recording.
On the iPhone, you do not usually load the whole audio in RAM, because size decreases and disk speed. By using the AudioQueue API, you type a callback function that pops up buffers from disk (usually using audiofile methods) to run the audio playback of your application smoothly, to properly calculate buffer size and buffer calculations You can select.
You should also check the possibilities of compression; Just like a lossless AAC, if you do not have any quality in quality, 50% reduction in file size should be bought at the cost of enlarged processing overhead.
Actually it seems that you are trying to optimize here very quickly by writing some experimental code to see if you can get 200 BPM out of the standard file loading style of the audio playback routine. . It may be that the file loading style using WAV due to WDO is actually faster than the ramp.
Comments
Post a Comment