Maximus Intro and Overview PART 1 | FL Studio 21 Tutorial 

You're very welcome! Maximus is a great plugin! 🤙🤙

thanks dude!!

I do too!! There are lots of cool plugins they have. I particularly like the regular multi band compressor too.

And beyond! Lol

thanks man!! I'm glad you enjoyed it!!

Thank you so much!! I'm very happy to hear the videos have been helpful to you. I can definitely do more stock FL plug ins, is there any certain one in particular you would like to see covered?

@@jonaudio yes, there is 😆 I think there are really good mixer plugins which can make our beats more interesting. Plugins like: GROSS BEAT, VOCODEX, FRUITY DELAY BANK and FRUITY LOVE PHILTER I hope you make tutorials with them💪🏻

That's right. Today the official FL21 was released! Super exciting day, this update is a very exceptional one. A lot of FLs stock plug-ins are very capable and very good. I think a lot of people are led astray because they may think stock is bad for some reason? The goal is to have courses for the majority of FLs synths and their other effect plug-ins, to show that they are quite usable, not to mention the integration with the software, less plug-ins to manage in sessions and great CPU usage. Its easy to get lost in the hunt for new and shiny plug-ins but at the end of the day a Compressor compresses, EQs EQ, sure some do a slightly better job but the difference isn't that great. You'll never hear someone say "you know, this mix would be so much better if they used instead of . The concepts are what matters most rather that the gear for the most part.

You're very welcome, there are still more videos to come in this series. What's currently uploaded as of now will definitely give you a great foundation of the plugin.

Those are some very good points you bring up. Generally the mixing and mastering stages should be kept separate. Some mastering chains can use a lot of CPU so having the entire mixing going (lots of tracks, synths, effects, automation) can be CPU intensive as well, and then adding more on the mastering can choke the CPU. But a more important reason is that mastering sessions look different that mixing sessions. In a typical mastering session where you have more than one song, each song gets its own channel and inserts. The songs should cascade on the playlist. This way in addition to bringing the mixes to the target level, we can also add the right about of fade in/out times of the song, as well as the silence after a song. We let the song finish out, and let the air settle a bit, and then put a marker when the next song should begin. By doing this we can export the master as a selection, while retaining the extra time we add at the end. The end result being that all the songs flow into each other as a cohesive whole. Another goal of mastering is to make sure that all the mixes sound tonally related, so starting with a good master for the first track, you can save that as a preset and add that to the next mixes for a good starting base to further adjust from there the specific needs of the next track. Automation does play a role in mastering as well, bringing up the volume for the chorus in a range from 0.5 to 1.5 dB can give the feeling of a more energetic chorus. Presets like Clear Master, can be great starting points for you track, and once you get really comfortable with maximus you can work from that preset and really customize it to suit your track the best. Those are just a few reasons to have a separate mastering session. Hope that's helpful for you.

@@jonaudio awesome, thx for the explanation. That's some pro level knowledge that the majority of FL users prob don't know hah. I haven't really heard of loading multiple songs into one project to master them all at once. Then again, I haven't really done any mastering in general. I did also hear the advice that if you're going to use a compressor on your song on the master mixer track, that you might want to put that on at the beginning of the mixing rather than at the end. That way you can "mix into" the compressor and make your decisions that way, rather than make a bunch of mixing decisions and then throw the compressor on at the end which might change the sound a lot Having the mastering separated from mixing seems like it could cause issues, if you make the song sound good "raw", but then change it more with a plugin like Maximus after. But maybe mastering is more for polishing / making the song shine, whereas mixing is the core of the sound Many people I'm guessing don't even use mixing or mastering at all in FL and just slap plugins in and export the song. Which can still sound good I think. Bouncing audio to .wav and loading that back into a project, and / or exporting a mix and loading it into a mastering project are things I want to do more. Def saving on CPU could be good for a large project that might start tanking your CPU

One of the main problems I've seen when someone slaps mastering plugins onto their master channel in their mix session is a huge game of chasing their tail. What frequently happens is that they are making their mix decisions while it's running through the mastering chain, then later they may change stuff in their mastering chain, which changes their mix, so then then change the mix and so on and so on. It's a very non constructive loop that does a lot of harm in the long run. If you have a great mix, you'll get a great master. The goal of mastering shouldn't be radically changing the mix. but more so to bring it to the target level of what platform it is being released to, make all the tracks tonally similar and perhaps add some 'glue' to the track with the right about of compression for the song. If there are a lot of peaks in the mix, the compressors are there to bring the peaks closer to the average perceived level of the track, so everything can be brought up together and sound good by doing that. Mastering should generally be more transparent than not, if you find yourself struggling to get a good master, 9 times out of 10, it will be the mix that needs to be fixed not the master. Aside from cutting very low end and tightening some bolts, mastering shouldn't require fixing. I've gotten tracks I had to kick back because the mixing wasn't right, and if the mixing isn't right, the master won't be either.

@@jonaudio So would you suggest not using and compressor plugins on your master mixer track for your "mix" project, and just save the compressors and mastering plugins for once you export the mix and load up the mastering project? It seems that compression on instrument buses are still important in the mix, to glue related sounds together. E.g. have a drum bus track in your mixer, and use a compressor and eq on that to glue the drum sounds together