pseudostereo

I can't get jit.change to accurately report changes out of its right outlet.

When report is set to 1, it sometimes constantly sends out "report 1", other times constantly "report 0". But it never has any relationship to whether any frames are actually being passed.

Could somebody else check and confirm this (or not). Or maybe I'm doing something wrong, but I can't imagine what.

jit-change-report-attribute-not-working

1 frame at the time can pass or not, so I dont think it will ever 

report any other number than 1 or 0. If you want to know how many 

frames have been passed or stopped just start counting the frames in 

On 10-Aug-08, at 3:21 PM, pseudostereo wrote:

> I can't get jit.change to accurately report changes out of its 

> When report is set to 1, it sometimes constantly sends out "report 

> 1", other times constantly "report 0". But it never has any 

> relationship to whether any frames are actually being passed.

> Could somebody else check and confirm this (or not). Or maybe I'm 

> doing something wrong, but I can't imagine what.

1 frame at the time can pass or not, so I dont think it will ever  
report any other number than 1 or 0. If you want to know how many  
frames have been passed or stopped just start counting the frames in  
each state (1-0).
JS

>
> I can't get jit.change to accurately report changes out of its  
> right outlet.
>
> When report is set to 1, it sometimes constantly sends out "report  
> 1", other times constantly "report 0". But it never has any  
> relationship to whether any frames are actually being passed.
>
> Could somebody else check and confirm this (or not). Or maybe I'm  
> doing something wrong, but I can't imagine what.
>
> Max 5.0.4, MacBook Pro, OS X 10.5.4


Nope, all I wanted to know was whether a frame has been passed or not.

But I reread the reference, and I see my mistake - jit.change reports a 0 when a frame is passed, and a 1 when it's not. I thought it was the reverse, which got me confused.

Seems to me it would make more sense the other way round, but whatever.

Nope, all I wanted to know was whether a frame has been passed or not. 

Seems to me it would make more sense the other way round, but whatever.


jit.change report attribute not working?