![save a montage as a 24 bit wave file in wavelab 6 save a montage as a 24 bit wave file in wavelab 6](https://usermanual.wiki/Steinberg/wavelable8open.3418149861/asset-d.png)
This helps me feel I can use the POW-r Dither feature in Sonar 4 with confidence. I hope this information was of some help.
![save a montage as a 24 bit wave file in wavelab 6 save a montage as a 24 bit wave file in wavelab 6](https://i.ytimg.com/vi/mRLlvnirwA8/maxresdefault.jpg)
#Save a montage as a 24 bit wave file in wavelab 6 pro#
In Sonar 4 we use 3 different Pow-r algorithms which are used throughout the industry by many pro audio companies, if one of the Pow-r algorithms are selected in Sonar 4 when exporting audio the Pow-r will apply dithering in the same order, first sample rate conversion on floating point data, and then dither to the destination bit depth just before writing to the target file. When you have apply dithering enabled in Sonar 3 and you export audio to 44.1/16bit, at export time we first do sample rate conversion on floating point data, and then dither to the destination bit depth just before writing to the target file. I had to get a developer involved and wait a day for an email response to my phone call to technical support, but here is the official response:įrom: Michael Nixon On Behalf Of PhoneSupport AT I wanted an official response from Cakewalk on when their internal dither is applied during the export process. Now that POW-r dither is on the scene with Sonar 4, and because it's not documented anywhere. like Sound Forge or WaveLab, I always perform SRC during the export of the mastered stereo file to a 44.1/24 file and apply 16 bit dither in CD Architect just prior to burning the CD. Since I don't use Sonar's internal dither, and I don't use another application for mastering. When performing word length reduction for 16 bit CD projects, it is important to perform sample rate conversion prior to dithering to 16 bit. I sometimes master 24 bit depth projects in Sonar at sample rates greater than 44.1khz.