Re: Dithering??
Re: Dithering??
- Subject: Re: Dithering??
- From: Brian Willoughby <email@hidden>
- Date: Tue, 16 Sep 2008 12:55:47 -0700
I have two comments.
Dithering should only be done once, and only as the last step, and
that is why the CoreAudio SRC does not apply dithering. There's just
no way for the AudioConverter to know whether dithering would be
appropriate in each individual case.
Unfortunately, CoreAudio does not provide everything you might need
as an audio developer, and dithering is one of the things you will
have to develop or license yourself. MusicDSP.org might be a good
place to start for a variety of basic dithering algorithms. More
advanced dither such as POW-r are available as part of commercial
software, so you might need to look into automated DAW software with
scripting if you don't want to write or license code.
For QuickTime questions, there is a QT mailing list. My guess is
that it's doubtful they're applying dither in QuickTime.
Brian Willoughby
Sound Consulting
On Sep 16, 2008, at 12:42, Ryan Gilligan wrote:
I just got a demo of a new audio conversion program called Sound
Grinder, which apparently uses the built in Core Audio SRC to convert
sample rates. I will be converting 88.2 24 bit wav files down to 44.1
16 bit to burn redbook cd's. The developer of Sound Grinder believes
that the current Core Audio SRC would not do any dithering to
accomplish this. Is this true? Does the Core Audio API simply not
include any dithering?
Also, I'm not sure if this is beyond the realm of this particular
mailing list, but does the Quicktime SRC use dithering? Its pretty
much a necessity for what I need to do, which is batch converting
lots of these files, with no artifacts in the 16 bit files.
I hope someone can help! Thank you!
Ryan Gilligan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
References: | |
| >Dithering?? (From: Ryan Gilligan <email@hidden>) |