I actually care about this topic, so I spent some time pouring through that thread.
I'm sure everything those guys said had some merit and value, but I have no idea what 99% of it means. All I wanna' know is, how do I not kill the highs, right? I was going to post in that forum to address the comments about "not hearing" the difference, but I think it would have been a waste of time. It's obvious to me that I've got some setting enabled that shouldn't be, but all the discussions about
One thing I am absolutely certain about, though...is that if you take a 16bit file and hit "mixdown" with no other variables, then it changes it...
HERE'S WHAT I THINK - I understand that when you do this, what CEP is doing is actually converting the 16bit file to a 32bit file for internal processing, then BACK to a 16bit file (this is where the dithering happens). So theoretically, if this is right, then the only way to avoid it would be to record in 32 bit, do premixes in 32 bit, and mixdown to 32 bit. That's the only way CEP won't be dithering and re-dithering (whatever the fuck that is) numerous times...it'll do it once, on the final mixdown to 16bit.
I'm frequently wrong about these things, though. Groucho, you started that thread, and you at least typed near the end like you understood what was going on. AM I RIGHT???
For the record, I typically DON'T have all the 32bit boxes checked, b/c of hard drive space limitations. But I frequently have as many as 6 drum tracks open that I've gotten via CD (16bit), so I figure why convert it to a higher bitrate?? Well, the reason would seem to be because CEP does it anyway (transparently) and then BACK to 16 bit, so there's no telling how much "dithering" noise I've been introducing into the process.
FROM THE SYNT FORUM:
Basically, it doesn't matter how you go about doing this, whether you use multitrack or edit view, if you have two instances of the same information in two separate files, they will always differ by the uncertainty of the last bit, because of the fact that regardless of the supposed integer format of the files, internally they are still both converted to a FP format. The noise you get by doing this via the multitrack view is no different from the noise you get by adding them in edit view. The noise is inherent in the file saving process. If you didn't dither, then you'd end up with a file that may ultimately rsolve to a flat line, but which would have all of the problems associated with an undithered 16-bit file.
Stuff like that helps me none. I'm stoooopid. Can anybody tell me if I should have the options set to "open all files in 32 bit" and all the other 32bit options enabled to avoid this?
thanks,
chris