[FFmpeg-trac] #8475(avfilter:new): pad filter fails in certain edge cases because of rounding

[FFmpeg]

#8475: pad filter fails in certain edge cases because of rounding
-+-
 Reporter:  imiddle  | Type:  defect
   Status:  new  | Priority:  normal
Component:  avfilter |  Version:  git-
 Keywords:  pad filter   |  master
  rounding   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 In certain cases, the `pad` filter fails to configure itself properly.
 Here's an example, using imagemagick to create an appropriate test file:

 {{{
 $ convert -size 15x15 xc:red -sampling-factor 4:2:0 red.jpg
 $ ffmpeg -i red.jpg -vf pad=iw+16:ih+16:ow-iw:oh-ih pad.png
 ...
 ...Input area 16:16:31:31 not within the padded area 0:0:30:30...
 }}}

 It seems like `ow-iw` and `oh-ih` should always work as values of `x` and
 `y`; this should put the image in the lower right corner.

 The failure occurs because the values of `w:h:x:y` are first computed as
 `31:31:16:16` and then rounded down (via `ff_draw_round_to_sub`) to
 `30:30:16:16` due to chroma considerations. Since the values of `w` and
 `h` have shrunk but `x` and `y` have not, the image is no longer validly
 placed.

 A possible solution is to round off `w` and `h` before evaluating `x` and
 `y`. In my example, this would result in `w:h` being evaluated as `31:31`
 and rounded to `30:30`, then `x:y` being evaluated as `15:15` and rounded
 to `14:14`.

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

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #8474(undetermined:new): rtcpport param doesn't add a=rtcp to SDP

[FFmpeg]

#8474: rtcpport param doesn't add a=rtcp to SDP
-+-
 Reporter:  juannm   |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  unspecified  |   Resolution:
 Keywords:  rtp, sdp |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * version:  4.2 => unspecified
 * component:  ffmpeg => undetermined


Comment:

 Is this issue not reproducible with current FFmpeg?

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

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #7068(undetermined:new): ffmpeg SDP file generation : incorrect header

[FFmpeg]

#7068: ffmpeg SDP file generation : incorrect header
-+-
 Reporter:  chacha   |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  unspecified  |   Resolution:
 Keywords:  sdp  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * version:  4.2 => unspecified
 * component:  ffmpeg => undetermined


Comment:

 The version you tested is old: Is the issue not reproducible with current
 FFmpeg git head, the only version supported on this bug tracker?

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

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #8474(ffmpeg:new): rtcpport param doesn't add a=rtcp to SDP

[FFmpeg]

#8474: rtcpport param doesn't add a=rtcp to SDP
--+--
 Reporter:  juannm|Owner:
 Type:  defect|   Status:  new
 Priority:  normal|Component:  ffmpeg
  Version:  4.2   |   Resolution:
 Keywords:  rtp, sdp  |   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+--
Changes (by juannm):

 * cc: oneorjuan@… (removed)


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

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #7068(ffmpeg:new): ffmpeg SDP file generation : incorrect header

[FFmpeg]

#7068: ffmpeg SDP file generation : incorrect header
+--
 Reporter:  chacha  |Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  ffmpeg
  Version:  4.2 |   Resolution:
 Keywords:  sdp |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+--
Changes (by juannm):

 * cc: oneorjuan@… (removed)


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

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #8474(ffmpeg:new): rtcpport param doesn't add a=rtcp to SDP

[FFmpeg]

#8474: rtcpport param doesn't add a=rtcp to SDP
--+--
 Reporter:  juannm|Owner:
 Type:  defect|   Status:  new
 Priority:  normal|Component:  ffmpeg
  Version:  4.2   |   Resolution:
 Keywords:  rtp, sdp  |   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+--
Changes (by juannm):

 * cc: oneorjuan@… (added)


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

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #7068(ffmpeg:new): ffmpeg SDP file generation : incorrect header

[FFmpeg]

#7068: ffmpeg SDP file generation : incorrect header
+--
 Reporter:  chacha  |Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  ffmpeg
  Version:  4.2 |   Resolution:
 Keywords:  sdp |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+--
Changes (by juannm):

 * cc: oneorjuan@… (added)
 * version:  unspecified => 4.2
 * component:  undetermined => ffmpeg


Comment:

 I'm adding the full command line output in an attempt to make this a valid
 ticket, although for this specific case it shouldn't really be needed.
 Anyone who has ever seen an SDP message ever, knows that starting with
 "SDP:" is not valid.

 Test command:

 {{{
 ffmpeg \
 -re \
 -i video.mp4 \
 -an \
 -c:v copy \
 -f rtp \
 -sdp_file video.sdp \
 "rtp://127.0.0.1:5004"
 }}}

 Generated SDP file:

 {{{
 SDP:
 v=0
 o=- 0 0 IN IP4 127.0.0.1
 s=No Name
 c=IN IP4 127.0.0.1
 t=0 0
 a=tool:libavformat 58.29.100
 m=video 5004 RTP/AVP 96
 a=rtpmap:96 H264/9
 a=fmtp:96 packetization-mode=1; sprop-parameter-
 sets=Z0LAH9kAUAW7ARAAAD6QAAu4CPGDJIA=,aMuMsg==; profile-level-id=42C01F
 }}}

 Offending line:

 {{{
 SDP:
 }}}

 Expected SDP file:

 {{{
 v=0
 o=- 0 0 IN IP4 127.0.0.1
 s=No Name
 c=IN IP4 127.0.0.1
 t=0 0
 a=tool:libavformat 58.29.100
 m=video 5004 RTP/AVP 96
 a=rtpmap:96 H264/9
 a=fmtp:96 packetization-mode=1; sprop-parameter-
 sets=Z0LAH9kAUAW7ARAAAD6QAAu4CPGDJIA=,aMuMsg==; profile-level-id=42C01F
 }}}

 Tested version: latest available as of right now in John Van Sickle's
 website: https://www.johnvansickle.com/ffmpeg/

 Full, uncut console output generated with '-report' and provided in the
 attached file.

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

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #7068(ffmpeg:new): ffmpeg SDP file generation : incorrect header

[FFmpeg]

#7068: ffmpeg SDP file generation : incorrect header
+--
 Reporter:  chacha  |Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  ffmpeg
  Version:  4.2 |   Resolution:
 Keywords:  sdp |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+--
Changes (by juannm):

 * Attachment "ffmpeg-20200115-195214.log" added.

 Full, uncut console output

--
Ticket URL: <https://trac.ffmpeg.org/ticket/7068>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #8474(ffmpeg:new): rtcpport param doesn't add a=rtcp to SDP

[FFmpeg]

#8474: rtcpport param doesn't add a=rtcp to SDP
--+--
 Reporter:  juannm|Owner:
 Type:  defect|   Status:  new
 Priority:  normal|Component:  ffmpeg
  Version:  4.2   |   Resolution:
 Keywords:  rtp, sdp  |   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+--

Comment (by juannm):

 Ticket syntax failed when linking to the related bug report:
 https://trac.ffmpeg.org/ticket/7068 - "ffmpeg SDP file generation :
 incorrect header"

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

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-trac] #8474(ffmpeg:new): rtcpport param doesn't add a=rtcp to SDP

[FFmpeg]

#8474: rtcpport param doesn't add a=rtcp to SDP
--+--
 Reporter:  juannm| Type:  defect
   Status:  new   | Priority:  normal
Component:  ffmpeg|  Version:  4.2
 Keywords:  rtp, sdp  |   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+--
 Summary of the bug:
 It is possible to specify an RTCP port that is not the default RTP + 1.
 For this, we just have to add the parameter "rtcpport" to the output URL:

 {{{
 rtp://127.0.0.1:5004?rtcpport=54321
 }}}

 However, FFmpeg is not adding the corresponding media-level attribute
 "a=rtcp:54321" to the generated SDP file.

 This seems like a bug to me instead of a missing feature, because in SDP,
 the omission of the "a=rtcp" attribute is nominally equivalent to an
 implicit presence of that attribute, where the value is RTP + 1.

 So, in short, FFmpeg is generating an SDP where the RTCP port is wrong.



 How to reproduce:
 {{{
 ffmpeg \
 -re \
 -i video.mp4 \
 -an \
 -c:v copy \
 -f rtp \
 -sdp_file video.sdp \
 "rtp://127.0.0.1:5004?rtcpport=54321"
 }}}

 generates an SDP file, "video.sdp", with these contents:

 {{{
 SDP:
 v=0
 o=- 0 0 IN IP4 127.0.0.1
 s=No Name
 c=IN IP4 127.0.0.1
 t=0 0
 a=tool:libavformat 58.29.100
 m=video 5004 RTP/AVP 96
 a=rtpmap:96 H264/9
 a=fmtp:96 packetization-mode=1; sprop-parameter-
 sets=Z0LAH9kAUAW7ARAAAD6QAAu4CPGDJIA=,aMuMsg==; profile-level-id=42C01F
 }}}

 Expected SDP would NOT have the invalid first line "SDP:" (that's a
 different bug: #7068), and also it would have the "a=rtcp" line:

 {{{
 v=0
 o=- 0 0 IN IP4 127.0.0.1
 s=No Name
 c=IN IP4 127.0.0.1
 t=0 0
 a=tool:libavformat 58.29.100
 m=video 5004 RTP/AVP 96
 a=rtcp:54321
 a=rtpmap:96 H264/9
 a=fmtp:96 packetization-mode=1; sprop-parameter-
 sets=Z0LAH9kAUAW7ARAAAD6QAAu4CPGDJIA=,aMuMsg==; profile-level-id=42C01F
 }}}

 Full, uncut console output generated with '-report' and provided in the
 attached file.

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

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #8474(ffmpeg:new): rtcpport param doesn't add a=rtcp to SDP

[FFmpeg]

#8474: rtcpport param doesn't add a=rtcp to SDP
--+--
 Reporter:  juannm|Owner:
 Type:  defect|   Status:  new
 Priority:  normal|Component:  ffmpeg
  Version:  4.2   |   Resolution:
 Keywords:  rtp, sdp  |   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+--
Changes (by juannm):

 * Attachment "ffmpeg-20200115-193654.log" added.

 Full, uncut console output

--
Ticket URL: <https://trac.ffmpeg.org/ticket/8474>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #8460(undetermined:closed): H.264 VFR timestamp hazards (which means frame duration... or playback experience hazards)

[FFmpeg]

#8460: H.264 VFR timestamp hazards (which means frame duration... or playback
experience hazards)
-+-
 Reporter:  gdgsdg123|Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
 |  undetermined
  Version:  git-master   |   Resolution:
 |  needs_more_info
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by gdgsdg123):

 * Attachment "ffprobe.7z" added.


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

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #8473(undetermined:closed): Reduced timestamp report accuracy for MKV container?..

[FFmpeg]

#8473: Reduced timestamp report accuracy for MKV container?..
-+-
 Reporter:  gdgsdg123|Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
 |  undetermined
  Version:  git-master   |   Resolution:
 |  needs_more_info
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * priority:  wish => normal
 * resolution:   => needs_more_info
 * status:  new => closed
 * component:  ffprobe => undetermined
 * type:  enhancement => defect


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

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-trac] #8473(ffprobe:new): Reduced timestamp report accuracy for MKV container?..

[FFmpeg]

#8473: Reduced timestamp report accuracy for MKV container?..
---+---
 Reporter:  gdgsdg123  | Type:  enhancement
   Status:  new| Priority:  wish
Component:  ffprobe|  Version:  git-master
 Keywords: |   Blocked By:
 Blocking: |  Reproduced by developer:  0
Analyzed by developer:  0  |
---+---
 The timestamp report accuracy for AVI and MP4 container is 6 digits after
 the decimal point, while for MKV it's only 3...

 Is there any reason for this (seemingly) weird behavior?
 [[BR]]
 [[BR]]
 Check [http://trac.ffmpeg.org/ticket/8464#comment:4 this] also.

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

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #8472(undetermined:closed): MPEG-TS Muxer: Bug when output multiple files

[FFmpeg]

#8472: MPEG-TS Muxer: Bug when output multiple files
-+-
 Reporter:  ahakon   |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
 |  undetermined
  Version:  git-master   |   Resolution:  invalid
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * keywords:  mpegtsenc =>
 * component:  avformat => undetermined


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

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #8063(ffmpeg:reopened): `-vsync cfr` tends to duplicate the wrong frames

[FFmpeg]

#8063: `-vsync cfr` tends to duplicate the wrong frames
+
 Reporter:  gdgsdg123   |Owner:
 Type:  defect  |   Status:  reopened
 Priority:  normal  |Component:  ffmpeg
  Version:  git-master  |   Resolution:
 Keywords:  fps |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+

Comment (by cehoyos):

 Replying to [comment:8 gdgsdg123]:
 > Replying to [comment:7 cehoyos]:
 > > ...a (minor) issue can be reproduced with the sample file.
 > The issue is first observed in (and experimented with) production clips.

 Feel free to provide such clips.

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

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #8472(avformat:closed): MPEG-TS Muxer: Bug when output multiple files

[FFmpeg]

#8472: MPEG-TS Muxer: Bug when output multiple files
+
 Reporter:  ahakon  |Owner:
 Type:  defect  |   Status:  closed
 Priority:  normal  |Component:  avformat
  Version:  git-master  |   Resolution:  invalid
 Keywords:  mpegtsenc   |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+
Changes (by ahakon):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Sorry, the correct syntax is:

 {{{
 ffmpeg -f lavfi -i testsrc -t 20 \
  -map "0:v" -program title=prog1:st=0 -f mpegts prog1.ts \
  -map "0:v" -program title=prog2:st=0 -f mpegts prog2.ts
 }}}

 The key point is that after the "-map" parameter the "st" values are
 reseted.

 So I close this ticket.

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

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-trac] #8472(avformat:new): MPEG-TS Muxer: Bug when output multiple files

[FFmpeg]

#8472: MPEG-TS Muxer: Bug when output multiple files
---+--
 Reporter:  ahakon | Type:  defect
   Status:  new| Priority:  normal
Component:  avformat   |  Version:  git-master
 Keywords:  mpegtsenc  |   Blocked By:
 Blocking: |  Reproduced by developer:  0
Analyzed by developer:  0  |
---+--
 Summary of the bug: Multiple MPEG-TS output files are incorrect

 How to reproduce:
 {{{
 ffmpeg -f lavfi -i testsrc -t 20 \
  -map "0:v" -program title=prog1:st=0 -f mpegts prog1.ts \
  -map "0:v" -program title=prog2:st=1 -f mpegts prog2.ts
 }}}

 - In the file prog1.ts all is OK.
 - But in the file prog2.ts the PMT is incomplete (not includes any stream)
 and the video stream doesn’t have PCR marks. Then the file can’t be
 played.

 Please, fix this problem.
 Thank you!

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

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".