Post here to ask any questions about hardware suitability, configuration in ZoneMinder, or experiences. If you just want to know if something works with ZoneMinder or not, please check the Hardware Compatibility sections in the forum, and the Wiki first. Also search this topic as well.
c0nf wrote:im running ubuntu 10.10 server, and when i try to make driver for my tw6805, this is what happened.
root@server:~/tw68-v2# make
make -C /lib/modules/2.6.35-27-generic-pae/build M=/root/tw68-v2 modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.35-27-generic-pae'
CC [M] /root/tw68-v2/tw68-core.o
/root/tw68-v2/tw68-core.c: In function ‘tw68_dma_free’:
/root/tw68-v2/tw68-core.c:113: warning: passing argument 1 of ‘videobuf_waiton’ from incompatible pointer type
include/media/videobuf-core.h:172: note: expected ‘struct videobuf_buffer *’ but argument is of type ‘struct videobuf_queue *’
/root/tw68-v2/tw68-core.c:113: warning: passing argument 2 of ‘videobuf_waiton’ makes integer from pointer without a cast
include/media/videobuf-core.h:172: note: expected ‘int’ but argument is of type ‘struct videobuf_buffer *’
/root/tw68-v2/tw68-core.c:113: error: too many arguments to function ‘videobuf_waiton’
make[2]: *** [/root/tw68-v2/tw68-core.o] Error 1
make[1]: *** [_module_/root/tw68-v2] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.35-27-generic-pae'
make: *** [all] Error 2
I've a TW6805A chip based card with 16 outputs. Installed correctly with Andreoli driver's under ubuntu 10.10, system added 8 inputs to dev dir (video0 - video7) and it works correctly only if I use one camera for every input device. When I add second camera on same video device (on zm channel1) the image alternates colours and b/w and sometime strange purple stripes appears. Anyone had same problem and has managed to solve it?
Also I've got a system iso from a complete DVR that use a soft linux distro (don't know which) and seems to works perfectly with techwell 68xx cards. I'd want to extract module driver from it but my linux knowledge are too low, is ther anyone capable to do it?
Adjust options::config::CAPTURES_PER_FRAME to a value of two or more.
ZM_CAPTURES_PER_FRAME
If you are using cameras attached to a video capture card which forces multiple inputs to share one capture chip, it can sometimes produce images with interlaced frames reversed resulting in poor image quality and a distinctive comb edge appearance. Increasing this setting allows you to force additional image captures before one is selected as the captured frame. This allows the capture hardware to 'settle down' and produce better quality images at the price of lesser capture rates. This option has no effect on (a) network cameras, or (b) where multiple inputs do not share a capture chip. This option addresses a similar problem to the ZM_V4L_MULTI_BUFFER option and you should normally change the value of only one of the options at a time.
I've already tried with 2,3 and 4 with no success. I've no interlaced frames, problem is with colors. With two cameras on same device images become in grayscale with only few frames in full color and this annoying purple/blu stripes effect at regular intervals.
bb99 wrote:Adjust options::config::CAPTURES_PER_FRAME to a value of two or more.
ZM_CAPTURES_PER_FRAME
If you are using cameras attached to a video capture card which forces multiple inputs to share one capture chip, it can sometimes produce images with interlaced frames reversed resulting in poor image quality and a distinctive comb edge appearance. Increasing this setting allows you to force additional image captures before one is selected as the captured frame. This allows the capture hardware to 'settle down' and produce better quality images at the price of lesser capture rates. This option has no effect on (a) network cameras, or (b) where multiple inputs do not share a capture chip. This option addresses a similar problem to the ZM_V4L_MULTI_BUFFER option and you should normally change the value of only one of the options at a time.
Performance when using Video 4 Linux devices is usually best if multiple buffers are used allowing the next image to be captured while the previous one is being processed. If you have multiple devices on a card sharing one input that requires switching then this approach can sometimes cause frames from one source to be mixed up with frames from another. Switching this option off prevents multi buffering resulting in slower but more stable image capture. This option is ignored for non-local cameras or if only one input is present on a capture chip. This option addresses a similar problem to the ZM_CAPTURES_PER_FRAME option and you should normally change the value of only one of the options at a time.
yes, I did. Also I've tried to decrease camera resolution and set different palette
bb99 wrote:Did you also try disabling ZM_V4L_MULTI_BUFFER?
ZM_V4L_MULTI_BUFFER
Performance when using Video 4 Linux devices is usually best if multiple buffers are used allowing the next image to be captured while the previous one is being processed. If you have multiple devices on a card sharing one input that requires switching then this approach can sometimes cause frames from one source to be mixed up with frames from another. Switching this option off prevents multi buffering resulting in slower but more stable image capture. This option is ignored for non-local cameras or if only one input is present on a capture chip. This option addresses a similar problem to the ZM_CAPTURES_PER_FRAME option and you should normally change the value of only one of the options at a time.
Also I've tried to decrease camera resolution and set different palette
Just guessing: All monitors set up on a single device (chip), using different channels, must be configured exactly the same with the exception of the channel number. An example: a monitor using /dev/video0 channel 0 and another monitor using /dev/video0 channel 1 must be set up identical to each other.
yes, I've configured all the monitors with the same specifications
bb99 wrote:
Also I've tried to decrease camera resolution and set different palette
Just guessing: All monitors set up on a single device (chip), using different channels, must be configured exactly the same with the exception of the channel number. An example: a monitor using /dev/video0 channel 0 and another monitor using /dev/video0 channel 1 must be set up identical to each other.
I also have a TW6805 card. 8 chips 16 channels. If i connect two cameras to the same chip or simple enable the second channel on a chop. both channels become gray (no color). but if only channel 0 is declared on zonemonder, there is color image.
gola10 wrote:I also have a TW6805 card. 8 chips 16 channels. If i connect two cameras to the same chip or simple enable the second channel on a chop. both channels become gray (no color). but if only channel 0 is declared on zonemonder, there is color image.
Same problem here and still not solved. I think it's a driver issue, I've tried all possible settings!
I really hope this driver gets in the main stream kernel finally got one myself. The techwell cards are mutch better than the old bttv we have all been useing and the techwells are stupid cheap.
I get 7.5 FPS out of a Teachwell6805 chip on my bttv i got 4.5. Sharing 1 chip with 2 cams. Wow.
Any idea if the Techwell6868 is suported? PCI-E and 4 inputs on a chip.
The card appears to work, but when there is movement, for instance someone walking past the camera, then the edge of the moving part (person in this case) is zigzag with black lines in, the rest of the image is fine.
If my description of the problem is a bit unclear I can post one of the captured images.
