[Ef] More IP Camera questions

Thomas Marullo tmm3 at lehigh.edu
Fri Jun 17 08:50:32 CDT 2016


I've since moved on from my question about trying to convert my old IP cam
MJPEG streams to RTSP so I could get them into my NVR. But now I have
another question for the educated community!

My new Sony SNC-EP550 cams support FFMPEG H264 stream and MPEG4 MJPEG
stream along with JPEG. With the older Sony RZ30N cams, they had an MJPEG
stream that we'd pull in either flexTPS or iSpy or my own recorder which
parsed the MJPEG stream boundary to dump the images. I used this to sync up
images to test data.

The problem I'm running into now with the new streams are that I cannot
figure a way to record them. First, I tried the MJPEG stream
(http://[ip]/image)
and it's a raw stream of jpeg images with a CamTim and Frame Rate meta that
repeats from time to time and there are no --myboundary or other type of
JPEG boundaries to parse. So I haven't been able to figure out a way to
capture the JPEGs.

The other method I thought was using ffmpeg to capture the h264 stream. I
can listen for an external trigger in linux to start a process (as I did
with the MJPEG Sony's) and I can get a stream, but the problem I'm running
into with ffmpeg is the timing of capture. If I capture say 60 seconds of
video data in real-time, the resulting video may be 80-90 seconds long and
have some choppy parts. I rather it drop frames instead of buffering, or
whatever it does.

So my thoughts to the community. Any processes you use to trigger and
capture modern h264 or mjpeg wrapped streams? Any ideas on how to use
ffmpeg properly to capture a stream? Or is there a way to properly dump
JPEG images from an MJPEG stream that has no boundaries?

Thanks,
Tommy


-- 
-- 
*Thomas M. Marullo, *Research Scientist III & RTMD IT Manager
ATLSS Engineering Research Center
Lehigh University, 117 ATLSS Drive, Bethlehem, PA 18015
(610) 758-6683
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.designsafe-ci.org/pipermail/ef/attachments/20160617/e5c7fb4c/attachment.html>


More information about the EF mailing list