I agree it's not quite there as a workstation replacement yet. It does have a lot of really good features that allow you to create freely away from a pc. My only gripe with Akai is the firmware updates are not vetted well. Instead of fixing things they break something new with each one.
Another thing about setting key ranges or key span is when you dealing with keygroups. On the old S series samplers you can set key ranges with an external midi keyboard by selecting which notes you want. With the Force they haven't thought about that one, you can't even use the pads in note mode to set it. You have to dial everything in. I've always thought that they forgot to add a front end for for the keygroups, its all a bit raw and half baked if you know what i mean. Other areas are the same like macro assignments. Also whoever Akai have hired to program these units doesn't seem to know much about midi and how its supposed to work. I know they've done some bizzare programing routines with the midi side from people that have looked at the code. Lazy coding almost.
The most hilarious part is that in 3.2 update if you play your c-36 on one keyboard you CANNOT play it on another. I almost laughed till I cried. 4-6 hrs fkn lost night before gig trying to convert from 3.1.3. to 3.2. Old one stutters whenever I play from disk, while new one eats up midi notes... Pick your poison as they say.
@@micindir4213 Oh, my. Now that you say it, I remember that I read about this bug. Just tried it with 3.2.1 and it is still there, you cannot even work around it with an additional MIDI channel...
YOU CAN SWITCH SOUNDS AUTOMATICALLY. If you use scenes you can set up MIDI track for each instrument you want to use with SEND to track parameter. Basically keep midi routing and sound sources separate. Now you should create midi clip on each midi track and INSERT 'mixer off' event in your clip, then you can copy it to other MIDI tracks. To select a sound you must create 'mixer on' event for your selected MIDI track. Keep in mind that you can select sounds without quantization, i.e. immediately. If you want ability to manually select sounds, you should add more MIDI tracks with AUTO setting, that would allow to override your MUTES ( but still need to resolve 'current playing sound problem'). If you set your PROGRAM CHANGE to track select you can basically select sounds with program change and shuffling around track numbers. Keep in mind that you better off with populating EACH CELL with off/on clips, that would keep your set glitch free, especially if you jump around your songs. I got to a point where my set is refusing to load if I populate 100 scenes x 40+ tracks. Oh and I use Force hack for MPC, so best of both I would say.
I don't think Force fits in the category of Fantom and other similar workstations (which is good!) As for the update , there are lot of bugs , it seems rushed only to push for buying the new synths , I didn't update ,although I like the track reorder (finally) PS. On 4:32 I'm totally lost , can't understand about the lack of sequences (and mute groups?) for changing sounds 😁
Watch my previous video about the "MPC as a workstation" which works pretty nicely as a workstation replacement. This should make things clearer. With the MPC you can switch sounds by switching Sequences or using Mute groups: th-cam.com/video/DI9KT-wLPmU/w-d-xo.html
@@mossgraber ok ,now I understand (should re-watch the previous video before posting) As a workaround on Force ,for playing live, you could program the Macros (knobs or pads) to mute/unmute certain tracks (or balance sounds) :)
To me it is. Split is a big problem. Used a fantom x before. Use the force as playback and synth with akai miniak as midi controller which can send out key ranges on different midi channels and let’s you choose which channel responds to the sustain pedal.
you can set keyrange like on mpc by using custom firmware. custom firmware reveals hidden mpc pages so you are allowed to set keyranges
I agree it's not quite there as a workstation replacement yet. It does have a lot of really good features that allow you to create freely away from a pc. My only gripe with Akai is the firmware updates are not vetted well. Instead of fixing things they break something new with each one.
The Force is all set up to do it, but not fully implemented yet... I would make an educated guess that it's on the way...
Another thing about setting key ranges or key span is when you dealing with keygroups. On the old S series samplers you can set key ranges with an external midi keyboard by selecting which notes you want.
With the Force they haven't thought about that one, you can't even use the pads in note mode to set it. You have to dial everything in.
I've always thought that they forgot to add a front end for for the keygroups, its all a bit raw and half baked if you know what i mean. Other areas are the same like macro assignments.
Also whoever Akai have hired to program these units doesn't seem to know much about midi and how its supposed to work. I know they've done some bizzare programing routines with the midi side from people that have looked at the code. Lazy coding almost.
We can only hope that this will improve. On the MPC you can already set the keyrange from an external keyboard.
The most hilarious part is that in 3.2 update if you play your c-36 on one keyboard you CANNOT play it on another. I almost laughed till I cried. 4-6 hrs fkn lost night before gig trying to convert from 3.1.3. to 3.2. Old one stutters whenever I play from disk, while new one eats up midi notes... Pick your poison as they say.
@@micindir4213 Oh, my. Now that you say it, I remember that I read about this bug. Just tried it with 3.2.1 and it is still there, you cannot even work around it with an additional MIDI channel...
It is certainly a workstation, you can create full tracks with it, may it be standalone or as central hub of your studio.
In the original meaning that a workstation should empower you to create a full track, absolutely!
YOU CAN SWITCH SOUNDS AUTOMATICALLY. If you use scenes you can set up MIDI track for each instrument you want to use with SEND to track parameter. Basically keep midi routing and sound sources separate. Now you should create midi clip on each midi track and INSERT 'mixer off' event in your clip, then you can copy it to other MIDI tracks. To select a sound you must create 'mixer on' event for your selected MIDI track. Keep in mind that you can select sounds without quantization, i.e. immediately. If you want ability to manually select sounds, you should add more MIDI tracks with AUTO setting, that would allow to override your MUTES ( but still need to resolve 'current playing sound problem'). If you set your PROGRAM CHANGE to track select you can basically select sounds with program change and shuffling around track numbers. Keep in mind that you better off with populating EACH CELL with off/on clips, that would keep your set glitch free, especially if you jump around your songs.
I got to a point where my set is refusing to load if I populate 100 scenes x 40+ tracks.
Oh and I use Force hack for MPC, so best of both I would say.
Great tips! Just tried them and they work fine. But still quite a bunch of work to set up.
@@mossgraber It works for specific way of playing. i.e. Force is the master of the band, providing click, samples/ backing etc.
I don't think Force fits in the category of Fantom and other similar workstations (which is good!)
As for the update , there are lot of bugs , it seems rushed only to push for buying the new synths , I didn't update ,although I like the track reorder (finally)
PS. On 4:32 I'm totally lost , can't understand about the lack of sequences (and mute groups?) for changing sounds 😁
Watch my previous video about the "MPC as a workstation" which works pretty nicely as a workstation replacement. This should make things clearer. With the MPC you can switch sounds by switching Sequences or using Mute groups: th-cam.com/video/DI9KT-wLPmU/w-d-xo.html
@@mossgraber ok ,now I understand (should re-watch the previous video before posting)
As a workaround on Force ,for playing live, you could program the Macros (knobs or pads) to mute/unmute certain tracks (or balance sounds) :)
@@pdmidipd_patch7476 Yes, I need to look into this as well.
To me it is. Split is a big problem. Used a fantom x before. Use the force as playback and synth with akai miniak as midi controller which can send out key ranges on different midi channels and let’s you choose which channel responds to the sustain pedal.
@@arthurflink Ah yes, forgot to mention that you can still use a keyboard which can handle different zones!
Your not helping me from not buying a force Jurgen!
But at least I tried 😂