A couple of super-basic questions
Total newbie here, so I apologize if these are dumb questions. I did search before posting and read all the manuals.
First, does having more than one device viewing the cameras at the same time create extra network traffic — for instance, running another view-only instance of SS on a laptop, or TinyCam on a tablet — or, since the cameras are already sending streams to the recording version of Security Spy does it not matter?
Second, if the built-in web server is running, but no browser is accessing the site, does SS still encode the images and use more CPU cycles? Or, does it only encode any camera windows that are actively being viewed (meaning the more windows viewed at once, the larger the CPU load)?
Thanks,
Steve
First, does having more than one device viewing the cameras at the same time create extra network traffic — for instance, running another view-only instance of SS on a laptop, or TinyCam on a tablet — or, since the cameras are already sending streams to the recording version of Security Spy does it not matter?
Second, if the built-in web server is running, but no browser is accessing the site, does SS still encode the images and use more CPU cycles? Or, does it only encode any camera windows that are actively being viewed (meaning the more windows viewed at once, the larger the CPU load)?
Thanks,
Steve
Comments
-
Hi Steve,
Welcome to the forum, and to SecuritySpy! To answer your questions:
Yes, any additional device on your network that is actively viewing a camera stream is adding additional traffic to your network. Whether this is significant or not depends on many factors: the speed of the network, other network traffic, the number of camera streams, and the resolution, format and frame rate of the video formats in use. Generally this is only going to become a problem if your network is unusually slow and/or the camera streams are unusually high-bandwidth, so it's typically not something you have to worry about.
If the SS web server is enabled but there are no connected clients, then it just sits there idle, using virtually no CPU resources. It's only when a client connects and requests a video stream that it then starts to encoding and send images.
Let me know if you have any further questions.
