Pro Audio Files

FL Studio is Badass, If You Don’t Make These 7 Mistakes

Digital Audio Workstation Bias (DAW Bias for short) is real, and it’s a problem. Notable signs of someone with DAW Bias are: blaming the DAW for the music made in that DAW, making sweeping statements about the capabilities of a DAW (without spending time to actually learn it), and randomly cursing people out on the internet for not using their DAW of choice.

The most common and one of the most damaging forms of DAW Bias is FL Studio Bias. This is marked by the belief that only amateurs and people without talent use FL Studio, and is usually accompanied by being a low-key hater of Hip-Hop and EDM. Countless smash hit records have been made in FL Studio. It’s a great tool in all forms of electronic production, including Music For Film, Experimental Rock, and of course Hip-Hop, EDM and Electronica.

However, behind many biases are a grain of truth. DAWs are complex and reading manuals is boring. This leads to a lot of mistakes that are simple to fix, but often go unchecked. I mix a lot of records that were produced in FL Studio and there’s a few stand out mistakes I think need to be addressed.

Help end DAW/FL Studio Bias today!

Mistake 1: Clipping Your Channels/Master

Let’s be honest, we all want our productions to be more thumpy, and a big part of that is making the playback level loud and proud. However, there is a good way to do this, and a not-so-good way to do this. The most common mistake I see is people overloading either their individual channels, or their master channel.

What does overloading mean? In the digital world we have a level ceiling, and once a sound exceeds that volume level it distorts. While we get the signal louder by turning it up, up, and up, we also lose punch and create a tonal quality that is usually worse than what we started with.

Unfortunately, it’s very easy to do this. Why? Because most of our drum samples are starting out normalized to maximum volume. Drum sample producers want their drums to appear as loud as possible, so they maximize the level of the sample. That means when we program this sample into FL Studio, there is no more room to turn it up without distorting!

Solution: Turn your sample level down right at the beginning and turn your monitoring level up if you want that thump while you’re producing. By doing this, you leave yourself room to turn things up or down. Watch for those little red squares at the top of your channels. If they show up, that means you’ve overloaded the system.

But how do you make the playback loud? On your master channel place a device called a Limiter and use that to turn up your levels. The limiter will prevent clipping. And while it may seem counterintuitive, by turning things down at the very beginning you will actually have an easier time getting things even louder at the end.

Lastly, running your sessions at 32-bit Float will prevent clipping as well, but be wary because there are some pitfalls.

Mistake 2: Relying on 32-bit Float

When you start a FL Studio project you have the option of selecting 16-bit, 24-bit or 32-bit float. 16 and 24-bit are fixed value systems, meaning they have a hard digital ceiling which cannot be exceeded. 32-bit float has a floating ceiling, meaning as we turn things up, the ceiling is moved up as well which prevents clipping. Seems like it immediately solves our original problem of overloading our channels, right?

Well, yes and no. The first problem with this is that if your final export is converted to 24 or 16-bit, that ceiling moves right back down to where it would have been had the project been mixed that way to begin with. That means we could go from no overloads to distortion city. And that’s exactly what happens when we run an MP3, burn a CD or send the file to someone else who imports the file incorrectly.

We also have the issue that while the digital ceiling might be moving, the internal calibration of our plugins are not. If you’re running a signal +15dB and you put a compressor on it, you’re seriously handcuffing the capability of that compressor, because all the settings are still based on the idea that 0dB is the loudest anything will go. If we put on a saturation plugin, we’ll struggle to get subtle saturation because, again, our lowest value is 15dB above what the plugin thinks the maximum value should be. We won’t internally clip our plugins, but we’re going to limit our workflow.

Solution: Personally, I skip working in 32-bit Float. It’s great to prevent the potential of clipping our channels, but that can be accomplished just as easily by turning our initial sample levels down. Going that route doesn’t incur the possible headaches that come along with a floating system.

Mistake 3: Ignoring Velocity, Time Offset and Swing

FL Studio has a ton of capability — even within the primary sequencer itself. But alas, many aspiring producers don’t go even a few steps further to explore these capabilities. While I don’t think it’s necessary to learn every nuance of FL Studio (although … why not?), I think there are three that are an absolute must when producing music: Velocity, Time Offset and Swing.

Music is dynamic — meaning it changes. If everything hits exactly the same, exactly on the beat, it sounds like robots made it. Which in some circumstances can be ok. Freezepop has made an entire subgenre of their own from strictly quantized, robotic sounding music. The perfect sequencing of Muse’s “Madness” is effective. And the hi-hat rolls in Trap kind of work, somehow. However, most music benefits from dynamics and pocket (changes in level and timing).

By default, FL will put a hit at a designated velocity on the exact timing of a beat. But if you open up the sequencer window you can find that all of this is adjustable. Just by doing something as simple as drawing a contrast in velocity between your “big beats” (the really important drum hits you want to accent) and “inside beats” (the less important ones that just help the groove along) can make a profound difference.

Making some micro-timing adjustments can give the record an exciting feel. If you want something relaxed and groovy like the kind of Hip-Hop we like to smoke wee … err … relax to, drag those snares ever so slightly late. If you want something really upbeat and exciting, put whatever is on the second quarter note (probably a snare/clap) exactly on grid or a little late, and put whatever is on the fourth quarter note (probably also a snare/clap) ever so slightly early. And I’m talking just subtly enough so that you feel it, not so much hear it.

Congrats, you’re in a whole new world of thinking now.

It’s also worth playing with the Swing slider. Just mess with it, you’ll hear what it does. There’s a whole new world of potential grooves out there. Swing Trap? Somebody better do it, or I will.

Mistake 4: Stagnant Arrangements

Music is progressive. If you start at point A, go to point A, and then end at point A, you haven’t told a story. You’ve just repeated a sentence. No one is trying to hear that. People want arc, drama and excitement. Don’t make a two bar loop, copy it eight times, copy it four more times with one new element on top of it, and then go back to the original loop eight more times and call it a verse – chorus – verse. It’s 2017 — c’mon now.

Create variations of your original loop and bring them in and out during the verse. When you go from the verse to the chorus, put in something to build tension and make the listener want that chorus to kick in. Don’t forget an intro and maybe a bridge. Even if you’re just making a beat and there’s no lyrics yet, give the lyricist some energy to go off of. Make a format to help them tell their story!

Mistake 5: Missing The MIDI Functions

FL Studio is centered around its wonderful step sequencer. It also has MIDI capability that allows you to plug in a keyboard and play a part in real time. The best producers know this and take full advantage of being able to both play live and program by sequence.

Even if we go under the hood and meticulously sculpt every note velocity and bit of timing, it still doesn’t account for all the possibilities one can create by simply playing a part in real time.

Mistake 6: Not Optimizing Your Export

After spending hours to days to weeks producing a song, don’t drop dead at the finish line! When exporting, we want the absolute highest quality file we can print out. For this I would just straight up copy these settings:

  1. Under “Project Type” select “Full Song” and “Leave Remainder”.
  2. Select “Wav” and under “Wav Bit Depth” select 24.
  3. Under “Quality” select the highest resampling rate you can pick. Currently that number is 512. Enable “HQ For All Plugins”, “Disable Max Polyphony” and “Alias free TS404”. If you ran your session at 32-float, enable “Dithering” as well. If you ran your session at 24-bit or less, it isn’t necessary.

Mistake 7: No “Re-Recording” Mix or No Individual Trackouts

This one is for folks who are selling instrumentals online. When advertising your production on your sales page, I completely advise making a heavily compressed, pumped up, loud version of the instrumental. Your potential customers don’t understand the process of production, they just know what they hear and they expect the record to be loud. However, when it comes time to record the vocals for the production, that’s an entirely different story.

In order to get the vocals to blend well with the music, whoever is recording and mixing needs space in the record. If the record is slammed, whether through compression, limiting or hard-clipping the master channel — there is no more room. In order to make the vocals work, the engineer will have to make concessions. And again, counterintuitively, the final product will probably be less loud than it would have been had the engineer been given a less compressed file to begin with.

Once a beat is purchased, make an alternate version that is less compressed to help the process. Your name is going on this record and over the long term, everything that can help the success of the song benefits you!

You know what’s better than a less compressed mix? The complete individual trackouts of each audio element.

This one takes a bit of judgement. If you don’t know whose hands the instrumental is going to end up in for mixing, you may want to stick with the 2-track (just the beat, without the trackouts). However, if you know that a badass engineer will be handling the mixdown, give us the versatility to make the record the best it can be.

In order to do this, under “Miscellaneous” in the Export menu, select “Split Mixer Tracks”.

Now, again, here’s a bit of subjectivity. There is also an option labeled “Enable Insert Effects”. With that selected, all the processing like EQ and compression you have on your sounds will be printed into the trackouts. Personally, I’m an advocate for enabling that button. It’s your song and your sound. Mix engineers are not here to reinvent your music — we’re here to make it sound incredible. As long as you like what you did, you’ll love what you get back. However, if you are new to producing or unsure of your choices in effects, it’s ok to leave them off.

With these things in mind, FL Studio is every bit as good (if not better in some regards) as any DAW out there. So go make your music and let haters stand in the dark.

Missing our best stuff?

Sign up to be the first to learn about new tutorials, sales, giveaways and more.

We will never spam you. Unsubscribe at any time. Powered by ConvertKit
Matthew Weiss

Matthew Weiss

Matthew Weiss is a Grammy nominated and Spellemann Award winning audio engineer from Philadelphia. Matthew has mixed songs for Snoop, Sonny Digital, Gorilla Zoe, Uri Caine, Dizzee Rascal, Arrested Development, 9th Wonder, !llmind & more. Get in touch: Weiss-Sound.com.


Free Video on Mixing Low End

Download a FREE 40-minute tutorial from Matthew Weiss on mixing low end.

Powered by ConvertKit
  • Simba Zuva

    Why not write articles like these with illustrations included or simply make a youtube video??

/> /> /> /> /> /> /> /> /> />