jit.plume does will not pass through gate?
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
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:
-- Pasted Max Patch, click to expand. --Copy all of the following text. Then, in Max, select New From Clipboard.----------begin_max5_patcher---------- 839.3ocyXtsbZCCDF9Z3oP0SuLkwR1xG5c8AnOAcxjQfULJ0VhXKBzlIu6UG vTmD7IvlDlA7nEiz+94cWshmmOyYoXOszA7cvu.yl877YyLlzFlcX7Lmbx9U YjRys4rRjmS4RmaremjtWZrmHnk.tPB1IJ9M3dFm9E.3mhmn.o.HWSAErz0R .gm.JoTikbRJaU0DcufKKY+kpmLHZg6Ay7s4hsxLpzr5UV2TPKUhfHYB9cEz URqGfhiT+P.FZt3d3Cvs0VBNI2rDN+nfQxpVbVhwlX4CeyCUYbCQtZMimVeA 70yoOzL0dtw5Kn5KgRtLdkZgZauLet9iatP7poZoEqmEw5muCaw2gdFmGgv5 KAQiuu+.StXyNFOQry4jNC5fUqI4e1PsRyw4F06iBognCXXf4wlevIiNpwAT babvFDfvtVB.WDndEhtA.wvEH7mOdT2y7ayyrQ2d3o1wjhzzL5o8IXS9DSkU bRWxqEWJz3RPWbUz5XGylSKKIoz2kutJiRJFTlZiNtyvJfAi6lGgFd3EZFD0 DOPmAO3zcJQ7NbHAKGGXrjvSGJPB6FHGRl8G+.jF.RJQR+XBOB5lFd1825fF iX3goRW117ggjFK+olt6xIxB19WWHre.B2VIRydGHaC.X73CnlpmTPIIfDV4 ZZ4hbwSeLgNst4QjgF9FxDGO9UVZjLpLIvWgeLDwq0FEf+mH1lNFWhbelPMG iSJiZtHRc1x4TfE0MELJBfmfcfUSvR5o2pEt.GqNLP3vPgtQiyDDs0+b.Zh4 PykVeTpqYvn.OjqZSN2OCUYc6rJanMvA5c0X0i4TYg.LP.Ml8pD2IUrkSBlf sdF0txi5zQrYBCombyc3joNC7a9GKLqg19q8tRw1hUUBsZqcv+WnDZojwMGS r1MoOhTsaZMKIgxqeT5bVxFgxuOHBvsmj08VSt8PSuQ3Stl5EmhGllP3EXcK 1H8Enm2wQWpXim..FYkmqscO7wAWCvp6PG.GLXssqq2t8cif1rr3niCtP+Pe l694GWwf1v9no3qqlB5ilButZxuOZxcXZBF6qisBpkuDLBoKn9HUuqK97lB7 oNw83iundnzqa9P7DvtK84IrmTBdlRRM3k4+Cf7sRWI -----------end_max5_patcher-----------
Ah, thank you Ben, simply getting rid of the clear message fixed it up!
Forums > MaxMSP