By Wanderer
Mon Nov 03, 2025 4:00 pm
Importing wav file into Akai Force v3.6
Basically I import wav files from Cubase in the format of 32bit float @ 44.1kHz.
I like to import with warping and bpm detection turned off in the preferences so that no cpu is being used in the Force. In the example in the photos I have imported a 4_4 kick drum of length 1 bar at 128bpm.
I then go to Sample Edit and ensure the stated bpm matches that of the Force project.
However, in the Clip edit the sample, although correctly lined up on the beat has a chunk missing off the end both visually and audio-wise. It does a similar thing to 2, 4 or 8 bar audio files.
The arranger loop length and project length are set to lengths equal to or greater than the sample length.
I cannot remember this behaviour in 3.3.
Workarounds:
I can halve the clip length of a 2,4 or 8 bar import.
I can switch on warping and bpm detection in the preferences – will it really take up a lot of cpu if I am using a lot of audio files?
But surely this is a bug. Can anyone reproduce this before I report to Akai?
The reason I am doing this is because I also use my Live 2 for a lot of gigging. In the past I have launched clips on v2.15. I was hoping to re-do my projects on the Force and then import them to the Live 2 updated to 3.6 and the pro pack clip launcher. I don’t want to make an already big job into an impossibility. Any help or advice would be appreciated.
Basically I import wav files from Cubase in the format of 32bit float @ 44.1kHz.
I like to import with warping and bpm detection turned off in the preferences so that no cpu is being used in the Force. In the example in the photos I have imported a 4_4 kick drum of length 1 bar at 128bpm.
I then go to Sample Edit and ensure the stated bpm matches that of the Force project.
However, in the Clip edit the sample, although correctly lined up on the beat has a chunk missing off the end both visually and audio-wise. It does a similar thing to 2, 4 or 8 bar audio files.
The arranger loop length and project length are set to lengths equal to or greater than the sample length.
I cannot remember this behaviour in 3.3.
Workarounds:
I can halve the clip length of a 2,4 or 8 bar import.
I can switch on warping and bpm detection in the preferences – will it really take up a lot of cpu if I am using a lot of audio files?
But surely this is a bug. Can anyone reproduce this before I report to Akai?
The reason I am doing this is because I also use my Live 2 for a lot of gigging. In the past I have launched clips on v2.15. I was hoping to re-do my projects on the Force and then import them to the Live 2 updated to 3.6 and the pro pack clip launcher. I don’t want to make an already big job into an impossibility. Any help or advice would be appreciated.


