I brought this camera but the eye4 software has very poor record quality and motion recording does not work properly so i am trying to connect with NetCam Studio but can’t get any picture or audio
the rtsp feed is rtsp://192.168.1.102:10554/udp/av0_0
i entered rtsp://user:pass@192.168.1.102:10554/udp/av0_0 in custom url but camera will not connect
i have tried all stream types but none will work, what am i doing wrong please?
Hi Winston!
I would say that most certainly the URL is not correct. The URL seems a little bit odd to me. Where did you find that? Was it here http://www.eye4.so/FAQ/943 I see they use UDP so did you set stream type to rtsp_udp ?
I also see that to get audio and video they say Secondary stream + Audio: rtsp / ip: port/udp/av1_1 so in the URLs below it should maybe be /av1_x
Here are my suggestions:
The camera supports the ONVIF standard. When adding a new source use the tab ONVIF Source and search for it there. Hopefully it will find the camera there. If not, continue.
There are 2 things in the URL that I like you to change and test when adding as Custom URL:
Set Stream Type to rtsp_tcp.
a. I like you to change udp to tcp
rtsp://user:passw@192.168.1.102:10554/tcp/av0_0
b. normally cams that support ONVIF use standard ports so I like you to change 10554 to 554 which is standard for rtsp.
rtsp://user:passw@192.168.1.102:554/tcp/av0_0
c. or when it is ONVIF it can also be as simple as:
rtsp://user:passw@192.168.1.102:554/
rtsp://user:passw@192.168.1.102/
If nothing of the above works I see that the cam have a Hisilicon processor built in. So test
rtsp://192.168.1.102:554/user=xx&password=xx&channel=1&stream=0.sdp?
Sometimes you can figure out the correct URL from the configuration in the camera.
Adding a cam is not always straight forward, but I hope some of the suggestions or combinations above will solve the problem.
Good luck and please report back how it goes to help other users in the forum.
-Henrik
The URL I got from system configuration, log in via web browser to 192.168.1.102:81/index.htm and use “server push mode” on chrome
camera configuration → network settings → basic network settings
there is says RTSP URL which is the URL I quote in first post
today I try ONVIF source and it found camera so i added it but still no picture.
I then disconnect all cameras, changed port to 554 and restart NetCam Studio
I add camera again using ONVIF and click save
I still have no picture so I checked custom source and it say RTSP_TCP feed and url rtsp://USER:PASS@192.168.1.102:554/TCP/av0_0
i change feed to UDP and also adjust URL and now it works great, thank you very much for your help!
in the camera configuration the port was set to 10554 though so i had to change it to 554 using web browser login
for the ONVIF profile I selected “PROFILE_000 - RTSP_UDP (1280x720)”
I have also found that if I log in with the eye4 mobile app then NCS loses the connection and i have to reboot camera to get it working again, this may be the reason i was having problems connecting last night
Fast answer!
Im trying also add the cameras in Fibaro for home automation, so i can have one dashbord open on an ipad on the wall.
But it seems like the fibaro app dosent support mjpg just jpg screenshots =(
I wanted to use another application like Onvifer or Wirecast stream but my RTSP URL was not working.
THen I changed the port to 554 and it started working, and even using VLC its fine.
However I need to use in this format:
rtsp://USER:PASS@192.168.1.102:554/udp/av0_0
or
rtsp://USER:PASS@192.168.1.102:554/tcp/av0_0
Now if I reverted back to port 10554, its works now.
Can someone explain why switching back to 554 and then to 10554 works for me now ?
I have noticed that UDP works all the time, but TCP is giving problems and works intermittently.
I want to add this in one of the network DVR’s which are ONVIF compatible so want to make sure that settings are correct.
Did you give a try to the new 1.4.1 as well ? We made many improvements around onvif (and now support PTZ over onvif).
Fact it works after switching ports: no explanations
UDP vs TCP: just a remark here, it’s very common to have artefact / decoding issues when using UDP as the packets are not verified and may arrive in the wrong order so for this reason we recommand using RTSP TCP whenever possible.
As you have onvif cameras, we’d love to have your feedback on the new 1.4.1 which should also provide better performances and the all new web client 2.0. You’ll find it in the first topic of the community.
Thanks for a quick reply, I tried net cam studio 1.4.1, which looks good as of now?
I will report if I come across any issues.
Also to check that I have two ONVIF cameras in my network, should both be running on same port 554, as I am only able to view one camera and the other one is not showing up ?
Asking this because I also have 1-2 “onvif” cameras (out of 7-8 real onvif cameras) that are advertised so but that no application can discover. Usually if OnvifDM cannot see it find them then no other software will and it also won’t be visible in Netcam Studio.