Do we need to change the client code?

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 1 Dec 2016, at 15:59, Stéphane Letz <l...@grame.fr> wrote:
> 
> Yes, all these new methods are also exported in LLVM dsp generated  (see the 
> lllvm-dsp.h header file)
> 
> Stéphane 
> 
>> Le 1 déc. 2016 à 16:55, Victor Lazzarini <victor.lazzar...@nuim.ie> a écrit :
>> 
>> Would that affect the Faust 2 JIT compiler and/or the API?
>> ========================
>> Prof. Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952 
>> 
>>> On 15 Sep 2016, at 09:53, Stéphane Letz <l...@grame.fr> wrote:
>>> 
>>> Hi all,
>>> 
>>> We have revisited the generated DSP « init »  code to allow a finer control 
>>> of the different init phases.
>>> 
>>> Up to now the Faust compiler generated the « init » method  has the 
>>> following shape :
>>> 
>>> virtual void init(int samplingFreq) {
>>>    classInit(samplingFreq);
>>>    instanceInit(samplingFreq);
>>> }
>>> 
>>> where « classInit » is initializing data (like readtables..) shared between 
>>> all instances of the DSP class,
>>> where « instanceInit » is initializing data for the given instance.
>>> 
>>> «  instanceInit » has been splitted in 3 new public methods:
>>> 
>>>    - instanceConstants(samplingFreq); that computes constants values, 
>>> tables… for the instance
>>> 
>>>    - instanceResetUserInterface(); that reset user interface elements to 
>>> their default values
>>> 
>>>    - instanceClear(); that clears internal delay lines..etc…
>>>    
>>> virtual void instanceInit(int samplingFreq) {
>>>    instanceConstants(samplingFreq);
>>>    instanceResetUserInterface();
>>>    instanceClear();
>>> }
>>> 
>>> This way architecture files may decide to use any of the new methods for 
>>> finer control of the DSP internal state during it's life cycle. The new 
>>> generated code does not change the current behavior of the init call, thus 
>>> does not break any architecture file. 
>>> 
>>> The new generated code model has been done in both master and faust2 
>>> branches.
>>> 
>>> Stéphane
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Faudiostream-users mailing list
>>> Faudiostream-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/faudiostream-users
>> 
> 

------------------------------------------------------------------------------
_______________________________________________
Faudiostream-users mailing list
Faudiostream-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Reply via email to