On Wed, May 21, 2014 at 4:25 PM, yann orlarey <orla...@gmail.com> wrote:
> rdtable has three input signals. The first one must be contant and known at
> compile time, it define the size of the table, The second input signal
> defines the content of the table and must be also known at compile time. And
> the third signal is the read index and it must generate values in the limits
> of the table.
>
> In your first example the compiler will compute the first 2048 samples of
> the second signal and store in the table. But in your second example the
> signal used to fill the table is not known at compile time (because it
> depends of the audio input). This is why it is rejected.
Ok, _now_ I get it, thanks.
I will express my understanding for future confused people ;)
The reason it appeared to me that there was a 4th input was that the
input piped into rdtable through the ":" operator was actually
becoming an input to "func". I didn't realize that "func" must
defined without any inputs, I'd assumed it was a single-input function
with an implied index used during fill().
That is, if you want an rdtable containing function f(x), you must
express it with x as a compile-time defined counter, eg.:
process = ind : rdtable(N, f(x)) with {
x = int(+(1) ~ %(N) : -(1));
}
where "ind" is whatever the run-time read index function should be,
and N and f() are defined elsewhere.
Steve
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Faudiostream-devel mailing list
Faudiostream-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-devel
