You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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
The text was updated successfully, but these errors were encountered: