https://www.kvraudio.com/forum/viewtopic.php?f=33&t=543334&p=7729328#p7729328
___
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users
Hi Bart,
I am not sure I understand you, but I'll try to answer anyway ;)
Please correct me.
On 04/16, Bart Brouns wrote:
>
> Somehow the initial value of `u` got lost in the last commit to this
> function:
> https://github.com/grame-cncm/faustlibraries/commit/ba34ca657a8c98efc804061c5b2e1d4f7e6
Hi Oleg,
Thanks for your watchful eye!
Somehow the initial value of `u` got lost in the last commit to
this function:
https://github.com/grame-cncm/faustlibraries/commit/ba34ca657a8c98efc804061c5b2e1d4f7e6bc6ff.
The oscillator doesn't seem to work without it.
The other changes where to bri
About memory access, my current understanding is that external memory access is
much slower compared to internal one. So there is no perfect setup AFAICS.
Stéphane
> Le 16 avr. 2020 à 16:01, Gary Worsham a écrit :
>
> I just found a configuration option (under "make menuconfig") that allows
True, but for my own applications I'm not so interested in reverbs and am
more interested in a few delay lines, as discrete echoes. So in that
regard, having 2.5 seconds to use rather than 150 msec makes this a lot
more usable. Ultimately I think I would have one of these boards as some
sort of u
I just found a configuration option (under "make menuconfig") that allows
you to set the external SPI RAM to be usable by malloc(). At first glance
this allows configuration of delays up to about 2.5 seconds using
ef.echo(), whereas previously I could only get about 150 msec. However,
3.5 second
Sorry to keep rattling on about this...
#1 I realize there is no "interpolated write" possibility.
#2 This isn't much different than a tape delay with wow/flutter in that
there is a physical medium used for temporary storage whose speed at both
write and read locations is subject to relatively sm
Bart,
could you explain the commit 4fb8849b833629 ("Fixup quadosc") ?
It looks absolutely wrong.
- It removes the 1st output (cosine), why ??
- It makes the 2nd output less precise
- It makes the generated C++ code worse.
Oleg.
___