Forums > Jitter

Creating & affecting a matrix of polygons – a.k.a "Shatter Effect"

January 12, 2007 | 4:35 pm

Quote: Nadav Assor wrote on Fri, 12 January 2007 17:35
—————————————————-
> Hi all.
> I’m attempting to create a "shatter" type effect, in which the overall video frame is broken into many irregular polygons, and this grid of polygons may then be affected by control matrices, in a way similar to jit.gl.multiple.
[snip!]
Hello Nadav,

I am afraid I have nothing useful to say, other than the fact that the patch is very inspirational to me, and that I really hope you crack it soon enough :)

Your patch is a LOT faster than mine, if it helps…

Best,
Andreas Wetterberg


January 15, 2007 | 5:25 pm

Hi again. Sorry to be continuing my own thread, but I really need feedback from someone about this, and it is I think an interesting problem. I’ll try to shortly recap the main problems I’m facing, please look in the above patch for details, I tried to make it as clear as possible and commented simply everywhere. So:

Main Objective:
See first post. Basically trying to split a video frame into many irregular pieces and then manipulate their GL attributes using matrices as per jit.gl.multiple.

Problems:
1. Looking for a way to efficiently translate and rotate the polygons, as in jit.gl.multiple. Currently this works in a limited way, maybe I’m not using the right GL commands.
2. Unlike the isolated experiments I did, Rotation here seems to happen only in 2d, which is wierd. Haven’t managed to isolate the reason for that yet.
3. I’d really like to be able to take the matrixouput from something like jit.gl.gridshape, and use it to shape the overall grid of polygons- as i’ve done in the past with jit.gl.multiple.

Thanks,
-Nadav


January 15, 2007 | 7:03 pm

i tried using some of opengl methods to create display lists for this patch.
glbeginlist, glendlist, glnewlist etc. do not appear in the sketch list of
gl methods. nor in the js reference for the sketch object.
they do appear in the redbook.
my original thought would have been to create several master triangles and
then spreading them in the cmdlist.
referring "end users" to the red book is natural but i feel/hope more effort
should/would be made by the powers of cycling to translate what can and
what can not be applied to jitter. i mostly learn by example. the sketch
tutorial is fine but from salvaging the list its easy to tell its just the
tip of the berg. rant mode off.

On 1/15/07, Nadav Assor wrote:
>
>
> Hi again. Sorry to be continuing my own thread, but I really need feedback
> from someone about this, and it is I think an interesting problem. I’ll try
> to shortly recap the main problems I’m facing, please look in the above
> patch for details, I tried to make it as clear as possible and commented
> simply everywhere. So:
>
> Main Objective:
> See first post. Basically trying to split a video frame into many
> irregular pieces and then manipulate their GL attributes using matrices as
> per jit.gl.multiple.
>
> Problems:
> 1. Looking for a way to efficiently translate and rotate the polygons, as
> in jit.gl.multiple. Currently this works in a limited way, maybe I’m not
> using the right GL commands.
> 2. Unlike the isolated experiments I did, Rotation here seems to happen
> only in 2d, which is wierd. Haven’t managed to isolate the reason for that
> yet.
> 3. I’d really like to be able to take the matrixouput from something like
> jit.gl.gridshape, and use it to shape the overall grid of polygons- as
> i’ve done in the past with jit.gl.multiple.
>
> Thanks,
> -Nadav
>


January 15, 2007 | 7:30 pm

> referring "end users" to the red book is natural but i feel/hope more effort
> should/would be made by the powers of cycling to translate what can and
> what can not be applied to jitter.

It’s been my experience that references to the Red Book are only made in those situations in which something IS supported. But in a situation in which you don’t find something listed in either the Javascript-in-Max section on OpenGL or in the jit.gl.sketch list, it’s reasonable to assume that it’s not supported, or not supported "yet." Beyond demanding that everything be supported, what else could one do? You weren’t ranting, by the way.


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