|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#11
|
|||
|
|||
Re: 24 or 32 bit float
Not that it really matters but, the other thing that has not been mentioned here is that an audio file that has been recorded at 32 bit can not be clipped. You can always bring the waveform back down to a point below clipping with the clip gain trim. This is, of course, provided that you have not clipped the converter or mic pre's on the way in. Of course this is pretty irrelevant to anyone who follows the principles of proper gain staging but worthwhile mentioning nevertheless.
|
#12
|
||||
|
||||
Re: 24 or 32 bit float
Quote:
The way I think of it is audio written full scale 23 bit with a gain control that can be adjusted after the fact. This allows you in some, but not all, cases to perform signal processing that results in numbers that exceed full scale while retaining the ability to reduce the level after the fact back to where it won't clip a converter. Digital audio emerges from an A to D converter chip dithered to a 24 bit stream. There's no reason to record more than that. Once you start crunching numbers, you then need to worry about both dither and clipping. Using 32 bit float can certainly speed up a work flow but it isn't the magical solution lots of people seem to think it is. In the earliest days of the internet we had some of the most knowledgeable engineers in the world posting to usenet about the technology. I only learned enough to be dangerous but thankfully some of us who were curious did get to learn quite a bit during the late 1980s.
__________________
Bob's room 615 562-4346 Interview Artists are the gatekeepers of truth! - Paul Robeson |
#13
|
|||
|
|||
Re: 24 or 32 bit float
Basically 32 bit float is good for if you're going to be doing a lot of editing where you will be changing the gain of certain files, using audiosuite plugins (think Vocalign, Pitch Correction, etc), and stuff like elastic audio.
|
#14
|
|||
|
|||
Re: 24 or 32 bit float
If you have a 32-float file, processes it at 32-float, and save it back to 32-float, no audio program I know of will offer to dither it. Some, like iZotope products, will offer dither when saving a 32-bit processed file to 24-bit fixed. So maybe it would be clearer to say that the advantage is, you don't have to worry about dither when you stay 32-float because it's not an option.
E.g., when I do a bunch of noise reduction work on a file with RX, I begin by saving a version of the file at 32-float. Then I do my overall EQ pass, broadband NR pass, and then fix all the little individual problems. When I save my work every few minutes, I don't have to think about whether or not to dither it. It just saves to 32-float and I go on, which is conceptually the same as what happens in Pro Tools when an audio stream gets passed along from plugin to plugin to a buss to more plugins at 32-float. When the NR work is done, I save it, then save-as to 24-bit with TPDF dither. That file goes back into the Pro Tools session the original came from. I find that that workflow ends up sounding better than if I save the 32-float processes of RX back to 24-bit a few dozen times over the course of working on it. Better to keep it at one rate than to convert it back and forth repeatedly. This is probably one reason HDX is perceived to sound superior to TDM in many cases, since the TDM signal path sometimes has to convert the signal to 24-fixed and back a few times. If I were to decide to do all that NR work in PT instead of RX, I would want the session rate to be 32-float. My experience is, one or two layers of conversion are no big deal. After a few, quality may start to suffer noticeably. After a dozen or so, it starts getting ugly. That's why I say that a movie session with lots of sound design work going on may benefit from the 32-float session format. It all depends on how much of the processing is going to take place offline or is going to be reprinted after successive changes.
__________________
David J. Finnamore PT 2023.12 Ultimate | Clarett+ 8Pre | macOS 13.6.3 on a MacBook Pro M1 Max PT 2023.12 | Saffire Pro 40 | Win10 latest, HP Z440 64GB |
#15
|
|||
|
|||
Re: 24 or 32 bit float
I haven't read in-depth on the processing side of things, but though 24 bit is more than good enough in terms of the dynamic range of human hearing but I have found 32 bit extremely handy (alongside clip gain) for overages something 24 bit is not so kind with.
When setting up a session quickly and if those odd spikes come up when a singer gets too close to the mic, the track can be easily "fixed" with clip gain as long as the pre amp was not overloaded and distorted for too long. So in that respect I have found 32 bit an advantage.
__________________
"Are you sure what side of the glass you are on?" www.facebook.com/thereapersofficial |
#16
|
|||
|
|||
Re: 24 or 32 bit float
Quote:
J.
__________________
2010 Dolphin Award for Production / Engineering AVID Certified Instructor |
#17
|
|||
|
|||
Re: 24 or 32 bit float
Actually, this is only true with respect to clipping. If all one is doing is tracking and mixing, simple and straightforward, then it's true. For anyone doing offline processing where using a fixed bit format results in multiple layers of either dither or quantization distortion, it becomes a factor. You can't avoid quantization distortion with proper gain staging. You can avoid it with dither, but at the cost of a raised noise floor. Raise that floor just so many times, and you begin to cloud your sound. For film people who are printing submixed elements, printing them again with effects, printing stems with those included, printing mixes of stems, and so on, the problems can creep up. That's where a floating point file format can make a difference.
__________________
David J. Finnamore PT 2023.12 Ultimate | Clarett+ 8Pre | macOS 13.6.3 on a MacBook Pro M1 Max PT 2023.12 | Saffire Pro 40 | Win10 latest, HP Z440 64GB |
#18
|
|||
|
|||
Re: 24 or 32 bit float
Quote:
And if the pre-amp or converter (=24bit) clips any recording should be equally distorted, no matter if the software stores the converter's output as 32-float or 24bit. Or am I missing something here? Cheers, Jan
__________________
2010 Dolphin Award for Production / Engineering AVID Certified Instructor |
#19
|
|||
|
|||
Re: 24 or 32 bit float
You can only restore a 32 bit file to an undistorted waveform with clip gain. It is not possible to do this with a 24 bit file. Clip gain can make the 24 bit file lower in level but the waveform will still be clipped if it was clipped in the first place.
|
#20
|
|||
|
|||
Re: 24 or 32 bit float
Try it.
__________________
David J. Finnamore PT 2023.12 Ultimate | Clarett+ 8Pre | macOS 13.6.3 on a MacBook Pro M1 Max PT 2023.12 | Saffire Pro 40 | Win10 latest, HP Z440 64GB |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
32 Bit Float | boogiemotel | macOS | 76 | 01-20-2013 09:28 PM |
32 Bit Float | boogiemotel | Pro Tools 10 | 28 | 01-09-2013 10:22 AM |
new recorders run 24 bit vs 32 bit float | rockguitarist1255 | Pro Tools 10 | 1 | 01-07-2012 10:06 PM |
32 bit Float | Logichead | Pro Tools 10 | 0 | 10-22-2011 11:08 AM |
Help! What is a 32-bit Float Mix ????? | Rhapsody | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 6 | 02-27-2010 09:46 AM |