By AndyRAW
Fri Nov 04, 2022 11:43 am
Major bug in the Force 3.2 update - key group error in drum tracks is cutting off pads. I have reported this as a bug, but no clear response from support yet.
With drum tracks that have pads outside of the core 16, the other pads are behaving as if they are in a key group when no key groups are set. That is, if you play and hold a pad in the A section, then play a pad in any of the B, C, or D sections, then the first note is cut off. This is making many of the tracks I have created unusable.
I rolled back to 3.1.3, which is fine, but projects that I saved when on 3.2 are now not opening due to some undefined error. This update process has been a disaster for my current projects.
I really like the Force, but Akai need to improve on their quality control of firmware updates.
With drum tracks that have pads outside of the core 16, the other pads are behaving as if they are in a key group when no key groups are set. That is, if you play and hold a pad in the A section, then play a pad in any of the B, C, or D sections, then the first note is cut off. This is making many of the tracks I have created unusable.
I rolled back to 3.1.3, which is fine, but projects that I saved when on 3.2 are now not opening due to some undefined error. This update process has been a disaster for my current projects.
I really like the Force, but Akai need to improve on their quality control of firmware updates.