No more missed important slingbox 500 user manual pdf updates! The database recognizes 1,746,000 software titles and delivers updates for your software including minor upgrades.
Download the free trial version below to get started. Double-click the downloaded file to install the software. The Premium Edition adds important features such as complete software maintenance, security advisory, frequent minor upgrade versions, downloads, Pack exports and imports, 24×7 scheduling and more. Simply double-click the downloaded file to install it. You can choose your language settings from within the program. Custom gadgetry for the discerning hacker The Store is now open!
The whole reason I looked into buying this setup is that it was cheap. Hooking up the system and using the onscreen menu was fairly easy. DVR is the direction Q-See went with their network interface design and software development. When it comes to network connected video devices, I’m used to the concept of streaming. I’m used to IP video cameras that streaming technologies like MJPEG and MPEG.
While the QSD2316C16-500 DVR locally records analog video using the H. 264 compression codec, it does not stream video in any kind of standard format over the network interface. The DVR does have a web interface, but it is simply is a launchpad for an ActiveX component. This limits you to accessing the DVR via a Windows PC running Internet Explorer. Furthermore, the ActiveX component is highly unstable. I determined I couldn’t even pull a live static JPG snapshot from any of the cameras, let alone get a decent video stream. I called Q-See tech support to find out if there was a developer toolkit or SDK or even just some documentation on how the DVR’s network interface worked, but got shutdown immediately.
I want Q-See to open up documentation for the DVR command and video streaming methods. That, or introduce standard web streaming technologies like MJPEG or MPEG video streams, and utilize those streaming technologies via a standardized web interface. This ActiveX component is ridiculously limiting, and very unstable. I really don’t get why they didn’t create a standard web interface in the first place. I would think it would capture more market share and cost less to dev and support than a wonky ActiveX component. I wonder what their response will be, if any. This entry was posted on Monday, May 11th, 2009 at 10:15 am and is filed under Reviews.
You can follow any responses to this entry through the RSS 2. You can leave a response, or trackback from your own site. Having SDK or at least API documented would not harm Q-See, moreover will help them sell product. For example they implemented remote backup, but it is not sufficient. For instanse lets imagine that intruder has stollen DVR with other valuables.
It makes all this records useless. Adding functionality to send data to remote ftp,e-mail box or what ever on alarm event could bring peace of mind. Wish Q-See to change their mind. I hope you have also filled out the contact form on their website.