Mixing 32,24-bit?
-
- KVRAF
- 2028 posts since 18 Mar, 2004 from New York, N.Y.
My projects are set to 24 bit by default. When rendering individual tracks, I see I have the option to create a 32-bit file. Is there any advantage to doing this in a 24-bit project?
-
- KVRAF
- 9600 posts since 17 Sep, 2002 from Gothenburg Sweden
You'll get slightly reduced CPU usage as it always converts everything to 32 bit float. And the downside is of course a bigger filesize.
-
- KVRAF
- 6478 posts since 16 Dec, 2002
And also there won't be any conversion related bit truncation of the files in case you process them. Any VST input and output is always 32bit. Good to keep the files at that too.
-
- KVRAF
- Topic Starter
- 2028 posts since 18 Mar, 2004 from New York, N.Y.
So just to make sure I understand this correctly, if I work at 32-bit, it would actually reduce CPU usage? I always thought it would be the opposite!
Hard disk space is so much cheaper than CPU, I would gladly start doing everything at 32 if that's the case...
Hard disk space is so much cheaper than CPU, I would gladly start doing everything at 32 if that's the case...
-
- KVRAF
- 2285 posts since 20 Dec, 2002 from The Benighted States of Trumpistan
As Kingston wrote, "Any VST input and output is always 32bit." Input is converted to 32-bit before processing, and the output is 32-bit. You're already working in 32-bit; going from 32-bit to 24-bit involves extra processing, and it isn't just a matter of knocking off the last 8 bits. If I understand correctly, the 32-bit format in VST is floating-point, and all 24-bit files are integer (but it's extra processing either way).My spies inform me that jplanet wrote:So just to make sure I understand this correctly, if I work at 32-bit, it would actually reduce CPU usage? I always thought it would be the opposite!
Still, I doubt it'd make a perceptible difference, especially when using VSTis; it'd be an interesting study, anyway.
Wait... loot _then_ burn? D'oh!