Re: [Faudiostream-users] GUI and rates

2020-02-29 Thread Alejandro Olarte
Thank you for the information. I will keep an eye on the updates about this. PD: I am enjoying a lot the web IDE well done! Alejandro > On 29 Feb 2020, at 16.20, Stéphane Letz wrote: > > OK I see. > > Yes, even if driven by a AR signal in SuperCollider, the controllers > (sliders..etc..)

Re: [Faudiostream-users] GUI and rates

2020-02-29 Thread Stéphane Letz
OK I see. Yes, even if driven by a AR signal in SuperCollider, the controllers (sliders..etc..) will only change at KR, so depending of the underlying buffer-size. This is something that you cannot do simply with the current model and that we want to improve. Stephane > Le 29 févr. 2020 à

Re: [Faudiostream-users] GUI and rates

2020-02-29 Thread Alejandro Olarte
Thank you Stéphane for the reply I will try to illustrate the question. If I export the code in the first email as Example1 for a supercollider uGen it can be modulated with another uGen either running at the audio rate or at the control rate. However with an audio rate uGen it clearly sounds

Re: [Faudiostream-users] GUI and rates

2020-02-29 Thread Stéphane Letz
I’m not sure to understand, but: - ma.SR is the audio frequency that will be given by the audio underlying layer at runtime, and so accessible in the DSP code. So when exporting for SuperCollider uGen, the actual ma.SR value will be given by the SuperCollider host at runtime. - DSP code is

[Faudiostream-users] GUI and rates

2020-02-29 Thread Alejandro Olarte
Hi, Is there a way to specify in the rate of the parameters when exporting from the web IDE? For example: in the example below when exporting to SuperCollider uGen what is the rate of frequency? is it possible to set it to audio rate or control rate? import("stdfaust.lib"); decimalpart(x) =