John
Its a little disingenuous to add this when before I was talking only about sample rates.
I am definitely not being disingenuous, John - not intentionally, and I think not at all. I'm trying hard to understand the details of the sample-rate stuff, SRC, and dither.
I brought it up b/c I could see the higher frequencies in the analyst I was using.
Nika was nice enough to chime in. Frankly, I think I may still have misunderstood him. At one point I thought I understood him to say that at double rates to use Pow-r for internal bouncing, but re-reading I think I just misunderstood that. He clearly is talking about exporting the final bounce. And he does say to use POW-r.
I think the order of events would matter a lot.
Here's a guess at order of events...
- upsample to lowest common denominator for sample rates
- filter out frequencies above the new nyquist frequency - increasing bit depth to 64 float
- reduce sample rate (now safe to do because there is no information in the wave that can't be represented within the new sample rate)
- apply dither
- truncate bits from 64 to 24 (or other)
John
I don't know about dithering for sample rate reduction. I believe there is no artifacts due to truncation when changing the sample rate. I could be wrong though.
I think there can be aliasing if you change the sample frequency for audio that contains sound information above the new nyquist frequency. By this, I mean that if you have a 88.2 stereo wave with reverb tails that go above the human audible range say to 32kHz, if you down-sample without filtering out the content above 22.05 kHz you will get
aliasing in the audible range as the DA convertor tries to recreate the wave form from the samples.
John
Heck plugins upsample and downsample. Its called oversampling and I doubt dither is used for that. All high sample rates do is increase bandwidth.
I'm sure I don't know. It appears Nika thinks that
oversampling does justify dither. The linked Wikipedia article on Oversampling also mentions dither.
So, whether it's worth making adjustments to your dither settings in Sonar as you work your way through a project seems like a fair question. Personally, I rarely make changes and usually leave it on Pow-r 3. If I should change it to Rectangular or to None at various times, I need it spelled out. The only time I leave it at none is when exporting a 24 bit 44.1 recording at 24 bit 44.1. All other cases I leave it on.
It is clear in Nika's book that for internal bouncing, he recommends non-shaped dither like rectangular or triangular and for exporting Pow-r. For a second I thought he suggested Pow-r for internal bouncing when the sample rate was double or quad, but I don't think he actually said that... I think I just heard it. :-)
The Wikipedia article on
Sample Rate Conversion (SRC) gives the same reason for possibly using dither or noise shaping algs when doing SRC.
bitflipper
That's the first I've heard of dither being required for (or having anything to do with) SRC, but it's been quite awhile since I read Nika's book. If you can cite a page from the book, I'd like to read what he has to say about that.
Man, I just can't find it. I've been flipping and flipping through the pages. I'm sure I've quoted it in a Thread with John back in 2008 or so, but I can't find the thread and I can't find the quote now. You can see in this thread what Nika Aldrich says about it in an email to me, but I can't find the quote in the book. Sorry.
bitflipper
Of course, the question is moot in most cases, because downsampling during export is usually done in conjunction with wordlength reduction, which is where dither comes into the picture. That may be the source of confusion.
So, it's possible that every time Sonar uses the 64 bit audio engine it applies a anti-aliasing filter then dither then truncates to the required bit depth when bouncing to tracks, assuming you aren't using 64 bit as your render bit depth size. If it does apply dither, does it apply your default dither set in Preferences > Audio > Playback and Recording? I have no idea. It could just truncate, but I would think that could have bad aliasing issues into the audible ranges.
post edited by gswitz - 2014/01/08 00:26:10