|
|
|
i-Catcher Help
Learn how to set up and use i-Catcher's features to their full potential. read more... File download areaDownload all the i-Catcher software products, including legacy versions. 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... CCTV ShopWe have an online shop where you can buy video and capture hardware, as well as i-Catcher bundles at discounted price. read more... |
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. We also provide a programme for manufacturers to ensure their products are supported in future versions of the i-Catcher software. For more information, please see the i-Catcher Manufacturer Support programme. Devices by manufacturer - PCI, PCI-Express and USB devices
Devices by manufacturer - Network/IP devices                                                                                
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 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 Console supports switching inputs on these cards to achieve multiple port use at the cost of reduced framerate. The Osprey-50 USB device will operate with i-Catcher, but is not recommended for long-term use. 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. i-Catcher Console supports switching inputs for multi-port use on capture cards that correctly implement the Microsoft WDM standard for video capture devices and those cards that can be used with the generic BT878 driver, though frame rate will be reduced when more than one input is in use. 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. If you have successfully used a manufacturer and/or model not listed here, please contact us with the details including manufacturer, model, and any URLs and video types used with the camera. 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. Video Stream: iCatcher will use a multi-stream model with two or three streams connected to the camera. One of these will be a low-resolution low-framerate stream (if available at the device) for motion detection, with a second stream at higher quality and framerate recorded to disk. A third stream may sometimes be used for live display. The format of the recorded and live display streams will be MotionJPEG or H.264 depending on device. Some devices support multi-streaming in either format. Audio Support
Audio is supported on cameras that are able to provide an audio track accompanying the H.264 video track over an RTSP connection. To be usable with iCatcher the audio track must be 8kHz G.711 (aka μLaw) format. Some cameras support multiple audio formats and will need to be configured appropriately for audio support to operate correctly. Eyseo TV 7240/7230 PTZ
    PTZ is via the simple mode driver. Please contact us if you need PTZ support with this camera.
NC601
These devices use a proprietary image protocol and are not compatible with i-Catcher.
AL9603
 AL9643
AL9663
AL9684
AL9685
AL9211
AL9211W
ALC-9272
ALS-7743
The IP module on these cameras appears to be rebranded Aviosys 9000 device. When using the AL7743 in RTSP mode the analytic stream will be fixed to D1 resolution.
Older Models
Newer Models
ACM-1231
ACM-1232
ACM-3311
ACM-3511
ACM-4200
ACM-4201
ACM-5611
ACM-7411
ACTI2200
TCM-1231
TCM-1511
TCM-3401
TCM-3411
TCM-3511
TCM-4201
TCM-5311
TCM-5601
TCM-5611
TCM-7411
TCM-7811
The older variants of the ACTi cameras use a proprietary image protocol and are not compatible with i-Catcher. Newer models have a MotionJPEG stream availale that is supported by i-Catcher Console 3.3 onwards. MotionJPEG support appears to be firmware dependent (meaning older models may be upgradeable) but we have not confirmed this. Audio is not currently supported from ACTi devices because the audio stream is delivered in a way that is not compatible with iCatcher at this time.
AIC250
AIC250W
AIL310
AIC500
SkyIPCam 747W
These devices appear to be rebranded CellVision devices. Supports MotionJPEG only when used without authentication. AIL310 Appears to be a Planet ICA-110 clone and only supports still JPEG.
WL-5420CAM
These devices use a proprietary streaming format and are not compatible with i-Catcher.
All Models
These appear to be a rebranded Toshiba IK-WB11A. Compatible with i-Catcher.
Arecont 8360
Arecont 3100
Arecont 3105
As far as we are aware, all models of Arecont Vision cameras use the same interface. Please contact us if you have an Arecont Vision camera that behaves differently.
CAM414
CAM415
These devices use a proprietary image protocol and are not compatible with i-Catcher.
SF1301
Appears to be a clone of the D-Link DCS-2102.
IP Kamera 9000
IP Kamera 9000A
IP Video 9100
IP Video 9100A
IP Video 9100B
IP Kamera 9060
IP Kamera 9060A MP
IP Kamera 9060-I
IP Kamera 9060 O
IP Kamera 9070
IP 9360Q
IP 9360QW
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. The 9060 models (except the IP Kamera 9060) use a broken HTTP/authentication mechanism and can not currently be supported. The 9360 models use a proprietary format.
All Models
 These appear to be rebranded Gadspot devices, and support varies depending on camera model. Specific camera support has not been confirmed. Please see Gadspot for further compatibility information.
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 and I/O support. i-Catcher supports MPEG4 and H.264/RTSP streams on cameras with appropriate capability. 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. Audio is supported on Axis devices with a built-in microphone or line in/microphone input.
iDC-421M
Video Stream 2 must be configured to JPEG mode for use with i-Catcher.
BD4070DH
This camera will need to be configured with MJPEG support under the Streaming/Video Format settings of the camera. The first stream needs to be H264 to use RTSP mode. The Motion JPEG stream is on port 8008 and will be need to be set if configured manually.
All Models
The Bikal IP Cameras appear to be rebranded AVTech cameras. They have MotionJPEG via RTSP over HTTP, which is not currently supported in i-Catcher.
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.
Dinion range
VG4 500i series
NWC-0455
NWC-0495
NWC-0700
NWC-0800
NBC-225-P
NBC-255-P
Motion JPEG is not available but the still JPEGs support a high frame rate.
PD100H
All models
These devices use a proprietary image protocol and are not compatible with i-Catcher.
CAR-RS250IP
CAR-R250IP
CAR-R300IP
CAR-R3020HQIP
The CAR-R250IP and CAR-R300IP cameras both have two variations and the supported features are dependant on the firmware version in use. Some firmwares drop support for single JPEG. For these devices, MotionJPEG support is available via alternate protocol.
VB-C50i
VB-C300
Other models may also be supported. The VB-C300 does not appear to support single JPEG images, and MotionJPEG support has not been confirmed.
PVC300
Some cisco cameras are based on Vivotek models while athers are based on Linksys.
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-910
DCS-920
DCS-950
DCS-1000
DCS-1000W
DCS-2000
DCS-2100+
DCS-2102
DCS-2121
DCS-3410
DCS-5220
DCS-5230
DCS-5300
DCS-5300W
DCS-5300G
DCS-6511
DCS-5610
DCS-6620
DCS-6620G
DVS-104
Support varies between models. No models support MotionJPEG streams, with the exception of the DCS-2102 and the DVS-104 video server. PTZ support for the DCS-5220 is inaccurate, and has been disabled.
EX36
EX85
The EX85 is based on the Arecont Vision cameras. The EX36 uses a proprietary video format which is incompatible with i-Catcher.
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.
IC-1500
IC-1500Wg
IC-3010
These cameras are based on Planet ICA-107 cameras.
PTC-200 Series
PTC-400 Series
PTC-402C
Please note that the PTC-402C may require a firmware update to operate with i-Catcher in MotionJPEG mode.
C800IP
These appear to be rebranded CellVision cameras. Support for other models than those above may vary. It has been reported that some versions of the C800IP do not work with MotionJPEG.
EST-IP901
The EST-IP901 uses an unsupported proprietary image format only. Support for other devices may vary.
Original Series Models
EV6150A
EV6151A
EV6153A
EV6156A
EV6551A
EV6552A
EV6552R
EV6353A
EV6355A
EV6356A
EV6250A
EV3150A
EV3151
EV3151A
EV8150A
EV6750
EV8180A
EV8180U
EV8180F
EV8280U
EV8383F
EV8580A
EV8580U
EV8580F
EV8780A
EV8780U
EV8781A
EV8781U
EV8781F
EV8782A
EV8782U
Original Series Etrovision devices are supported via alternate protocol.
FW-1130
FW-3110
Other models are untested, but may also work.
FI8905W
FI8908W
PTZ for these cameras only allows simple directional control.
FUM T10 II
These appear to be rebranded A-Soni cameras. Video streams are delivered using a proprietary protocol that is not supported by i-Catcher. Other models may be supported.
NC-800
NC1000
GS1200G
NC1600
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 GS1200G are unconfirmed.
ZN-YH305
ZN-D2024A
These cameras are rebrands of the Vivotek FD7131. However, Motion JPEG for the ZN-YH305 is not delivered in a format compatible with i-Catcher. These cameras will need to be put into JPEG mode in the camera's configuration.
All Models
The Genie cameras are supported by the RTSP support in i-Catcher or via a separate protocol. Some newer devices support analytics via a Motion JPEG stream.
Genius IP Cam Secure 300R
Halocam IPC
The Halocam IPC can be used in individual virtual camera mode or in overview image mode. PTZ support is not available in overview mode.
Grand IP Cam II
Other models are untested, but may also work. The Grand IP Cam II seems to have undergone a firmware update in recent versions, breaking the MotionJPEG stream. Please contact us if you require support for this version.
HNC300
HNC320W
These devices appear to be rebranded CellVision devices. Supports MotionJPEG only when used without authentication.
HCV72
HCV73
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. The HCV72/73 devices
will work if the device's firmware is updated to 2.55 or higher, however the device occasionally returns web data instead of an image.
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.
Command View CV-D2000
Please ensure the camera is running the latest firmware.
IQeye302
IQeye855
IQeye832N
IQeye711
Other cameras may be supported but are untested.
Web Camera 5
Appears to be an AVIOSYS based device. MotionJPEG support unconfirmed.
All models
These devices use a proprietary image protocol which is not compatible with i-Catcher.
VN-V25U
VN-V26
All Other Models
Most models appear to use the same interface, however this has not been confirmed. The VN-V25U and VN-V26 cameras require the expected framerate for MotionJPEG to be specified in the URL. i-Catcher defaults this to 10 frames per second, and instructions are provided for changing this.
NT-IPC360
There are two versions of this camera. The newer variant is based on the AVIOSYS 9060 camera, and is supported by an alternate protocol handler. Single JPEG support on the newer variant requires an explicit URL containing camera credentials. Please contact us if you need to connect this camera in this way. The PTZ controls may be supportable using a pre-release PTZ driver for simple devices. Please contact us if you have one of these cameras and would like to test PTZ support.
WCS-2003
FCS-1030
FCS-0040
FCS-1131
This appears to be a CellVision-based camera, but with a different interface. MotionJPEG stream support is available by alternate protocol.
All Models
MotionJPEG is reportedly available from this camera in a standard format, but this has not been confirmed. Please contact us if you would like to use a Linudix camera with i-Catcher.
WVC54G
WVC54GC
WVC200
WVC210
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
WCS-2040
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.
LNE3003
Camera will need to be switched to Motion JPEG mode to be used with i-Catcher.
IP EYE Anywhere
RoboCam 8
RoboCam 21
The IP EYE Anywhere and RoboCam 21 appear to be a TRENDnet TV-IP312 clones. MotionJPEG is supported in Console 3.3 onwards. Other camera models may also be supported.
IP Fast Dome Series
These appear to be rebranded Pixord devices and are compatible with i-Catcher's generic Pixord support. We are aware of a Merti Li-Lin PTZ device, but have not seen one to confirm PTZ support. Please contact us if you have a Merit Li-Lin PTZ camera and would like to use it with i-Catcher.
M6810
This camera is a rebranded AVIOSYS IP Kamera 9060 SL. The MotionJPEG stream is delivered by a broken HTTP connection and can not currently be supported in i-Catcher. The single jpeg support requires a special URL to be used. When adding this camera, select "Custom" as the type, and when prompted for URL, use "/snapshot.jpg?account=username&password=password" (without the quotes). The username and password should be filled in with the details used to log in to the camera. Other models may also be supported.
M10 Series
D12 Series
M12 Series
M22 Series
Q22 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 video capture. MxPEG support is available in i-Catcher Console 3.3 onwards. Other Mobotix cameras should also be supported. The Virtual PTZ of the Q22 is not current supported.
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-C10
BL-C20
BL-C30
BL-C111
BL-C131
BL-C140
BL-C160
BL-C210
BL-C230
BB-HCM311
BB-HCM331
BB-HCM371
BB-HCM381
BB-HCM511
BB-HCM515
BB-HCM527
BB-HCM547
BB-HCM531
BB-HCE481
BB-HCM580
BB-HCM581
BB-HCM735
Panasonic IPro range
WV-NM100
WV-SP105
WV-NP240
WV-NS202
WV-NF284
WV-SP302
WV-NF302
WV-NP304
WV-SP305
WV-SP306
WV-SF332
WV-SF336
WV-SP342
WV-SF346
WV-SW352
WV-SW355
WV-SC385
WV-SW484S
WV-NP502
WV-NW502
WV-NS950
WV-NS954
WV-NW960
WV-NW964
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. When using H.264 over RTSP ensure that streams 1 and 2 ore set to H.264 and Internet mode. Stream 1 will be recorded and stream 2 will be used to show on screen.
All Models
These appear to be rebranded Neu-Fusion cameras. See Neu-Fusion for compatibility.
IXS0
IX10
IXE10
IXE20
IX30
IMS0
IM10
IDS0
ID10
IDE10
IDE20
ID30
IES0
IE10
IEE10
IEE20
IE30
All Sarix Models
Other cameras may be supported but are untested.
MDCAS-100IR
MJCAS-210IR
MCAS-300PT
MCAS-300PTW
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
P423
Some older cameras
Some older video servers
The older Pixord devices used the same interface, some with multiple video sources. Newer models use a proprietory stream and can't be used in i-Catcher.
ICA-100
ICA-100W
ICA-100PE
ICA-106
ICA-107
ICA-107P
ICA-107W
ICA-108
ICA-108W
ICA-110
ICA-150
ICA-150W
ICA-151
ICA-300
ICA-312 *
ICA-500
ICA-510
ICA-530
ICA-530N
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. MotionJPEG is available on the ICA-108/W via alternate protocol. The ICA-510 does not support HTTP/1.1 requests for the MotionJPEG stream, and its single snapshot JPEG image must be updated by another request, and is therefore not supportable in i-Catcher. * The ICA-312 is unconfirmed. IPCAM P1000
IPCAM P1000A
No MotionJPEG support is available on these cameras, and Still JPEG support is unconfirmed.
VCC-HD2500P
VCC-HD4000P
VCC-HD4600P
VCC-HD5400P
VCC-HD5600P
VDC-HD3500P
G1 Devices
G2 Devices
G3 Devices
SerComm devices are rebranded by a number of manufacturers. They also sell a few of their own cameras. Please contact us if you have a SerComm branded device to determine if support is available.
SCNC2607
SCNC3606
The SCNC2607 is a Y-Cam clone and works with both JPEG and MotionJPEG. Other Sharx models may be supported.
LN-400
LN-401
These appear to be rebranded CellVision devices, however MotionJPEG is only available if authentication is not used.
C1002
C1212HW
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-CH120
SNC-CS3P
SNC-CS10
SNC-CS11
SNC-Z20
SNC-CS50
SNC-DF40
SNC-DF50
SNC-DF70
SNC-DF80
SNC-DH120
SNC-DM110
SNC-RS46
SNC-RZ25
SNC-RZ30
SNC-RZ50
SNC-RX550
SNC-RX570
SNC-RH164
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 N/P suffix denotes NTSC or PAL variant. Support is identical between NTSC and PAL variants of any given camera.
The RS46 and CH120 models require that Image 2 and Image 3 in the camera's settings are both set to use the JPEG codec and that Image 2 is set to 320x240. For best performance the framerate for Image 2 should be set to 8. CAS-330
CAS-330W
These appear to be rebranded CellVision devices.
NetCam SC
Express 2 Video Server
Express 4 Video Server
Express 6 Video Server
A Motion JPEG stream is available via an alternate protocol.
Son-IPC1
This appears to be a FosCam clone and uses the Simple PTZ driver available on request.
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.
Max-IP-Cam
Appears to be a rebranded AVIOSYS 9060 camera, but with a broken MotionJPEG stream. This camera may now operate with the AVIOSYS support in Console 3.3 onwards. Please contact us if you would like to use one of these cameras with i-Catcher.
IP Cam
Appears to be a rebranded AVIOSYS device.
All models
These devices are based on the ACTi cameras. These may work using the ACTi camera support. Please contact us if you have a Topica camera so we can confirm support.
TS802
The TS802 is based on a Zavio device as uses a broken web server to provide MotionJPEG streams which is not currently compatible with i-Catcher. Other models may be supported.
IK-WB01A
IK-WB11A
IK-WB15A
IK-WB16A
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-IP312W
TV-IP400W
TV-IP422
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. MotionJPEG is supported in Console 3.3 onwards.
All Models
These cameras are rebranded Y-Cam cameras.
NW-7500
These appear to be rebranded CellVision cameras, with unconfirmed MotionJPEG support.
USN-141
Seems to be a rebranded Linudix camera, with broken JPEG image encoding.
VG5000
VG5001
These cameras use a proprietary image format that is not compatible with i-Catcher.
VIPC1431EP
VIPC7301EP
These are clones of the newer ACTi cameras, some of which are supported in i-Catcher Console 3.3 onwards. The 7301 does not support MotionJPEG as a streaming video format, and is not compatible with i-Catcher. Other models may be supported.
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.
VHSD810IPEXT
This camera uses a complex custom protocol that is not supported by i-Catcher at this time. This camera may be branded under other manufacturers, including Samsung. Support for other models is unknown.
All models
All models appear to use the same interface, however this has not been confirmed.
VS-IPC1002
Other models may also be supported.
2000 Series
3000 Series
6000 Series
FD6111V
FD6121V
7000 Series
PZ7121
FD7131
PT7135
IP7330
IP8151
IP8161
IP8330
IP8332
IP8362
FD8133
FD8134
FD8161
FD8361
SD8111
SD8121
Video servers
VT2402
VS8102
The older cameras don't have any kind of MotionJPEG support, with the exception of the FD7131, IP7330, VT2402. The IP7330 will need to be put into MotionJPEG mode to be used with i-Catcher.
SPD-160
These cameras don't appear to have any kind of MotionJPEG support.
Y-Cam White
Y-Cam Black
Y-Cam Knight
Y-Cam Bullet
Y-Cam Bullet HD
Support for these cameras is dependant on firmware versions. Instructions are included in the i-Catcher application.
RYK-IP3400E
This camera is based on the original series Etrovision cameras and uses the same protocol.
F721A
All other models
Most of these devices implement MotionJPEG via a broken web server that is not compatible with i-Catcher. Still JPEG uses a complex updating protocol which is not supported by i-Catcher.
Last updated on 07/03/2011. |
|
