On Aug 30, 2004, at 2:57 PM, Ben Kennedy wrote:
True but as I indicated in my posting, how to do this in an effective, pleasant manner is the design challenge.
Boy, I hear *that*!
As you're aware it is necessary to fully render the song before knowing what the max is;
True, but even setting a "clipped" flag during the mixing...
interrupting the user and then prolonging the process
...and then reporting it after the fact would be the least-intrusive/fastest-way to handle it... ...although it would drive me batty to keep inching the master volume down and re-rendering. :-/
two-fold seems a bit irksome but perhaps there is no better way around it.
True, although having a "don't clip-check" flag while mixing shouldn't be too much overhead... Shark-time! ;-)
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.
Ooooo... I really like this idea (I'm a sucker for multithreading) - but if you've got the logic to check in the renderer anyway... ya' know?
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.
Wow... sounds like a big ol' bite to chew off... ::Glenn --- I'm listening to "Riot, Religion & Righteousness" by PIG from Genuine American Monster <http://www.gracenote.com/music/search.html? q=PIG+Genuine+American+Monster&f=artist&f=disc&x=0&y=0>