On 30 8 2004 at 5:49 pm -0400, Glenn Sugden wrote:
Understood, but would be a *lot* nicer to have a normalize/clip-check:
True but as I indicated in my posting, how to do this in an effective, pleasant manner is the design challenge. As you're aware it is necessary to fully render the song before knowing what the max is; interrupting the user and then prolonging the process two-fold seems a bit irksome but perhaps there is no better way around it. One solution I have had in mind is to run a render thread in the background which would then be able to visually indicate (e.g. red back- fill) points where clipping will occur. Alternatively, it was already suggested awhile ago to at least make this part of real-time playback so you'd be able to tell while working where the problem areas were.
If max greater than 65535 (16-bits)
Everything is mixed internally as 32-bit float, FWIW. This reminds me, note to RevRat and everyone else putting together high quality kits... don't assume that Doggiebox will forever be limited to 44.1khz. :) -b -- Ben Kennedy, chief magician zygoat creative technical services 613-228-3392 | 1-866-466-4628 http://www.zygoat.ca