kinomatic

I started doing some work with jit.gl.lua and thought I would post 

I noticed if I use an instance of jit.expr in lua I had to bracket 

the input and output with an instance of jit.matrix (vpoint, vgen) to 

be able to perform the matrixcalc and use the data within lua code or 

output it. Is there a simpler way to calculate matrix messages in 

jit.gl.lua? This is the only way I could get it to work so far...

-- called on every gl.draw unless @automatic 0

    local vpoint = jit.matrix(2, "float32", points, points)

    local vgen = jit.matrix(2, "float32", points, points)

    local vexpr = jit.new("jit.expr")

    vexpr.expr = {"norm[0]", "norm[1]"}

    vexpr:matrixcalc(vpoint.name, vgen.name)

    outlet(0, "jit_matrix", vgen.name)

I started doing some work with jit.gl.lua and thought I would post  
what I found out.
I noticed if I use an instance of jit.expr in lua I had to bracket  
the input and output with an instance of jit.matrix (vpoint, vgen) to  
be able to perform the matrixcalc and use the data within lua code or  
output it. Is there a simpler way to calculate matrix messages in  
jit.gl.lua? This is the only way I could get it to work so far...

render_context = this.drawto
autogarbage = 1
autowatch = 1
gc = 1
points = 50

-- called on every gl.draw unless @automatic 0
function draw()
	makepoints()
end

-- generate points
function makepoints()
	local vpoint = jit.matrix(2, "float32", points, points)
	local vgen = jit.matrix(2, "float32", points, points)
	local vexpr = jit.new("jit.expr")
	vexpr.expr = {"norm[0]", "norm[1]"}
	vexpr.inputs = 1
	vexpr.type = "float32"
	vexpr:matrixcalc(vpoint.name, vgen.name)
	outlet(0, "jit_matrix", vgen.name)
end

-- set the dimensions of the matrix
function dim(x)
	points = x
end


lua-gencoord

The following should work. Note that even in a patcher jit.expr

requires an input jit.matrix object so that being also the case in

jit.gl.lua is consistent. All I did below was make the calculations

local vpoint = jit.matrix(2, "float32", points, points)

vexpr:matrixcalc(vpoint.name, vpoint.name)

The following should work.  Note that even in a patcher jit.expr
requires an input jit.matrix object so that being also the case in
jit.gl.lua is consistent.  All I did below was make the calculations
happen in-place.

-- called on every gl.draw unless @automatic 0
function draw()
       makepoints()
end

-- generate points
function makepoints()
       local vpoint = jit.matrix(2, "float32", points, points)
       local vexpr = jit.new("jit.expr")
       vexpr.expr = {"norm[0]", "norm[1]"}
       vexpr.inputs = 1
       vexpr.type = "float32"
       vexpr:matrixcalc(vpoint.name, vpoint.name)
       outlet(0, "jit_matrix", vpoint.name)
end

-- set the dimensions of the matrix
function dim(x)
       points = x
end


sweet. thanks that gives me a new view of things. so I only need to 

create an instance of one matrix and pass it along.

another question which I haven't quite found an answer to: If I 

create an instance of jit.qt.movie how do I reference the output 

matrix when it plays? In jitter I would just send it a bang, but in 

lua I am having trouble getting a matrix. the read message I seem to 

have working... but it seems some messages work and others don't. Am 

I right to assume that messages take the : and atributes the . 

    local vframe = jit.matrix(2, "char", 320, 240)

    -- I get an error: "jit.qt.movie: could not create gworld" if I 

call the following but no film has been read

    vmovie:matrixcalc(vframe.name, vframe.name)

    outlet(0, "jit_matrix", vframe.name)

On Oct 23, 2007, at 10:58 PM, Wesley Smith wrote:

> The following should work. Note that even in a patcher jit.expr

> requires an input jit.matrix object so that being also the case in

> jit.gl.lua is consistent. All I did below was make the calculations

> -- called on every gl.draw unless @automatic 0

> local vpoint = jit.matrix(2, "float32", points, points)

> vexpr:matrixcalc(vpoint.name, vpoint.name)

sweet. thanks that gives me a new view of things. so I only need to  
create an instance of one matrix and pass it along.

another question which I haven't quite found an answer to: If I  
create an instance of jit.qt.movie how do I reference the output  
matrix when it plays? In jitter I would just send it a bang, but in  
lua I am having trouble getting a matrix. the read message I seem to  
have working... but it seems some messages work and others don't. Am  
I right to assume that messages take the : and atributes the .  
between the instance and message?

function load(a)
	vmovie = jit.new("jit.qt.movie")
	vmovie.colormode = "uyvy"
	vmovie.adapt = 1
	vmovie:read(a)
	local vframe = jit.matrix(2, "char", 320, 240)
  	-- I get an error: "jit.qt.movie: could not create gworld" if I  
call the following but no film has been read
	vmovie:matrixcalc(vframe.name, vframe.name)
	outlet(0, "jit_matrix", vframe.name)
end

> The following should work.  Note that even in a patcher jit.expr
> requires an input jit.matrix object so that being also the case in
> jit.gl.lua is consistent.  All I did below was make the calculations
> happen in-place.
>
> wes
>
> render_context = this.drawto
> autogarbage = 1
> autowatch = 1
> gc = 1
> points = 50
>
> -- called on every gl.draw unless @automatic 0
> function draw()
>        makepoints()
> end
>
> -- generate points
> function makepoints()
>        local vpoint = jit.matrix(2, "float32", points, points)
>        local vexpr = jit.new("jit.expr")
>        vexpr.expr = {"norm[0]", "norm[1]"}
>        vexpr.inputs = 1
>        vexpr.type = "float32"
>        vexpr:matrixcalc(vpoint.name, vpoint.name)
>        outlet(0, "jit_matrix", vpoint.name)
> end
>
> -- set the dimensions of the matrix
> function dim(x)
>        points = x
> end


works for me. BTW, you might want to make your matrix 4 plane. Are

you in windows or OSX? What version of jit.gl.lua do you have?

> sweet. thanks that gives me a new view of things. so I only need to

> create an instance of one matrix and pass it along.

> another question which I haven't quite found an answer to: If I

> create an instance of jit.qt.movie how do I reference the output

> matrix when it plays? In jitter I would just send it a bang, but in

> lua I am having trouble getting a matrix. the read message I seem to

> have working... but it seems some messages work and others don't. Am

> I right to assume that messages take the : and atributes the .

> local vframe = jit.matrix(2, "char", 320, 240)

> -- I get an error: "jit.qt.movie: could not create gworld" if I

> call the following but no film has been read

> vmovie:matrixcalc(vframe.name, vframe.name)

> On Oct 23, 2007, at 10:58 PM, Wesley Smith wrote:

> > The following should work. Note that even in a patcher jit.expr

> > requires an input jit.matrix object so that being also the case in

> > jit.gl.lua is consistent. All I did below was make the calculations

> > -- called on every gl.draw unless @automatic 0

works for me.  BTW, you might want to make your matrix 4 plane.  Are
you in windows or OSX?  What version of jit.gl.lua do you have?

On 10/23/07, (())_n  wrote:
> hi wes,
>
> sweet. thanks that gives me a new view of things. so I only need to
> create an instance of one matrix and pass it along.
>
> super.
>
> another question which I haven't quite found an answer to: If I
> create an instance of jit.qt.movie how do I reference the output
> matrix when it plays? In jitter I would just send it a bang, but in
> lua I am having trouble getting a matrix. the read message I seem to
> have working... but it seems some messages work and others don't. Am
> I right to assume that messages take the : and atributes the .
> between the instance and message?
>
> function load(a)
>         vmovie = jit.new("jit.qt.movie")
>         vmovie.colormode = "uyvy"
>         vmovie.adapt = 1
>         vmovie:read(a)
>         local vframe = jit.matrix(2, "char", 320, 240)
>         -- I get an error: "jit.qt.movie: could not create gworld" if I
> call the following but no film has been read
>         vmovie:matrixcalc(vframe.name, vframe.name)
>         outlet(0, "jit_matrix", vframe.name)
> end
>
> (())_n
>
> On Oct 23, 2007, at 10:58 PM, Wesley Smith wrote:
>
> > The following should work.  Note that even in a patcher jit.expr
> > requires an input jit.matrix object so that being also the case in
> > jit.gl.lua is consistent.  All I did below was make the calculations
> > happen in-place.
> >
> > wes
> >
> > render_context = this.drawto
> > autogarbage = 1
> > autowatch = 1
> > gc = 1
> > points = 50
> >
> > -- called on every gl.draw unless @automatic 0
> > function draw()
> >        makepoints()
> > end
> >
> > -- generate points
> > function makepoints()
> >        local vpoint = jit.matrix(2, "float32", points, points)
> >        local vexpr = jit.new("jit.expr")
> >        vexpr.expr = {"norm[0]", "norm[1]"}
> >        vexpr.inputs = 1
> >        vexpr.type = "float32"
> >        vexpr:matrixcalc(vpoint.name, vpoint.name)
> >        outlet(0, "jit_matrix", vpoint.name)
> > end
> >
> > -- set the dimensions of the matrix
> > function dim(x)
> >        points = x
> > end
>
>


On Oct 24, 2007, at 1:23 AM, Wesley Smith wrote:

> works for me. BTW, you might want to make your matrix 4 plane. Are

> you in windows or OSX? What version of jit.gl.lua do you have?

Thanks. I overlooked the 4 planes. Yes it works but not until I have 

read a file into jit.qt.movie. if I haven't read a file I get the 

error: "jit.qt.movie: could not create gworld." So matrixcalc is the 

only way for an instance of jit.qt.movie to output a matrix in 

I am on 12" pwrbk g4 GeForce FX Go5200 osx 10.4.10 max 4.6.3 jitter 

Note: I updated to the Jitter "1.6.4-x1 :: Experimental Jitter 

here is the code that illustrates this behavior:

    local vframe = jit.matrix(4, "char", 320, 240)

-- I get an error: "jit.qt.movie: could not create gworld"

-- if I call the following but no film has been read

> works for me.  BTW, you might want to make your matrix 4 plane.  Are
> you in windows or OSX?  What version of jit.gl.lua do you have?
>
> wes

Thanks. I overlooked the 4 planes. Yes it works but not until I have  
read a file into jit.qt.movie. if I haven't read a file I get the  
error: "jit.qt.movie: could not create gworld." So matrixcalc is the  
only way for an instance of jit.qt.movie to output a matrix in  
jit.gl.lua?

I am on 12" pwrbk g4 GeForce FX Go5200 osx 10.4.10 max 4.6.3 jitter  
1.6.3 jit.gl.lua is b4
Note: I updated to the Jitter "1.6.4-x1 :: Experimental Jitter  
framework" and still get the same error.

render_context = this.drawto
autogarbage = 1
autowatch = 1
gc = 1

function script_load()
	vmovie = jit.new("jit.qt.movie")
	vmovie.colormode = "uyvy"
	vmovie.adapt = 1
end

function read(a)
	vmovie:read(a)
	local vframe = jit.matrix(4, "char", 320, 240)
	vmovie:matrixcalc(vframe.name, vframe.name)
	outlet(0, "jit_matrix", vframe.name)
end

-- I get an error: "jit.qt.movie: could not create gworld"
-- if I call the following but no film has been read
function play()
	local vframe = jit.matrix(4, "char", 320, 240)
	vmovie:matrixcalc(vframe.name, vframe.name)
	outlet(0, "jit_matrix", vframe.name)
end


I am confused by the play function. Don't you want to do something 

more like this? Also fixes the gworld error:

        local vframe = jit.matrix(4, "char", 320, 240)

        vmovie:matrixcalc(vframe.name, vframe.name)

        outlet(0, "jit_matrix", vframe.name)

On Oct 24, 2007, at 9:45 AM, (())_n wrote:

> On Oct 24, 2007, at 1:23 AM, Wesley Smith wrote:

>> works for me. BTW, you might want to make your matrix 4 plane. Are

>> you in windows or OSX? What version of jit.gl.lua do you have?

> Thanks. I overlooked the 4 planes. Yes it works but not until I 

> have read a file into jit.qt.movie. if I haven't read a file I get 

> the error: "jit.qt.movie: could not create gworld." So matrixcalc 

> is the only way for an instance of jit.qt.movie to output a matrix 

> I am on 12" pwrbk g4 GeForce FX Go5200 osx 10.4.10 max 4.6.3 jitter 

> Note: I updated to the Jitter "1.6.4-x1 :: Experimental Jitter 

> framework" and still get the same error.

> here is the code that illustrates this behavior:

>     vmovie = jit.new("jit.qt.movie")

>     local vframe = jit.matrix(4, "char", 320, 240)

>     vmovie:matrixcalc(vframe.name, vframe.name)

>     outlet(0, "jit_matrix", vframe.name)

> -- I get an error: "jit.qt.movie: could not create gworld"

> -- if I call the following but no film has been read

I am confused by the play function. Don't you want to do something  
more like this? Also fixes the gworld error:

-- I get an error: "jit.qt.movie: could not create gworld"
-- if I call the following but no film has been read
function draw()
	if (vmovie.framecount > 0) then
		local vframe = jit.matrix(4, "char", 320, 240)
		vmovie:matrixcalc(vframe.name, vframe.name)
		outlet(0, "jit_matrix", vframe.name)
	end
end

> On Oct 24, 2007, at 1:23 AM, Wesley Smith wrote:
>
>> works for me.  BTW, you might want to make your matrix 4 plane.  Are
>> you in windows or OSX?  What version of jit.gl.lua do you have?
>>
>> wes
>
>
> Hi Wes,
>
> Thanks. I overlooked the 4 planes. Yes it works but not until I  
> have read a file into jit.qt.movie. if I haven't read a file I get  
> the error: "jit.qt.movie: could not create gworld." So matrixcalc  
> is the only way for an instance of jit.qt.movie to output a matrix  
> in jit.gl.lua?
>
> I am on 12" pwrbk g4 GeForce FX Go5200 osx 10.4.10 max 4.6.3 jitter  
> 1.6.3 jit.gl.lua is b4
> Note: I updated to the Jitter "1.6.4-x1 :: Experimental Jitter  
> framework" and still get the same error.
>
> (())_n
>
> here is the code that illustrates this behavior:
>
> render_context = this.drawto
> autogarbage = 1
> autowatch = 1
> gc = 1
>
> function script_load()
> 	vmovie = jit.new("jit.qt.movie")
> 	vmovie.colormode = "uyvy"
> 	vmovie.adapt = 1
> end
>
> function read(a)
> 	vmovie:read(a)
> 	local vframe = jit.matrix(4, "char", 320, 240)
> 	vmovie:matrixcalc(vframe.name, vframe.name)
> 	outlet(0, "jit_matrix", vframe.name)
> end
>
> -- I get an error: "jit.qt.movie: could not create gworld"
> -- if I call the following but no film has been read
> function play()
> 	local vframe = jit.matrix(4, "char", 320, 240)
> 	vmovie:matrixcalc(vframe.name, vframe.name)
> 	outlet(0, "jit_matrix", vframe.name)
> end
>
>


this is great. I guess I should be calling it on the draw and check 

for frames to see if a movie has been loaded.

On Oct 24, 2007, at 1:20 PM, MarkDavid Hosale wrote:

> I am confused by the play function. Don't you want to do something 

> more like this? Also fixes the gworld error:

>     if (vmovie.framecount > 0) then

>         local vframe = jit.matrix(4, "char", 320, 240)

>         vmovie:matrixcalc(vframe.name, vframe.name)

>         outlet(0, "jit_matrix", vframe.name)

this is great. I guess I should be calling it on the draw and check  
for frames to see if a movie has been loaded.

> I am confused by the play function. Don't you want to do something  
> more like this? Also fixes the gworld error:
>
> -- movieplayer.lua
>
> render_context = this.drawto
> autogarbage = 1
> autowatch = 1
> gc = 1
>
> function script_load()
> 	vmovie = jit.new("jit.qt.movie")
> 	vmovie.colormode = "uyvy"
> 	vmovie.adapt = 1
> end
>
> function read(a)
> 	vmovie:read(a)
> end
>
> -- I get an error: "jit.qt.movie: could not create gworld"
> -- if I call the following but no film has been read
> function draw()
> 	if (vmovie.framecount > 0) then
> 		local vframe = jit.matrix(4, "char", 320, 240)
> 		vmovie:matrixcalc(vframe.name, vframe.name)
> 		outlet(0, "jit_matrix", vframe.name)
> 	end
> end
>
>
> here is my patcher:
>
> max v2;
> 


You don't have to call it on the draw but it can be convenient. If

you're not using opengl, you can just send a message to output a frame

> this is great. I guess I should be calling it on the draw and check

> for frames to see if a movie has been loaded.

> On Oct 24, 2007, at 1:20 PM, MarkDavid Hosale wrote:

> > I am confused by the play function. Don't you want to do something

> > more like this? Also fixes the gworld error:

> > -- I get an error: "jit.qt.movie: could not create gworld"

> > -- if I call the following but no film has been read

> > local vframe = jit.matrix(4, "char", 320, 240)

> > vmovie:matrixcalc(vframe.name, vframe.name)

You don't have to call it on the draw but it can be convenient.  If
you're not using opengl, you can just send a message to output a frame
whenever you want.

On 10/24/07, (())_n  wrote:
> Hi mark,
>
> this is great. I guess I should be calling it on the draw and check
> for frames to see if a movie has been loaded.
>
> thanks
>
> (())_n
>
>
> On Oct 24, 2007, at 1:20 PM, MarkDavid Hosale wrote:
>
> > I am confused by the play function. Don't you want to do something
> > more like this? Also fixes the gworld error:
> >
> > -- movieplayer.lua
> >
> > render_context = this.drawto
> > autogarbage = 1
> > autowatch = 1
> > gc = 1
> >
> > function script_load()
> >       vmovie = jit.new("jit.qt.movie")
> >       vmovie.colormode = "uyvy"
> >       vmovie.adapt = 1
> > end
> >
> > function read(a)
> >       vmovie:read(a)
> > end
> >
> > -- I get an error: "jit.qt.movie: could not create gworld"
> > -- if I call the following but no film has been read
> > function draw()
> >       if (vmovie.framecount > 0) then
> >               local vframe = jit.matrix(4, "char", 320, 240)
> >               vmovie:matrixcalc(vframe.name, vframe.name)
> >               outlet(0, "jit_matrix", vframe.name)
> >       end
> > end
> >
> >
> > here is my patcher:
> >
> > max v2;
> > #N vpatcher 501 427 1101 827;
> > #P window setfont "Sans Serif" 9.;
> > #P window linecount 1;
> > #P message 368 138 80 196617 read dozer.mov;
> > #P message 303 140 58 196617 read dozer;
> > #P newex 300 164 64 196617 prepend call;
> > #P user jit.pwindow 303 216 82 62 0 1 0 0 1 0;
> > #P newex 277 289 75 196617 jit.window foo;
> > #P newex 147 160 50 196617 t b erase;
> > #P toggle 147 106 15 0;
> > #P newex 147 135 57 196617 qmetro 33;
> > #P newex 147 236 82 196617 jit.gl.render foo;
> > #P newex 304 192 166 196617 jit.gl.lua foo @file movieplayer.lua;
> > #P connect 3 0 2 0;
> > #P connect 2 0 4 0;
> > #P connect 4 1 1 0;
> > #P connect 4 0 1 0;
> > #P connect 9 0 7 0;
> > #P connect 8 0 7 0;
> > #P connect 7 0 0 0;
> > #P connect 0 0 6 0;
> > #P pop;
>


On Oct 24, 2007, at 3:02 PM, Wesley Smith wrote:

> You don't have to call it on the draw but it can be convenient. If

> you're not using opengl, you can just send a message to output a frame

Yes I was just trying to think to keep the CPU and GPU processes 

Will see what is more effective in the long run.

So I now made a player based on your input. I noticed that if I call 

a local matrix on every draw() or play() for the matrixcalc it slowed 

down and crashed after a while. So now I create the processing matrix 

in the setup. With this code I noticed that dozer.mov and other short 

movies play fine, but that the frame rate drops proportionately on 

longer movie files with the same photo-jpeg 320x240 compression 

settings. The longer files play fast in jit.qt.movie in a patch. I 

went back to jitter 1.6.3 but it didn't change anything.

    vplane = jit.new("jit.gl.videoplane", render_context)

    vframe = jit.matrix(4, "char", 320, 240)

        vplane:jit_matrix(vframe.name)

> You don't have to call it on the draw but it can be convenient.  If
> you're not using opengl, you can just send a message to output a frame
> whenever you want.
>
> wes

Yes I was just trying to think to keep the CPU and GPU processes  
separate.
Will see what is more effective in the long run.

So I now made a player based on your input. I noticed that if I call  
a local matrix on every draw() or play() for the matrixcalc it slowed  
down and crashed after a while. So now I create the processing matrix  
in the setup. With this code I noticed that dozer.mov and other short  
movies play fine, but that the frame rate drops proportionately on  
longer movie files with the same photo-jpeg 320x240 compression  
settings. The longer files play fast in jit.qt.movie in a patch. I  
went back to jitter 1.6.3 but it didn't change anything.

The patch and code here (and below):
http://home.earthlink.net/~posit/lua/

function script_load()
	vmovie = jit.new("jit.qt.movie")
	vmovie.colormode = "uyvy"
	vmovie.adapt = 1
	vplane = jit.new("jit.gl.videoplane", render_context)
	vplane.colormode = "uyvy"
	vplane.scale = {1.333, 1., 1.}
	vframe = jit.matrix(4, "char", 320, 240)
end

function play()
	if (vmovie.framecount > 0) then
		vmovie:matrixcalc(vframe.name, vframe.name)
		outlet(0, "jit_matrix", vframe.name)
	end
end

function draw()
	if (vmovie.framecount > 0) then
		vmovie:matrixcalc(vframe.name, vframe.name)
		vplane:jit_matrix(vframe.name)
	end
end

On Oct 24, 2007, at 4:15 PM, (())_n wrote:

>     vframe = jit.matrix(4, "char", 320, 240)

Very important: in UYVY mode you should use *half* resolution for the 

x-axis. If you connect jit.fpsgui in dim mode you should see that the 

output matrix for a "320x240" file uses "160x120" in UYVY mode due to 

the chroma reduced "macro-pixel". See the "colorspaces" tutorial for 

more info if this doesn't make sense to you.

> 	vmovie = jit.new("jit.qt.movie")
> 	vmovie.colormode = "uyvy"
> 	vframe = jit.matrix(4, "char", 320, 240)

Very important: in UYVY mode you should use *half* resolution for the  
x-axis. If you connect jit.fpsgui in dim mode you should see that the  
output matrix for a "320x240" file uses "160x120" in UYVY mode due to  
the chroma reduced "macro-pixel". See the "colorspaces" tutorial for  
more info if this doesn't make sense to you.

Wes is probably better able to address the issue you are describing 

here as it relates to the code you posted. But, I was wondering, what 

is your end goal? do you want to do some video processing on a slab? 

Do some matrix processing with video? or do you want to just texture 

Depending on what you're trying to do I have some sample patches that 

could help you and are definitely not suffering from this slow down 

A couple of little notes about this patch:

- you should erase your renderer after each bang i.e. [t b erase]

- it's really not important, but I would change the name of play() to 

bang(), this way you can just run the metro directly to the [prepend 

call] without the play message. It's more intuitive to me since this 

is the way max objects work. Almost not worth mentioning however...

> On Oct 24, 2007, at 3:02 PM, Wesley Smith wrote:

>> You don't have to call it on the draw but it can be convenient. If

>> you're not using opengl, you can just send a message to output a 

> Yes I was just trying to think to keep the CPU and GPU processes 

> Will see what is more effective in the long run.

> So I now made a player based on your input. I noticed that if I 

> call a local matrix on every draw() or play() for the matrixcalc it 

> slowed down and crashed after a while. So now I create the 

> processing matrix in the setup. With this code I noticed that 

> dozer.mov and other short movies play fine, but that the frame rate 

> drops proportionately on longer movie files with the same photo- 

> jpeg 320x240 compression settings. The longer files play fast in 

> jit.qt.movie in a patch. I went back to jitter 1.6.3 but it didn't 

lua gencoord