![]() The BIG culprit of the memory issue is custom strings and choirs pulled in from a real sampler. These won't impact memory when you assign them to an instrument, but they will when you load the instrument onto a track in a song. Some of these samples are up to 4MB each so these custom instruments are a little bigger than the defaults. I've loaded about 40GB of samples out of Kontakt, Bluezone and other places into BM2 (not a problem as long as you have the storage capacity). Where it really starts to become a problem is with custom instruments with custom samples. So with say 20 tracks of the default instruments with an effect or two on each you'll end up using up about 110MB of memory. Most effects don't make much of a difference but meatier ones like Delays will use up to 2MB. Once you get into composing, most of the instruments in BM2 load with about 1-2MB of samples behind them into memory when the song is loaded, plus about 1MB for the track itself. Loading BM2 itself will use up between 45-60MB RAM at start up for the app. Hope I don't make this too complicated to follow.īaseline for reference - iPad 2 has 512MB RAM iPad 4 and iPad Air have 1GB RAM I originally thought this would only be pertinent to iPad 2 owners but since picking up an iPad Air last week I know this may impact even users with the latest gear if you find yourself pushing the envelope (which I've already done with an Air). Spent the night doing some calculations and some tests and have calculated how BM2 uses RAM and how it can effect your compositions. ![]() I posted this in another thread but thought it might be worthwhile to post this in its own discussion so others can find it if they need to search for it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |