Re: [PD] variable outlets in dsp object

Thanks. You do what I'm doing: reassigning the samples out pointers that are stored in the class structure to a local variable in the perform loop. This seems to work better than accessing the stored pointers (on windoze anyway). On 6/8/17 12:36 PM, Pierre Guillot wrote: I don't fully

Re: [PD] variable outlets in dsp object

Or even simpler this code: https://github.com/pierreguillot/pd.dummies/blob/master/src/leeloo_tilde.c 2017-06-08 12:36 GMT+02:00 Pierre Guillot : > I don't fully understand what you do in your code without the rest of it. > I think the simplest approach is to keep all

Re: [PD] variable outlets in dsp object

I don't fully understand what you do in your code without the rest of it. I think the simplest approach is to keep all the DSP information you need in your object's structure(number of samples, pointers to the inlets, pointers to the outlets, etc.) and to call the dsp routine with only your

Re: [PD] variable outlets in dsp object

Now I realize that everything I posted in the last post makes absolutely no sense at all. Something else is causing the crashes. Damn! On 6/8/17 10:51 AM, David Medine wrote: I am writing a DSP extern that can have a any number of outlets depending on the creation arguments (like [fexpr~],

[PD] variable outlets in dsp object

I am writing a DSP extern that can have a any number of outlets depending on the creation arguments (like [fexpr~], e.g.). In order to interact with the outlets in the XXX_tilde_perform loop, I made a member of my t_XXX_tilde data structure thus: t_sample **lcl_outs; Then, when I know how