yeah it makes sense. > We plan to improve that as some point, with a new mechanism to output the > value each time it changes.
That’s a good news! OK I’ll try to organize my codes somehow….somehow! 松浦知也 Tomoya Matsuura +818035934157 [email protected] <mailto:[email protected]> [email protected] <mailto:[email protected]> https://matsuuratomoya.com <https://matsuuratomoya.com/> > On Apr 10, 2019, at 3:49 PM, Stéphane Letz <[email protected]> wrote: > > Right now h/vbargraph values are generated once per audio block, even if they > change at a higher rate. We plan to improve that as some point, with a new > mechanism to output the value each time it changes. > > In the meantime, you’ll have to restructure you code to possible generate > meaningful value at audio rate, and handle the associated audio output > buffers in the appropriate way. Would il make sense ? > > Stéphane > > >> Le 10 avr. 2019 à 03:03, 松浦知也 <[email protected]> a écrit : >> >> Hi, >> >> I’m trying to make a compressor plugin with JUCE for GUI and faust for dsp >> inside JUCE. >> >> I want to give an loudness & reduction history graph on GUI like fabfilter’s >> compressor, however, now its refresh rate depends on a size of audio buffer >> because faust’s h/vbargraph is a scalar parameter. >> >> Is there any nice way to pick up a raw intermediate signal in dsp? Maybe >> should I split dsp code into a section of loudness measurement and a gain >> reduction? >> >> Thanks. >> >> 松浦知也 Tomoya Matsuura >> [email protected] >> [email protected] >> https://matsuuratomoya.com >> >> >> >> >> _______________________________________________ >> Faudiostream-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/faudiostream-users >
_______________________________________________ Faudiostream-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/faudiostream-users
