Akai Force Forum: Everything relating to the Akai Force, the iconic 64 pad, clip-based standalone sampler/groovebox from Akai.
User avatar
By K. Rah Thu Nov 02, 2023 9:15 pm
Hello, I made a ton of progress with my song on the force and now I can’t save it on the mpcstuff drive or an SD card! I get a message saying “error saving force project” and I tried to save a single sample (less than 1 mb) and got this message:

“Error saving your sample, make sure you have permission to write to this location, that you have sufficient disk space and file path is not too long”

Running latest OS, 5 tracks, 5 launch rows, memory 20%, cpu 4%. Fabric piano is the only plug in being used. Any ideas? I’m going to have to leave the force on till I figure it out.. thanks

By B-Wise Thu Nov 02, 2023 10:22 pm
K. Rah wrote:Hello, I made a ton of progress with my song on the force and now I can’t save it on the mpcstuff drive or an SD card! I get a message saying “error saving force project” and I tried to save a single sample (less than 1 mb) and got this message:

“Error saving your sample, make sure you have permission to write to this location, that you have sufficient disk space and file path is not too long”

Running latest OS, 5 tracks, 5 launch rows, memory 20%, cpu 4%. Fabric piano is the only plug in being used. Any ideas? I’m going to have to leave the force on till I figure it out.. thanks


That sucks! Happen to me like 4 times. I was never able to save it after I got that message. You're better off taking notes & starting over while you can still remember your progress. You may need to record the Audio/MIDI data to somewhere else then record it back to the Force after you reboot.
Sorry but the Force ain't with today Jedi.
User avatar
By K. Rah Fri Nov 03, 2023 3:34 am
Ha, that’s what I started to do, send the midi data out to my mpc live, which worked fine, but then I tried saving the project on the force again and it worked. scary. Also it seems the levels on the mixer page are jittery and laggy along with the playback timeline at times.. like it’s struggling even when there’s not much going on.
By B-Wise Fri Nov 03, 2023 10:44 am
K. Rah wrote:Ha, that’s what I started to do, send the midi data out to my mpc live, which worked fine, but then I tried saving the project on the force again and it worked. scary. Also it seems the levels on the mixer page are jittery and laggy along with the playback timeline at times.. like it’s struggling even when there’s not much going on.

Well than I stand corrected Jedi :wink:

If it saved afterwards but now it's acting crazy the project may still be corrupt. To be safe I would restart the Force & see if that makes it stable or just start a fresh project & load the backup stuff from your Live.

Did you do anything in particular to get it to save after the save error message?
I always feel like there must something that could be done to do a force save.

Remember to press Shift+Save after any significant changes you make to the project. You can also use auto-save that will save every 10mins or whatever.

I'd just get used to pressing the save short cut, which is a good approach on these modern units with their fragile file system. It's happened multiple times when I was remaining/deleting samples for projects that I loaded up.

Maybe it was user error, but I don't know what I did wrong. Maybe it was expecting certain files to be saved as they was loaded but since I edited them & then try to save them it cause the saving error, which may just really be a saving glitch that Akai need to be made aware of & fix.

The file system is something that's really needs to redone & modernized. Why can't we move files around between the SSD & SD, load a whole folder of samples instead of 1 at a time, audition the whole sample not just 30 seconds & batch Delete? :smh:

Good luck with "saving" your project. I hope it's worth it. :lol:
User avatar
By Lampdog Fri Nov 03, 2023 5:31 pm
Corrupt project has happened to me just a few times on MPC X, never on Keys61 (yet).

I had save files on usb thumb so I started empty project and loaded individual files one by one to see which would make the machine act up. I ran into the actual xpj (project file) being corrupted a few times and others a single program. Rarely a wav file. But, I’d always find it by ruling out every file individually. Sometimes on a project this slow process is worth it, sometimes not.