[FFmpeg-trac] #5921(undetermined:new): Can not read mjpeg from IP camera

[FFmpeg]

#5921: Can not read mjpeg from IP camera
-------------------------------------+-------------------------------------
             Reporter:  qqqzhouhk    |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
              Version:  unspecified  |  undetermined
             Keywords:               |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------

Comment (by qqqzhouhk):

 Replying to [comment:6 llogan]:
 > Replying to [comment:5 qqqzhouhk]:
 > > {{{
 > > $ ffmpeg -i http://192.168.10.123:7060 -qscale 2 -vcodec mpeg4 out.mov
 > > -bash: ffmpeg: command not found
 > > }}}
 >
 > You need to have a `ffmpeg` binary to run `ffmpeg`. So far you haven't
 provided any method for us to duplicate the issue, and we have no idea how
 FFmpeg is involved here. Are you using the FFmpeg libraries, or are you
 somehow using the `ffmpeg` cli tool (although if you are it appears not to
 be in your `PATH`)?
 >
 > I'm assuming you're using the libraries because you mentioned something
 called "FFmpegDemo", but we do not support third-party tools. Testing with
 a recent `ffmpeg` binary will more easily show if the issue is valid here.
 >
 > > {{{
 > > $ curl -o stream http://192.168.10.123:7060
 > >   % Total    % Received % Xferd  Average Speed   Time    Time     Time
 Current
 > >                                   Dload  Upload   Total   Spent
 Left   Speed
 > > 100 108M    0  108M    0   0        299k      0     --:--:--  0:06:11
 --:--:--  338k
 > > }}}
 > > Received data seems to keep going up continuously. So what else should
 I do?
 >
 > You have to eventually stop the command. Because we do not have access
 to your input, creating a sample file can possibly be used as an
 alternative input to attempt to duplicate the alleged issue.


 I have already upload the sample file, please check the attachment. :)

--
Ticket URL: <https://trac.ffmpeg.org/ticket/5921#comment:7>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker