Freezing/freeze tracks and proper levels?

[Metrobot]

Hello,
This may be a dumb question:
I have some midi tracks that are pushing into the red by about .5 - 1.5 db.
However, things are quite well balanced as they are.
Should I bother adjusting them?
Just wondering if it matters at 64 bit?
-M

[Coachz]

It doesn't matter unless it annoys you or unless you're driving into some plugin that is gain level sensitive

[Fabian]

Unless this happens for the master track, it shouldn't be a problem. As you indicate, using 64-bit fp Reaper has a *lot* of internal headroom. Do not let the master track clip, though.

[Metrobot]

Originally Posted by Coachz

It doesn't matter unless it annoys you or unless you're driving into some plugin that is gain level sensitive

Nope, just instances of Kontakt and other virtual synths.
Thanks Coachz.
-M

[Metrobot]

Originally Posted by Fabian

Unless this happens for the master track, it shouldn't be a problem. As you indicate, using 64-bit fp Reaper has a *lot* of internal headroom. Do not let the master track clip, though.

Thanks Fabian.
-M

[Judders]

There is always the philosophy that if it doesn't sound broken, then it isn't broken.

However, whether those freeze files are clipped or not depends on your render/freeze setting in prefs. If you freeze 32 bit floating point files then there will be no clipping. If you are freezing 24 bit fixed integer files then you will (though you may not hear it, in which case only you can say if that matters or not).

[ashcat_lt]

There is a Project Setting that tells Reaper what format to use for Render/Freeze/Apply FX and etc. IF that is set to a floating point format, THEN it doesn't matter at all because it won't actually get clipped off in the process. BUT by default or using the Automatic setting, it quite definitely does NOT go to a floating point file, so DOES clip in the process.

Whether that actually makes a meaningful, noticeable difference in the end depends on just about everything else, but it's safest to go to floating point so you never have to worry about it.

BUT that's a Project Setting, and changing it for one project won't change it for others. You can save it as default project settings, but that still doesn't fix your other existing projects, so...


Edit - Sorry, I didn't notice that Judders had mentioned the setting... Also, changing the setting won't actually change any files that have already been freezed to fixed point.

[Judders]

Originally Posted by ashcat_lt

Edit - Sorry, I didn't notice that Judders had mentioned the setting... Also, changing the setting won't actually change any files that have already been freezed to fixed point.

Great minds...

Plus, I forgot it was in project settings and directed the OP to prefs.

[Metrobot]

Originally Posted by ashcat_lt

There is a Project Setting that tells Reaper what format to use for Render/Freeze/Apply FX and etc. IF that is set to a floating point format, THEN it doesn't matter at all because it won't actually get clipped off in the process. BUT by default or using the Automatic setting, it quite definitely does NOT go to a floating point file, so DOES clip in the process.

Whether that actually makes a meaningful, noticeable difference in the end depends on just about everything else, but it's safest to go to floating point so you never have to worry about it.

BUT that's a Project Setting, and changing it for one project won't change it for others. You can save it as default project settings, but that still doesn't fix your other existing projects, so...


Edit - Sorry, I didn't notice that Judders had mentioned the setting... Also, changing the setting won't actually change any files that have already been freezed to fixed point.

Thanks Ashcat and Judders,
Is that Project settings > Track mixing bit depth?
I have it set to '64 bit float (default)
-M

[Coachz]

Originally Posted by Metrobot

Thanks Ashcat and Judders,
Is that Project settings > Track mixing bit depth?
I have it set to '64 bit float (default)
-M

There goes the hard drive space ! :-)

[ashcat_lt]

Nope.

Project Settings|Media|Format for Apply FX, Glue...

IDK who recommended Automatic, but they're frickin wrong.

[ashcat_lt]

Originally Posted by Coachz

There goes the hard drive space ! :-)

That setting for the mix engine doesn't impact drive use at all (except maybe your page file???). I use 32 bit for the rendering setting which only 1/3 bigger than 24, and really all we need unless we're doing super stupid things.

[Judders]

Originally Posted by ashcat_lt

I use 32 bit for the rendering setting

Same.

Especially as I might freeze child tracks and then, later on, the parent. Sometimes sends, then the receive aux, then the folder they are all in. 32 bit means I never have to worry about quantisation error or dithering with all those generations.

[Metrobot]

Originally Posted by ashcat_lt

Nope.

Project Settings|Media|Format for Apply FX, Glue...

Thanks..I just relised you already posted it in your previous reply.
Do you use 32bit FP for 'wave bit depth' and track mixing bit depth at 32 bit float as well? Is that what you mean by the 'Rendering setting'?
-M

[Judders]

Originally Posted by Metrobot

Thanks..I just relised you already posted it in your previous reply.
Do you use 32bit FP for 'wave bit depth' and track mixing bit depth at 32 bit float as well? Is that what you mean by the 'Rendering setting'?
-M

Under "recording"?

No, your audio interface will not give you floating point audio when you record, so leave that at 24 bit PCM.

Under that setting it says "format for apply FX, glue, freeze, etc.", set that too custom: 32 bit FP WAV.

Track mixing bit depth should be 64 bit float (default).

[Metrobot]

Originally Posted by Judders

Under "recording"?

No, your audio interface will not give you floating point audio when you record, so leave that at 24 bit PCM.

Under that setting it says "format for apply FX, glue, freeze, etc.", set that too custom: 32 bit FP WAV.

Track mixing bit depth should be 64 bit float (default).

Thank you Judders
-M

[Judders]

No problem