<div dir="ltr">Are the raw waves likely to be added to in the future?<div><br></div><div>I think having a separate raw file file resolver makes a lot of sense. Following the single responsibility principle resolving wave files should only be the responsibility of the wave file resolver. This should be interface/virtual base class based and injected as a dependency wherever needed.</div>
<div><br></div><div>Then we could have a static float array wave file resolver, an iOS wave file resolver and a file based wave file resolver. You could even have a wave file resolver that downloads the raw files as it needs them from some network location.</div>
<div><br></div><div>Resolving wav files should not be a function of a synthesis engine.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Mar 13, 2014 at 5:11 AM, Perry R 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">For interest, ChucK has all rawwaves it uses compiled<br>
into static float arrays.<br>
<div class="im HOEnZb"><br>
PRC<br>
<br>
----- Original Message -----<br>
</div><div class="im HOEnZb">I wonder if there really is any use for filesystem-based rawwaves.<br>
Maybe the rawwaves can be converted at build time into a C array.<br>
<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Stk mailing list<br>
<a href="mailto:Stk@ccrma.stanford.edu">Stk@ccrma.stanford.edu</a><br>
<a href="http://ccrma-mail.stanford.edu/mailman/listinfo/stk" target="_blank">http://ccrma-mail.stanford.edu/mailman/listinfo/stk</a><br>
</div></div></blockquote></div><br></div>