Ok, this might be a bit of a stretch (especially since there doesn't seem to be an Android "source" client yet), but I'd like to see support for iCam Source on a device like the Nvidia Shield. I know for myself, I'd like to get rid of the old Mac Mini I use for running Source to get something that uses less power, etc.
Just starting today (without an update to the computer client or anything), another one of my cameras started giving the "Network Camera Offline" graphic frequently in the newest iCamSource Pro beta. Are my cameras going bad, or is there something going on in the client? I'll restart the cameras when I get home to see if that fixes it, but is there some way at least to keep iCam from notifying me every time the camera goes off- and on-line (which seems to happen several times an hour...)?
Previous versions of the BETA silently reconnected to the camera if the connection was lost, but 1.3.4.4 introduced the same "Network Camera Offline" image that the MJPEG/JPEG camera connections use when the connection is lost and the iCamSource Pro is waiting to reconnect.
We are noticing a lot more reconnections occurring when running the iCamSource Pro on an older (Early 2009) Mac mini running macOS 10.11 as opposed to more modern Macs. What Mac and version of macOS are you currently running it on?
I'm running on a Late 2009 (so still older) Mac mini running 10.11.6.
Regarding schmegs comment of “Network Camera Offline” I am only getting that for a new camera RTSP ip addresses that I set-up in iCamSource Pro when the camera is unplugged. Do you have an ip address entered in the camera list for a camera that is no longer connected or for an ip address that has changed? It is interesting that I have a few other ip addresses assigned in iCam Source Pro for my older cameras using MJPEG and these simply show the text ’No Image” instead of “Network Camera Offline”. A useful software feature would be to have an enable/disable feature per camera whereby if a specific camera will not be used temporarily it can be disabled in the software without having to use the minus button to delete it permanently and loose all the settings.
I'm using the same camera and same IP that I've had for years. The only thing I changed was making the address an rtsp address for the H264 stream now (instead of the MJPEG and still streams I used to use). The camera is always plugged in, and when it goes "offline," it's only gone for a few seconds (just enough to trip the motion detection, which bugs me now several times a day because of that...) before the picture comes back. I didn't have that happen on the old betas, but, then again, they weren't out for a long period of time...
It works! I have to put the URL in the format of "rtsp://x.x.x.x:port/videoMain" with the username and password in their respective fields in iCamSource Pro, but it seems to work now. I'll be playing with it this week to see if I have any other problems
I've tried it with a Foscam FI9821Pv2, and it instantly crashes. I've tried both entering the "rtsp://IP:port" (with username and password for the camera), and, following the instructions on this page: https://www.foscam.com/Faqs/view/id/81.html , I've tried using the "rtsp://username:pwd@IP:port/videoMain" format (both with and without using the username/password fields in iCamSource Pro). Anytime I put in an rtsp url, the application crashes instantly upon starting. I've tried using the URL format from that page in VLC, and that does work, so the stream exists...
Sorry, I got sucked into a vortex of work and stuff. Right now, I have my camera set for just the pic update option, so I'll have to reconfigure iCamSource later to send the error code, etc. That'll probably happen later this week or this weekend. Thanks for looking into it!
The specs for the camera only shows that the camera uses H.264. You would have to contact the manufacturer where they would hide the MJPEG video compression that is not listed in the specs.
Thank you again, but I already know how to access the MJPEG compression, and it works.
What I'm trying to figure out is if anyone else on the forum who uses it has been able to get it to work with iCamSource Pro. From what I picked up in another post, the MJPEG command output from the camera seems to mess up the URL, so iCamSource Pro has a problem parsing it. Is there any fix for that? Or has someone written a script/application/etc. that could go in between the two and "fix" the mess so that a clean URL could be sent to iCamSource Pro?
That camera has H.264 video compression and will not work with iCamsource. IP cameras need MJPEG or JPEG video compression to work with iCamsource.
Thanks, but I was asking about the hidden MJPEG setting for the camera. I have seen other topics on the forum where people have seemingly been able to get it to work with iCamesource, but I haven't had any luck yet.
Okay, I just got an FI9821 to try out with iCam Pro. I set up the MJPEG stream on the camera using "ip address:port/cgi-bin/CGIProxy.fcgi?cmd=setSubStreamFormat&format=1&usr=admin&pwd=" (using the http, which I can't add because the forum considers it an external URL...) and got the correct result. I can paste the MJPEG Stream URL "ip address:port/cgi-bin/CGIStream.cgi?cmd=GetMJStream&usr=admin&pwd=xxx" in my web browser and get the view from my camera.
I'm not quite sure how to set it up in the iCamSource Pro application. I've put that URL in the URL field and put my username and password in their respective fields, but I keep getting an error. I've tried not including the user/pass (leaving it blank in the fields), tried taking the user/pass off the URL, and tried cutting down the URL right after the CGIStream.cgi (which, of course, didn't work). For anyone who's been able to do this, how did you get it to work?
Show Posts
