Re: [FFmpeg-trac] #5283(avcodec:new): Add bitstream filter to remove Closed Captions from h264

[FFmpeg]

#5283: Add bitstream filter to remove Closed Captions from h264
-+---
 Reporter:  cehoyos  |Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  h264 cc  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by feno):

 I'm very surprised to see that this feature does not exist in ffmpeg. I
 was almost sure I could do that with ffmpeg so I was looking to docs to
 see how to do that. Then found out it's actually not possible.

 I found link to this issue in some forums where other people were asking
 how to do this in ffmpeg. So it's something that people actually need and
 ask around.

 No response to this issue for years since it was reported. So looks like
 no hope to see it implemented :(

 I really need this function so badly, would appreciate a lot if any dev
 interested in implementing it :\

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7053(avformat:new): bitpacked codec too limited

[FFmpeg]

#7053: bitpacked codec too limited
-+
 Reporter:  chacha   |Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  rtp  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by cehoyos):

 Please send your patch to the FFmpeg development mailing list where it can
 be reviewed.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #6386(avformat:new): Timebase is written as frame duration for mkv if framerate is unkown

[FFmpeg]

#6386: Timebase is written as frame duration for mkv if framerate is unkown
+
 Reporter:  fthiery |Owner:
 Type:  defect  |   Status:  new
 Priority:  minor   |Component:  avformat
  Version:  git-master  |   Resolution:
 Keywords:  webm mkv|   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+

Comment (by fthiery):

 -fflags +genpts not working for me, ffmpeg still duplicating frames by the
 thousands.

 {{{
 $ ffmpeg -fflags +genpts -i input.webm output.mp4
 ...
 Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p,
 1280x720 [SAR 1:1 DAR 16:9], 2049 kb/s, 1k fps, 1k tbr, 16k tbn, 2k tbc
 (default)

 }}}

 @kicco what am i doing wrong ?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

[FFmpeg-trac] #7054(ffmpeg:new): stream_loop "Seek to start failed" with H.264 rawvideo file

[FFmpeg]

#7054: stream_loop "Seek to start failed" with H.264 rawvideo file
-+-
 Reporter:   | Type:  defect
  Serveurperso   | Priority:  important
   Status:  new  |  Version:  git-
Component:  ffmpeg   |  master
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 Hello, I'm free to make more testing, just ask.

 Summary of the bug:
 How to reproduce:
 % ffmpeg -i input ... output


 ./ffmpeg -re -stream_loop -1 -i /tmp/robot.264 -codec copy -f rawvideo
 tcp://127.0.0.1:8004


 ffmpeg version N-90197-gaa294ad Copyright (c) 2000-2018 the FFmpeg
 developers
   built with gcc 4.9.2 (Debian 4.9.2-10+deb8u1)
   configuration:
   libavutil  56.  8.100 / 56.  8.100
   libavcodec 58. 13.100 / 58. 13.100
   libavformat58. 10.100 / 58. 10.100
   libavdevice58.  2.100 / 58.  2.100
   libavfilter 7. 12.100 /  7. 12.100
   libswscale  5.  0.101 /  5.  0.101
   libswresample   3.  0.101 /  3.  0.101
 Input #0, h264, from '/tmp/robot.264':
   Duration: N/A, bitrate: N/A
 Stream #0:0: Video: h264 (Constrained Baseline), yuv420p(progressive),
 720x576, 25 fps, 25 tbr, 1200k tbn, 50 tbc
 Output #0, rawvideo, to 'tcp://127.0.0.1:8004':
   Metadata:
 encoder : Lavf58.10.100
 Stream #0:0: Video: h264 (Constrained Baseline), yuv420p(progressive),
 720x576, q=2-31, 25 fps, 25 tbr, 25 tbn, 25 tbc
 Stream mapping:
   Stream #0:0 -> #0:0 (copy)
 Press [q] to stop, [?] for help
 Seek to start failed.=-1.0 size= 906kB time=00:00:11.20 bitrate=
 662.7kbits/s speed=   1x
 /tmp/robot.264: Operation not permitted
 frame=  280 fps= 25 q=-1.0 Lsize= 906kB time=00:00:11.20 bitrate=
 662.7kbits/s speed=   1x
 video:906kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB
 muxing overhead: 0.00%


 ffmpeg version
 built on ...
 }}}
 Patches should be submitted to the ffmpeg-devel mailing list and not this
 bug tracker.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7053(avformat:new): bitpacked codec too limited

[FFmpeg]

#7053: bitpacked codec too limited
-+
 Reporter:  chacha   |Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  rtp  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by chacha):

 I have added a patch that adds 12, 14, 16 bit depths variations to YUV422
 packed.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7030(avcodec:open): qsv in ffmpeg

[FFmpeg]

#7030: qsv in ffmpeg
-+-
 Reporter:  palich2000   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  qsv  |   Blocked By:
  regression |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by palich2000):

 {{{
 Linux 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC 2015 x86_64
 x86_64 x86_64 GNU/Linux
 }}}
 {{{
  [ OK ] Media SDK HW API level:1.19
  [ OK ] Media SDK SW API level:1.19
  [ OK ] OpenCL check:platform:Intel(R) OpenCL GPU OK CPU OK
 }}}

 {{{
 ffmpeg -t 30 -v verbose -i rtmp://x \
 -c:v h264_qsv -b:v 1000k\
 -strict experimental -acodec aac -ab 64k -ar 44100 \
 -f flv rtmp://127.0.0.1/vip/_77_
 }}}

 {{{
 ffmpeg version N-90198-g7056d06 Copyright (c) 2000-2018 the FFmpeg
 developers
   built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-11)
   configuration: --prefix=/home/palich/ffmpeg-test/ --extra-
 cflags='-I/home/palich/ffmpeg-test//include -Ofast -march=native' --extra-
 ldflags='-L/home/palich/ffmpeg-test//lib -ldl' --enable-avresample
 --enable-static --enable-shared --enable-nonfree --enable-gpl --enable-
 version3 --enable-libx264 --enable-libfdk-aac --enable-librtmp --enable-
 gnutls --enable-libfreetype --enable-filters --enable-postproc --disable-
 doc --enable-libmp3lame --disable-stripping --enable-debug=3 --enable-
 runtime-cpudetect --enable-libmfx
   libavutil  56.  8.100 / 56.  8.100
   libavcodec 58. 13.100 / 58. 13.100
   libavformat58. 10.100 / 58. 10.100
   libavdevice58.  2.100 / 58.  2.100
   libavfilter 7. 12.100 /  7. 12.100
   libavresample   4.  0.  0 /  4.  0.  0
   libswscale  5.  0.101 /  5.  0.101
   libswresample   3.  0.101 /  3.  0.101
   libpostproc55.  0.100 / 55.  0.100
 Routing option strict to both codec and muxer layer
 Parsing...
 Parsed protocol: 0
 Parsed host: vr0.dpl-streaming.com
 Parsed app : virtual
 RTMP_Connect1, ... connected, handshaking
 HandShake: Type Answer   : 03
 HandShake: Server Uptime : 134225664
 HandShake: FMS Version   : 0.0.0.0
 HandShake: Handshaking finished
 RTMP_Connect1, handshaked
 Invoking connect
 HandleServerBW: server BW = 500
 HandleClientBW: client BW = 500 2
 HandleChangeChunkSize, received: chunk size change to 4096
 RTMP_ClientPacket, received: invoke 190 bytes
 (object begin)
 Property: 
 Property: 
 Property: 
 (object begin)
 Property: 
 Property: 
 (object end)
 Property: 
 (object begin)
 Property: 
 Property: 
 Property: 
 Property: 
 (object end)
 (object end)
 HandleInvoke, server invoking <_result>
 HandleInvoke, received result for method call 
 sending ctrl. type: 0x0003
 Invoking createStream
 RTMP_ClientPacket, received: invoke 29 bytes
 (object begin)
 Property: 
 Property: 
 Property: NULL
 Property: 
 (object end)
 HandleInvoke, server invoking <_result>
 HandleInvoke, received result for method call 
 SendPlay, seekTime=0, stopTime=0, sending play: vrm_foot_live
 Invoking play
 sending ctrl. type: 0x0003
 HandleCtrl, received ctrl. type: 0, len: 6
 HandleCtrl, Stream Begin 1
 RTMP_ClientPacket, received: invoke 96 bytes
 (object begin)
 Property: 
 Property: 
 Property: NULL
 Property: 
 (object begin)
 Property: 
 Property: 
 Property: 
 (object end)
 (object end)
 HandleInvoke, server invoking 
 HandleInvoke, onStatus: NetStream.Play.Start
 RTMP_ClientPacket, received: notify 24 bytes
 (object begin)
 Property: 
 Property: 
 Property: 
 (object end)
 RTMP_ClientPacket, received: invoke 110 bytes
 (object begin)
 Property: 
 Property: 
 Property: NULL
 Property: 
 (object begin)
 Property: 
 Property: 
 Property: 
 (object end)
 (object end)
 HandleInvoke, server invoking 
 HandleInvoke, onStatus: NetStream.Play.PublishNotify
 RTMP_ClientPacket, received: notify 387 bytes
 (object begin)
 Property: 
 Property: 
 (object begin)
 Property: 
 Property: 
 Property: 
 Property: 
 Property: 
 Property: 
 Property: 
 Property: 
 Property: 
 Property: 
 Property: 
 Property: 
 Property: 
 Property: 
 (object end)
 (object end)
 Metadata:
   ServerNGINX RTMP (github.com/arut/nginx-rtmp-module)
   width 1280.00
   height720.00
   displayWidth  1280.00
   displayHeight 720.00
   duration  0.00
   framerate 25.00
   fps   25.00
   videodatarate 976.00
   videocodecid  7.00
   audiodatarate 62.00
   audiocodecid  10.00
 [h264 @ 0x138b040] Reinit context to 1280x720, pix_fmt: yuv420p
 Input #0, live_flv, from 'rtmp://':
   

Re: [FFmpeg-trac] #7030(avcodec:open): qsv in ffmpeg

[FFmpeg]

#7030: qsv in ffmpeg
-+-
 Reporter:  palich2000   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  qsv  |   Blocked By:
  regression |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by jkqxz):

 Replying to [comment:13 palich2000]:
 > Look above, there I described everything.

 If might help if you could increase the scope of "everything" to include:
 * Operating system details, including kernel version.
 * What version of the Media SDK you are using (some specific proprietary
 version, the open-source one?).
 * A complete log of ffmpeg output for the failing case.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7030(avcodec:open): qsv in ffmpeg

[FFmpeg]

#7030: qsv in ffmpeg
-+-
 Reporter:  palich2000   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  qsv  |   Blocked By:
  regression |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by palich2000):

 Believe me, this will not help.
 You can choose the parameters for which there will be no error. But the
 encoding will occur on the CPU and not on the GPU.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7053(avformat:new): bitpacked codec too limited

[FFmpeg]

#7053: bitpacked codec too limited
-+
 Reporter:  chacha   |Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  rtp  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by chacha):

 I have attached a program I made to genenerate such streams and their sdp
 files.
 Currently it can generate RGB888, YUV422-8b, YUV422-10b, YUV422-12b,
 YUV422-14b, YUV422-16b
 It can be compiled under Windows or Linux with a c++-11 compliant compiler

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7030(avcodec:open): qsv in ffmpeg

[FFmpeg]

#7030: qsv in ffmpeg
-+-
 Reporter:  palich2000   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  qsv  |   Blocked By:
  regression |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by heleppkes):

 The message even has a hint of what to do - try choosing a different rate
 control mode.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7030(avcodec:open): qsv in ffmpeg

[FFmpeg]

#7030: qsv in ffmpeg
-+-
 Reporter:  palich2000   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  qsv  |   Blocked By:
  regression |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by palich2000):

 Look above, there I described everything.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7030(avcodec:open): qsv in ffmpeg

[FFmpeg]

#7030: qsv in ffmpeg
-+-
 Reporter:  palich2000   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  qsv  |   Blocked By:
  regression |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by jkqxz):

 Then I suggest providing more information about your setup, and a complete
 log of a failing command.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7030(avcodec:open): qsv in ffmpeg

[FFmpeg]

#7030: qsv in ffmpeg
-+-
 Reporter:  palich2000   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  qsv  |   Blocked By:
  regression |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by palich2000):

 Without this parameter, the situation is as follows.
 The codec tries to code programmatically and it does not work.

 {{{
 [h264_qsv @ 0x1e87ec0] Selected ratecontrol mode is not supported by the
 QSV runtime. Choose a different mode.
 Error initializing output stream 0:0 -- Error while opening encoder for
 output stream #0:0 - maybe incorrect parameters such as bit_rate, rate,
 width or height
 [aac @ 0x1e8a540] Qavg: 62368.684
 }}}

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7030(avcodec:open): qsv in ffmpeg

[FFmpeg]

#7030: qsv in ffmpeg
-+-
 Reporter:  palich2000   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  qsv  |   Blocked By:
  regression |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by jkqxz):

 This works fine for me.  At a guess you are somehow opening the DRM master
 device rather than a render node and therefore the unused top-level device
 has exclusive access to the GPU and stops the encoder from opening it?

 If that's the problem then not creating the unused top-level device
 (remove the `-init_hw_device` option) should make it work for you.  (That
 device did automatically get passed to an encoder in 3.4, but there was
 disagreement about that feature being useful because ffmpeg was unable to
 tell whether the device was required or not (it isn't here, the internal
 session works for isolated encoders) and offered unhelpful warnings.)

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7053(avformat:new): bitpacked codec too limited

[FFmpeg]

#7053: bitpacked codec too limited
-+
 Reporter:  chacha   |Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  rtp  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+
Changes (by cehoyos):

 * keywords:   => rtp
 * priority:  normal => wish
 * version:  3.4 => git-master
 * component:  avcodec => avformat


Comment:

 Where can I find sample streams?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

[FFmpeg-trac] #7053(avcodec:new): bitpacked codec too limited

[FFmpeg]

#7053: bitpacked codec too limited
-+---
 Reporter:  chacha   | Type:  enhancement
   Status:  new  | Priority:  normal
Component:  avcodec  |  Version:  3.4
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---
 I am currently using ffplay to check RTP streams generated by third-party
 programs (along with their SDP files)
 Currently, ffplay can only decode YUV422 8 and 10 bits, sent to the
 bitpacked codec.

 However the RFC4175 (about RTP streams) submits far more formats :
 YUV422 12bits,
 YUV422 16bits,
 RGB888,
 RGB101010,
 RGB121212,  (with variants BGR/RGBA...)

 it would be great if rtpdec_4175.c and bitpacked.c could be updated to
 handle those formats (that must be decoded somewhere else in libavformat
 with another codepath linked to another codec)

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7052(avformat:new): rtmp_write dead loop

[FFmpeg]

#7052: rtmp_write dead loop
-+-
 Reporter:  palich2000   |Owner:
 Type:  defect   |   Status:  new
 Priority:  important|Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  rtmp |   Blocked By:
  deadlock   |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by palich2000):

 Yes, and thus it should be YouTube.
 The problem occurs when the network source (hls) and the network receiver
 (rtmp)

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7030(avcodec:open): qsv in ffmpeg

[FFmpeg]

#7030: qsv in ffmpeg
-+-
 Reporter:  palich2000   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  qsv  |   Blocked By:
  regression |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by palich2000):

 OK
 Sended.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7030(avcodec:open): qsv in ffmpeg

[FFmpeg]

#7030: qsv in ffmpeg
-+-
 Reporter:  palich2000   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  qsv  |   Blocked By:
  regression |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by cehoyos):

 Please send your patch - made with {{{git format-patch}}} - to the FFmpeg
 development mailing list where it can be reviewed.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7052(avformat:new): rtmp_write dead loop

[FFmpeg]

#7052: rtmp_write dead loop
-+-
 Reporter:  palich2000   |Owner:
 Type:  defect   |   Status:  new
 Priority:  important|Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  rtmp |   Blocked By:
  deadlock   |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * keywords:  rtmp_write dead loop => rtmp deadlock
 * priority:  critical => important


Comment:

 Is network input required to reproduce this issue?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

[FFmpeg-trac] #7052(avformat:new): rtmp_write dead loop

[FFmpeg]

#7052: rtmp_write dead loop
-+-
 Reporter:  palich2000   | Type:  defect
   Status:  new  | Priority:  critical
Component:  avformat |  Version:  git-
 Keywords:  rtmp_write   |  master
  dead loop  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 ffmpeg hangs tightly in the function retry_transfer_wrapper when the rtmp
 stream is published. This can happen in 5 minutes or an hour after the
 start of the broadcast. The function RTMP_Write () returns 0, this is not
 an error, but it indicates that it could not transfer data, this causes
 the write cycle to hang.

 {{{
 ffmpeg -nostats -xerror -err_detect compliant -loglevel info -vsync
 passthrough -frame_drop_threshold 4 -headers Accept-Charset:
 ISO-8859-1,utf-8;q=0.7,*;q=0.7? User-Agent: Mozilla/5.0 (X11; Linux
 x86_64; rv:10.0) Gecko/20150101 Firefox/47.0 (Chrome)? Accept:
 text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8? Accept-
 Language: en-us,en;q=0.5? Youtubedl-no-compression: True? Accept-Encoding:
 gzip, deflate?  -fflags +genpts -i
 
https://manifest.googlevideo.com/api/manifest/hls_playlist/id/r1L1J7E4oog.0/itag/95/source/yt_live_broadcast/requiressl/yes/ratebypass/yes/live/1/cmbypass/yes/goi/160/sgoap/gir%3Dyes%3Bitag%3D140/sgovp/gir%3Dyes%3Bitag%3D136/hls_chunk_host/r4
 ---sn-bpb5oxu-
 
3c26.googlevideo.com/ei/tQWZWqz7PNqFyAXCgLLoDA/playlist_type/DVR/gcr/ua/initcwndbps/133470/mm/32/mn
 /sn-bpb5oxu-
 
3c26/ms/lv/mv/m/pl/24/dover/10/keepalive/yes/mt/1519977742/ip/195.137.167.181/ipbits/0/expire/151510/sparams/ip,ipbits,expire,id,itag,source,requiressl,ratebypass,live,cmbypass,goi,sgoap,sgovp,hls_chunk_host,ei,playlist_type,gcr,initcwndbps,mm,mn,ms,mv,pl/signature/828CDB2191F0FD1BCEB3D09693C9FD38A5019093.843CBBCAA1E3C32882E36DDD448A15AB1F595D53/key/dg_yt0/playlist/index.m3u8
 -init_hw_device qsv:hw -filter_complex
 yadif=0:1:0,eq=1.1:0:1.25,scale=640:360:1 -g 50 -aspect 16:9 -c:v h264_qsv
 -profile:v main -pix_fmt nv12 -tune zerolatency -level 4.1 -aspect 16:9
 -preset medium -b:v 800k -minrate:v 800k -maxrate:v 800k -bufsize:v 2400k
 -g 25 -strict experimental -strict experimental -acodec aac -ab 64k -ar
 44100 -af aresample=async=1:min_hard_comp=0.20:first_pts=0 -f flv
 rtmp://localhost/vip/_1_

 ffmpeg version N-90182-g40102a2
 built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-11)
 }}}
 {{{
 Thread 1 (Thread 0x7fa95f2a6840 (LWP 18390)):
 #0  0x0041f523 in decode_interrupt_cb (ctx=0x0) at
 fftools/ffmpeg.c:471
 #1  0x7fa95e420ca7 in retry_transfer_wrapper
 (transfer_func=0x7fa95e477e30 , size_min=32768, size=32768,
 buf=0x2a87640 "\t", h=0x2904900) at libavformat/avio.c:374
 #2  ffurl_write (h=0x2904900, buf=0x2a87640 "\t", size=32768) at
 libavformat/avio.c:429
 #3  0x7fa95e423b61 in writeout (len=32768, data=,
 s=0x2a8f780) at libavformat/aviobuf.c:163
 #4  flush_buffer (s=0x2a8f780) at libavformat/aviobuf.c:184
 #5  avio_write (s=s@entry=0x2a8f780, buf=0x3ee5550 "", size=32752) at
 libavformat/aviobuf.c:231
 #6  0x7fa95e446f10 in flv_write_packet (s=0x29dde80,
 pkt=0x7ffe3a82fd80) at libavformat/flvenc.c:1031
 #7  0x7fa95e4cf8f5 in write_packet (pkt=0x7ffe3a82fd80, s=0x29dde80)
 at libavformat/mux.c:747
 #8  av_interleaved_write_frame (s=s@entry=0x29dde80, pkt=0x0,
 pkt@entry=0x7ffe3a830250) at libavformat/mux.c:1231
 #9  0x00421c82 in write_packet (pkt=pkt@entry=0x7ffe3a830250,
 ost=ost@entry=0x2901500, unqueue=unqueue@entry=0, of=0x1e5f940,
 of=0x1e5f940) at fftools/ffmpeg.c:807
 #10 0x00424515 in output_packet (of=of@entry=0x1e5f940,
 pkt=pkt@entry=0x7ffe3a830250, ost=ost@entry=0x2901500, eof=0) at
 fftools/ffmpeg.c:878
 #11 0x00425450 in do_video_out (of=of@entry=0x1e5f940,
 ost=ost@entry=0x2901500, next_picture=next_picture@entry=0x39e7bc0,
 sync_ipts=, sync_ipts@entry=72723.160011291504) at
 fftools/ffmpeg.c:1312
 #12 0x00429226 in reap_filters (flush=flush@entry=0) at
 fftools/ffmpeg.c:1498
 #13 0x00408fe9 in transcode_step () at fftools/ffmpeg.c:4592
 #14 transcode () at fftools/ffmpeg.c:4636
 #15 main (argc=, argv=) at
 fftools/ffmpeg.c:4839

 }}}

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7040(undetermined:closed): transcode mp4 using qsv get "Error opening the internal VPP session"

[FFmpeg]

#7040: transcode mp4 using qsv get "Error opening the internal VPP session"
-+-
 Reporter:  zzugyl   |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  qsv  |   Resolution:
 Blocking:   |  needs_more_info
Analyzed by developer:  0|   Blocked By:
 |  Reproduced by developer:  0
-+-
Changes (by cehoyos):

 * status:  new => closed
 * component:  ffmpeg => undetermined
 * priority:  important => normal
 * version:  3.4 => unspecified
 * keywords:  qsv hwaccel h264_qsv => qsv
 * resolution:   => needs_more_info


--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #7048(build system:reopened): building 3.4.2 with gcc 7.3.0 with altivec support enabled fails on ppc (Gentoo Linux)

[FFmpeg]

#7048: building 3.4.2 with gcc 7.3.0 with altivec support enabled fails on ppc
(Gentoo Linux)
-+-
 Reporter:   |Owner:
  ernsteiswuerfel|   Status:  reopened
 Type:  defect   |Component:  build
 Priority:  normal   |  system
  Version:  unspecified  |   Resolution:
 Keywords:  gcc altivec  |   Blocked By:
  ppc|  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Unrelated: {{{--disable-runtime-cpudetect}}} does not do what you/Gentoo
 expect, you cannot disable the call to the cpu detection function.

 I assume this is the the same issue as Gentoo bugs 578802 and 645778:
 Perhaps you can find out if completely removing {{{--optflags}}} from the
 build has a disadvantage (after confirming this is also your issue)?

 I wonder if it would be an advantage for you if configure would detect the
 broken custom compilation flags and disable !AltiVec...

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac