Akai Force Forum: Everything relating to the Akai Force, the iconic 64 pad, clip-based standalone sampler/groovebox from Akai.
By JackD Thu Oct 27, 2022 2:00 pm
Hi Guys,

I’m Quite new with Akai Force, I did start to sample drums and rhythm stuff, then I realized that there is a cool randomizer wishing keygroup track. That could be useful to randomize the pitch of the snare for instance.
So it is the 4th page within the “sample” tab (in the keygroup editing).
I started to customize it for keygroup 1 but then I realized that this setup is applied for each keygroup and only the one that I setup.

Is it correct or I’m doing something wrong?
It looks like a bug, no? :worthy:
User avatar
By MPC-Tutor Thu Oct 27, 2022 2:27 pm
Set 'keygroup' to ALL to apply any changes to all keygroups. TBH, drums are better handled in a 'DRUM' program, keygroups are typically used for melodic instruments.

In a DRUM program, hit the icon at the top of the screen and select 'ALL' pads. Remember to set back to 'CURRENT' after editing everything.
By JackD Thu Oct 27, 2022 3:00 pm
MPC-Tutor wrote:Set 'keygroup' to ALL to apply any changes to all keygroups. TBH, drums are better handled in a 'DRUM' program, keygroups are typically used for melodic instruments.

In a DRUM program, hit the icon at the top of the screen and select 'ALL' pads. Remember to set back to 'CURRENT' after editing everything.


Please doublecheck.. it applies to ALL keygroup, also if I edit just Keygroup 1 (the issue is valid for this setup page only)

The issue with Drum program is that I cannot use Auto-Sampler and I am limited with 4 velocity layers.. :shock:
User avatar
By MPC-Tutor Thu Oct 27, 2022 3:17 pm
Sorry, what do you mean by ''doublecheck' it applies to ALL keygroup'?

Second issue - use autosampler to physically create the samples, then manually assign the samples to a drum program.

In DRUM programs you use simultaneous play to utilize more layers. However, there is currently no way to randomize more than 4 layers, not in a drum program, not in a keygroup program. you can however utilise more than 4 layers for 'velocity switching'.
By JackD Thu Oct 27, 2022 4:55 pm
MPC-Tutor wrote:Sorry, what do you mean by ''doublecheck' it applies to ALL keygroup'?

Second issue - use autosampler to physically create the samples, then manually assign the samples to a drum program.

In DRUM programs you use simultaneous play to utilize more layers. However, there is currently no way to randomize more than 4 layers, not in a drum program, not in a keygroup program. you can however utilise more than 4 layers for 'velocity switching'.

Sorry, probably I wasn’t clear enough.
I meant: please check again your Akai Force before to confirm that is currently working as you mentioned. I did try several times to set this pitch randomization for a specific layer within a specific Keygroup, but I always end up with applying the change to all the existing keygroup. And this issue is valid only for this page setup (only for randomization).
With the rest of setup for keygroup, the Akai Force is working as you mentioned.

Hope I have been clearer :Sigh:

A short vídeo to explain the issue:
https://www.youtube.com/watch?v=gLL5AdEP70E
By JackD Thu Oct 27, 2022 9:13 pm
MPC-Tutor wrote:Sorry, I thought you meant random layer playback (where you assign 4 samples to a keygroup and randomly play back one at a time.

Randomisation settings for layers are indeed the same for all keygroups. Only depth attack/decay/cutoff and res are unique to each keygroup.


Ok then it is not a bug, but looks like. :WTF:
Thanks for the feedback :worthy:
By JackD Fri Oct 28, 2022 6:08 am
JackD wrote:
MPC-Tutor wrote:Sorry, I thought you meant random layer playback (where you assign 4 samples to a keygroup and randomly play back one at a time.

Randomisation settings for layers are indeed the same for all keygroups. Only depth attack/decay/cutoff and res are unique to each keygroup.


Ok then it is not a bug, but looks like. :WTF:
Thanks for the feedback :worthy:


Hi,

In any case, on Drum track side, the behavior is the one I expected.
The issue is only on keygroup side, I did write to the support, let’s see if they can provide an explanation

Thanks