I seem to be getting a clipped section in my exported song, and I'm not sure why... The song is here: <http://www.aggroculture.com/audiotrocities/doggiebox/ skullhunter.dbsong>, I'm using the latest build (1C10), ns kit version 7, and I haven't tweaked anything in The Dog (that I know of ;-) A screenshot of the clipped section is here: <http://www.aggroculture.com/audiotrocities/doggiebox/clipped.pdf> And the full AIFF file is here: <http://www.aggroculture.com/audiotrocities/doggiebox/skullhunter.aiff> It's in the second hit in the "main" section. Thanks! ::Glenn --- I'm listening to "Sympathy For The Devil" by The Electric Hellfire Club from Empathy For The Devil (Disc 1) <http://www.gracenote.com/music/search.html? q=The+Electric+Hellfire+Club+Empathy+For+The+Devil&f=artist&f=disc&x=0&y =0>
Slide your master volume slider down to about 75 percent. Re-export the file. I went through the same thing and this fixed it. On Aug 29, 2004, at 10:38 PM, Glenn Sugden wrote:
I seem to be getting a clipped section in my exported song, and I'm not sure why...
The song is here: <http://www.aggroculture.com/audiotrocities/doggiebox/ skullhunter.dbsong>, I'm using the latest build (1C10), ns kit version 7, and I haven't tweaked anything in The Dog (that I know of ;-)
A screenshot of the clipped section is here: <http://www.aggroculture.com/audiotrocities/doggiebox/clipped.pdf>
And the full AIFF file is here: <http://www.aggroculture.com/audiotrocities/doggiebox/ skullhunter.aiff>
It's in the second hit in the "main" section.
Thanks!
::Glenn
--- I'm listening to "Sympathy For The Devil" by The Electric Hellfire Club from Empathy For The Devil (Disc 1) <http://www.gracenote.com/music/search.html? q=The+Electric+Hellfire+Club+Empathy+For+The+Devil&f=artist&f=disc&x=0& y=0>
----------------------------------------------------------------------- -- Zygoat Doggiebox discussion list - <http://www.doggiebox.com> To unsubscribe, view archives or change your options: <http://lists.zygoat.ca/mailman/listinfo/doggiebox>
On Aug 30, 2004, at 5:20 AM, Mike Carlyle wrote:
Slide your master volume slider down to about 75 percent. Re-export the file. I went through the same thing and this fixed it.
Understood, but would be a *lot* nicer to have a normalize/clip-check: Pseudo-code (off the top o' me head): set max to 0 for every sample point currently being mixed add all of the samples together in the sample point (e.g. drum1 + cymbal2) store resultant as an unsigned (absolute value) long (>16-bit) integer if resultant is greater than max set max to resultant If max greater than 65535 (16-bits) blare loud horn exclaiming "clipping occurred! clipping occurred!" ask "do you want to normalize your song you sound engineering n00bie?" if yes continue else if no say "then dammit Janet, turn down the master volume slider!" break ..and if you wanted to normalize: for every sample point currently being mixed add all of the samples together in the sample point store resultant as an unsigned long integer (normalized) sample point = resultant * 65535 / max ::Glenn --- I'm listening to "Critical Mass" by Numb from Blood Meridian <http://www.gracenote.com/music/search.html? q=Numb+Blood+Meridian&f=artist&f=disc&x=0&y=0>
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
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>
participants (3)
-
Ben Kennedy -
Glenn Sugden -
Mike Carlyle