The camera is a GE easycam (found in basement...)

The console message that seems to appear when I start up BBTouch is:

8/15/08 11:51:13 AM kernel USBF: 469.551 IOUSBPipe[0x2bc9900]:ClosePipe for address 2, ep 4 had a retain count > 1.  Leaking a pipe

...does this console message indicate that the camera is where the problem lies? (Total shot in the dark based on the USB & IO....)

LOL! and indeed when I unplug the camera it shuts down BBTouch. (why didnt I try that before?  I guess yanking hardware makes me a little nervous)

Hey samalotriviera,

got your email, thanks for that

definitely sounds like it is a problem with the USB drivers for the camera.  Are there newer drivers that you can get?

That said, there may be something that BBTouch is doing (or not doing that it should be) that is causing the problem.  You say you get that error when you open BBTouch? (as opposed to when it tries to close?)

I will have a look and double check my sequence grabber stuff. (altho i am right in the middle of a big calibration upgrade so if i do find something it may have to wait a week or so before i can get it into the repository.)

cheers!
-panda

Thanks Ben!  I’ll sniff around the net for drivers but in all reality i should probably just get a better camera...I have a feeling that it’s all camera and not BBTouch so much.

Take your time my man! You’ve done quite a bit for the community and we appreciate it!

This is the entire output from a (start up) of BBTouch:

8/16/08 9:58:57 AM kernel USBF: 6606.821 IOUSBPipe[0x4c0f3c0]:ClosePipe for address 2, ep 3 had a retain count > 1.  Leaking a pipe
8/16/08 9:58:57 AM kernel USBF: 6606.834 IOUSBPipe[0x4bfe640]:ClosePipe for address 2, ep 3 had a retain count > 1.  Leaking a pipe
8/16/08 9:58:57 AM kernel USBF: 6606.843 IOUSBPipe[0x4c00c40]:ClosePipe for address 2, ep 3 had a retain count > 1.  Leaking a pipe
8/16/08 9:58:57 AM kernel USBF: 6606.851 IOUSBPipe[0x4c9fb40]:ClosePipe for address 2, ep 3 had a retain count > 1.  Leaking a pipe
8/16/08 9:58:57 AM kernel USBF: 6606.859 IOUSBPipe[0x2f71dc0]:ClosePipe for address 2, ep 4 had a retain count > 1.  Leaking a pipe
8/16/08 9:58:57 AM kernel USBF: 6606.865 IOUSBPipe[0x4c296c0]:ClosePipe for address 2, ep 3 had a retain count > 1.  Leaking a pipe
8/16/08 9:58:57 AM kernel USBF: 6606.872 IOUSBPipe[0x4cba6c0]:ClosePipe for address 2, ep 3 had a retain count > 1.  Leaking a pipe
8/16/08 9:58:57 AM kernel USBF: 6606.880 IOUSBPipe[0x4c0f3c0]:ClosePipe for address 2, ep 4 had a retain count > 1.  Leaking a pipe
8/16/08 9:58:57 AM kernel USBF: 6606.895 IOUSBPipe[0x4c00c40]:ClosePipe for address 2, ep 3 had a retain count > 1.  Leaking a pipe
8/16/08 9:58:57 AM BBTouch[571] sample time too long throw it out: 0.747896

samalotriviera,

yikes, yeah that doesn’t bode well for the camera drivers.  I really hate to lay blame on some other bit of code, bit i am not sure there is much i can do to the BBTouch code to help that :-(

the last ditch effort (if you want to) would be to go into the code and add some old-school debugging: (since breakpoints wont really help since it appears to be an outside driver issue)

in the file CSGCamera.m

there are two methods that deal with the camera startup:
- (id) init
and
- (BOOL)startWithSize:(NSSize)frameSize;

you can go into those methods and
put in a boatload of NSLog(@"sumthin sumtin"); type comments so you can see when the error occurs in the bbtouch timeline

an example: in the start with frame
these two lines:

// Set the channel’s bounds
theErr = SGSetChannelBounds(channel, &boundsRect);

would be changed to look like:
// Set the channel’s bounds
NSLog(@"trying to set channel bounds");
theErr = SGSetChannelBounds(channel, &boundsRect);
NSLog(@"did set channel bounds");

and do that with every call to the sequence grabber in both methods (looks like about a dozen calls or so) and then open up BBTouch and look at the logs, you should be able to tell at which point the driver problem starts.

Anyhow, new drivers would be the best solution. but if you get bored and put in a bunch of logs and send me the results, i can have a look to see if there is possibly (not probable) something i could do.

Cheers!
-panda

Thanks Ben.

I’ll just keep yanking the cam as the Maccam drivers haven’t been updated since June ...and GE offers no drivers for OS X (and I should just get a better camera sometime soon...I mean GE easycam, really!?! hahaha).  Thanks for taking the time to help me out on this issue.  BBTouch is the ‘bizomb’.