L4Z3RC47

Iv been working on a patch that uses several of the standard jitter objects for processing video in real-time and I have come across what I can only assume is a bug. in the patch attached to this post there is a section that controls the jit.plume object. It is essentially a cut and paste from the help file however as soon as the video signal reaches the next gate (the next object after the jit.plume) all video stops. I have tested this by putting a jit.pwindow between the jit.plume and the gate and the jit.pwindow displays the video out just fine. If I put the video out after the gate video from plume stops! (this is not because the gate is closed because video from other jit objects will pass through just fine.)

Iv been working on a patch that uses several of the standard jitter objects for processing video in real-time and I have come across what I can only assume is a bug. in the patch attached to this post there is a section that controls the jit.plume object. It is essentially a cut and paste from the help file however as soon as the video signal reaches the next gate (the next object after the jit.plume) all video stops. I have tested this by putting a jit.pwindow between the jit.plume and the gate and the jit.pwindow displays the video out just fine. If I put the video out after the gate video from plume stops! (this is not because the gate is closed because video from other jit objects will pass through just fine.)
Any ideas? let me know
Thanks!


jit-plume-does-will-not-pass-through-gate

This is an order of operations thing. The key is the 'clear' message you are sending to jit.plume that is triggered by the matrix output. I'm not sure what exactly you are trying to achieve by the 'clear' message, but maybe a trigger would help? Anyways, start there. A distillation of the issue:

This is an order of operations thing.  The key is the 'clear' message you are sending to jit.plume that is triggered by the matrix output.  I'm not sure what exactly you are trying to achieve by the 'clear' message, but maybe a trigger would help?  Anyways, start there.  A distillation of the issue:

Ah, thank you Ben, simply getting rid of the clear message fixed it up!

jit.plume does will not pass through gate?