> Le 19 avr. 2019 à 10:19, Hermann Meyer a écrit :
>
>
> Am 19.04.19 um 10:03 schrieb Kjetil Matheussen:
>> On Fri, Apr 19, 2019 at 9:41 AM Hermann Meyer wrote:
>>>
>>> Am 29.11.17 um 12:18 schrieb Stéphane Letz:
> I'm still on faust(0.9.90), but this reads very interesting. I'll check
>
On Fri, Apr 19, 2019 at 11:23 AM Kjetil Matheussen
wrote:
>
> The reason I noticed this was because in Debug mode I always run the
> -fsanitize=address, which sometimes increases CPU usage a lot, and the
> zita reverb often caused overruns. This stopped when not using -vec.
The difference in memo
On Fri, Apr 19, 2019 at 10:20 AM Hermann Meyer wrote:
>
>
> As well, no proper benchmark here, but, I just give zita_rev1 a shot
> here, and didn't see any spices in guitarix. zita rev in vector mode
> (32) use here ~0.8% DSP when switched on in guitarix.
>
guitarix probably don't use enough memo
Am 19.04.19 um 10:03 schrieb Kjetil Matheussen:
On Fri, Apr 19, 2019 at 9:41 AM Hermann Meyer wrote:
Am 29.11.17 um 12:18 schrieb Stéphane Letz:
I'm still on faust(0.9.90), but this reads very interesting. I'll check that
out as soon I've switched to the latest faust-git.
OK
Surly we can'
On Fri, Apr 19, 2019 at 9:41 AM Hermann Meyer wrote:
>
>
> Am 29.11.17 um 12:18 schrieb Stéphane Letz:
> >> I'm still on faust(0.9.90), but this reads very interesting. I'll check
> >> that out as soon I've switched to the latest faust-git.
> > OK
> >> Surly we can't use that in our dsp2cc script
Am 29.11.17 um 12:18 schrieb Stéphane Letz:
I'm still on faust(0.9.90), but this reads very interesting. I'll check that
out as soon I've switched to the latest faust-git.
OK
Surly we can't use that in our dsp2cc script (without implement it ;-) ) but
I'll check it out and find out if it cou
>
> I'm still on faust(0.9.90), but this reads very interesting. I'll check that
> out as soon I've switched to the latest faust-git.
OK
>
> Surly we can't use that in our dsp2cc script (without implement it ;-) ) but
> I'll check it out and find out if it could help to reduce the CPU usage e
Am 29.11.2017 um 11:43 schrieb Stéphane Letz:
Faust options been forwarded from the caller to faust. Usually the dsp2cc
script calls faust. and read the stdout from it.
The dsp script checks if a special option is given and act accordingly. For
example:
if self.options.vectorize:
>
> Faust options been forwarded from the caller to faust. Usually the dsp2cc
> script calls faust. and read the stdout from it.
> The dsp script checks if a special option is given and act accordingly. For
> example:
>
>if self.options.vectorize:
>s["compute"] = self.replac
Am 29.11.2017 um 10:46 schrieb Stéphane Letz:
Le 29 nov. 2017 à 10:04, Hermann Meyer a écrit :
Am 29.11.2017 um 09:27 schrieb Stéphane Letz:
Thanks Hermann.
Although we know the work done for the guitar project, we do not (in general…)
recommend hacking the generated C++ code. The reaso
> Le 29 nov. 2017 à 10:04, Hermann Meyer a écrit :
>
>
>
> Am 29.11.2017 um 09:27 schrieb Stéphane Letz:
>> Thanks Hermann.
>>
>> Although we know the work done for the guitar project, we do not (in
>> general…) recommend hacking the generated C++ code. The reason is that since
>> the comp
Am 29.11.2017 um 09:27 schrieb Stéphane Letz:
Thanks Hermann.
Although we know the work done for the guitar project, we do not (in general…)
recommend hacking the generated C++ code. The reason is that since the compiler
class output shape may change.., this method can be quite « fragile ».
Thanks Hermann.
Although we know the work done for the guitar project, we do not (in general…)
recommend hacking the generated C++ code. The reason is that since the compiler
class output shape may change.., this method can be quite « fragile ».
Our experience developing architecture files ove
Hi
In the guitarix project we using a python script with included templates
to parse the output of the faust compiler.
This allow us to replace the virtual keywords, in-lining some stuff, and
format the classes to the way we need in our project.
For reference here you'll find our dsp2cc sc
If the compiler knows about the most derived class, it doesn't need to
access the vtable to resolve the actual method call.
so when everything is known to the compiler at compile time, the
virtualness doesn't cost you anything.
that said a virtual method call is cheap when ammortized over a b
Several things:
- you can read the « Developing a new architecture file » section in the
documentation (faust-quick-reference.pdf)
- in case you can’t avoid that, the cost of virtual method call one per audio
audio (compute…) is probably negligible… Or do you plan to call the « compute
» m
Hi all,
A slightly more deep question this time..
In my use case I would like to embed faust code within my own node-based
modular DSP system. Therefore I would like to composite a faust-generated
dsp class within my own Node class. In that case I would use a templated
Node that would call MyFaus
17 matches
Mail list logo
