how to [gate] a matrix?
i´d like to replace some of my older jitter "gates" abstractions with my regular messages gates abstractions, which means i am packing the incoming matrix with e.g. [prepend video] and then use different objects such as [gate] or [route] to switch output or to switch between different inputs to the abstraction, as opposed to utilizing jit.crossfade or jit.alphablend.
in many situations now unwanted frames do appear when i modulate such "gates".
example: say i am using [switch] and change its argument (by sending 1 to switch so that a different source is been passed through). in about 50% of the cases there is one unwanted frame now on the output, and that even in a situation where the origin of the frames of both matrixes is the same metro ...
i believe that my problem is caused mostly in my mind, because i just cant stop thinking in right-to-left order when working with video. but isnt there a general trick how to solve this?
-110
difficult to help without patch, but right to left order should apply too
ie, the last received matrix will be the one displayed
How about [selector] within jit.gen? Very simple to implement. It was designed as a switch object for matrices. Are you able to run Gen on your machine?
jit.gen is a good idea which i will keep in my mind, but of course i´d prefer a solution which would work on older systems, too. first step is to reuse my existing max gates.
will post a simplified example patch tomorrow.
Can you post an example that generates those unwanted frames?
i dont have max here now.
basically i do stuff like this:
metro 200
jit.qt.movie 400 200 jit.qt.movie 400 200 (use still images for this test)
prepend video prepend video
gate gate (controlled by a toggle, one of them with reversed order of 0 and 1)
route video
jit.pwindow
for me this flickers, and about every other time i press the toggle, one wrong (or black/emtpy) frame appears. this remains like it is even when you put a [del 0] behind the toggle and turn overdrive on.
i must be not seeing something very obvious.
no problems here... at least not with this:
what if you use two different "route video" and then use a op+ or something?
@metamax: i can no longer reproduce the problem. no idea what went wrong.
Sounds like you have no idea what went right. Not such a bad place to be. :)