1-chip bt878 4 cam PCI card.
As subject suggests, camera one cycles through all cameras. Funny thing, off Melin's liveCD, and after the install, it worked fine as video(0). Only after I added cameras 2-4 at video(1-3) did cam1 start to cycle.
I know I'm a noob, haven't yet tried to set my camera as type 77 yet, but the reading is taking too long (2-3 days while working, it's a work machine, and I'm constantly interrupted).
I'm just asking for help so that I can get at least some barebones functionality for the months-long process that it will take for me to finish learning and tweaking it further. There's so much!
The other three cameras are on mocord already, with some fun zones, but this last angle misses much information.
One more thing, would an XP3000 drive this baby with ample headroom, or should I go dual core?
camera one cycles through all cameras SOLVED
camera one cycles through all cameras SOLVED
Last edited by eh_ch on Thu Oct 02, 2008 4:51 pm, edited 1 time in total.
-h
Depending on what your watching that it's cycling in, it's an expected behavior as a single chip can only see one input at a time so zm has to scan though the inputs to grab an image from each configured input. Any external applications will see it scanning though where in zm it will just appear as one input.
right, should have clarified. happens on cam1 view and in "montage". the "Cycle" function is separate, and I am aware of it. I am also aware that the chip switches very quickly through the separate ports when displaying montage, and switches at a longer, user defined interval when cycling.
When I say cam1 view, i mean the view from camera one, which should be the view from my first camera. If I choose cam2, I see the view from camera two. cam3, view from camera 3 and cam4 you can guess.
So I turn on cam1, and all I see are half frames of all the different cameras drawing over each other. It's very noisy. I could remove all of the other cameras again to verify that cam1 is capable of delivering a steady picture, but it's too much work to undo and then do again (very laggy AthlonXP2100). And, as I said, I know that cam1 worked before all of the other cameras were added. The machine has been rebooted at least 4 times after the initial install.
It has just occurred to me that I can verify cam1 without hassle by booting from the liveCD. This I will do.
When I say cam1 view, i mean the view from camera one, which should be the view from my first camera. If I choose cam2, I see the view from camera two. cam3, view from camera 3 and cam4 you can guess.
So I turn on cam1, and all I see are half frames of all the different cameras drawing over each other. It's very noisy. I could remove all of the other cameras again to verify that cam1 is capable of delivering a steady picture, but it's too much work to undo and then do again (very laggy AthlonXP2100). And, as I said, I know that cam1 worked before all of the other cameras were added. The machine has been rebooted at least 4 times after the initial install.
It has just occurred to me that I can verify cam1 without hassle by booting from the liveCD. This I will do.
-h
What returns from
Code: Select all
dmesg |grep bttvThanks for your time. dmesg |grp bttv yields:
bttv: driver version 0.9.16 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 17) at 0000:00:06.0, irq: 10, latency: 64, mmio: 0xdfdfe000
bttv0: subsystem: 82cd:a111 (UNKNOWN)
bttv0: using: *** UNKNOWN/GENERIC *** [card=0,autodetected]
bttv0: gpio: en=00000000, out=00000000 in=00feffff [init]
bttv0: using tuner=-1
bttv0: i2c: checking for MSP34xx @ 0x80... not found
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
bttv0: i2c: checking for TDA9887 @ 0x86... not found
bttv0: registered device video0
bttv0: registered device vbi0
what's it look like, doc?
bttv: driver version 0.9.16 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 17) at 0000:00:06.0, irq: 10, latency: 64, mmio: 0xdfdfe000
bttv0: subsystem: 82cd:a111 (UNKNOWN)
bttv0: using: *** UNKNOWN/GENERIC *** [card=0,autodetected]
bttv0: gpio: en=00000000, out=00000000 in=00feffff [init]
bttv0: using tuner=-1
bttv0: i2c: checking for MSP34xx @ 0x80... not found
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
bttv0: i2c: checking for TDA9887 @ 0x86... not found
bttv0: registered device video0
bttv0: registered device vbi0
what's it look like, doc?
-h
Really, I'm not a dumb guy, but...
Yep. Only cam1 was on Video0 channel 0.
The others were on Video channels (1-3). As in no numerical suffix to video, and I didn't notice until I went back in to check.
I had assumed that I was already on video0, because I would have expected black screens if I had gotten the video0 thing wrong. Trust me, I had been reading for almost a week, had read that video0 thing enough times, thought I had it licked.
What disppoints me most is that I never noticed in the ZM Console window where everything is so nicely lined up. I've combed spreadsheets and code, and photo-hunt before, but I didn't catch that cam1 had the extra digit in the source column until just now.
To be super clear, ISSUE RESOLVED IN LESS THAN A DAY. I WAS NOT CAREFUL ENOUGH. I'll be bugging you guys in the next few months, but only after significantly more homework.
Thanks again,
-h
Yep. Only cam1 was on Video0 channel 0.
The others were on Video channels (1-3). As in no numerical suffix to video, and I didn't notice until I went back in to check.
I had assumed that I was already on video0, because I would have expected black screens if I had gotten the video0 thing wrong. Trust me, I had been reading for almost a week, had read that video0 thing enough times, thought I had it licked.
What disppoints me most is that I never noticed in the ZM Console window where everything is so nicely lined up. I've combed spreadsheets and code, and photo-hunt before, but I didn't catch that cam1 had the extra digit in the source column until just now.
To be super clear, ISSUE RESOLVED IN LESS THAN A DAY. I WAS NOT CAREFUL ENOUGH. I'll be bugging you guys in the next few months, but only after significantly more homework.
Thanks again,
-h
-h
I spotted it straight away as I also have that card and spent 3 days working it out myself..