<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 19 February 2015 at 18:59, Perry Cook <span dir="ltr"><<a href="mailto:prc@cs.princeton.edu" target="_blank">prc@cs.princeton.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Ack! This is a common problem, and I thought I had caught all of<br>
the clipping/distortion cases on Windows/Linux with our last<br>
passes on checking the source code. I'll check it all again and<br>
put it in our Errata file for future ChucK/Mini releases, and future<br>
printings of the book.<br></blockquote><div><br></div><div>Perry, now that you mention the OS's I'd like to share a thought. I wanted to postpone debating OS audio infrastructure because debates on OS features tends to lead to debates on OS preferences and the next step is likely to be total war and so I thought I'd try to figure out what was going on on my own. ;-)</div><div><br></div><div>Am I correct in understanding that you are saying the files could have been made on OSX with the system audio gain set to -say- 0.5? Then ChucK's output could reach peaks of -say-1.5 , it's get attunated and be at .75 when hitting the DAC; perfectly fine. In this case the audio reaching such amplitudes at ChucK's output might go unnoticed by the file's author. Under OS's with a audio infrastructure expressed in int's a output of 1.5 at the ChucK dac would clip at 1 at hitting the OS's audio rating and the final output (assuming identical system volume) would end up at a 0.5 amplitude while being heavily clipped. Is that correct?</div><div><br></div><div>Yours,</div><div>Kas.</div></div></div></div>