Jitter 1.6 Bug report with jit.op

Jun 25, 2006 at 3:41am

Jitter 1.6 Bug report with jit.op

Hello

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.

Expected behavior – works as in jitter 1.5.4

Thanks,

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

v a d e //

http://www.vade.info
abstrakt.vade.info

#26546
Jun 26, 2006 at 10:59pm

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.

#79554
Jun 26, 2006 at 11:39pm

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 //

http://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.

#79555
Jun 27, 2006 at 12:06am

im an ass. int is 0-255

float scales. 0 255 0 1.0

duh. sorry.

v a d e //

http://www.vade.info
abstrakt.vade.info

On Jun 26, 2006, at 7:39 PM, vade wrote:

> 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 //
>
> http://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.
>

#79556

You must be logged in to reply to this topic.