Forums > Jitter, moving the camera, and

Sep 01 2013 | 4:08 pm

So I’m sending drawing instructions to using a little sketchpad subpath I got from an old Jitter tutorial, then capturing the sketch to a texture to process with — and the chain of effects slabs ends in a

However, when I modulate the camera location in the drawing instructions, it shifts the whole rendering plane. It’s as if the is registering the camera instructions after the has captured the scene….or something.

Any idea what’s going on? How I can keep the camera movement from affecting the videoplane? I’d like to be able to move the camera around and not have it moved the videoplane. I’ve tried to copy the patch below, but I’m not sure it reproduces the problem. I’d definitely appreciate any thoughts. Thank you!


-- Pasted Max Patch, click to expand. --


Sep 01 2013 | 4:38 pm

I actually did figure this out.

But now I have a simpler question: the quality of the output is very low. When I render the sketchpad directly, it looks sharp. But when I capture the sketch to a texture and render the videoplane output, it looks extremely pixelated. Changing from dim 20 20 doesn’t help. Any tips?

Sep 02 2013 | 2:05 am

Checked your patch. I see no shapes or content to test the pixelation.
I have my video plane on dim 2 x 2 and an all images are super sharp.
Try the argument @transform_reset 2 on your plane for correct resizing instead of using the scale command. Scale will distort the image if all scale of one axis is different than the rest.

Sep 02 2013 | 11:14 am

maybe set @adapt 0 on you, and explicitly set the dimensions with the @dim attribute to whatever you want.

the @dim attribute of is related to the geometry dimensions, not the dimensions of the incoming texture.

Sep 02 2013 | 11:31 am

Thank you both for the replies. The original problem I solved by setting up a second drawing context and sending the to it.

I also found a way to fix the second problem. I was looking through some of Andrew Benson’s Jitter recipes and found instances of and that worked for me. I’m sending this initialization message to ‘capture_depthbits 16, capture_source color, dim 1280 720’. Then I have these arguments in the instance: ‘@transform_reset 2 @automatic 0’.

Now I know this combination of things has solved my problem, but I’m not exactly sure why.

Viewing 5 posts - 1 through 5 (of 5 total)

Forums > Jitter