Thought I'd post this one too. This has only really been a problem over
a 802.11g netcam mjpeg-streamer link. It has also just started happening
on a 100MB Ethernet link that also uses mjpeg-streamer.
I have had that occasional problem where part of a saved image gets
covered by a grey blind. I'll always get the first part of the image,
just the balance gets greyed. The amount of grey varies.
I assume that this comes from the TCP packet being clobbered and motion
decides to not allow the resent data into the capture. Kind of like how
UDP would work. In a sense the reason is obvious. You don't want the
hassle of reassembling packets when you are trying to process in real time.
I haven't delved into the netcam code yet, but I'd appreciate any
insight or links to how it works or whether there is a timeout or buffer
that could be adjusted. Of course it may be a mjpeg-streamer problem
too, but given it really only is flaky link related I think motions
netcam.c more likely. Any thoughts?
Get latest updates about Open Source Projects, Conferences and News.