[FFmpeg-trac] #7810(undetermined:new): ffmpeg will automatically pause (Konx KW01 gen2)

[FFmpeg]

#7810: ffmpeg will automatically pause (Konx KW01 gen2)
-------------------------------------+-------------------------------------
             Reporter:  branqueira   |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  unspecified  |               Resolution:
             Keywords:  rtsp         |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Changes (by Jun):

 * cc: junli1026@… (added)


Comment:

 Replying to [comment:3 branqueira]:
 > I checkout the code and build the head branch with the patch provided.
 > I always get the same error
 >
 >
 > {{{
 > Moi at CARL MINGW64 /d/ffmpeg/build/ffmpeg
 > $ git remote show origin
 > * distante origin
 >   URL de rapatriement : git://source.ffmpeg.org/ffmpeg
 >   URL push : git://source.ffmpeg.org/ffmpeg
 >   Branche HEAD : master
 >   Branches distantes :
 >     master       suivi
 >
 >
 > D:\ffmpeg\build\ffmpeg>git status
 > HEAD detached at origin/master
 > Changes not staged for commit:
 >   (use "git add <file>..." to update what will be committed)
 >   (use "git checkout -- <file>..." to discard changes in working
 directory)
 >
 >         modified:   libavformat/http.c
 >         modified:   libavformat/icecast.c
 >         modified:   libavformat/rtsp.c
 > }}}

 Trace2.log says UDP timeout and ffmpeg start retry with tcp, and the last
 request is TEARDOWN in the log.
 But the code tells me, if the TEARDOWN succeeds, a new SETUP will be sent
 out, which I didnot see in the log.

 1. So do you mind sharing more log here ?
 2. Could you have a try with "-rstp_transport tcp"? it will run in
 RTP/RTSP interleaving mode, all traffic is tunneled in TCP, it may work in
 your case.

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