I'm not able to render a movie trough jit.gl.videoplane as a node of jit.world.

jit-gl-node-function-in-jit-world

thanks for the reply, but I read the documentation about it.world and it declares that the object includes the functionality of jit.gl.node too. So I would imagine the object supposes to not use jit.gl.node. But I don't understand how…

Hi Tobias,
thanks for the reply, but I read the documentation about it.world and it declares that the object includes the functionality of jit.gl.node too. So I would imagine the object supposes to not use jit.gl.node. But I don't understand how…

"includes the functionality of jit.gl.node"

i might be wrong, but doesn't that mean that you can capture your world and output as a texture with further image processing.. (see also the in-built cornerpin functionality!)

What sense else would it make? If you want to work with multple sub.render contexts that go into your jit.world you then still need jit.gl.node objects. if there is more about it, i would also be happy to hear more...

i might be wrong, but doesn't that mean that you can capture your world and output as a texture  with further image processing.. (see also the in-built cornerpin functionality!)
What sense else would it make? If you want to work with multple sub.render contexts that go into your jit.world you then still need jit.gl.node objects. if there is more about it, i would also be happy to hear more...


I suppose I have to wait for a fuller explanation of how jit.world is in relation to jit.gl.node directly from some Cycling74 master…

It makes sense, of course!
I suppose I have to wait for a fuller explanation of how jit.world is in relation to jit.gl.node directly from some Cycling74 master…
thanks


In your patch I notice that jit.movie is set to @colormode uyvy.

I used to connect after jit.uyvy2argb in my patches to communicate with openGL and GPU

Do I understand that it is now done automatically with jit.world? What do you think ?

I don't find any attributes for that in jit.world

Talking about attributes ... how to hide the title bar like previously with jit.window ...

In your patch I notice that jit.movie is set to @colormode uyvy.
I used to connect after jit.uyvy2argb in my patches to communicate with openGL and GPU
Do I understand that it is now done automatically with jit.world? What do you think ?
I don't find any attributes for that in jit.world 

Talking about attributes ... how to hide the title bar like previously with jit.window ...
"border" attributes ? I can't find any

you can send message "sendwindow border 0"..

same way you can also send "sendcornerpin xyz" .

actually I just left @colormode uyvy from op at top, but because of output_texture the movie is not outputted at all as a jitter matrix...

hi marie-helene,
you can send message "sendwindow border 0"..

actually I just left @colormode uyvy from op at top, but because of output_texture  the movie is not outputted at all as a jitter matrix...

Not as convenient to send a message to be bangned but really glad that it's there :-)

Do you know if it's outputted as a jitter matrix in the process if I go directly from

I used Vade formula before to speed up the performance of my video patches

jit.qt.movie @colormode uyvy @unique 1 … attached to

Do you know if it's outputted as a jitter matrix in the process if I go directly from
jit.movie - jit.slab - jit.world 

I used Vade formula before to speed up the performance of my video patches
jit.qt.movie @colormode uyvy @unique 1 … attached to
jit.uyvy2argb
jit.gl.videoplane …

you don't need jit.uyvy2argb anymore when you output a texture from jit.movie and feed it into a gl-slab-chain... 

here a patch that doesn't need jit.gl.node.

Hi Tobias,
here a patch that doesn't need jit.gl.node.

there's no need to specify a name argument (mkfView), and then rename it with the @name attribute (mfk).

the first argument sets the @name attribute automatically.

there's no need to specify a name argument (mkfView), and then rename it with the @name attribute (mfk).
simply say [jit.world mfk].
the first argument sets the @name attribute automatically.


However removing the @name and attributing the same name for jit.world and videoplanes doesn't work.

It seems jit.world isn't able to create the sub-contexts of the respective videoplanes to play them in the same window.

On the other hand, the different name seems to create the necessary connection to videoplanes.

So the jit.world name is overwritten by the @name but it seems still necessary, if different. Strange…

Hi Rob,
thanks to look at the patch.
However removing the @name and attributing the same name for jit.world and videoplanes doesn't work.
It seems jit.world isn't able to create the sub-contexts of the respective videoplanes to play them in the same window.
On the other hand, the different name seems to create the necessary connection to videoplanes.
So the jit.world name is overwritten by the @name but it seems still necessary, if different. Strange…
Am I missing something essential?

typo in your patch. the jit.world arg is mkf and the vplane args are mfk.

I've got this video player with your recommandations here running pretty well and the performance is at 60 fps with all kinds of codec (H264, PNG, ProRes4444, Photo JPEG ..). But I"m wondering why the fps drops to 30 sometimes 25 when the clip loops.

Set attribute @fps 60 to your jit.world mhp should work well.

jit.gl.node function in jit.world