From: bob <bob...@gm...> - 2009-06-29 14:22:03
|
True. I haven't dealt with the mpeg4 stream, but it sounds interesting. Bob Story _________________________________________ / "You have a cough? Go home tonight, eat \ | a whole box of Ex-Lax, tomorrow you'll | | be afraid to cough." - Short and funny | \ quote by, Pearl Williams. / ----------------------------------------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || Aurélien wrote: > On Sun, Jun 28, 2009 at 2:40 PM, bob<bob...@gm...> wrote: > >> I haven't had too much experience with them.. but I have used a couple. >> Since I use Linux only one usually has to do a network scan (nmap or >> something) to find the network address and see what ports are open. It >> seemed fairly straightforward to me. What exactly is the problem you are >> having? >> >> >> > > Hi Bob, > > There's the URL problem: most IP cameras are using HTTP for access to > the video stream. Every camera has its own specific video URL. Some > use /mjpeg.cgi, others /cgi-bin/mjpeg.cgi, etc. So a port scan won't > do all the work here. > > There's also a format problem: some cameras stream only mpeg4, which > motion can't read at this time. Some others stream mjpeg, but in a > variety of formats (ie, flow of single jpeg images, separated by http > headers, or a flow of images in a proprietary stream format, etc)... > So, unless Motion implements support for the format the camera is > using, it won't work. > > Best regards, > |