Jump to content

jasonkkn

Members
  • Content Count

    23
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. jasonkkn

    Milestone Software

    hi "thewireguys" i don't have preference. That was a generic question which allows me to better understand the background software architecture that Milestone uses. as the size of an installation grows, it becomes more apparent that a video management software with a sound design architecture will withstand scaling. I remember the first few versions of Milestone software (dated some time back to 2003) has a limit of 600,000 images per camera. They were using proprietary database then. I'm not sure how much is done to correct that, as the database is usually considered the core of the coding. (i do not mean to proclaim that I am a programmer; but these are based on fairly generic assumptions). So when I hear dealers propose Milestone for large projects (eg 300 camera systems with alarms and all), i was just wondering if they had incorporated the MS SQL Server 2005 database into ALL their software offerings? I had this suspicion that only the Milestone Corporate works on MS SQL Express / Server database. (Suffice to say that they have positioned themselves as a low- to mid-end solution)
  2. jasonkkn

    Hi There from Singapore

    hi there, just joined this forum not too long, and am still browsing around. Just a little background - was employed by Axis, Bosch, DVTel, and represented them in the Asia Pacific region. I'm not sure what to expect from the forum, but guess it's good to be in like-minded community. cheers. jason
  3. jasonkkn

    Milestone Software

    thanks for taking time out to explain Twilo. i've spoken to a local dealer who handles Milestone, and he does not seem to be able to explain clearly as well. I was looking through www.totalcontrolapp.com - something interesting. Just to clarify - the application communicates directly with the IP camera ya? And not pull video via another application (eg. Milestone, Axis Cam Station...)
  4. jasonkkn

    Milestone Software

    thanks for the reply Twilo. I was trying to figure this out - something the manual does not specify. SQL Express 2005 is the free version from Microsoft, but this version will only database file size to grow up to 4GB. (With previous MSDE database, it was 2GB) I'd like to assume Milestone keeps the system configuration data, maybe even metadata and all relevant system information into this database. When the system is large, more information is stored in the database. What i was trying to find out is this - when i size a system, the free MS SQL Express 2005 is good for system up to x size? x cameras? i hope i am making sense here.
  5. jasonkkn

    Best wireless cctv system

    it's not easy to pin-point a wireless manufacturer that is 'good' in CCTV application. most wireless transmitters were not manufactured to handle video-type of wireless transmissions, until of late (maybe). Even network switches - they were not capable of doing video transmissions for long, until quite recently. Suffice to say there are several considerations to choose your wireless device: 1. What is datarate the IP Camera / Encoder transmits? 1Mbps? 4Mbps? 2. What mode of transmission - unicast TCP? Unicast UDP? Multicast UDP? 3. what type of transport protocol used by the IP Cam / encoder - RTP/ RTSP? 4. does the wireless device support IGMP - for multicast routing? the above questions will help select a wireless product that is more suitable for video transmission. The question on distance, line of sight, signal strength and all also has to be addressed. hope this gives somewhat of an idea.
  6. Milestone software has several catergories - XProtect Central, Transact, Business.... Does anyone know what database they are using? Under what circumstances (eg. where there are 300 cameras recording at 4CIF 30fps for 30days??) does the user need to purchase a MS SQL Server 2005? Thanks...
  7. yup, Pelco got their initial encoders from VCS (a german manufactuer, which was bought out by Bosch in 2004/5) - and they named it PelcoNet. Then Pelco introduced the Endura system - and they made it so difficult for dealers to sell. A Dealer has to pass a NETWORK exam, before they can sit for a Pelco Endura training. And the software runs on Linux - this is a soft-spot for a lot of debate. Suffice to say, how many engineers can be readily find that can support a surveillance application running on LINUX? Yes, DVTel encoders (some) are from Verint. (Verint bought SmartSight years back). Pelco does not make their cameras as well - they just assembled them, and did a great job making them good. The camera modules in the CCTV market is dominated by Sony & Hitachi anyway. So who's to say they make their own camera module....
  8. i understand DVTel's Latitude v5 and above supports Arecont's and even Axis' H24. just take note that at the viewing end (the client workstation), you might require just a little more computational power compared to viewing MPEG4/MJPEG.
  9. i understand Pelco is re-doing their NVR software. Their first version of Endura was based entirely on Linux platforn, which I understand they did not sell alot. (if at all in most countries). The barrier to entry in their first gen Endura was too great for most dealers. Anyway, guess they should be launching their next generation of NVR software before too long. you might want to be sure you got the correct/relevant NVR information.
  10. CMOS vs CCD : usually CMOS will require more light in order for the image quality to be sharp and decent. CCD will generally perform better in lower light conditions when compared to CMOS. However, there are technology (such as PIXIM) that compensates for the lack of sensitivity in the CMOS sensor. As a rule of thumb, the bigger the CCD, the better it is (and the more expensive it is too). Those found in IP cameras are usually 1/4" or 1/3" CCD (interlaced / progressive) In order of image quality, i'd go PROGRESSIVE SCAN CCD > Interlaced CCD > CMOS. because Interlaced CCD will produce a "motion blurr" image when objects are moving, most cam mfg have incorporated a 'deinterlacing' in their decoding software which generally removes this blurring.
  11. jasonkkn

    ONVIF standard

    and i read of the 3 mfg who initiated this (Sony, Bosch, Axis), Axis is not even ready to implement the standard as yet.
  12. Yes, the iP camera has an RJ45 connection. This can either be connected to your network switch or directly to your router which has additional network ports. if you want to configure the camera to be able to transmit video over the INTERNET (which includes recording outside of your LAN), then these are the things you will need to do: 1. assign a local IP address to your IP camera (probably in the 192.168.x.x or whatever the IP addressing schema is being used by your router). 2. then configure your router's NAT to port forward the public ports to the private IP address of your IP Camera. There's a post somewhere ( pardon me, i Can't recall) which details how to configure such a connection. If you have a PoE enabled switch (eg. NetGear's 8port), and the camera is PoE ready, then the power will be provided by the switch to the camera. If your switch is not PoE enabled, then you can opt to purchase a power injector.
  13. yup, you surely do have the options of configuring the motion detection parameters, as well as configuring how and where to send the motion-detected image to. Most brands of network cameras have these features built into it.
  14. jasonkkn

    How to Design Video Surveillance Systems

    hi Jhonovich, Maybe it might be good to also highlight the networking aspect. (ie. multicast, bandwidth consumption, subnetting..) It's an arguable issue - some say it's the IT's side of the responsibility. However, most video surveillance systems are running on their own IT infrastructure. A good understanding of the network field will make the 'video system designer' more complete i think.
  15. Firstly, the video signal from your CCD-based camera is 1Vp-p composite video signal, which is compatible with those of your TV. Now, your camera is connected to the DVR directly. What you need to do is this: 1. remove the existing connection to the DVR 2. the camera is connected to the Coax-splitter (see image). 3. connect the coax-splitter to the DVR 4. have another coax cable from the coax-splitter connect to the BNC-RCA converter (see image) 5. and connect the RCA end into the TV. this should solve your problem
×