Curly

I have three IIDC firewire cameras plugged into a firewire 400 hub, then coming into a macbook pro. This is just a test but I don't understand my results. I only want to grab two cams at any one time, but want to be able to change which two I have open (ie input0 + input1, then change to input0 + input2) .

If I start the patch with all three cams plugged in, then the framerate is unworkable - so I assume I am over the limits of the macbook pro's firewire bus.

BUT, if I start the patch with only two cams plugged in, open them both, THEN plug in the third camera... I am able to switch between input 1 and 2, while input 0 keeps running just as I wanted to - getting 30fps.

Does anyone know why this is, and if there is a way to get this to work starting with all 3 cams plugged in?

(also, would it make a difference if I ran them all in through a firewire 800 hub into a firewire 800 plug? I guess not, right?)

I have three IIDC firewire cameras plugged into a firewire 400 hub, then coming into a macbook pro. This is just a test but I don't understand my results. I only want to grab two cams at any one time, but want to be able to change which two I have open (ie input0 + input1, then change to input0 + input2) . 

(also, would it make a difference if I ran them all in through a firewire 800 hub into a firewire 800 plug?  I guess not, right?)

grab-question

Look at Jitter movie playback optimizations from Vade (

Use @unique 1 for grab object. You can also route the bang signal depending witch camera you use instead of powering all grab objects.

Look at Jitter movie playback optimizations from Vade (http://abstrakt.vade.info/?p=147) 
Use @unique 1 for grab object. You can also route the bang signal depending witch camera you use instead of powering all grab objects.

thanks for your response. actually, I think the fact that the timing 

that different cameras are plugged in affects whether it works or not 

suggests that it is a camera issue. perhaps something to do with 

different compressions, or how the old isight camera is programmed to 

communicate with the computer. i'll post back when I get hold of 

On Mar 22, 2008, at 12:44 PM, jasmin wrote:

> Look at Jitter movie playback optimizations from Vade (

> Use @unique 1 for grab object. You can also route the bang signal 

> depending witch camera you use instead of powering all grab objects.

> #P user jit.fpsgui 492 389 60 196617 0;

> #P user jit.pwindow 491 310 82 62 0 1 0 0 1 0;

> #P newex 492 236 146 196617 jit.qt.grab @unique 1 @input 2;

> #P number 137 21 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 326 124 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P user jit.fpsgui 326 392 60 196617 0;

> #P user jit.pwindow 325 313 82 62 0 1 0 0 1 0;

> #P user jit.pwindow 95 314 82 62 0 1 0 0 1 0;

> #P newex 326 239 146 196617 jit.qt.grab @unique 1 @input 1;

> #P newex 96 237 146 196617 jit.qt.grab @unique 1 @input 0;

thanks for your response. actually, I think the fact that the timing  
that different cameras are plugged in affects whether it works or not  
suggests that it is a camera issue. perhaps something to do with  
different compressions, or how the old isight camera is programmed to  
communicate with the computer.  i'll post back when I get hold of  
three non-isight firewire cameras.

>
> Look at Jitter movie playback optimizations from Vade (http:// 
> abstrakt.vade.info/?p=147)
> Use @unique 1 for grab object. You can also route the bang signal  
> depending witch camera you use instead of powering all grab objects.
>
> just an idea :
>
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P message 64 78 14 196617 3;
> #P user jit.fpsgui 492 389 60 196617 0;
> #P user jit.pwindow 491 310 82 62 0 1 0 0 1 0;
> #P message 548 213 33 196617 close;
> #P message 505 214 30 196617 open;
> #P newex 492 236 146 196617 jit.qt.grab @unique 1 @input 2;
> #P newex 72 117 40 196617 gate 3;
> #B color 5;
> #P message 20 78 17 196617 1;
> #P message 41 78 17 196617 2;
> #P message 0 78 17 196617 0;
> #P number 137 21 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P number 326 124 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P message 326 148 47 196617 input $1;
> #P user jit.fpsgui 326 392 60 196617 0;
> #P user jit.fpsgui 96 388 60 196617 0;
> #P user jit.pwindow 325 313 82 62 0 1 0 0 1 0;
> #P user jit.pwindow 95 314 82 62 0 1 0 0 1 0;
> #P message 382 216 33 196617 close;
> #P message 160 215 33 196617 close;
> #P message 339 217 30 196617 open;
> #P message 122 215 30 196617 open;
> #P newex 96 48 52 196617 metro 33;
> #P toggle 96 23 15 0;
> #P newex 326 239 146 196617 jit.qt.grab @unique 1 @input 1;
> #P newex 96 237 146 196617 jit.qt.grab @unique 1 @input 0;
> #P fasten 24 0 18 0 69 105 77 105;
> #P connect 20 0 19 0;
> #P connect 21 0 19 0;
> #P connect 19 0 22 0;
> #P fasten 18 2 19 0 107 173 497 173;
> #P connect 22 0 23 0;
> #P fasten 18 1 1 0 92 180 331 180;
> #P fasten 18 0 0 0 77 185 101 185;
> #P fasten 17 0 18 0 25 105 77 105;
> #P fasten 16 0 18 0 46 105 77 105;
> #P fasten 15 0 18 0 5 105 77 105;
> #P fasten 3 0 18 1 101 78 107 78;
> #P connect 12 0 1 0;
> #P connect 5 0 1 0;
> #P connect 7 0 1 0;
> #P connect 1 0 9 0;
> #P connect 6 0 0 0;
> #P connect 4 0 0 0;
> #P connect 0 0 8 0;
> #P connect 9 0 11 0;
> #P connect 13 0 12 0;
> #P connect 14 0 3 1;
> #P connect 8 0 10 0;
> #P connect 2 0 3 0;
> #P window clipboard copycount 25;
>
>
> --
> jaz


grab question