Alternative is if you can give me access to the camera so I can do the tests here on my system or access with TeamViewer? I suggests changes in NCS and in the camera configuration. So if you are interested I´d like to propose some tests to see if we can fix this. I bet that most of these recorded videos are about 10 seconds long. in default and if they are different MD is triggered and a video is recorded. MD in the frame mode compare frames from the camera every 0,25 sec. If you feed something with garbage you also get garbage out meaning that feeding MD with that video it will not give any good results. Second, that you get hundreds of false alerts with Motion Detection tells me that MD works correct. Did it work fine in NCS with only one camera or did I misunderstand that? Yes, this really sucks so we have to do something about it since the camera is a good oneįirst, you say that you added a second one to your configuration. The other to choices are not standard yet what I know. It seems that it must be in BASIC to work. If I remember correct it is Basic, Medium or High. In the configuration of the camera for the video Reolink have a choice on the h.264 codec. Let´s start with this and you are welcome back if/when needing more assistance.Įdit: I forgot. At the bottom you can also see the CPU load.It is always tricky to find the correct rtsp, but I hope this one is correct.ġ0, Please, read the manual where you have more info about motion detection and all the other features. The address and password to the camera.Ĭlick on Save and you should have the video image from the camera, I hope.You can check this later on the CPU load at the bottom line of NCS. If it is only one cam it will probably be ok. That amount of pixels, motion detection and maybe more will put some demands on your computer.Your camera with a lot of pixels only use h.264 and rtsp so we must configure NCS to communicate that language so the computer and camera and communicate with each other.Other protocols for video is mpeg4, mjpeg, jpeg … It depends on the application which one is best to use. Then it is transmitted to the computer where the computer decode that information using the backward algorithm of h.264 into data that can be stored and viewed on the computer. The protocol h.264 is an efficient mathematical algorithm that first compress the data in the camera. To not kill the networks the data need to compressed and then transfered to a computer to be viewed. Today it is megapixel cameras like your camera 2560x1440 pixels and to send that amount of pixels 20, 25 or 30 times per second is a LOT of data. For some years ago it was 640x480 pixels that was very good. Especially, when you have cameras with a very high resolution for good video. Transporting video on the network involves a lot of data transfer today.RTSP is another protocol for transporting data on the Internet, but rtsp is optimized for transporting video and audio in real time. It is used for communication between your web browser and the web server. HTTP is another protocol that you might recognize that you use when using a browser like Internet Explorer or Firefox. Excellent choice to move to Netcam Studio (NCS).Then it will be much easier for me as well.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |