<div dir="ltr">Eric Hedekar;<span dir="ltr"></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr">
<br><div class="gmail_quote"><div>I would actually think it might truncate either up or down depending on the extra place value (but I don't know enough about how floating point truncation works to tell you). Does this behavior change from language to language - or architecture to architecture?<br>
</div></div></div></blockquote><div><br>I'd imagine that it does. In audio, BTW, if we're going to be rounding (and we are) I could imagine that rounding towards 0 could avoid exploding feedback loops. Rounding means noise and we wouldn't want noise to build up.<br>
<br>I'm really just speculating here but it sounds like a nice idea to me right now....<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr"><div class="gmail_quote"><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr"><div class="gmail_quote">
<div>Another thing is that I'm not sure at what point the .phase() is actually calculated. When you call to .last() you get the sample at the last UGen tick so that value is at that point on average .5::samp out of date. I'm not sure whether .phase() is also calculated at that moment or whether it can be calculated in between ticks. This could be another factor.<br>
</div></div></div></blockquote></div><div><br>well this one is easy to figure out:<br></div></div></div></blockquote><div><br>Ok... so that would mean this factor would make the zero crossing appear sooner then we'd expect it as we're calculating it based on "out of date" data. This is looking more and more tricky with various factors pulling the outcome in both directions, apparently.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr">I'm tempted to guess that it's not possible unless we could calculate an audio sample before it is reached i.e. s.next() but I don't think Chuck has that capability (yet). But please prove me wrong!<br>
</div></blockquote><div><br>I'm going to look into this (I do think it should be possible, that next sample is based on factors we can know) but I also have a sound-design gig that requires quite a bit of material and that needs to be done by Monday... <br>
</div></div><br>Yours,<br>Kas.<br></div>