![]() ![]() 32 bit audio takes up twice the memory of an equivalent 16 bit version of the same audio file, and 50% more memory than the equivalent 24 bit file. Hence it does not matter if the audio file you load is a 24 bit WAV, a 16 bit WAV or even a compressed mp3 file, it all gets converted into 32 bit audio within your project. When you load or sample audio into your MPC is that it is stored as 32 bit floating point audio which is a more efficient and accurate format for the MPC Software to work with. How the MPC X, MPC One & MPC Live Manage Audio RAM is cleared each time you turn off your MPC. Remember we are not talking about disk storage here, RAM is the dynamic memory used by the MPC to physically hold your currently active project. ![]() Any left over RAM can be used in your project to dynamically store all the samples, audio tracks, programs, sequences and effects you have inside your currently active project. Upon booting up your machine, this RAM has to manage the operating system (which we believe is Linux) and also the MPC Software application itself. The MPC X, MPC One and MPC Live (and the Akai Force!) contain 2GB of RAM which forms part of the main board – this is a fixed amount of RAM and cannot be upgraded. This tutorial is likely to useful for Akai Force owners as the Force has the same internal board, same RAM and similar OS. While I was writing this article Akai released some additional information regarding the MPC Live/MPC X/MPC One memory usage which seemed to confirmed my findings, however it’s important that we look at how these numbers can be translated into ‘real world’ sample usage. There’s been a lot of discussion about the actual amount of ‘available’ memory in the MPC Live, MPC One and MPC X, so I’ve spent some time investigating this to try to get a clearer picture. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |