External MIDI Controllers:
No MIDI Learn from external controllers, as thomaso said, since Force wants to be the MIDI controller. But there is bi-directional MIDI with OLED feedback like a Nord Lead 3 or Modular G2.
Here’s an example - first use Macros to map Force’s encoders to Elektron encoders via CCs, and when turning the Elektron encoders you’ll see the Force’s OLEDs reflect what you’re doing on the Elektron. It’s all recordable and editable in a MIDI track.
Switching Kits on the Fly:
No, since the biggest difference between the MPC and Force is their sequencer workflow. You already know how the MPC works - all sequences are the same length and each obeys the master sequence. Think of Force’s clips as independent sequencer lanes - each has different lengths and start offsets, but they all can follow the global clock. There is no master sequence, but there is a master clock. With the classic MPC sequencer workflow, there is a master sequence and all track sequences are locked to it, including length and start. JJOS has ‘simultaneous sequence’, but it’s limited and not as flexible as Force’s clip-based sequencers.
With Force, you can replace a drumkit with another, and all existing MIDI data in its track is retained, since kits aren’t tied to a sequence - they’re separate entities, but it’s not as convenient as MPC’s programs, where a sequence can drive any loaded program. But on Force, you can copy any MIDI clip from any track to another track. And of course you can copy an entire track, along with all of its clips, and paste it to a new track and change the kit there. It’s nearly instantaneous too.
Live Time-Stretching/Warp:
Two algorithms - Basic and Pro 10. Neither is as good as some of the CPU-intensive live algos in major DAWs. But I believe Force 10 is on par with Elastique Efficient live stretching. But from what I’ve heard so far, Maschine+ sounds better. But Force 3.0.5 now has offline Elastique Pro time-stretching, which is considered the best algo in most major DAWs. It costs more to license, so it’s nice that Akai didn’t charge us for the 3.0.5 update.
Currently Testing: Ableton Live Set (.als) Import:
Force only has 8 audio tracks, but has up to 128 Drum/Keygroup/MIDI/CV tracks.
iPad apps that can export .als:
- Ampify/Novation Blocs Wave can export audio, to Files Apps, etc.
- Ampify/Novation Groovebox can export both audio and MIDI, to Files Apps, etc.
- Dmitrij Pavlov Groove Rider GR-16 can only export audio, to Files Apps, etc.
- Korg Gadget 2 can only export audio or MIDI, not both, and only to Dropbox or iTunes File Sharing, which is inconvenient.
Desktop software that can export .als:
- Ableton Live.
Everything is imported - Audio + MIDI clips, Drum Kit samples are automatically loaded into a Drum program, keygroups are auto-created and sustaining sample loops are retained, track colors & names are imported, etc. Arrangement & Session View both look identical to Live. Still needs more work, but currently works fairly well.
Wishlist:
- Tempo automation and different time signatures. The old MPCs had this - I don’t know why the new MPCs don’t. It would be more difficult to implement on Force due to its clip-based sequencers. A separate tempo track and time signature track may work.
- Modern Elektron sequencer tricks for its step sequencer. Parameter locks, probability/chance, trig conditions, scale divider/multiplier for each clip…
- MIDI Learn for external controllers
- Track re-ordering
- Disk-streaming
- More LFOs for the AIR synths
Force 3.0.6:
Rumor is the new drum synth is coming. Drum synth apparently has more parameters than the ones in Maschine. Disk-streaming possibly later. Better step sequencer even later. Hopefully we see all this early next year, but who knows, it could take >1.5 years like 3.0.5. Or never.
