Force Firmware 3.5 is out.

I did the update but had to switch back to 3.3 due to crashes.

While creating a new project or opening an old project created in 3.3 with a limited number of tracks works, opening an old project with many track causes 3.5 to crash during loading or shortly after.

Has anyone experienced the same and maybe found a fix? Thanks in advance for sharing

I wrote a mistake, it won’t work when set to ableton link…….

Bought the bundle too. Jura is beautiful, by itself worth the money. The rest is bonus for me, although the effecs are very good too!

Kind of a lazy post but is there a good reverb in the bundle?

Ordinairy_Rebel wrote:Kind of a lazy post but is there a good reverb in the bundle?

For what I heard so far, only delays….. but damn good!

What does this mean:

PLUGIN CONTENT FOLDER(S) MISSING

1 of your plugin content folder(s) could not be found. Please, check that your storage media is attached.

Do you wish to keep scanning this location for content?

What is "this location"?

HouseWithoutMouse wrote:What does this mean:

PLUGIN CONTENT FOLDER(S) MISSING

1 of your plugin content folder(s) could not be found. Please, check that your storage media is attached.

Do you wish to keep scanning this location for content?

What is "this location"?

I had this message too, but all the plugins are there as far as I know. So I clicked "don't show again"........

HouseWithoutMouse wrote:What does this mean:

PLUGIN CONTENT FOLDER(S) MISSING

1 of your plugin content folder(s) could not be found. Please, check that your storage media is attached.

Do you wish to keep scanning this location for content?

What is "this location"?

"this location" is either internal sd, or your sdcard where you have it set to download the synth content in the downloadables section of the settings menu... if you have to ask these questions housewithoutmouse then dont argue with me on threads where I make valid points. you just lost all credit..

You can’t know everything though? What a hostility.

Ordinairy_Rebel wrote:You can’t know everything though? What a hostility.

Are you new here? Do know the history between these 2?
Let Mouse speak for himself.

It was an argument over the hardware's being hopelessly inadequate - or not. I was saying that the current hardware is far from out-done, and it is better to keep making more use of the current hardware, because the real issues are with usability and missing features. Bringing a completely new hardware platform would be not only unnecessary, but actually a bad idea. And I was not convinced or impressed by mentions of computer geek things. I also have no use for any "credit" I may lose or gain.

From what I can see, Akai/Inmusic are improving the software as they should, fixing usability issues and adding missing features, for the benefit of the large number of owners of existing devices.

HouseWithoutMouse wrote:From what I can see, Akai/Inmusic are improving the software as they should, fixing usability issues and adding missing features, for the benefit of the large number of owners of existing devices.

I'm of the same opinion. There's no point in releasing new hardware, not fixing the current issues, making the existing units obsolete... Inmusic would be sending the wrong message to their customers: buy our new stuff, but it will be unmaintained and obsolete soon).

Fixing the current issues and adding new features is the right thing to do, despite all the GAS in the user base, is what sells their products as reliable and not as a shitty gadget that lasts a couple years and goes unmaintained.

bitermc wrote:

HouseWithoutMouse wrote:From what I can see, Akai/Inmusic are improving the software as they should, fixing usability issues and adding missing features, for the benefit of the large number of owners of existing devices.

I'm of the same opinion. There's no point in releasing new hardware, not fixing the current issues, making the existing units obsolete... Inmusic would be sending the wrong message to their customers: buy our new stuff, but it will be unmaintained and obsolete soon).

Fixing the current issues and adding new features is the right thing to do, despite all the GAS in the user base, is what sells their products as reliable and not as a shitty gadget that lasts a couple years and goes unmaintained.

I agree, but this gen of MPC has been out for like 8 years now, while getting many updates over that time & more to come. That's a lot more love than most gear gets including any other gen of MPCs, but if they could've fix this MIDI Note Off bug they would've, which makes me think, what if they can't fix it for whatever reason & the best they can do is start fresh & learn from their fu*ck up. Is it better to keep pushing or just come clean & tell us the deal, than make a new & better device that doesn't have this MIDI bug & the audio-interface problems?

Back to the "this location" thing. When it asks "Do you wish to keep scanning this location for content," if I press YES, then I suppose it will keep doing whatever it's doing, the next time. But if I press NO, then will it break some existing things, and what things exactly will break?

What are the plugins it's trying to find content for? Are they registration/online-activation-requiring plugins ONLY? Or is there some new content available somewhere I could download and place somewhere?

I want to stay completely clear of any functionality that might suddenly decide it wants to connect to the internet for authorization or whatever. I have decided to base my Force-music-making mainly on plain old dumb WAV samples.

Also, how do I get rid of the "Welcome to Force" thingy on startup? I have checked "Don't show this again" every single time, and it still shows the same crap every time.

Answering my own question about "legato" in the new keygroups - no, it doesn't do actual legato even with "legato" on, it will re-trigger the sample and the envelopes every time anyway. How the hell is that "legato".

I can get envelope-retriggering to stop by switching on GLOBAL: ON on the AMP/etc ENV pages, but how to get the actual sample to not re-trigger? I don't want the attack portion of the sample to repeat when playing LEGATO. And re-triggering will cause an unnecessarily sharp glitch even for single-cycle samples, because it will cause a discontinuity.

By the way, I found a funny glitch. Set sample start to, say, 1024, sample end to 1025 and loop to 1024. Interesting noises. And if I play a very high note, the sample playback will actually skip over the loop-end point and continue to the dark post-loop area that Akai shouldn't be able to play? Or is this some new behavior with the new keygroup engine.