jit.cellblock vs. jit.iter data behavior


    Oct 08 2008 | 7:10 pm
    I have a movie downsampled by a jit.matrix attached to both jit.iter and jit.cellblock, trying to get luminance values. Two things are confusing:
    1. jit.iter gives different values upon banging it than the values that appear in jit.cellblock -- why these different values?
    2. If I click in jit.cellblock or change it's size with the mouse or even command-click in a different part of the patch when edit mode is on, the jit.cellblock values change, EVEN THOUGH THE MATRIX DATA IS NOT GOING THROUGH THE CONNECTION. Even if I disconnect the matrix from the cellblock, these data values change with every click of the mouse. Only if I stop the metro that runs the jit.qt.movie do these values stop changing.
    I have not seen in any documentation why this behavior. Why are the values different coming out of jit.iter than those I see in jit.cellblock? Why do jit.cellblock values constantly change for no apparent reason. And finally, which values do I believe are the correct ones for the matrix values?
    Thanks.
    JT

    • Oct 08 2008 | 8:18 pm
      it's not that the values are different. it's that with iter you're getting a lot of values very quickly. look at jit.iter's output with a print object.
      On Oct 8, 2008, at 3:10 PM, John Toenjes wrote:
      > > I have a movie downsampled by a jit.matrix attached to both jit.iter > and jit.cellblock, trying to get luminance values. Two things are > confusing: > > 1. jit.iter gives different values upon banging it than the values > that appear in jit.cellblock -- why these different values? > > 2. If I click in jit.cellblock or change it's size with the mouse or > even command-click in a different part of the patch when edit mode > is on, the jit.cellblock values change, EVEN THOUGH THE MATRIX DATA > IS NOT GOING THROUGH THE CONNECTION. Even if I disconnect the matrix > from the cellblock, these data values change with every click of the > mouse. Only if I stop the metro that runs the jit.qt.movie do these > values stop changing. > > I have not seen in any documentation why this behavior. Why are the > values different coming out of jit.iter than those I see in > jit.cellblock? Why do jit.cellblock values constantly change for no > apparent reason. And finally, which values do I believe are the > correct ones for the matrix values? > > Thanks. > > JT > > max v2; > #N vpatcher -6 44 654 808; > #P origin -54 88; > #P window setfont "Sans Serif" 9.; > #P newex 134 292 43 196617 print zl; > #N vpatcher 20 74 647 302; > #N comlet bang to select/output values; > #P inlet 91 34 15 0; > #P window setfont "Sans Serif" 9.; > #P user umenu 472 47 105 196647 1 64 63 1; > #X add individual output; > #X add output as one list; > #X add output as one symbol; > #P message 472 72 85 196617 mode outmode $1; > #P message 360 72 90 196617 mode selmode $1; > #P user umenu 360 48 105 196647 1 64 64 1; > #X add no selection; > #X add one cell select; > #X add column select; > #X add row select; > #X add header select; > #X add in-place edit; > #P message 92 57 55 196617 select 0 0; > #P message 287 70 61 196617 colwidth $1; > #P number 287 50 35 9 1 0 1 3 0 0 0 221 221 221 222 222 222 0 0 0; > #P message 184 69 45 196617 rows $1; > #P message 238 70 41 196617 cols $1; > #P number 184 50 35 9 1 0 1 3 0 0 0 221 221 221 222 222 222 0 0 0; > #P number 238 49 35 9 1 0 1 3 0 0 0 221 221 221 222 222 222 0 0 0; > #P outlet 267 154 15 0; > #P connect 12 0 7 0; > #P connect 2 0 4 0; > #P connect 1 0 3 0; > #P connect 7 0 0 0; > #P connect 4 0 0 0; > #P connect 3 0 0 0; > #P connect 6 0 0 0; > #P connect 9 0 0 0; > #P connect 10 0 0 0; > #P connect 5 0 6 0; > #P connect 8 0 9 0; > #P connect 11 0 10 0; > #P pop; > #P newobj 226 496 80 196617 p cellblkContrls; > #P user jit.cellblock 215 525 592 746 3 9 16 1 24 17 0 1 1 0 0 0 1 1 > 3 0 0 0 255 255 255 2 0 198 0 0 0 191 191 191 0 0 0 198 125 205 1 1 > 1 1 0 0 0 0; > #P newex 134 270 55 196617 zl group 3; > #P newex 134 245 37 196617 zl rev; > #P newex 39 163 66 196617 jit.rgb2luma; > #P user jit.fpsgui 39 504 60 196617 0; > #P toggle 222 132 15 0; > #P message 222 169 45 196617 mode $1; > #P comment 132 169 78 196617 try banging; > #P message 164 80 31 196617 start; > #P message 134 80 27 196617 stop; > #P newex 71 190 150 196617 jit.matrix 1 char 16 1 @thru 0; > #P button 112 167 15 0; > #P user jit.pwindow 38 369 162 122 0 1 0 0 1 0; > #P newex 71 218 131 196617 jit.iter; > #B color 5; > #P flonum 198 60 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; > #P message 198 80 42 196617 rate $1; > #P message 104 80 28 196617 read; > #P flonum 73 59 35 9 0.5 0 1 3 0 0 0 221 221 221 222 222 222 0 0 0; > #P toggle 39 59 15 0; > #P newex 39 79 44 196617 metro 2; > #P newex 39 118 103 196617 jit.qt.movie 320 240; > #P user jit.pwindow 214 368 162 122 0 1 0 0 1 0; > #P connect 3 0 2 0; > #P fasten 13 0 1 0 169 106 44 106; > #P fasten 12 0 1 0 139 106 44 106; > #P fasten 5 0 1 0 109 106 44 106; > #P fasten 6 0 1 0 203 106 44 106; > #P fasten 2 0 1 0 44 111 44 111; > #P connect 1 0 18 0; > #P connect 18 0 9 0; > #P connect 9 0 17 0; > #P fasten 18 0 11 0 44 185 76 185; > #P fasten 10 0 11 0 117 185 76 185; > #P connect 11 0 8 0; > #P fasten 15 0 8 0 227 212 76 212; > #P connect 4 0 2 1; > #P fasten 8 1 19 0 139 235; > #P connect 19 0 20 0; > #P fasten 8 0 20 0 76 265 139 265; > #P connect 20 0 23 0; > #P connect 7 0 6 0; > #P fasten 11 0 0 0 76 211 60 211 60 353 220 353; > #P connect 0 0 21 0; > #P connect 22 0 21 0; > #P connect 16 0 15 0; > #P pop; > > > -- > jtdancemusician