Over on CDM, Peter has another great, but controversial article. I guess that it's just supposed to be a run down of the new features in FruityLoops 8, but as a dedicated FruityLoops user, I find some of the assertions somewhat puzzling.

FruityLoops' custom version of synthmaker ... hawt (pic from CDM)

In Peter's article, he points out that FruityLoops isn't like the other DAWs on the market. Like Ableton, it kind of needs its own category. Peter then goes through a list of some of the new features, and I admit that a few of them are geenuinely hawt. The two most important upgrades, in my opinion, are the addition of a bundled version of SynthMaker, and an improved version of Edison.

Make your own instruments and effects: FL is bundled with FL SynthMaker, an “FL-native” version of one of the best DIY plugin makers on any platform. You can now build your own MIDI “dashboards”, effects, and instruments without coding and share what you’ve made with other FL users.
...
Beefed-up Edison: Edison, an editor/recorder that’s integrated with FL, was already good stuff. Now it also does audio-to-MIDI analysis, records larger files, and lets you mark and dump sound to the Playlist. There’s also an interesting improvement that does gaps filling and drum loop stretching — more on that and the overall workflow here soon.

Still, FruityLoops has faced the same flaws since its inception, and these apparently aren't going to be addressed in version 8. Peter hypes up version 8 to the Nth degree, but he ignores the fact that what makes FruityLoops great is also what makes it terrible (I say this as a current and long time FruityLoops user). For instance, take a look at the list that he cites:

1. FL’s approach to sequencing is like nothing else.
2. It’s kind of a ridiculous value.
3. It keeps getting better.
4. It’s not for everyone.
5. It’s a reason to use Windows.

Do you see the contradiction there? It's kind of subtle.

As a semi-professional user of FruityLoops 3 through 7, I can unequivocally state that numbers 1 and 4 on that list conflict with numbers 2 and 3.

The truth is that number 1 on that list basically negates number 2. FruityLoop's approach is so unique that it negates the value pricing. If you want to use FruityLoops, you basically have to commit to another DAW. So while you will save money by getting everything you get with FruityLoops, you will still find it necessary to purchase another DAW to streamline your recording ... so the final price you pay will end up being about as much as if you had just bought another product in the first place.

Some people will probably strenuously disagree with that assertion, but let me explain.

The FL interface is built like a hybrid tracker/sampler. Normally, you run it with a sampler window open and a tracker-style sequencing window open (and probably your mixer window). What's missing from that equation? A traditional timeline view. So in version 7, they tack the timeline view onto the bottom of the tracker window in a way that is neither convenient nor pretty. This way you can see how your recorded audio lines up with your loops. If you're like me, however, most of your projects blend loops AND recorded tracks. Personally, I often use about 4 or 5 loop tracks with about the same number of audio tracks. Each loop track usually has 8 to 10 loops in it, so this amounts to around 40 loops. This creates a massive visualization problem where you can't see all of your loops and audio tracks at the same time, and you end up spending so much time scrolling around the window that your productivity goes down.

Where is the dedicated timeline view? Honestly, you're about 3 years overdue with that one.

The other issue I have is with plugins. You can only add 8 plugins per mixer channel. That doesn't sound like much of a limitation, until the day you need to use 10 plugins. Then you have to use 2 mixer channels for one instrument ... and that is lame.

I have no idea why Image-Line hasn't reverted to the somewhat industry standard implementations of these two things. It seems like basic intransigence, since the way most programs handle plugins and the timeline is pretty standard and pretty solid.

I have a bunch of other little quibbles with the interface, and the overall design of the program, and until those issues are addressed, none of these extra little features are going to help. I hate to rain on your parade, Image-Line, but beat slicing effect became industry standard about 2 years ago, so slicex seems kind of gratuitous. Especially when free plugins like Glitch and LiveCut already address this issue (for the most part).

Finally, I want to point out that I am a FL Studio apologist. I LOVE FL Studio for making drum loops. Image-Line's FPC is my favorite drum sampler, especially with all the free kits that come with it! I also love Image-Lines general sampler plugin, DirectWave. It is, in my opinion, actually better than Kontakt, and that is quite a feat.

RANT CONCLUSION: I want to love FruityLoops version 8, I do. And I can see that Image-Line is trying, but they seem to be missing the point. Until they address the design problems at the core of the FruityLoops experience, those flaws will always force it to be a second-rate DAW. Until Image-Line redesigns the experience from the ground up, FL Studio will always be your backup piece of music software. It will remain the software that is great to have around, but isn't good enough to be your number one.

Thanks, Peter for continuing to run my favorite blog, and writing another piece that forces me to write a rebuttal. Keep it up!