Ip camera slow response
The director of household finances has decreed that we need a new doorbell when we I redecorate the hallway. So I went looking and there are lots of options I know there is an old thread about it but I can't find anything newer. I like my Ring. No, it doesn't need a static IP. It connects, outbound, to their web service kind of like TeamViewer, so you don't need to worry about the IP.
If yo just want a wireless doorbell there are other options on the market. Is there something specific about the work area that video would increase security? If she wants that particular brand then get it and install it.
Anybody complains point them to to Director of household finances. Brand Representative for Microsoft. I have the Nest cams set up outside my place. There is about a second lag between what I see onscreen and what is actually happening. Maybe less of a lag, but it is pretty good for what I paid for it. I already have a traditional electric bell so the lag problem shouldn't be too much of an issue hopefully and I probably wouldn't need the extra ringer thing.
My Wi-Fi is excellent at the back of the house and inside the house but I have never actually checked it by the front door! A little test for tonight methinks :. My cable upload speed is about 28 Mbps and my download is I think around Mbs Then you can also makes rules like if input goes high someone presses the button then send an email with picture s attachment s.
Then, since it's an IP camera, you can record it continually with something like Sighthound video. I feel any of this would be better than depending on some cloud service to keep working, just for your doorbell to.
I have an old iPhone4S and a couple of Android phones which are about a year old it's an odd story I work in a few different old peoples homes where my normal phone doesn't work and only the VOIP phone they provide me with works. I have the Ring Pro. I would definitely recommend getting the pro over the standard. It seems like they fixed a lot of the issues people were complaining about with the standard model.Post by Edward.
Bradley widcombe. Please log in to reply to this post. I have tested this in EW and it does not work. You can add it as a feature request here. Click Here. Terry Stout EasyWorship Support www. Easyworship 7 now has support for NDI. NDI is a form of IP streaming with a multicast discovery protocol. It has a higher compression rate and medium latency. FYI anyone else reading, there is a workaround available that you can use.
Not ideal, but a useful workaround for now. Jump to. About Our Company. EasyWorship began as a software solution for churches to amplify the worship experience from the sound booth to the stage. From bringing you the best church presentation software, worship media and customer support we can offer, we purpose to do everything with excellence and bring glory to God. Create the service you want with stunning backgrounds for worship and eye-catching sermon videos from our media store.
We are running the ST software on a computer dedicated to be the camera server. I currently have 29 cameras all running on the system. Now all my cameras are working and coming up on my client's machines around my location.
My issue is that the cameras are choppy and almost seem to freeze for a second at times. I have gone through and set the bitrate to 2 mbps and the frame rate to 15 on all the cameras like is recommended by Vivotek.
If anyone could give me a suggestion on how to make the cameras run smooth on my computers. I have been told that multicast might solve the issue but not sure on that. I did use a Sonicwall tz to separate my network into a Separating the two network seemed to help the situation but has not fully resolved the issue.
Start Free Trial. View Solution Only. Distinguished Expert This award recognizes someone who has achieved high tech and professional accomplishments as an expert in a specific topic. Commented: What type of switches areally you using for the cameras? I am assuming that your cameras are POE. You might need to update the firmware or consider upgrading the switch itself.
Top Expert This award recognizes someone who has achieved high tech and professional accomplishments as an expert in a specific topic. You created two different IP subnets. How are the subnets separated? That is, are you using VLAN's or separate switches? Is the server on the same network as the cameras? At 2 Mbps for 29 cameras, that is almost 60 Mbps. What is the LAN speed of your network? Does the camera traffic have to pass through the Sonicwall tz to get from the cameras to the server?
What resolution are you recording at? Ryan Niggeling. Author Commented: Most cameras are set to X resolution, some cameras have audio and that's the main concern here since our costumer relies on that audio. The server is on the same network as the cameras, the traffic from the cameras does not have to go through the router to get to the server, at this point all the traffic from the cameras has to go through the router to the viewing clients, the computer are on a separate switch that connects to port 1 I have an Axis QE camera.
Overall I like the camera but the PTZ response time with Milestone SmartClient is about 2 seconds it takes 2 seconds after I click the mouse before the camera pans or zooms. Using the web interface to the camera bypassing Milestone the PTZ response time is about. From a usability point of view the. The 2 second delay makes it difficult to follow a suspect. I'm not sure if there is an industry standard or target response time for an IP camera using PTZ control.
If not perhaps IPVM should rate and try to set one. I realize that the Milestone Client will buffer several frames to make the video appear smoother.
So I'm not sure where the problem is. I suspect using Milestone as the inbetween is just adding some delay. I haven't researched any possible issues with the various Milestone's device pack camera driver versions yet. I'd appreciate any insights into this issue.
Is my experience typical, thus I just have to live with it. This will result in increased bandwidth requirements but less storage space. Aaron, let me run this by Axis and Milestone and see what they recommend.
I am sure some members have practical experience with this combo as both products are frequently used. By default RTSP sessions have ms of caching latency, which might be the reason why you're seeing the delay in case of H. This is also mentioned in Axis user manuals about streaming H. The same happened, we had a latency at around sec. With Milestone I had an issue couple of years ago with latency and live viewing.
We wanted to find out the reason so replaced the switch which had gigabit ports. One thing that is quite easy to check are the client side buffering settings in the camera view. If this is set abnormally high then it will give the appearance of latency.
An often helpful troubleshooting step would be to open both the web page and the Smart Client simultaneously, execute the commands from the Smart Client and note what happens in the web view. By doing this we can determine if the latency is in the PTZ command execution, the video or both. They will also want to make sure they have updated to the most current device pack.
Aaron, can you try the experiment of opening up the Smart Client and camera web client making sure it's set to H. From what you have already, it appears that you have checked the client side buffer settings?
Top 10 IP Camera Troubleshooting Tips
Just for fun I decided to run the test you suggested. When I use the Milestone client to pan the camera the Web Client shows the movement about 1 second before the Milestone client. The Milestone Xprotect Smart Client 7. I don't see any way to remove buffering all together.
I set the web client for H. Although the Q is built like a workhorse, with signifigantly better hardware than many HD PTZs, so there could be another explanation. Did you try using VLC by playing H. You should see a reduced latency when you set "caching latency" to ms.
I have watched surveillenace workstations crash due to trying to decode 16 or 32 simultaneous H. My laptop crashes trying to decode more than 2 H. I find its best practice to record with H.I am trying the ispy Connect security camera software.
My first impression is that the video quality is horrible. I didn't know what group to put this in so I put it into security since it is dealing with security cameras.
I am using Milestone now instead. A lot more features and all I had to do was register to get a serial to use with it. Might need to see if you can configure the camera for a higher resolution. Also check to see what quality the software is recording. Are they IP's cameras? I have all my cameras set to "normal" video quality and framerate of 5 FPS.
I have a few cameras that record at a higher FPS because they record a higher profile area. I had some really odd videos until I realized I got it backwards.
Cat would suddenly appear jumping away from the bathroom sink. I was using this to monitor my basement bathroom since I had a cat that decided to use the sink as a urinal.
That wouldn't have been so bad but there are 4 cats to choose from, and the sink was sitting on the floor not yet attached to plumbing. I don't see any real settings to change the resolution.
They are Ubiquiti AirVision Camera's. Mike, have you ever tried Milestone? We were using the pay version at my last job for cameras that monitored ports. Coast Guard needed remote access, etc I haven't tried Milestone. I had a ton of issues with their previous version of software and I tried iSpy, Zoneminder, Blue Iris, and one other.
Blue Iris worked best for me until Trendnet put out their latest version of SecurView. It works pretty great for me, but it is only for Trendnet cameras. It doesn't appear that Milestone supports Ubiquiti cameras.
Ubiquiti was nowhere to be found. Perhaps I missed something? See the jpeg quality in settings and the options under recording profile when editing the camera it allows you to set the recording profile to web or mobile content or. No idea why it was slow on your LAN - it's ridiculously fast on mine.
IP Camera choppy and slow
March 24, by Don Stephens. A very popular choice of camera is the Pan Tilt Zoom camera and it can do just that. Using an additional PTZ controller or the on-screen controller of the DVR, the user will be able to move the camera lens around and zoom in and out. With that being said, PTZ cameras need additional setup to ensure that it functions properly and keeps functioning properly.
If something does go wrong after the initial installation there are two main things the user should inspect to get their PTZ camera working again.
The first thing the user should look at is the power supply. It is very important that the camera owner uses the power supply that comes with their particular camera. If the PTZ does require a new power supply it needs to be replaced by one that matches the exact specifications of the original one.
For example, if a mini PTZ is connected to a 24V power supply it will burn out the circuitry in the camera or cause it to malfunction. This is because the voltage and amperage are simply too much for a mini PTZ to handle.
Another thing to pay attention to when it comes to the power supply of the PTZ camera is the distance between it and the camera itself. If the power supply is very far from the camera 50 feet or more you could potentially suffer from a power drop in amperage and voltage.
This may cause the PTZ camera to malfunction or even worse, stop working completely You should always try to keep the power supply as close to the camera you possible. If circumstances prevent it and the power supply must be run a long distance, a 14AWG wire is recommended. This particular gauge wire will be thick enough to carry all the power that the PTZ will need to function properly. In addition to troubleshooting potential power issues, the user should also check the data connection of the PTZ camera.
The first and most obvious thing to do is to ensure the connection is secure on the back of the DVR. To display these settings, the user must power down the PTZ camera and power it back up. As the camera is booting back up, a splash screen will show up displaying the baudrate, protocol, and ID configurations of the camera. Follow the images below for step-by-step instructions on configuring the PTZ camera settings.
Once these settings are entered the user just needs to hit save. The PTZ camera should now function properly.Troubleshooting IP cameras can be tricky and frustrating.
Despite everything looking correct, it can still take some extra effort to bring IP cameras up and operational. As IP video matures, the technology gets easier to configure, but it is still far from "plug and play". Every technician should have a few basic troubleshooting techniques up their sleeve to get IP cameras online and working.
In this note, we detail the Top 10 basic troubleshooting tips for IP camera connections. Reboot the camera: Some consider the 'Golden Rule' of IT troubleshooting to first reboot the device before proceeding. Simply restarting the camera gives the chance for cache to flush, settings to recalibrate, and connections to be renegotiated.
This step is the least difficult and cheapest to perform, one only has to remove power, wait 10 or 15 seconds, and then restore power. Ping the camera and discover it: Type " cmd " into the Windows search box to open a DOS command prompt and the use the "ping" command to see if you can connect to the camera.
For example, if your camera's address is There can be many reasons for that, the most basic being that the camera and the computer are on different networks or subnets.
If you are receiving proper connection replies, use a web browser or the manufacturer's discovery utility to connect to the camera. If you need help with this process, review this IPVM Basic Networking Tutorial on using manufacturer's camera discovery utilities, pinging cameras and setting your PC's IP address to be on the same network as the camera.
It's good practice to keep a record of the MAC and IP addresses of installed cameras for troubleshooting purposes. In a similar manner to ping in Tip 2 above, the ARP command can be used to show the IP and MAC addresses of devices connected to the network, just type "arp -a" at the command prompt. Confirm IP Addresses are not conflicting: Take care that two devices are assigned the same address, because this often has the result of 'cancelling out' network access to either device.
A simple "fat finger" while inputting the camera's address, gateway or subnet can cause all kinds of havoc. The ARP command listed in Tip 3 can help with this. Verify Camera Power and connection: If possible, look at the camera to make sure it is powered up. Most cameras have LED's that indicate the camera's power status, and if it is connected to and transmitting data to the network.
Many times these LED's may be concealed inside the camera's housing. If it is a PoE camera and not powered, check to see if it is plugged into a PoE switch or midspan. Another pitfall may be the PoE network switch itself. Some PoE switches do not have enough power to supply 15W to every port and will not supply power to another camera if it is already overloaded. To troubleshoot, connect the camera into a suitable PoE injector or midspan to see if that is the problem.
A high frequency of connection issues center around cabling problems. Basic IT troubleshooting places a huge emphasis on checking transmission cables. Since the final assembly is only as robust as it's weakest link, checking data cables for kinks, frays, shorts, and bad terminations is a very basic troubleshooting step. Cable and patch panel connections made in a hurry by hand can get crossed wires or connectors come loose.
Sometimes the power wires to a PoE camera in the cable may be powering the camera up, but the data wires may be crossed or not connected preventing network connection. To troubleshoot, use a cable tester to test the cabling or use a known good cable to connect to the camera and see if it connects.