I need to dither from 24 bit 88.2 Khz down to 16 bit 44.1 Khz. I would like to use iZotope's MBIT dither as, for the sort of music on this album, I like it better than any of the POW-r dithers. However the only way I have of applying this dither is in an offline stand alone application (RX3). However, if I dither to 16-44.1 and then bring the files into Logic (actually I'm using Waveburner for this but it applies equally to Logic) and top and tail or adjust the level of a track (when laying out the CD), presumably these files will be re-rendered when I bounce (to CD or PPD image). Processing and re-rendering the 16-44.1 files will result in lower quality (due to alaising) than if I'd done the top and tail and levels with the original 24-88.2 files. Am I correct? One option that occurred to me was to add the MBIT dither but keep the files at 24-88.2 and then bring the into Waveburner (Logic). Then I can top and tail and adjust levels at 24 bit which would be much better in terms of processing quality than 16 bit. My thought is that since the dither noise is in the 24 bit files, when I bounce to 16-44.1 the dither would still work its magic. But am I correct in this thinking? I'm presuming this because limiters from Waves and PSP allow you to add dither in the plugin. So in this case it seems that the dither noise is added to the signal before bouncing (when truncation occurs). On the other hand, these same plugins allow you to select a bit rate. This I've always found confusing, because presumably they don't do the truncation themselves, Logic does it when you select the bit rate in the bounce dialog. Or do they do the truncation and somehow magically tell Logic not to try and do it again? I've always found this last part a mystery. Thanks for any help someone more knowledgeable than me can offer.