vade

Bug Report - jit.op @op !pass does not pass rightmost matrix - and 

does not pass leftmost matrix if op is set to pass

Hardware/Software - Mac OS X 10.4.6 - Powerbook G4 1.6.7 128Mb VRam 

Max 4.6 public beta Jitter 1.6 public beta

To reproduce - open jit.op help file - load two movies - set op to ! 

Also, scalar int to value doesnt work. (try with @op *) floating 

Expected behavior - works as in jitter 1.5.4

Apologies if these are redundant - I am testing offline, so im not 

Bug Report - jit.op @op !pass does not pass rightmost matrix - and  
does not pass leftmost matrix if op is set to pass

Hardware/Software - Mac OS X 10.4.6 - Powerbook G4 1.6.7 128Mb VRam  
Max 4.6 public beta Jitter 1.6 public beta

To reproduce - open jit.op help file - load two movies - set op to ! 
pass, or abs, or pass.

Also, scalar int to value doesnt work. (try with @op *) floating  
point does however.

Apologies if these are redundant - I am testing offline, so im not  
sure what has been reported already.

jitter-1-6-bug-report-with-jit-op

I can reproduce the first thing, and have logged it in our bug tracking 

system. The int scalar thing, however, appears to be working fine here.

Hey Vade,
I can reproduce the first thing, and have logged it in our bug tracking 
system.  The int scalar thing, however, appears to be working fine here.

I just double checked, and it seems like the INT mode (@val 1 for 

For example, if I load a movie, start the metro, and set my op to * 

now change the int to 1 (which should mean no change to the incoming 

matrix), I get all black frames, but the appropriate FPS (ie matrices 

out). If I set the floating point value to 1.0, I get picture out and 

Thanks, btw, the md5 hash of my jit.op object is MD5 (jit.op) = 

b275b2996def59160cbf9a99405e56ef (of the executable within the mxo)

Just incase anythings changed since ive installed it.

On Jun 26, 2006, at 6:59 PM, Andrew Benson wrote:

> I can reproduce the first thing, and have logged it in our bug 

> tracking system. The int scalar thing, however, appears to be 

I just double checked, and it seems like the INT mode  (@val 1 for  
example) doesnt work with @op * .

For example, if I load a movie, start the metro, and set my op to *  
it works

now change the int to 1 (which should mean no change to the incoming  
matrix), I get all black frames, but the appropriate FPS (ie matrices  
out). If I set the floating point value to 1.0, I get picture out and  
it seems to work as advertised.

Thanks, btw, the md5 hash of my jit.op object is MD5 (jit.op) =  
b275b2996def59160cbf9a99405e56ef (of the executable within the mxo)
  - OS X 10.4.6 on Powerbook G4

> Hey Vade,
> I can reproduce the first thing, and have logged it in our bug  
> tracking system.  The int scalar thing, however, appears to be  
> working fine here.
>
> Cheers,
> Andrew B.

> Hi Andrew - thanks for checking it out.

> I just double checked, and it seems like the INT mode (@val 1 for 

> For example, if I load a movie, start the metro, and set my op to * 

> now change the int to 1 (which should mean no change to the 

> incoming matrix), I get all black frames, but the appropriate FPS 

> (ie matrices out). If I set the floating point value to 1.0, I get 

> picture out and it seems to work as advertised.

> Thanks, btw, the md5 hash of my jit.op object is MD5 (jit.op) = 

> b275b2996def59160cbf9a99405e56ef (of the executable within the mxo)

> Just incase anythings changed since ive installed it.

> On Jun 26, 2006, at 6:59 PM, Andrew Benson wrote:

>> I can reproduce the first thing, and have logged it in our bug 

>> tracking system. The int scalar thing, however, appears to be 

> Hi Andrew - thanks for checking it out.
>
> I just double checked, and it seems like the INT mode  (@val 1 for  
> example) doesnt work with @op * .
>
> For example, if I load a movie, start the metro, and set my op to *  
> it works
>
> now change the int to 1 (which should mean no change to the  
> incoming matrix), I get all black frames, but the appropriate FPS  
> (ie matrices out). If I set the floating point value to 1.0, I get  
> picture out and it seems to work as advertised.
>
> Thanks, btw, the md5 hash of my jit.op object is MD5 (jit.op) =  
> b275b2996def59160cbf9a99405e56ef (of the executable within the mxo)
>  - OS X 10.4.6 on Powerbook G4
>
> Just incase anythings changed since ive installed it.
>
>
> v a d e //
>
> www.vade.info
> abstrakt.vade.info
>
> On Jun 26, 2006, at 6:59 PM, Andrew Benson wrote:
>
>> Hey Vade,
>> I can reproduce the first thing, and have logged it in our bug  
>> tracking system.  The int scalar thing, however, appears to be  
>> working fine here.
>>
>> Cheers,
>> Andrew B.
>

Jitter 1.6 Bug report with jit.op