Akai Force Forum: Everything relating to the Akai Force, the iconic 64 pad, clip-based standalone sampler/groovebox from Akai.
By Vfire77 Thu Feb 10, 2022 12:01 am
Hey I was wondering if anyone has had this problem. After the update to 3.1 My projects take way longer to load, and saving too is much longer. Even if I just change 1 or 2 audio files and hit save it seems like it saves every file again. Last night it took 30 minutes to save one of my projects. Also mixing down was pretty much impossible after 10 mins only 10% was done. I tried to downgrade to 3.06 but it seems when you open the project in a newer version you can no longer open it in an older one. Pretty Crappy.

I have a SSD disk instaled, I also tried from an SD card and I have another Force which I tried and it is slow as well.

I enabled disk steaming but it doesn't seem to make a difference. Do I need to go into each project and set each file to stream from disk?? Even if thats the case there is still something wrong with these very long loading saving times. Wasn't this update supposed to make it quicker???

Its pretty crappy cause this update is killer but this problem is making it a big head ache. Any ideas?
User avatar
By EnochLight Thu Mar 17, 2022 8:47 pm
Manual Controller wrote:I've been having this same problem since updating. It sometimes takes, like, a minute to save one sample. Not sure what's going on. Prior to the update it was crazy fasst.

Following to see if anyone has an answer.


Exactly which firmware are you on? Firmware 3.1.2-3.1.3 should have addressed that.
By Cerijames Sat Nov 16, 2024 10:20 pm
I have the same problem but with key 37. I use it for live and it now takes too long to load a project so reluctantly switching back to 2.15. Maybe the user interface takes more time as there are more elements to it? No idea but really stops it being viable to load projects in a live setting
By B-Wise Sun Nov 17, 2024 9:47 pm
Cerijames wrote:I have the same problem but with key 37. I use it for live and it now takes too long to load a project so reluctantly switching back to 2.15. Maybe the user interface takes more time as there are more elements to it? No idea but really stops it being viable to load projects in a live setting

I haven't had this problem since updating the Force to 3.2. There goes your theory. MPC3 is still in Beta so it may have some unique bugs. Akai fixed on our end. Hopefully they'll fix it soon for the MPC3.
User avatar
By MPC-Tutor Mon Nov 18, 2024 8:19 am
Ultimately disk streaming introduced bottlenecks in the loading process (even if your project isn't using it). It's directly related to how many individual samples need to be loaded (rather than the file size). 100s of samples = sluggish loading.

Akai have tried to address this in MPC 3.4 by offloading much of the loading to a background process, which means your samples are still loading even after leaving the browser. This working well under most conditions but there's still instances where this causes issues (trying to play pads where the sample hasn't actually loaded yet, hence no audio emitted for up to 30 seconds). Hopefully the next release will address this.

Although this may be irrelevant considering the Force is discontinued, unless Akai are feeling charitable and push out one final Force firmware update.