I’ve had a fair few issues… They seem specific to Camera’s we’ve bought… however They work fine in VLC
Initially I was getting what i’m calling keyframe drift… where the bottom half of the screen appears to slowly drift to the Green Spectrum… Changing Decoder to VLC has fixed this…
However now when we reboot the server it fails to connect to the camera… It connects to a foscam camera just fine… but these ones it doesn’t… I have to login to the server click edit the camera settings and then just click save to force it to reconnect… which it does and then it’s all good…
At the moment we just avoid restarting… However long term this just isn’t going to work… I was planning to buy a license as I’ve got 3 more cameras to put in… However I emailed support and have never heard back at all… So I’m attempting contact via the forums then i’ll give up and go use something else…
I did like your product due to it’s comprehensive feature list and that it’s well written… my coding knowledge tells me you thought this software out before getting into it… However an intermittent security software is no security at all…
I haven’t even tried all the features yet because I’ve been battling these issues
Hi Ryan! I agree, quite anoying. I am just leaving for the weekend and back on Monday morning. I hope you can wait until then. In the meantime can you support me with what cameras, “these ones”, you use and if they are added to NCS using Template or Custom URL. Are the cameras set to DHCP or fixed IP? What operating system do you use?
Have a nice weekend!
Henrik
Camera’s are almost noname Chinese - But found this on the site : TinoSec - YN-IPC-BT511S-P-20-1
Camera’s have been set Statically, and are connected via a Custom URL
of the order rtsp:///user=&password=&channel=1&stream=0.sdp
It’s currently running on Server 2016 Release Candidate 2, But doubt it has much to do with the Connection Issues
Thanks for getting back to me… Hopefully we can get these issues resolved
Thanks for info. The rtsp seems a little bit strange to me. When adding a camera in Custom Url the other tabs musty be empty and in Custom URL use rtsp_tcp and the URL
rtsp://ipnumber/user=&password=&channel=1&stream=0.sdp
or
rtsp://username:password@ipnumber/stream=0.sdp
The last rtsp is the standard for NCS, but the first one might also works depending on camera. The missing part is the ipnumber. The OS is of interest since is it important to use the latest .Net framework 4.5.2
Please report back how it goes.
-Henrik
NCS (ver. 1.2.8) is running on a windows 10 with .NET framework 4.6.1 installed (if you have same problem and need to find out your .Net framework version look here: Link).
I belive that Server 2016 Release Candidate 2 too has .Net framework 4.6.1 and Mircrosoft say that it should be work with with .Net framework 4.5.2. I will how ever be testing this by installing a NCS ver. 1.2.8 on a windows 7 PC and adding my cam’s. Hope to bring news monday
Also running 10Pro. The settings above are default. However, after some restarts for other reasons it seems to be working fine now. The classical Windows trick with restarts still works ;). Hopefully it is solved for the guys above also.