|
|
|
|
Highlights >>>>>>
Implementing i-Catcher
Learn how to implement an i-Catcher system, from single camera residential to multi-camera - multi-site. read more... Sample i-Catcher SitesMany thousands of people around the world use i-Catcher software. See i-Catcher images live. read more... Wildlife picture galleryi-Catcher Wildlife captures fantastic scenes from nature. Have a look at some of the best. read more... Capture equipmentFind out about suitable equipment for use with i-Catcher, from cameras to lighting, and more. read more... i-Catcher Business PartnersWould you like to learn more about how to do business reselling i-Catcher solutions? read more... |
Supported Capture Sources USB Webcams, PCI Capture Cards & IP/Network Cameras & Video Servers i-Catcher supports a wide range of capture sources including USB cameras/web cams, composite/S-Video cameras connected by suitable capture device (e.g. PCI capture card), and digital Network/IP cameras and video servers. However, not all devices are compatible, due to limitations involving proprietary interfaces. This limitation is most common on network cameras, but applies to some PCI devices as well. The following is a list of devices that have been tested with i-Catcher, and shows their compatibility. Note that a device being listed here does not guarantee its compatibility with i-Catcher. Any device not listed here is untested, and may or may not be compatible. If you have experience of using i-Catcher with any device not listed here, please contact us with your experience via icatcherenquiries@icode.co.uk. Devices by manufacturer
Capture Devices These cards historically use proprietary drivers which either provide no standard interface at all, or only provide access to one input on multi-input cards. Some people have reported that the more recent WDM drivers provide better support for these cards. These cards use proprietary drivers that do not provide a standard interface, and as such are not supported by i-Catcher. These cards use proprietary driver interfaces to use multiple inputs, and only provide a standard interface to use one input at a time. Euresys PCI/PCI-Express (PCIe) Capture Cards Euresys capture cards provide a standard interface to access multiple inputs simultaneously by default. i-Catcher's compatibility extends to providing a direct interface to the card driver, allowing each input to be used as a single capture source. A full list of supported Euresys cards is here. The Osprey range of cards use standard WDM drivers, but typically for only one input at a time. i-Catcher Video Server will allow multiple inputs by use of input switching, at the cost of heavily reduced framerate. The Hauppauge range of PCI cards have historically been completely compatible with i-Catcher with the limitation that only one input may be used at a time. More recent revisions of the Hauppauge drivers seem to have broken compliance with the WDM standard and now only operate with the supplied Hauppauge software. Our enquiries to Hauppauge on this matter have been ignored by Hauppauge. The same is true for USB devices, as Hauppauge now uses a "unified" driver for both PCI and USB devices. There are a number of cards being sold on the online auction site eBay that are advertised as "DVR" cards, often promoting connection of up to 4 cameras at once. Unfortunately, this description is a little misleading. The cards are nearly always BT878-based cards (the same chip used in the WinTV series, the Osprey cards, the Euresys cards, and 90% of all other PCI video capture cards). The software supplied with them that allows multiple camera connections is the Pico 2000 software and driver, which is not a WDM standard compliant driver and will not operate with i-Catcher. It is possible to install a generic driver for these cards, however it will typically only allow one input to be used at a time. IP/Network Cameras & Video Servers The following cameras/video server devices are listed by manufacturer, along with any notes on compatibility and setup with i-Catcher. Key
Still JPEG: Images are captured by repeatedly requesting a single JPEG image file from the network device. This is slower than MotionJPEG, as there is the additional overhead of repeatedly connecting and disconnecting, and the camera processing the request. MotionJPEG: Images are captured by making a single connection to the network device, and requesting a MotionJPEG stream. The device then continuously sends video frames as JPEG images on the same connection. This is the preferred method for i-Catcher network video capture. NC601
 These devices use a proprietary image protocol and are not compatible with i-Catcher.
AL9603
 AL9643
 AL9663
AL9684
AL9685
The IP module on these cameras appears to be rebranded Aviosys 9000 device.
All Models
These devices use a proprietary image protocol and are not compatible with i-Catcher.
AIC250W
These devices appear to be rebranded CellVision devices. Supports MotionJPEG only when used without authentication.
All Models
These appear to be a rebranded Toshiba IK-WB11A. Compatible with i-Catcher.
CAM414
CAM415
These devices use a proprietary image protocol and are not compatible with i-Catcher.
IP Kamera 9000
IP Kamera 9000A
IP Video 9100
IP Video 9100A
IP Video 9100B
IP Kamera 9060A
IP Kamera 9060A MP
The IP Video 9100/A/B functions best as a single channel device. Multi-channel capture is supported by i-Catcher Console only, and reduces framerate per channel.
All Models
 These appear to be rebranded Gadspot devices, and support varies depending on camera model. Specific camera support has not been confirmed.
All Models
These devices use a proprietary image protocol and are not compatible with i-Catcher.
All Models
All the current cameras and video servers are fully compatible with i-Catcher, including PTZ support. PTZ Support for the Axis 212 Virtual PTZ camera will only operate correctly when the camera is zoomed in fully. Some older camera models with very old firmware are not supported due to limitations imposed by the manufacturer.
BE-1200
BE-1200W
BE-1202
BE-1203
BE-3201
BE-4211
BE-4240
These appear to be rebranded Videology cameras.
IP-630
IP-630W
Other Models
These appear to be rebranded CellVision cameras. Support for other models than those above may vary.
All models
These devices use a proprietary image protocol and are not compatible with i-Catcher.
CAR-RS250IP
CAR-R250IP
CAR-R300IP
The CAR-R250IP and CAR-R300IP cameras both have two variations and the supported features are dependant on the firmware version in use.
VB-C50i
Other models may also be supported.
All Models
These appear to be rebranded CellVision devices, and support varies depending on camera model. Specific camera support has not been confirmed.
All Models
There does not appear to be an actual CellVision branded camera, however they are rebranded by a large number of manufacturers. The basic configuration supports still JPEG, but not a MotionJPEG stream. Rebranded CellVision cameras should be compatible with i-Catcher in still JPEG mode.
DCS-900
DCS-900W
DCS-950
DCS-1000
DCS-1000W
DCS-2000
DCS-2100+
DCS-5220
DCS-5300
DCS-6620
DCS-6620G
Support varies between models. No models support MotionJPEG streams.
IP-230E
IP-230W
Other Models
The IP-230E/W appear to be rebranded CellVision devices, and support varies depending on camera model. Specific camera support has not been confirmed.
PTC-200 Series
PTC-400 Series
PTC-402C
Please note that the PTC-402C is different to the rest of the 400 series cameras and as such the video streaming and PTZ do not work in i-Catcher.
C800IP
These appear to be rebranded CellVision cameras. Support for other models than those above may vary.
All models
These devices use a proprietary image protocol which is not yet compatible with i-Catcher. We are looking to add support at a later date.
FW-1130
FW-3110
Other models are untested, but may also work.
NC-800
NC1000
GS1200G
NC4600
Most Other Models
Most of these appear to be rebranded AVIOSYS devices, and are reported to work as such with i-Catcher with the exception of the NC4600 which uses a propreitory format. The NC-800 and GS2300G are unconfirmed.
Grand IP Cam II
Other models are untested, but may also work.
HNC300
HNC320W
These devices appear to be rebranded CellVision devices. Supports MotionJPEG only when used without authentication.
The ICAMView device converts a USB webcam into a network camera. While the documentation shows that the URL http://<username>:<password>@<host>/showimg_pda.cgi should work, we have yet to sucessfully
obtain an image from these devices in anything except a web browser, suggesting a reliance on a complex cookie/session system, which is beyond the scope of i-Catcher's capture source support.
550710
550703
Camera must be set to JPEG mode before it can be used with i-Catcher. Some variants of these cameras may not work using the feed wizard due to a change in the JPEG image path.
All models
These devices use a proprietary image protocol which is not compatible with i-Catcher.
All Models
All models appear to use the same interface, however this has not been confirmed.
WCS-2003
This appears to be a CellVision-based camera, but with a different interface. MotionJPEG stream support is available by alternate protocol.
WVC54G
WVC54GC
WVC200
These cameras will need to be configured to output MotionJPEG rather than MPEG4 to operate with i-Catcher. MotionJPEG support is available by alternate protocol on the WVC54GC and WVC200.
CAS 200
CAS 200W
CAS 390
CAS 501
The Link Server cameras need to switched to Motion JPEG mode to use them with i-Catcher. This is achieved by accessing a hidden URL on the camera. Instructions are provided in the i-Catcher feed wizard on how to do this. Switching to MotionJPEG mode will make the camera's own live view non-functional.
IP Fast Dome Series
These appear to be rebranded Pixord devices and are compatible with i-Catcher's generic Pixord support.
M10 Series
Control of the lens selection is not available in i-Catcher, but the lens selection can be controlled through the camera's web interface independent of i-Catcher's videol capture.
SOHO Camera
This appears to be rebranded Neu-Fusion camera, which in turn appears to be a variant of CellVision. See Neu-Fusion for compatibility.
NCS-230W
NCS-330W
These appear to be variants of the CellVision cameras but with a broken MotionJPEG stream output.
BL-C1
BL-C20
BL-C10
BL-C30
BL-C111
BL-C131
BB-HCM311
BB-HCM331
BB-HCM511
BB-HCM531
BB-HCM515
BB-HCM381
BB-HCE481
BB-HCM580
BB-HCM581
Panasonic IPro range
WV-NM100
WV-NS202A
Some Panasonic cameras (notably the C10/C30) have a limited PTZ interface on the camera that prevents i-Catcher from accurately positioning the camera. This will manifest as auto-tracking losing accuracy of an extended period of time.
All Models
These appear to be rebranded Neu-Fusion cameras. See Neu-Fusion for compatibility.
MDCAS-100IR
MJCAS-210IR
MCAS-300PT
MJCAS-310PTD
MCAS-400PT
The MCAS-400PT uses an RTSP-only stream format and the The MDCAS-100IR uses an ASF format stream, neither of which are currently supported by i-Catcher.
P411
Some older cameras
Some older video servers
The older Pixord devices used the same interface, some with multiple video sources. Newer modesl use a proprietory stream and can't be used in i-Catcher.
ICA-100
ICA-106
ICA-107
ICA-100W
ICA-100PE
ICA-110
ICA-150
ICA-150W
ICA-151
ICA-300
ICA-500
ICA-530
IVS-100
Most of these cameras default to no password for the admin user account. A password will need to be set before i-Catcher can capture from these cameras. The ICA-150 provides MotionJPEG through an alternate protocol, and the camera must be configured to output MotionJPEG before i-Catcher can capture from it.
The ICA-530 camera has two variations and the supported features are dependant on the firmware version in use. IPCAM P1000
IPCAM P1000A
No MotionJPEG support is available on these cameras, and Still JPEG support is unconfirmed.
LN-400
LN-401
These appear to be rebranded CellVision devices, however MotionJPEG is only available if authentication is not used.
All models
These devices are rebranded BSTI cameras and use a proprietary image protocol which is not compatible with i-Catcher.
SNC-P1
SNC-P5
SNC-M1
SNC-M1W
SNC-M3
SNC-M3W
SNC-P1
SNC-CS3P
SNC-CS10
SNC-CS11
SNC-CS50P
SNC-Z20
SNC-DF40
SNC-DF70
SNC-RX550
SNC-RZ25
SNC-RZ30
SNC-RZ50
The M1, M1W, M3 and M3W output MotionJPEG in a format that is not usable by i-Catcher and thus are currently unsupported. Most Sony cameras need to set to JPEG mode before they can be used with i-Catcher. The Z20 is a zoom camera but does not pan or tilt, so support is limited to zooming only. Additionally the zoom control for the Z20 is unreliable due to design problems with the camera's control interface. The CS3P, DF-40 and DF-70 untested.
CAS-330
CAS-330W
These appear to be rebranded CellVision devices.
NetCam SC
Express 6 Video Server
A Motion JPEG stream is available via an alternate protocol.
ANC-600V
ANC-600G
These appear to be rebranded Vivotek cameras. Support for other models than those above may vary.
All models
These devices use a proprietary image protocol which is not compatible with i-Catcher.
IP Cam
Appears to be a rebranded AVIOSYS device.
All models
These devices are based on the ACTi cameras and use a proprietary image protocol which is not compatible with i-Catcher.
IK-WB01A
IK-WB11A
IK-WB15A
IK-WB21A
Toshiba cameras do not use a standard authentication mechanism, so capture from these cameras is only possible when authentication is disabled.
TV-IP100
TV-IP100W
TV-IP201
TV-IP201W
TV-IP301
TV-IP301W
TV-IP400W
TRENDnet rebrand many different manufacturers' cameras. Most of these don't appear to support any kind of image standard (they use proprietary formats), and are probably unusable (we have not confirmed this). The TV-IP400W however appears to be a rebranded CellVision camera without MotionJPEG support, and should work as a Still JPEG capture source.
NW-7500
These appear to be rebranded CellVision cameras, with unconfirmed MotionJPEG support.
VIP 10
No MotionJPEG support.
Observer XT
All Other Models
Most of the Veo cameras (With the exception of the Observer XT) use only their proprietary image formats. i-Catcher is unable to capture from these cameras.
All models
All models appear to use the same interface, however this has not been confirmed.
2000 Series
3000 Series
6000 Series
7000 Series
These cameras don't appear to have any kind of MotionJPEG support.
All models
These devices use a custom streaming protocol which is not compatible with i-Catcher.
Last updated at 10:59 27/03/2008. |
|
|
