Open navid opened 7 years ago
Hi Navid!
In my experience, multigraph objects have never been very stable… I’m not sure that helps, but at least now you know you’re not alone ;-)
lol. That doesn't necessary help but ok at least me not alone!
Basically waveshaper= and filter= seem to crash easily when the number of channels are changed dynamically. But gain= is pretty stable for example. So could this be a pretty specific bug? I don't know but I like to use jamoma in concerts a lot and I love everything that multigraph is all about, freeing y from using scripting, etc to get adaptive multichannel patches.
nav
On Wed, Mar 22, 2017 at 6:47 AM, Pascal Baltazar notifications@github.com wrote:
Hi Navid!
In my experience, multigraph objects have never been very stable… I’m not sure that helps, but at least now you know you’re not alone ;-)
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jamoma/JamomaMax/issues/1019#issuecomment-288361771, or mute the thread https://github.com/notifications/unsubscribe-auth/AAI55dYG1JjS57qdUyJqFU70mYSIbbVcks5roPxFgaJpZM4MkogM .
--
Hi,
I am experiencing crashes caused by multigraph signal processors such as j.filter= and j.waveshaper= whenever a change is made to the number of incoming channels (within the multigraph cable).
For example try: //// in j.waveshaper='s help patch change the number of channels in j.pack= or //// in j.filter= try a similar test by changing the number of channels to be filtered. Also j.filter= seems to be generally buggy and crashy.
nav