Hi!
(I use FL studio 20).
In my synthpop songs I use many synth parts (for chords, melodies, etc).
I want to render many vst synths to audio, and then mix the audio of the synths.

At what quality should I render the vst synths to audio? :
a) 32bit wav float
b) 24bit wav (with dither)
c) 16bit wav (with dither)
?
(Let's say each song will have at least 10 synth parts to render)

Will I end up with a better sounding mixed track if I render the vst synths to 32bit wav VS 16bit wav?

 

When it comes to rendering your VST synths to audio, I recommend rendering them to 32-bit WAV float.

The reason for this is that 32-bit float offers higher dynamics and more headroom, giving you more flexibility when mixing. You can better adjust the volume and effects after rendering without any audible loss of quality.

In comparison, 24-bit WAV (with dither) also offers very good quality and is a common choice for most productions. 16-bit WAV (with dither) has a lower bit depth and can sound good in certain situations, but you probably won't have the same flexibility and quality as with 32-bit float or 24-bit.

To summarize, you'll probably get better sound quality and more mixing options with 32-bit WAV float, especially if you have a lot of synth parts.

Have fun producing!

 

Instead of rendering...cant u output it thru your mixing console and then record it again as an audiofile?...thats my way to do...but i understand not evryone is a happy owner of a decent mixing console.

 

https://audiosex.pro/threads/32-bit-float-vs-24-bit-for-recording.77526/#post-804237

There are quite some threads about this already.

 

This will give you the lowest noisefloor, so low (several hundred db) that you will never compress, distort, process your audio so much that you would hear the noisefloor/quantization error.

Depends. If you plan on post-processing your renders (with really heavy compression for example), you might end up putting so much gain on the noisefloor (16bit = -96db) that your dither noise becomes audible - or your quantization distortion if you didn't dither.

But maybe you like some added noise for analog vibes?! Up to you.

I render to compressed 32bit, size difference is whatever to me.

 

Last edited: Feb 20, 2025

You render to 32bit in some other format than wav?
This way you get the super low noise floor and a smaller file size at the same time?

 

Yeah, exactly. But I use Reaper & WavPack. The savings are about 30% for 32bit wavpack compared to 32bit wav. I don't know what FL supports. (FLAC can't do 32bit float btw, only 32bit integer)

 

32-bit float

Compared to fixed-point files (16- or 24-bit), 32-bit float files store numbers in a floating-point format. This is fundamentally different than fixed point, because numbers in these WAV files are stored with “scientific notation”, using decimal points and exponents (for example “1.4563 x 106“ instead of “1456300”). This difference is significant because much larger and smaller numbers can be represented compared to a fixed-point representation.

The formatting and encoding of the 32-bit word is not intuitive–it has been optimized for computers to be able to perform common math functions on it rather than for human-readability. The first bit indicates a positive or negative value, the next 8 bits indicate the exponent, and the last 23 bits indicate the mantissa. More info is available regarding this format (called IEEE-754).

The dynamic range that can be represented by a 32-bit (floating point) file is 1528 dB. Since the greatest difference in sound pressure on Earth can be about 210 dB, from anechoic chamber to massive shockwave, 1528 dB is far beyond what will ever be required to represent acoustical sound amplitude in a computer file.

There is one other aspect of 32-bit float files which is not immediately obvious. Files recorded with 32-bit float record sound where 0 dBFS of the 32-bit file lines up with 0 dBFS of the 24- or 16-bit file. Keep in mind that unlike the 24- or 16-bit files, the 32-bit file goes up to +770 dBFS. So compared to a 24-bit WAV file, the 32-bit float WAV file has 770 dB more headroom.

 

I've always gone at 24bit, it sounds fine, works for me.
That said, if it doesn't tax your system I know of no logical reason to not keep your bit depth as high as possible.

 

I always only use 24dB. That was the case then and will be the case in the future too!!!
EDIT: 24 Bit was of course meant!

 

Last edited: Feb 20, 2025

Dither is designed to be the last process in a mastering chain. Seriously. Otherwise you're just adding extra noise for no benefit.

24 bit is a safe choice, that's what I use personally, but I can't see 32bit hurting apart from the extra size.

 

Interesting. I usually use 90 dB. It's louder, so it'll give you various benefits:

1. Enhanced Emotional Experience
   • Amplified Emotions: Higher volume intensifies the emotional response to music, making happy songs feel even more exhilarating and sad songs more poignant.
   • Physical Sensation: Loud music can create a physical sensation that resonates with the body, adding a layer of tactile engagement to the auditory experience.
2. Increased Immersion
   • Engulfing Sound: Loud music envelops the listener, creating a more immersive experience. It helps to drown out external noises and distractions, allowing for a deeper connection with the music.
   • Concert-Like Feel: High volume can mimic the feeling of being at a live concert, where the powerful sound system makes every note and beat feel larger than life.
3. Improved Sound Quality
   • Clarity of Details: At higher volumes, the nuances and details of the music can become more apparent. Listeners can pick up on subtle elements like background instruments or intricate rhythms.
   • Dynamic Range: Loud volume accentuates the dynamic range of a track, making the differences between quiet and loud parts more pronounced and impactful.
4. Psychological Impact
   • Boosted Mood: Loud music can have a stimulating effect on the brain, releasing endorphins that elevate mood and create a sense of euphoria.
   • Increased Energy: The energizing effect of loud music can make it perfect for activities like working out or partying, where a high level of energy is desired.
5. Social Aspect
   • Shared Experience: Loud music fosters a sense of community and shared experience, whether at a club, concert, or even a car ride with friends. It brings people together through a collective auditory journey.

However, while high volume can enhance the music experience, it's essential to be mindful of hearing health. Prolonged exposure to loud sounds can lead to hearing damage, so it's wise to enjoy music at a volume that is both enjoyable and safe.

In summary, a higher volume in music can elevate the listening experience by enhancing emotional engagement, creating a more immersive environment, improving sound quality, and boosting psychological and social impacts. Just remember to take care of your ears along the way!

 

If you can both read music and are down with colloquial American popular culture/slang/music of a bygone age you'll understand the render of my post...

 

if your machine allows 24bit,is the way to go,imho.

 

Last edited: Feb 24, 2025 at 4:03 AM

I'll always do 48khz/24bit with no dither. I see no reason for anything over that, it's all made up stuff for non-issues. If you can push a higher sample rate it's actually fine, but 32bit is just a waste of space. There's infinite headroom in 24bit, especially since it's a VST.

 

Let this sink in: analogue tracks had noise all the way up to about -60dB, if not 50 even, and they made tons of fuckloads of great sounding tracks in the last century with that. Consider also that these days lo-fi is in and lots of people use bit and sample rate reduction to get "that sound" (whatever it may be). Consider also we've been killing music with better and better sounding limiters for more than 2 decades and people are so used to 32-bit lo-fi, distorting sounding tracks that sound like crap to my ears.

And you worry about rendering your tracks at 16-24-32 bits and noisefloors down to -144 (24-bit) or -96dB (16-bit)??

Having said that, 32-bit FP is a sure thing and the cleanest sounding, also the appropriate format for further editing.. But it won't make much difference if your song sounds bad, really. Stop worrying. Just make music. *All* of the most productive people I know know nothing or very little about bits and dBs. The difference between us and them is - they make music and make money. We overthink, download stuff, and update plugins all the time, not much else.

Cheers! (hic! )

 

Last edited: Feb 21, 2025

My answer would be a) 32bit float render, Yes.*** If you were to somehow average the precision over all 10 files, I believe this would be the best results in a cookie-cutter theoretical world. @Will Kweks reply is why I think this would be the textbook answer. You would be dithering multiple multi-track synths being rendered, each with dither; meanwhile you still have all your mixing and additional processing to do still. It's being summed. If you do employ dither, it should be reserved until your final render to your target delivery format.

 

To put it further into perspective, you can render 32 or more tracks to 24-bit dithered or even non-dithered WAVs, mix them and you will not be able to perceive any difference between that and 32-bit rendered tracks, as the noise floor and "digital crunch" will still be under -100-ish dB. Rare people can hear noise at that level.

 

The only reasons to render 32 bit float (or higher, i.e. 32 bit int, 64 bit float) are safer quality and because if you render 24 or 16 bit, your file will be automatically reprocessed into 32 or 64 bit float in your DAW or editor and further processing, but this will be done with file with lost quality. So why do you need to use lower quality formats and spoil the quality, if your file will be reprocessed automatically in 32 or 64 bit float for further processing?