[Stk] iOS static library

[Aran Mulholland]

Are the raw waves likely to be added to in the future?

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.

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.

Resolving wav files should not be a function of a synthesis engine.


On Thu, Mar 13, 2014 at 5:11 AM, Perry R Cook <prc at cs.princeton.edu> wrote:

> For interest, ChucK has all rawwaves it uses compiled
> into static float arrays.
>
> PRC
>
> ----- Original Message -----
> I wonder if there really is any use for filesystem-based rawwaves.
> Maybe the rawwaves can be converted at build time into a C array.
>
> _______________________________________________
> Stk mailing list
> Stk at ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/stk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ccrma-mail.stanford.edu/pipermail/stk/attachments/20140313/26b8edf7/attachment.html