djlbe

I'm on win7 amd 64bit using max msp 32bit,

I'm doing a jitter blur fx for process matrix that use gl.

so I use a gl render, That's the classic method using jit.gl.slab,

a video plane and an asyncread object. so in that way all goes

well. I get the blur effect and receive it in a new matrix.

but now I would like to encapsulate it for having a more generic

patcher that I can use everytime I need that blur fx. so in that

way I try to avoid that boring useless jit.window.

So I searched , i searched again and I found that :

1 ) Using draw_to method with gl render will ruin efficiency as it use software renderer and can cause a lot of problem even in max 7

2) Use jit.pwindow will not work if I encapsulate the patch as asyncread render into matrix what it 'see' exactacly. therefor reduce de jit.pwindow will result with a pixelated matrix etc...

3) using Jit.windows works fine but! if you want to use it , it needs to be visible or asyncread will render nothing. (that's what I get when I set @visible to 0)

so, in my exemple, if I want a different gaussian blur fx on each channels of a matrix that I separate with jit.unpack, I will need 4 huge jit.windows in the background of my patch, right ? and that's the only way...

Did I'm wrong somewhere ? did I missed something, i hope so... : (

I'm on win7 amd 64bit using max msp 32bit,
I'm doing a jitter blur fx for process matrix that use gl.
so I use a gl render, That's the classic method using jit.gl.slab,
a video plane and an asyncread object. so in that way all goes
well. I get the blur effect and receive it in a new matrix.

but now I would like to encapsulate it for having a more generic
patcher that I can use everytime I need that blur fx. so in that
way I try to avoid that boring useless jit.window.

So I searched , i searched again and I found that : 

1 ) Using draw_to method with gl render will ruin efficiency as it use software renderer and can cause a lot of problem even in max 7
2) Use jit.pwindow will not work if I encapsulate the patch as asyncread render into matrix what it 'see' exactacly. therefor reduce de jit.pwindow will result with a pixelated matrix etc...
3) using Jit.windows works fine but! if you want to use it , it needs to be visible or asyncread will render nothing. (that's what I get when I set @visible to 0)

so, in my exemple,  if I want a different gaussian blur fx on each channels of a matrix that I separate with jit.unpack, I will need 4 huge jit.windows in the background of my patch, right ? and that's the only way...

Did I'm wrong somewhere ?  did I missed something, i hope so... : (


encapsulate-gl-render

the following patch should help you going (if I understood you correctly)

Ok so, I just need to use jit.gl.texture insteed of jit.gl.videoplane and jit.asyncread.

Ok so, I  just need to use jit.gl.texture insteed of jit.gl.videoplane and jit.asyncread.


exactly. with texture to move from matrix-CPU-world into texture-GPU-world, here you can do your Shader-magic, and then you return to CPU world with a jit.matrix object (instead of a jit.pwindow). for this a render context and a window is required, and jit.gl.render needs a bang to initialize the context. but otherwise no rendering is happening (except the one inside the jit.gl.slab object).

in general best practice is to move with video as fast a possible into GPU world and stay there if performance is an issue.

So HOW do we encapsulate jitter patches? That was the original question and i'm also finding it impossible, to the extent that is looks like a bug with the software (albeit a silent one).

So HOW do we encapsulate jitter patches?  That was the original question and i'm also finding it impossible, to the extent that is looks like a bug with the software (albeit a silent one).

Encapsulate GL.Render