![]() But while Akai is the brand that popularized that way of working, it does seem that programming in rhythms fits the FL ethos. So instead of playing in those velocities, you’ll dial them in with encoders. What you don’t get, though, is velocity sensitivity, as on the MPC (original and current) and rivals like Maschine. ![]() That makes sense, as those music styles – both in terms of listeners and producers – are growing fast. It mirrors the iconic step sequencer that has always popped up first when you load FL Studio (back to the first Fruity Loops), and it makes programming rhythms easier, since you can see a whole bar’s worth of sixteenth notes.Īnd Akai are positioning this with trap and hip-hop in mind. Shifting from 8×8 to 16×4, though, makes a real difference in workflow. ![]() The difference: more triggers for software functions, and the grid is 16×4 instead of 8×8. It’s clearly descended from Akai’s own APC and Novation Launchpad (the latter still features in product images for FL software). What you get from the Fire is a big grid of buttons, four encoders, and then a whole bunch of triggers including transport and other functions. But first-time users may want an integrated package, and dedicated hardware can be pre-mapped to do useful stuff. Okay, so the pitch here is easy: yes, you can use any number of controllers with FL Studio. So can it bring something new to the integrated controller world? ![]() It looks like the step sequencing grid you see when you open FL, and it was created in collaboration with Image-Line. As the Akai APC40 was to Ableton Live, so the Akai Fire hardware controller is to FL Studio.
0 Comments
Leave a Reply. |