Thanks for sharing. I've wondered if there were any problems (since there often are) but didn't update yet. Appreciate you helping users be informed so as to avoid frustration.
Also great praise for this vid on the 3.2 bugs - If you search YT - yours is just about the only one out there too. I know it would be VERY useful for gigging musicians to hold off updating - but it also really helps out folks like me who just bought their first beatmaking device of any kind - & chose the Akai Force, less than 2 weeks ago. Of course I immediately updated the firmware. And I also have a Tascam Model 12 bought 2 months ago. Everything had sounded great coming out of the headphone jack of my Force - switched headphones to the Tascam mixer/interface so I could play along with my synth-workstation also connected to the Tascam (that worked great on its own), and got a fraction of the volume out of the Force, and a ton of glitchyness. Right out of the gate, what I wanted to do was impossible... so although my work is not critical, it's frustrating after months of shopping all new gear, & so looking forward to finally making some music, to be stopped in my tracks. Thanks!!! At least I won't now spend weeks trying to figure out if I it was something I did wrong!
The most annoying thing of the snapshot bug is that even if you delete all the snapshots you still have some parameters to zero on loading the project, so the project is totally messed up. Thanks for the video!
1 I have been experiencing in one project is the sample in one of my instruments is always switched out to a different one every time I open the project. I have to go in and replace the sample every time I open the project. 2. Some 3rd party instruments won't load because the effects that they use 'are not available' or something like that. The update is EXTREMELY buggy.
Thanks for this,good job summarising . I confirm the 2 priority issues,Faulty project File management and Audio interface Compatibility[Tascam model 12]. Akai should work urgently to provide a new release to address these as these primary 2 issues should have been flagged at a pre-release testing industry standard process. I found Loading drum kits from expansions often gives error report of effect plug in not found or available One additional issue I have noticed is that with Model D and Fabric plug ins, after loading a preset, Sound parameters like filter change without user intervention.Bizarre. Otherwise ,I have found the Akai Force to be a fantastic product, the new plug ins are great. The easy Work flow makes it my first go to instrument.
Hi Maxipok, I'm looking to purchase an interface or mixer to get more inputs in my Force but I'm having a hard time finding information on that. I'm sure there are other people with similar questions so perhaps this would be a good future video idea. Here are some of the questions I have: - How do you know if an interface is Class Compliant? - How would you choose an interface to pair with the Force? - Using the Sweetwater Computer Connectivity spec, if an interface is 16/4, will that work or do you need 16/16 to use the feature? I think that means outputs through usb but not sure. - If you use this feature with a mixer, will the EQ/Compressor knobs work or will they be bypassed? - Once you have an interface that works, how do setup audio routings? - Your top 3 choice of interface/mixers that work. Happy New Year!
Hi, yep that’s a good idea for a video, thank you. At the moment a bug in the firmware has stopped most of the interfaces working properly with Force, but when they fix it with an update I’ll look to make the video 🙂
@@MaxipokMusic Awesome and thanks! I really wish Akai had a list of supported devices that they tested against, it would make buying one a less confusing/scary 😑
@@hobonickel840 ‘fraid so. I don’t have any inside track with Akai so no idea when it will be fixed. Lots of grumbling about it in the community, unsurprisingly.
Having issues with saved song templates. No special midi mapping, no macros, no plugins. Purged my old one used the empty project to create a new one. Saved. After about two or three power on cycles and loads the same template is corrupted which causes the default midi assignment for my keyboard to stop working. I am only able to play directly from the force to my other midi gear. Also audio clips are drifting in tempo with and without time correction being used. If I record 3-4 basic audio clips each one will start to drift as I am recording a new one. Only thing I can do is frequently stop the recording and start again. This started in 3.1.3 and continues into 3.2. I have submitted tickets for both to akai so I’m not just complaining I’m documenting my issues.
Wether it's my Mac laptop or my DAW -Ableton, I'm very reluctant to update with major upgrades. There are always exciting new features but always issues/bugs that can range from minor annoyance to show stoppers. I'm doing the same with my Force just holding back for a while. It's very capable of doing what I need it to do in its current state.
I’ve recently noticed when I plug my USB keyboard before starting my AKAI Force, it’s not recognized by the OS. To resolve the issue, I disconnect it, wait a few seconds, and reconnect it.
Hi - what is the previous update? , I just got my Force , its showing 3.1.1 . Btw your beginner video is a must ! I've watched it several times while waiting for my force to arrive and I am so glad I did ! Thank you!
Hi, the most recent release is 3.2.1 which came out about a week ago. The Force page on the Akai website has a downloads tab, you can find the release notes etc there. I’m glad the video was helpful, enjoy your new Force!
@@MaxipokMusic Helpful - you bet it was ! , I plan on following it first thing .Akai page lists the updates in an odd way , Am I right to understand that 3.1.1 is right before 3.2.1 That may sound ignorant, but My Mac updates itself, I have never had to deal updates .
@@billyfreeze1893 There have been a few in between, the last major one was 3.2 (about a month ago) and then 3.2.1 last week which fixed a few bugs and added some new features like MPC project import. But as I understand it you can go straight to the most recent one, I don’t think you’ll need to bother with any of the intermediaries.
@@MaxipokMusic Thanks , I'm joining your tutorial page to learn more and to thank you for taking the time to answer my trite questions , I'm already looking for a lost zoom field recorder so I can load sounds once I learn how . Its in a box some where filled with many other accessories - it never ends :)
That screen problem i think is where its not getting updated correctly. Your seeing the last selected screen underneath. If you drop out to a different screen them go back in it clears. That's what it looked like to me having noticed it on mine. It used to be just the OLED's messing about at times.
Weird thing is that my Behringer Wing now works effortlessly. There were cracks and pops before which are now fixed. Unfortunately I also heard thst some interfaces that worked before now don’t anymore.
Sounds like they made an adjustment to fix one problem which broke the original code. They need a wider testing pool so they can see this type of stuff.
Have you noticed that pads choke automatically somehow in 64 pad note mode? I play 64 pad finger drumming and used to be able to play drums on the lower right 16 pads and the top left were chopped samples. Now when I play a beat while playing samples at the same time it chokes the pads on the top left.
I haven’t noticed that, but I have seen other people on Facebook mention it. I’ve also had the pads feel generally ‘weird’ or unresponsive in note mode. However 3.2.1 dropped today, I’ve installed it but not used it yet. Hopefully those bugs will have been fixed!
Did you checked out what's different with the Ableton link update? I am hoping it may open ways to change the Force's tempo externally. Thanks for all your content by the way 🙏
Thanks so much for this - one thing I did notice was a random remapping of midi cc’s to my midimix - strangest was that the pan control on channel 3 suddenly started affecting tempo, May or my not have been as a result of the update but suspicious timing! Track levels happening to me to, yet again I’ve paused doing anything serious until these bugs are fixed.
I’ve seen a couple of people say that mapping the Midimix causes some weird MPC screens to appear, so there is definitely an issue with that device in particular. Thanks for adding your experience, hopefully a patch is not too far away!
I get freezing on bootup sometimes. And I have made a 32 pad drum kit and when I load that in to a new project, it kills the sound engine. I get no sound from anything and the project becomes a potato because even if I reset the force, the problem remains. No sound. I created this drum kit on 3.2. I think it might have something to do with my deleting the fabric files after the trial expired as I don't want that one.
I hope that was taken with the British meaning of ‘a small annoyance’ and not in any other way. I probably shouldn’t have used that word in case it was misheard or misinterpreted 😬 🙏
I’ve had no trouble opening projects created in earlier firmware versions at all. Haven’t experimented with some of the other features mentioned so can’t comment.
Hey brother, is this still the status of the update… has there been any further release to address these items? Tempted to update but concerned about issues… any advice greatly welcomed! Thank you!
Hi! 3.2.1 came out a couple of weeks ago and it patched most of the ‘internal’ issues. However audio interface support is still broken, things like the Tascam Model 12 etc are still unusable. So it’s pretty stable if you are using it on its own, but best avoid the update if you use an interface.
Updated mine and now the midi out port is not showing so now im unable to use external midi gear.. also getting a bit of noise distortion from audio.. Akai need to get there act together ..
I'm on 3.2.1 and I have the problem of key group instruments from expansions screwing up on reload. If I reload the sound in it's fine but soon as I save and reload the project it gets some weird vibrato effect on it. tried it with a few different expansion key grouped instruments and same old problem.... Hmmm not happy
I’ve seen a few people say this is something to do with LFOs randomly changing settings when the project is saved. I haven’t experienced it myself, but that might be a place to look to fix the issue?
a lot of problems with controlling midi channels can not be divided on the external keyboard midi plugins layer split do not work separately midi channels failure
I’ve been using 3.2.5 for a few days and have encountered no bugs at all. Haven’t tried to stress test it or anything, but it’s looking good. The interface issue was fixed a version or two ago…
And then there is the elephant in the room. Warp, which distorts and clips audio loops. It most obvious on loud loops with loads of frequencies. Always a nasty click at the beginning of the loop, followed with more nasty crunchiness, usually on transients. It's been like that for a few versions now.
Wow so that’s what’s causing my clicking problem. I honestly thought it was my timing and I have spent hours having to go back over parts I was playing into a clip because I couldn’t get the popping resolved… ahhh. It’s the one thing I didn’t look at…
Thanks for mentioning this, im a pro user and cant have my levels randomly snap to silent...and its not just main levels, also submixes, returns, even inside effects like limiters etc etc...this is super dangerous when you are going live because sometimes its very difficult to find why you hear no sound...so DONT UPDATE YET if possible
@@czarecki80 yeah, i dont know what these Beta testers do, i had this error after 5 minutes of using the Force LOL...maybe its only one person doing all this programming due to cost :)
Seems like they depend exclusively on a small group of people who are not testing everything. This is why apple releases their beta software to the public and not just themselves. This allows them to experience bugs in all types of scenarios. They can then address the areas that are being reported. They also have more than one person coding so that maybe an issue as well. It takes a village on stuff like this… having a richer group of testers would probably lessen alot of these issues.
I lost 3 years worth of songs updating to 3.2. i was just to sign to a label and do live shows and now I have nothing. I've decided to sell all my music gear and just get a job in my fiancee's fathers accounting firm and prove he was right about me and chasing music dreams. I just hope he is going to be a good boss, I doubt it though.
The beta versions comment is an interesting one. It’d be interesting to know If the bug reports are coming from users whose machines have had beta firmware installed.
Yeah I love the update you get to use a bunch of cool plugins that you don't get to keep only if you want to spend like $1,000 you can buy them all thanks Akai.
I contacted Akai Support over a month ago about a different issue, they still haven't even opened the issue in their bug tracker, I recorded a video, and gave a good description of the issue, completely ignored. I'm guessing we will have to wait another year to get another update. I'm going to bitwig on a windows tablet with a push 2 controller, it's a much better solution that has none of the shortcomings of Akai's half baked software.
As I understand it from Facebook posts, the beta testers already have 3.2.1 so we shouldn’t have to wait too long for a fix for these new issues at least…
Pops and clicks mean a buffer reset. Windows users can simply lower the buffer when in computer mode. For Mac users: you use a consumer device- upgrade to an enterprise solution (sarcasm).
I think the project firmware issue stems from people making projects with previous unreleased BETA versions. 3.1 had a lot of pirated BETAs out there and that has always been a risk/issue with any BETS
i don't know but im using only official releases, no betas, still my projects are not working since the update. And my ES9 neither. i had luck everything came back to normal after downgrading...
Mine is booting in 4-5 minutes now, unfortunately I updated already last week, I didn't check other functions yet. The new plugins working well, let's see what 3.2.1 bring us proper fixes.
Thanks for adding this, hopefully people will comment with bugs they’ve encountered and it’ll turn into a somewhat definitive list. Also, sorry to hear you are having issues 😬
That sucks. In 3.0 my force took about 55 seconds to boot up. Now in 3.1 it takes 25 seconds which is much better. Im gonna wait to update until there’s another patch out.
God, this update instantly ruined 2/3 of all my tracks from the last 2 years. LFOs on drum tracks no longer retrig with the samples. Apparently you can edit the TEXT FILE of the drum track to make LFOs retrig, but they didn't put that function on the UI? Also, on keygroups the MOD>LFO setting just doesn't save. SO much garbage. Akai failed hard.
Snapshot bug is still here in 3.2.6 over 1 year later. Which just so happens to corrupt your project file. Thanks Akai. You are completely asleep at the wheel.
#bug Hype Synth Plugin > press EDIT + ASSIGN A or B buttons > LEARN any plugin parameter to the crossfader then play with the crossfader....will crash system
its funny, i'm sitting here drinking a beer after the last rehearse for tmrw's gig and RU-vid recommends me this just 3 days after updating hahuahua. a little tense to see how it will be on stage after watching your video but so far it seem like it actually fixed the bugs I've had in 3.1... hope it still ook.. my projects opened fine and everything seems to be fine while in 3.1 it was very unstable i had many sync and warp issues unfortunately ..
