TheUberOverLord

You are not going to get 100f of quality night vision any camera unless you have a large lens or get a ptz with optical zoom and strong IR...when you are zoomed in like that you will have a very narrow fov...mount the cameras closer to your target. Perhaps I worded wrong. Some of these nicer Dahua/Hikvision cameras around the $100-180 range state 30m IR range. And I'm sure that's good enough. The camera we have now was purchased at monoprice about 3 years ago for about $180, at that time it was one of their better cameras. It's alright, but I'm not too impressed. So anything better will be great. a 3mp camera I'm sure will impress. Very few cameras live up to their claimed IR ranges of 30m at any good quality at that distance, when the IR lights are in the camera itself. Also, you're better off to have as much IR light as possible for any camera that is 2MP or greater if you truly want to be able to see distances clearly at 100 feet, in near or complete darkness. With high quality. Other advantages of using an external IR light source are that if you decide to get a camera with a zoom lens and/or PTZ. You might see something that you might have not seen at night in the cameras view in better quality which you can now zoom into and/or move the cameras position towards. Some cameras when using their latest firmware can even do "object tracking" so if they have a viewing area that's of quality, the camera can use its PTZ controls and/or its zoom lens to zoom in or out to automatically track objects based on how you set this feature up. That said of course the camera would need to have a high quality view at night to do this correctly. You can set the minimum/maximum size an object must be to auto track it and place restrictions on where in the cameras view an object that meets that criteria should be auto tracked. This make sure your not auto tracking pets or small wild life or auto tracking objects in areas of the cameras view that you wish to exclude. Avoiding false positives. Once tracking is complete, you can set a default zoom and/or PTZ for the camera to reposition to. After the set time of your choice. Hikvision actually has a live camera, that shows this feature in action, working in real-time. Had you not said "About 100 foot of quality night vision would be ideal. No less" then I wouldn't have mentioned this. Operative words being "quality" and "no less". Don

If needed you can purchase an external IR Light source that itself has a sensor that will turn on and off as needed and mount it in the direction that you need to cover. You can use the search engine of your choice using search terms like "ip camera infrared illuminator for night vision". Please note the claimed distance for anything you locate and also make sure others have purchased same and that it has many excellent reviews. If there are few reviews or low rated reviews, please look at another external IR light source product vs. risking getting a lemon. Don

If you could live with automatically refreshed snapshots and shortcuts to media players like VLC for full-motion video for each Network IP Camera as needed. You could use these free methods, like the ones below without adding any hardware expenses for a NVR/DVR. You made no mention of what Foscam Network IP Cameras you currently have. So here are two links to these free methods for all Foscam Network IP Camera models. They both have live demos as well: For Foscam MJPEG based Network IP Camera models: http://foscam.us/forum/free-generic-browser-interface-for-foscam-ip-mjpeg-cameras-t2522.html#p10970 For Foscam H.264 based Network IP Camera models: http://foscam.us/forum/free-generic-browser-interface-for-foscam-h-264-cameras-t4341.html#p20338 Live demos using these free methods showing multiple cameras being displayed at the same time. Two different ways: http://107.170.59.150/foscam/GlobalZoomExample.htm http://107.170.59.150/foscam/FoscamUS.htm These methods actually work with any brand and models of Network IP Cameras that can use HTTP/HTTPS URL's to pull snapshots. These methods are compatible with all Internet browser capable devices running any Operating System and using any browsers. From Computers to Tablets to Phones and TV's. There is no website required to use them. The HTML can be stored locally on any device that wishes to use them. If you did have a website. You could also use a more secure version of these free methods. More details here about that: http://foscam.us/forum/showing-secure-methods-using-php-to-display-your-ip-cameras-t8721.html#p42139 I'm also a U.S. Air Force veteran. Thanks for your service. Don

Live demonstrations of using Hikvision Network IP Cameras in web pages on websites with PTZ ("Pan/Tilt/Zoom") and Preset controls. Which are compatible with any Internet browser capable devices using any Operating System and browser. No browser plugins or media players are required to ever be downloaded and/or installed at anytime. Nothing about the Network IP Cameras are exposed when using any of the examples below. No IP Address, No DDNS, No Port or User Credentials. Time limits can also optionally be imposed to use a button to prompt to continue after a set period of viewing time of your Network IP Cameras has been reached and/or to jump to another web page on your website. To better help limit bandwidth usage and/or abuse. Two Hikvision live examples with PTZ, Presets and Zoom lenses: Indoor Outdoor ("Using 4 and 3 second interval delays respectively") You can also optionally require mandatory User credentials using the values of your choice to access the Network IP Cameras on your website by your website visitors. Same Network IP Cameras and delays as above, User: admin Password: admin Indoor Outdoor HTTPS vs. HTTP can be used as well. Please note that the test server being used for these examples is using a self-signed certificate so you will see a warning when using these example HTTPS links. Same IP Cameras and delays as above: Secure Indoor Secure Outdoor User: admin Password: admin Secure Indoor Login Required Secure Outdoor Login Required Example: Google is now ranking websites that use HTTPS higher than websites that use HTTP: Google Starts Giving A Ranking Boost To Secure HTTPS/SSL Sites The total number of lines of code is less than 200 lines for both the client ("Browser side") and web server side combined, to provide all the functionality you see shown here using these examples. Of course the delays being used in the examples can be removed and the default Network IP Camera images can be larger than the examples used here. You can use the PTZ and Preset controls with live full-motion video or use automatic refreshed images as the examples are using here in your web pages on your websites. Any Hikvision Network IP Camera that has a RS485 interface can also use add on horizontal pan brackets for Hikvision Network IP Cameras that don't/didn't support PTZ when you purchased it. Like these examples: http://www.aliexpress.com/wholesale?catId=0&initiative_id=SB_20150530165206&SearchText=camera+bracket+Electrical+Rotating+255+degree+RS485 Don

Yes. It's opened but it is used for ptp/cloud access not for hacking. This would not cause the issue you are seeing. So please contact your seller as I suggested to in my prior post to see how they say to proceed. Don

You are very welcome. Don

Please contact your seller and ask them how to proceed. Most likely you will need to get the camera replaced. If your seller is Foscam.us, please see this: http://foscam.us/contactus.html Don

You are very welcome. Have you tried using a Ethernet cable without using PoE ("Using the AC/DC adapter for power instead") and do that directly from the camera to the Router/AP? My goal is to try and remove as many things as possible to see if the camera is faulty or something else is contributing to this issue. Don

Yes. I am sorry. Please re-read my post. I edited it after I realized you said you are on current firmware. Don

You are very welcome. What are your video settings and can you try another Ethernet cable connected directly to your Router/AP to see if that makes a difference? Something is obviously different then normal. So, I am trying to remove things to see if the camera itself is faulty. Don

Please see this. It applies to all Foscam IP Cameras MJPEG and H.264 based as well as cameras in wired an wireless modes. It suggests the most stable camera configuration settings: http://foscam.us/forum/post15934.html#p15934 Note: I have all the Foscam IP Camera models. Including this one. I have no issues like this. In wired or wireless modes. Two live Foscam FI9828W IP Cameras using automatic refreshed snapshots also not having any issues: U.S. China Please also verify you are using the most current firmware as well: http://www.foscam.com/down3.aspx Don

38 Unique Live Demos Using Live Automatic Refreshed Snapshots From Many Different IP Camera Brands and Models. Using free Interface. Because IP Cameras used in these live demos are from both the U.S. and China. It allows you to see different IP Cameras in the daytime and at night since the IP Cameras in China are 13+ hours ahead of U.S CDT time. At the same moments in time. Totally Secure. No information about any IP Cameras IP Address, DDNS, Port or user credentials are exposed and supports both HTTP and HTTPS access methods. As well as using a logon and password created by you ("As an option") that's unique and not a IP Camera User Id. Can also display/control any amount of IP Cameras at the same time using any image sizes on a per camera displayed basis and any mix of IP Camera brands and models, together at the same time as needed. The Interface is free and works with any IP Camera or imaging device that can supply Snapshots using HTTP/HTTPS access methods: http://107.170.59.150 Download link for this free interface ("This interface requires access to a web server with php"): http://107.170.59.150/V40/SecureImageDisplayV40.zip Can be used with or without IP Camera controls of your choice as well as for public access for websites and for private use for any Internet browser capable device you wish to use or that a visitor has that visits a website. Especially good for mobile devices that have limited monthly data plans when checking on your IP Camera(s) remotely and for controlling bandwidth for public access to IP Camera(s) in web pages. Don

You are very welcome. Most IP Camera brands and models that use Browsers with plugins and offer mobile device apps. Use a proprietary video/audio stream format that is not published for those interfaces. The issue is that proprietary format is not using RTSP and to access it. Most likely you would need to create/write a program to do so. Because of the above. One can't compare the RTSP delay with any proprietary video/audio format not having a delay. Since it's comparing apples to oranges. But what I mentioned in my prior post, for sure does happen and not just with Dahua IP Cameras but many different IP Camera brands and models when using RTSP. This is why many Media Players like ffmpeg, VLC and others have command line parameters to force TCP to skip this try UDP first then try TCP after failing UDP delay. Which is not IP Camera brand/model specific and applies to RTSP in general for those Media Players. Don

Yes, here is the issue most likely. Generally RTSP will try using UDP first. In many cases that will fail and then after failing RTSP will fall back to using TCP instead. To avoid this and any delay associated with it and use TCP from the start. Without first trying UDP. Try these: ffmpeg -rtsp_transport tcp -i "Your RTSP URL in between these double quotes" VLC Add this parameter to the VLC RTSP VLC command line: --rtsp-tcp Some say you can also use ?tcp with the Dahua RTSP URL as well that will force the camera itself to use TCP or via a NVR. Not sure I buy into this. But it maybe worth trying. Issue is, that you need to check several of these below. Not just one. Because they all suggest doing it a little differently in the RTSP URL and I can't find any official Dahua example RTSP URL with a ?tcp or &tcp in it: https://www.google.com/?gws_rd=ssl#q=dahua+rtsp+?tcp&spell=1 Maybe one or more uses of ?tcp or &tcp in the RTSP URL really does and can work with Dahua IP Camera in the RTSP URL? Don

That might be what I need, whatever it is that has no name, but that post feels like spam so I won't be going through all your links to maybe find a download. Thanks anyway. The names of these free Interfaces are "Generic Browser Interfaces" for IP Cameras. They are used worldwide by many IP Camera owners using many different brands and models of IP Cameras, for issues like you are having and for many other reasons. It's very obvious and apparent. That you did not take the time to read my prior post in its entirety. Yet you have taken the time to negatively comment on my prior post, anyway. There was and is no need to go through all the links in my prior post to ("Maybe Find") the download link for the Interface. As you are now claiming here, in this post. Since my prior post, specifically stated which link contained the download link. See quote from my prior post above. I took the time as a response to you here in my prior post. To take some of the available live demo examples for these free Interfaces, by using specific links to them. To make it easier for you to see how these free Interfaces function in real-life situations by using links to working examples, that apply to your specific situation vs. simply giving you a link to a list of dozens of live working examples for these Interfaces. That may not apply to your specific needs. I would include links to many testimonials about how people using these free Interfaces are happy with them as a response to you. But I would not want you to ("Feel") like they were also spam. So instead. I will simply state, that I have been and will continue to try to provide free solutions for others with my spare time, as I have for many years. Please see the "About Me" link in my signature if needed ("Unless that also feels like spam to you") and thanks for your kind and well thought out words. Good luck on your current quest and please remember that not allowing yourself to be "Thinking outside the box", is not always the best, quickest and/or cheapest solution to a problem. Hopefully, me stating this, won't be or feel spammy to you. Don

Removed by me. Please see above ("Prior post") instead. Merged this post with it: viewtopic.php?p=267757#p267757 Don

Post subject: Re: Is there an incredibly lightweight VIEWING software for IP? Yes, there is and it's free. This free Interface works with any IP Camera brands and models and imaging devices that support pulling snapshots using HTTP or HTTP access methods using any Internet browser capable devices using any browser. From Computers to Tablets, to Phones and TV's. It's fast and uses less bandwidth then many other interfaces do. Two live demo examples of the dozens of live demo examples available. Showing five different IP Camera models at the same time. While also using the Interfaces infinite zoom feature. Which does not require that any IP Camera have a zoom lens: Five Different Foscam IP Camera Models ("Located In U.S.") At The Same Time http://107.170.59.150/foscam/GlobalZoomExample.htm Five Different Hikvision IP Camera Models At The Same Time ("Located In China") Via iVMS Can also be directly to IP Cameras without NVR or iVMS as well. Which the other live demo examples shown here are doing: http://107.170.59.150/Hikvision/AllHikvisionWithZoom.htm Note: Any image sizes for any IP Camera can be used. Initial smaller image sizes are used for demonstration purposes above. Any number of IP Cameras can be displayed at the same time and they can be any combination of IP Camera brands and models as well. Fourteen Different IP Cameras At The Same Time ("Located In U.S.") http://107.170.59.150/foscam/FoscamUS.htm Note: Trying doing the above with fourteen different IP Cameras at the same time using other methods on many mobile devices without a fire extinguisher, spare batteries or needing to recharge that mobile device immediately afterwards. Not a problem with this Interface. It's Fast. Has low power requirements and low bandwidth requirements especially important for mobile devices with limited data plans and battery life. Plus it's free and works with any and all of your Internet browser capable devices. Live demo example ("Located In U.S.") of default IP Camera resolution ("1280x720") with a IP Camera model that also has a zoom lens using this Interface http://107.170.138.191/SecureImageDisplayControl.htm More Details Includes dozens of other live demo examples using this Interface with different configuration options and the download link for this free Interface. http://foscam.us/forum/showing-secure-methods-using-php-to-display-your-ip-cameras-t8721.html Don

I'm not aware of any masking techniques used in HTTP based unsecure web pages, that can't easily be unmasked. The only way to avoid that from being able to take place. Is that this cloud company or another, not expose this information in the clear from the get go. Don

Please see this. It's totally secure. Does not expose any information about your IP Camera. No IP Address, no DDNS, no port or user credentials are ever exposed. It's free and uses automatic refreshed snapshots vs. full-motion video. Because of that, it's compatible with any Internet browser capable device from Computers to Tablets to Phones and TV's without any device required to download or install anything to use it beforehand. Whereas most of these paid for video server services don't support any and all Internet browser capable devices visiting your website to view your IP Cameras. This would allow you to not require a paid service and host this on your own website as well. Note: Initially there was some confusion about my Interface. It's in fact free, but I do offer help for those technically challenged as well. It has many options. It also works with Hikvision IP Cameras and any IP Camera or image device brand or model, that allows pulling snapshots using HTTP/HTTPS access methods. More here. Including the download link: http://foscam.us/forum/showing-secure-methods-using-php-to-display-your-ip-cameras-t8721.html Many live example IP Cameras using this free Interface, in different ways. Including some Hikvision IP Cameras: http://107.170.59.150/ Don

It would require less resources to use automatic refreshed Snapshots at the interval of your choice. If you want to host this yourself on your own website. It would be more secure as well. Not exposing anything about your camera. No ISP IP Address, No DDNS, No Port or User credentials for the IP Camera. This free interface, also allows you to insert both text and images, into your IP Cameras images. It has many other features and options and it's free! Here is a live example of those methods being used with your camera model. It's in China. So there is some delay: http://107.170.59.150/Hikvision/Hikvision1.htm It also has a configuration option to allow it to be only accessed using a valid User and Password of your choice. For one or many IP Cameras. The User and Password you choose. Has nothing to do with any IP Cameras User. In this example. The User is: admin and the Password is: admin http://107.170.59.150/Hikvision/SecureImageDisplayLogin.php It supports both HTTP and HTTPS access methods. Even if the IP Cameras don't support HTTPS. You will see warnings when using the links below. Because the demo web server being used. Is using a self-signed certificate. But you can see that the same links used above. Also work using HTTPS access methods as well: https://107.170.59.150/Hikvision/Hikvision1.htm https://107.170.59.150/Hikvision/SecureImageDisplayLogin.php Don

You say "pics". So here is a free Interface that works with any IP Camera brand and model or imaging device like a Webcam for that matter. Including any of their front-ends. Like a NVR, DVR, NAS, CMS and so on. That can support supplying snapshots via HTTP or HTTPS and the Interface is totally secure as well. Not exposing anything about your IP Camera. No ISP IP Address, DDNS, Port or User credentials are ever exposed. Here is more detail about this Interface. Which is using Foscam IP camera models as live examples there. But again. The Interface works with any IP Camera brands and models and they can be mixed together as well: http://foscam.us/forum/showing-secure-methods-using-php-to-display-your-ip-cameras-t8721.html It gets fresh new images from the IP Cameras at the interval you configure and only stores the last image received from the IP Camera on disk, in the same file. Leaving no file clutter. Storing the last image received from any IP Camera on disk and reusing the same file to do so to avoid file clutter. Which is a configuration option of the Interface vs. simply getting the IP Cameras image in real-time and displaying it to your website visitors. Has another side benefit. Which is. That if the IP Camera were to be offline and not available. The last image received from that IP Camera will be displayed vs. leaving an empty image when/if that were to happen. Which is handled by the Interface automatically, when that option of the Interface is enabled. When/if that were to occur. The Interface will automatically resume normal processing for the IP Camera. Saving new images to disk and using your normal interval for fresh snapshots when that IP camera comes back online. This Interface is much better than using a fixed FTP image upload interval because say you wanted to grab a fresh image from your IP camera every 5 minutes. But if you had no website visitors for 10 minutes. Why pull a fresh image every 5 minutes, if that image is not required? All your doing is chewing up unneeded bandwidth in cases like that. When a website visitor visits your website. This Interface checks how old the current image for that IP camera is on disk. If it's older then what you say it should be? Say 5 minutes. Then a new fresh image is pulled from the IP Camera, saved on disk and also displayed to the website visitor. If another website visitor visits the website within the next 5 minutes. The Interface checks how old the current image is from that IP Camera currently on disk and since it's not yet 5 minutes old. The Interface automatically uses the stored image on disk for that IP Camera for that visitor instead of getting a new fresh image from the IP Camera. Of course as stated. This interval is configurable. It doesn't need to be a 5 minute interval. It could be as little as 1 second or less or as long as once a day or longer. If desired, you can also automatically refresh the IP Cameras image being displayed in a web page at the interval of your choice as well. Without a website visitor needing to reload that web page to see fresh images of the IP Camera(s). The Interface can be used with one IP camera or as many IP cameras as you wish on the same web page. You can mix different IP Camera brands and models and use specific image resolutions sizes for each as well. The image resolution sizes are not limited to what the IP Cameras provide. You can configure the Interface to display any IP Cameras image to the size you wish. For each individual IP Camera being displayed. The Interface also supports an optional what I call "Infinite Zoom" feature that if you enable that option allows any of the IP Camera images to be zoomed and unzoomed by each visitor for their personal view of your IP Cameras. Even with IP Camera models that don't have a zoom lens. You can set the interval of how often to get a fresh new image from the camera and the Interface handles all of that busywork, without any need to use FTP or Email to get the cameras images. Your website visitors will see new images automatically from the IP Camera(s) on your webpages at the Intervals of your choice. Which can be different for any IP Camera being displayed. Even on the same web page. Don

You are very welcome. My Point about using a VPN is that it's not some "Magical" solution or "Secret Sauce" to more secure remote access. With nothing more to do, then to simply turn it on. There are correct ways and very many incorrect ways to implement and manage a VPN, as an additional security layer. Doing it the wrong way, can very well open you and networks you access that VPN from. Too many more security vulnerabilities then you and those networks had, without that poorly implemented VPN being activated and used. You are paranoid....why do you think hikvision is more likely to do it than ipcamviewer (which is a great app)... If you are overly concerned, use vpn and dont port forward anything.. If someone needs to make ignorant comments about bringing that fact up. After they themselves suggested using a VPN ("With no suggested details on how to go about that"). Well, I don't have the required training to deal with their issues causing them to need to do that. Don

I could go into more details on the downsides of implementing VPN's the wrong way. As I am sure others here are also capable of explaining to you, those potential downsides. But I don't play well with people that insult me with ignorant comments with no valid reasons to do so. So, I will wait for those who might wish for more details or for others here. To help you better understand those downsides. But, thanks for sharing that you feel that using a phone within a local network is equal to using that same phone, with a VPN and remote access to access devices normally restricted to LAN access only. Is not creating any additional security risks, of any kind, when/while doing so. Don

You have every right to be concerned about security issues. It has nothing to do with "paranoia" and for sure I wouldn't sick "My Head In The Sand" because social media sites collect user demographics. Both of those comparisons are not even in the same class as being careless with devices that can be remotely accessed. 1. If/When possible. Never access IP Cameras remotely or via any "Front-End" remotely from a device using HTTP access methods over anything but very trusted and secure Internet connections. To do otherwise is asking for trouble. Especially more so when using administrative level access User credentials. Most IP Cameras and/or their front-ends, now support HTTPS access methods. I am more then amazed that many IP Camera owners who went out of their way to protect their property with IP Cameras use HTTP access methods to remotely access IP Cameras that support HTTPS access methods. I guess, once your property is protected. No need to worry about much of anything else. 2. Never when possible port forward the IP Cameras HTTP port or any other IP Camera ports besides the HTTPS port and any video port required to access the IP Camera remotely. If you're using a front-end like a NVR, NVS, CMS or other front-end that requires port forwarding. Use the same logic. Never access that front end when possible, using HTTP Access methods. 3. You should be able to create a User Level. Like an Operator level User id that can do most things remotely, but doesn't expose User credentials that if breached could expose IP Camera configuration data like stored FTP/Email User credentials or allow the IP Cameras firmware to be modified. For most of your remote access needs. This avoids always exposing administrative User level credentials when using remote access. Why always dig a hole in your yard while being dressed in your best suit. You could, but how smart would it be? This is not so much about simply having an IP Camera exploited as it's about someone gaining administrative access to the IP Camera or front-end for those IP Cameras. Which they then could abuse as an example to gain access to any User credentials for say FTP/Email accounts stored in the configurations of same. IMHO. If you have any User credentials like that stored in the configuration data of devices like that. You should make sure that as an example the FTP User Id is restricted to a subset of folders and does not have root access. In a perfect world it would be also best to have a different Email account when Email user credentials are stored that is IP camera specific. With no other Emails that may contain personal data that could be used for Identity theft purposes. If those IP Cameras or front-ends were ever breached. There are few ways to setup a VPN correctly and many ways to setup VPN's which will expose you to more possibilities of being exploited before you ever even used a VPN. Even if you only include cameras in that VPN. If they are exploited with malware. They can end up infecting many other devices on your own network as well as networks you access that VPN from. For sure, you would need to consistently use much more due diligence then you may be prepared to do when operating and maintaining a VPN properly. IP Cameras even complicate the activation of a VPN more than usual. Many IP Cameras have ports and default User credentials for those ports that while they may not be in the public domain. Many know what they are. If the VPN became breached. It would be very easy to use those IP Camera ports and those default User credentials to exploit those IP Cameras. Making you less secure then when you never were using a VPN. If/When that VPN became breached. It's not a stretch to see this Router/AP exploit being modified to run in Linux based IP Cameras or their front-ends soon. In fact, I would be rather amazed if it not already at least not being tested and played with at this time: http://krebsonsecurity.com/2015/01/lizard-stresser-runs-on-hacked-home-routers/ So, if a VPN becomes breached. Default ports and their default User credentials can instantly and very easily be abused ("Remotely"). Had that VPN not been activated. Then those ports would not have been available to exploit ("Remotely"). If only the IP Cameras or front-ends were only port forwarding the HTTPS and video ports ("Without a man in the middle attack or some other HTTPS exploit") or key logger like exploit or firmware exploit. Even then, if you were using a Operator level User Id when this happened. It would in most cases, not instantly allow administrative User level access with only port forwarding in place. While it's important to worry about if the User credentials stored in a device used to access your IP Cameras remotely are secure. It's equally important to not lose sight of how those User credentials are transported when using them, for those devices as well. You could do everything right to protect that data stored in that device and everything wrong on how that data is used when sent to the device it's meant for. So, both things need to be addressed. Not just one of them. It's never a bad idea to see if you can locate software for a specific device that will show and log access from/to that device. In many cases you can locate free software that can do this. The same can be done with Router/AP's to see what devices are receiving/sending data and on what ports. One does not need to always run this type of logging. But's it's a good idea to do it from time to time to see if you see any unusual access. Otherwise, there very may well me other things going on that you don't know about. Including potentially malware running on a device that's not been located yet. Being concerned about how remote IP Camera access or accessing any normally LAN restricted devices remotely, can and does impact your security. Is far from being foolish. Don

If speed is not a question. Meaning, if you could live with using Snapshots from the cameras at say 1 second or so intervals and you have the URL's to get those Snapshots from the cameras. Which generally are not hard to find if needed. You can also easily locate many of them using ONVIF for specific camera models vs. hunt the Internet for them. This could work well. As a deterrent, less bandwidth over the local network and less horsepower for each camera to provide. It makes the point, without the need to use as much resources ("All around") that other methods may require. It also could/can reduce required costs to implement a feature like this. As stated here earlier. If you could pull smaller Snapshots at 320 resolution, directly from the cameras. You may even be able to get 2-4 FPS per camera. Here is an example using these methods and 14 live cameras at the same time using 160x120 resolutions. Using only HTML/JavaScript. The example below. Is interfacing to a web server in this case to get the 14 different cameras images ("Remotely") over the Internet, to be totally secure. It's also adding date/time and custom text and receiving images from each camera of between 1280x720 - 640x480 and resizing them to 160x120. Which slows the FPS rates per camera down in the example above, because of all of that, extra work and the cameras not being located on a LAN. But you would not need to do all these extra things and could pull the images from these cameras directly from a LAN: http://107.170.59.150/foscam/FoscamUS.htm If the device displaying all the cameras has a touch screen or a mouse that can click on any of the cameras individually that are being displayed. One can view, zoom, control specific cameras movement as needed as well. As the above example also demonstrates, for each camera being displayed. Some of the 14 live cameras being displayed above are fixed cameras and have no PTZ controls or do have PTZ controls but don't have a zoom lens. But, any cameras displayed will support what I have termed as "Infinite Zoom" when they are individually selected. Even if the camera does not have a zoom lens. Allowing you to zoom the cameras current view. Some of the cameras being displayed above do have a zoom lens and support using both the cameras zoom lens and the "Infinite Zoom" feature, individually or combined together. The above might be too slow for some. But a solution for others. But it's compatible with any Internet browser capable device. You can test the link above with the devices of your choice. To verify that. The above methods can be used with any IP Camera brand and model that supports pulling images from it using HTTP/HTTPS access methods. Worse case, you can do the image resizing on the HTML/JavaScript browser side specific for each camera, as needed. If you can't pull specific image sizes directly from specific cameras but want all cameras to be displayed at the same time as the same image sizes. By simply adding a width="320" as an example, in any cameras HTML img tag, on the browser side instead. This will keep and maintain the height/width aspect ratio of any camera being displayed. You can display as many cameras as you wish at the same time using these methods and easily add more as needed. Don