Seems like most use 24/48. I'll likely go to 48 khz instead of 96khz, as I haven't heard any argument against.
I think I'll stay with Audacity's 32 bit depth for post. From the manual:
"Audacity uses "float" format for 32-bit recording instead of fixed integer format as normalized floating point values are quicker and easier to process on computers than fixed integer values and allow greater dynamic range to be retained even after editing. This is because intermediate signals during audio processing can have very variable values. If they all get truncated to a fixed integer format, you can't boost them back up to full scale without losing resolution (i.e. without the data becoming less representative of the original than it was before). With floating point, rounding errors during intermediate processing are negligible.
The (theoretically audible) advantage of this is that 32-bit floating point format retains the original noise floor, and does not add noise. For example, with fixed integer data, applying a compressor effect to lower the peaks by 9 dB and separately amplifying back up would cost 9 dB (or more than 2 bits) of signal to noise ratio (SNR). If done with floating point data, the SNR of the peaks remains as good as before (except that the quiet passages are 9 dB louder and so 9 dB noisier due to the noise they had in the first place).
In many cases you will be exporting to a 16-bit format (for example if you are burning to a standard audio CD, that format is by definition 16-bit 44100 Hz). The advantage of using 32-bit float to work with holds even if you have to export to a 16-bit format. Using Dither on the Quality tab of Audacity Preferences will improve the sound quality of the exported file so there are only minimal (probably non-audible) effects of downsampling from 32-bit to 16-bit."
Note the use of 'theoretically' and 'probably'.