>
> I've got another question regarding tables, hopefully not as silly as
>> the last one ->
>>
>> When creating a table in Faust it produces C++ code with a static global
>> variable to hold the data.
>>
>> `static float ftbl0mydspSIG0[65537];`
>>
>> (from example `generator/osci.dsp`, using Faust
that would work for us.
We have a program size limit of 64k, but 1M heap available, so heap
allocation is really important for us.
Martin
On 08/06/17 13:06, Stéphane Letz wrote:
>> Le 8 juin 2017 à 13:39, Kjetil Matheussen a écrit
>> :
>>
>>
>>
>> On Thu, Jun 8, 2017 at 1:14 PM, Stéphane Let
> Le 8 juin 2017 à 13:39, Kjetil Matheussen a écrit :
>
>
>
> On Thu, Jun 8, 2017 at 1:14 PM, Stéphane Letz wrote:
> The reason is that we want to share a unique table between all instances of
> the class. But… it appears that:
>
> - even if the table is shared, the classInit code is actual
On Thu, Jun 8, 2017 at 1:14 PM, Stéphane Letz wrote:
> The reason is that we want to share a unique table between all instances
> of the class. But… it appears that:
>
> - even if the table is shared, the classInit code is actually called each
> time in the instance::init(SR) method, which is rat
On Thu, Jun 8, 2017 at 12:31 PM, Martin Klang wrote:
> I've got another question regarding tables, hopefully not as silly as
> the last one ->
>
> When creating a table in Faust it produces C++ code with a static global
> variable to hold the data.
>
> `static float ftbl0mydspSIG0[65537];`
>
> (f
Would it be possible to generate a class that contains all tables (and
their initialisers) and pass a reference to the instance::init() method?
Then it is up to the container to manage the lifecycle and allocation of
shared data.
Martin
On 08/06/17 12:14, Stéphane Letz wrote:
> The reason is
The reason is that we want to share a unique table between all instances of the
class. But… it appears that:
- even if the table is shared, the classInit code is actually called each time
in the instance::init(SR) method, which is rather stupid…((-; and possibly
problematic.
- and the memory a
I've got another question regarding tables, hopefully not as silly as
the last one ->
When creating a table in Faust it produces C++ code with a static global
variable to hold the data.
`static float ftbl0mydspSIG0[65537];`
(from example `generator/osci.dsp`, using Faust 2.0.a73, owl.cpp
archite
Hi Martin,
Not sure what you're trying to achieve here, but the "standard" sine wave
oscillator in Faust (in oscillators.lib) is now based on a resonant filter
instead of a table, so if all you're trying to do is generate sine waves,
you shouldn't have this problem :).
Cheers,
Romain
On Tue, Ju
On 06/06/17 15:58, Stéphane Letz wrote:
> We are not generating any optimized version of math functions based on
> lookup tables
oh, okay!
I think I managed to confuse myself with different versions of patches
and Faust.
Looking at it again it seems clear that the tables I found are
expli
> Le 6 juin 2017 à 16:50, Martin Klang a écrit :
>
> Hello list, this is my first post - Martin in London here!
>
> I develop the OWL Pedal / Modular, an embedded platform which runs FAUST.
> We're trying to get up to speed with the latest version, but have hit a
> couple of snags.
>
> Somewhe
Hello list, this is my first post - Martin in London here!
I develop the OWL Pedal / Modular, an embedded platform which runs FAUST.
We're trying to get up to speed with the latest version, but have hit a
couple of snags.
Somewhere between v0.9.85 and 0.9.90 it seems that optimised versions of
ma
12 matches
Mail list logo
