From beginner to pro: Here are the top lessons/threads I learned in 15+ years of mixing that helped me elevate my craft 🚀

El Networking Mata al Talento: ¿Estamos en la Era de las Conexiones? ft. @slatinize @NaitoProducer https://t.co/rwhdWMQtSw

Probando en mi cabina nuevo temaaaa 🥵 ayer puse un trozo en stories y os flipó, así que me he dado prisa en hacer el mix y a que @slatinize lo masterice para que lo tengáis la semana que viene… y así va sonando 🖤😮‍💨😮‍💨😮‍💨😮‍💨🥴 HERE I HAVE TECHNOOOOO TECHNOOOOO TECHNOOOO 🥳 21/03

Produced by https://t.co/AYVsZrneyh 🫶

https://t.co/0xmicJVSP4

Volvemos a hablar de mastering en Conectados y lo hacemos con Ruslan Slatin (@slatinize), un versátil productor que nos muestra en detalle su estudio y un proyecto completo realizado en Reaper. https://t.co/fcFeBBSQ9d

Some people care a lot about latency even when mixing and/or mastering, and they tend to use the smallest buffer size that their cpu can handle. Speaking of myself, I do not care at all about latency when mixing, so 2048 it's my go-to 😎

For recording sessions or live gigs, a lower buffer size is preferable for that instant response. Meanwhile, when mixing or mastering - a larger buffer size will be your ally, ensuring smooth, glitch-free processing.

Your computer gets to breathe a little, handling more tracks and plugins without buckling under pressure. So…how do you choose the right buffer size? It's all about understanding your immediate needs.

On the flip side, we have the high buffer sizes - think 1024 or 2048 samples. These are your go-to when stability and resource efficiency are your top priorities. Perfect for mixing and playback scenarios where real-time responsiveness isn't as crucial.

This can lead to the dreaded audio dropouts or glitches, especially if your CPU isn't quite up to the task.

This feature is a godsend during live performances or recording sessions, ensuring your inputs and outputs are virtually in sync. But, as with most things in life, there's a catch Smaller buffer sizes ask a lot of your CPU, demanding it to process audio data more frequently.

Now, onto the nitty-gritty...High? Or Low? The low buffer sizes, say 32 or 64 samples... Low Buffers slash latency dramatically. That means the delay between, say, striking a key on your MIDI keyboard and hearing the note is minimal.

Imagine buffer size as a sort of digital "basket' that holds a specific amount of audio data your computer handles at any given moment. This size is measured in samples and plays a critical role in balancing processing speed against latency within your DAW.

Buffer Size is one of the most annoying things that you encounter when you start producing, right? 🤣 CPU hogs, latency... Let's dive into what it means and how it can impact your music production...

PRO-TIP: If you want to take it further, you can automate the Dry/Wet Mix knob on your Pro-C2 and affect only the parts that need extra control.

Be mindful that for this to work, that bump shouldn't be too aggressive, otherwise, it is very easy to destroy your well-crafted dynamics. Do not overdo it.

Place an instance of Pro-C2 and gentlv increase the midrange area on the internal sidechain EQ, usually around 1-2 kHz. This modification offers additional dominance in the most audible area that can "jump off" the mix.

You've almost perfected the mix, and the vocals are perfectly integrated... However, as soon as the vocalist hits the high notes or gets a bit more excited, their voice suddenly "pops out" from the mix. Here's a quick and effective solution 😎

Each of these tools has a unique algorithm, leading to a unique sound. So, for me, Clarity doesn't replace these tools - it's a fantastic addition to my toolbox. 🛠

Whenever a new tool like Clarity hits the market, people often wonder if it replaces existing tools like Soothe, Gullfoss, DSEQ+, Voxengo Teote, and others. The answer, as always, is a resounding no! ❌