Yeah I didn’t know 3.7.1 was buggy. I’m sure there is an impending point update on the way to address that, though. I’ll still update this weekend because I want to see how it behaves on my Force as well as my Live 3. Since both represent two very different cpu/ram platforms, that should be interesting.
I’d love to hear why he believes Akai’s sampler’s S&S was weak compared to Kurzweil, Emu, Ensoniq, Yamaha, Casio…
OK cool, I’ll look forward to your comparison. Most of 3.7.1 complaints came from the MPC & I think more Force users didn’t know it even came out.
I’m interested in the reason for Akai being the weaker sampler.
Four decades here, and a studio full of samplers. But nice try.
Well some good news that since the new FW my Roland MX-1 seems to hold a connection to the force again, haven’t stress tested it but compared to the previous version it does not immediately disconnect 
(I had previously downgraded to before 3.0 to get it working again)
Is a super nice and jam-able setup being able to map individual tracks or drums to diff channels. With the easy to grab master FX etc.
Fingers crossed it keeps working 
Close! I work in the financial sector measuring the frequency of clam vibrations.
Also available for the Force:
3.7.1 also changed the way Ableton Live Control works. In that mode, when viewing Devices, available Q-Links are now just one bank of 8, instead of two banks. That makes sense since there are only 8 parameters displayed at a time. Now when pressing the Knobs buttons, instead of showing 9-16, it shows track volumes.
And now pressing Menu while in Control mode doesn’t immediately switch to Standalone mode, so now we must remember to switch back before closing Ableton, otherwise it’ll transmit unneeded SysEx messages in Standalone mode.
That Akai Network MIDI driver doesn’t appear to be affected by the new Windows MIDI Services, at least on my system. Other InMusic drivers have issues Link.
These have a very “Korg Gadget” look about them. Wonder how they sound? Likely sample based.
