mgx

soft synth vs. making actual music

> I read [this post](https://jdtorian.bearblog.dev/buying-new-gear-vs-making-actual-music/) and it stuck with me. When [Serum](https://xferrecords.com/products/serum-2) dropped, everyone lost their minds (twice). And I get it -- it's a beautiful hybrid synth. Smooth interface, wavetable editing that actually makes sense, the whole thing is just _nice_ to look at. For a minute I thought maybe I was missing out, that I should upgrade my setup like everyone else seemed to be doing. But here's the thing: [Massive](https://www.native-instruments.com/en/products/komplete/synths/massive/) already did what I needed. It had character and I knew how to push it where I wanted to go. So I stayed. That wasn't stubbornness or some "back in my day" thing. It was just... practical. Why spend money and time learning a new interface when the one I had was already making sounds I liked? There's this weird pressure in production communities where you're supposed to always be chasing the next tool, the next preset bank, the next "industry standard." But that's just noise. Same thing applies now. I've got [Spire](https://www.reveal-sound.com/plug-ins/spire), FL's native stuff, [Ozone](https://www.izotope.com/en/products/ozone), [Voxity](https://cymatics.fm/pages/voxity-st2-c) -- and honestly, that's enough for almost everything. Could I grab [Kontakt](https://www.native-instruments.com/en/products/komplete/samplers/kontakt-8/) libraries or [Heavier7Strings](https://www.threebodytech.com/en/products/heavier7strings) for specific projects? Sure. Sometimes I do. But there's no emergency in it. The real work isn't about having all perfect tools anyway. It's about sitting down and actually making something. A [stock DAW](https://www.youtube.com/results?search_query=fl+studio+stock+plugins+only) can do almost everything. The difference between a finished track and an unfinished one has nothing to do with which synth you're using.

Tagged in music