Stick to your guns unless they're misfiring.
To paraphrase...if it ain't broke, don't fix it.
I've tried every DAW under the sun and found nothing comparable to the functionality of FL Studio for what I do. I'm on a Mac, so I settled in to Reason and 7.0 is making me happy with faders built in with the module because it's reminiscent of FL.
I've used FL since 3.56 I'm surgical with it. The step sequencer and sample cell alone provide more functionality than most programs for sampling and drums FACTUALLY, problem is, most people don't delve enough into the functionality to understand what they're missing.
While some complain about things within FL, 9/10 there is a workaround that you can save to template and start every song without those factors in place.
From my experience the only thing that can't be done in FL fluently as other programs is use of a mod wheel. That's a big issue depending on how you create, was always my biggest/ONLY issue, I can name like 20 with any other program.
Same time, if your list of shortcomings with FL are continuously growing, you may want to find something to fit your needs better.
I don't like how FL assigns (or "doesn't assign") channels to mixer tracks. The paradigm is powerful, but lends itself toward disorganization. Have you ever watched Avcii's Future Music interview on YouTube? He uses FL and basically says, "Yeah, I just assign things randomly and don't remember where they're assigned, so it's a big mess for me". Sure, you can go through and assign each channel one-by-one to sequential mixer tracks, but it's tedious and becomes a major PITA when you decide to delete channels or reorganize their order. You end up with orphaned mixer tracks and sequences that don't correspond to one another.
The mixer track names don't sync up with the channel names either! In the paradigm they're built on, I can understand why. Regardless, it just adds a lot of tedium if you like to keep large projects organized. If you "Auto-Assign" a mixer track, it will copy the channel's name to the mixer track initially. If you have an instance of Sylenth1 that you just loaded up, you had better decide the exact sound it's going to be before you assign it to a mixer track. Is it going to be a "buzzing synth"? Is it going to be a "goa lead"? Choose once and choose wisely, because if you decide to change it later, you have to change it in two places. If you forget to change it in both, you may very well confuse yourself in large projects. You'll find yourself thinking, "OK, Sylenth1 #1,
Sylenth1 #2, [...], Syleth1 #12. Which one is the secondary lead in the first part of the hook again? I renamed the channels, but not the mixer tracks. Argh!"
I think this is one of the reasons FL Studio gets a bad rap as having a "bad sound engine" (lol). The mixing workflow is really so tedious and unintuitive (albeit powerful, admittedly) that many producers don't really mix at all. The others generally avoid the established practices of setting up organized sub-mixes on different buses for different groups (i.e. drum sub-mix, vocal sub-mix, etc.). A few work in a more organized fashion, but with an amount of tedium that increases exponentially with project size/complexity.
I really, really like FL Studio apart from this paradigm, its instability (random crashes), and lack of native 64-bit support in the final release (although I know it's just around the corner and available in beta!). I've used it since version 3.0. Since version 11 just came out, I'm going to download it and give it a try.
-Ki
Salem Beats