Re: [FFmpeg-trac] #7702(undetermined:new): Incorrect video frame reporting

[FFmpeg]

#7702: Incorrect video  frame reporting
-+-
 Reporter:  budman1  |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 budman1):

 You are kidding right? I succeeded in creating a segment that has frame 0
 dts/pts timecode of 0.00 for better merging. Players play segment
 starting with frame 0 (1850).  You cannot extract frame 0 (1850/1851)
 because ffprobe displays the first frame as being crystal clear, complete
 frame, audio in sync 'B' frame.

 Bug is: Players view frame 0/1 (1850/1851) so they are included. ffmpeg
 cannot extract those frames because according to ffprobe they do not
 exist!

 One more item: 25 FPS and 29.97 FPS work correctly.  30 FPS does not.

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

Re: [FFmpeg-trac] #7704(avcodec:new): 8-bit pixel format is used when decoding 10-bit video using VideoToolbox

[FFmpeg]

#7704: 8-bit pixel format is used when decoding 10-bit video using VideoToolbox
--+---
 Reporter:  fumoboy007|Owner:
 Type:  defect|   Status:  new
 Priority:  normal|Component:  avcodec
  Version:  git-master|   Resolution:
 Keywords:  videotoolbox  |   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+---

Comment (by fumoboy007):

 Here is an unfinished patch. It is unfinished because we should probably
 check at runtime for macOS 10.13+ before using the 10-bit pixel format
 since that is when it was introduced. I don’t have time in the immediate
 future to figure out how to check the macOS version at runtime.

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

Re: [FFmpeg-trac] #7704(avcodec:new): 8-bit pixel format is used when decoding 10-bit video using VideoToolbox

[FFmpeg]

#7704: 8-bit pixel format is used when decoding 10-bit video using VideoToolbox
--+---
 Reporter:  fumoboy007|Owner:
 Type:  defect|   Status:  new
 Priority:  normal|Component:  avcodec
  Version:  git-master|   Resolution:
 Keywords:  videotoolbox  |   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+---
Changes (by cehoyos):

 * keywords:  10bit videotoolbox hdr hwaccel => videotoolbox


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

Re: [FFmpeg-trac] #7704(avcodec:new): 8-bit pixel format is used when decoding 10-bit video using VideoToolbox

[FFmpeg]

#7704: 8-bit pixel format is used when decoding 10-bit video using VideoToolbox
-+-
 Reporter:  fumoboy007   |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  10bit|   Blocked By:
  videotoolbox hdr hwaccel   |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-
Changes (by fumoboy007):

 * keywords:  10bit videotoolbox hdr => 10bit videotoolbox hdr hwaccel


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

[FFmpeg-trac] #7704(avcodec:new): 8-bit pixel format is used when decoding 10-bit video using VideoToolbox

[FFmpeg]

#7704: 8-bit pixel format is used when decoding 10-bit video using VideoToolbox
-+-
 Reporter:  fumoboy007   | Type:  defect
   Status:  new  | Priority:  normal
Component:  avcodec  |  Version:  git-
 Keywords:  10bit|  master
  videotoolbox hdr   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 Summary of the bug:
 `kCVPixelFormatType_420YpCbCr8BiPlanarVideoRange` is always used
 regardless of the bit depth of the video.

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

Re: [FFmpeg-trac] #7702(undetermined:new): Incorrect video frame reporting

[FFmpeg]

#7702: Incorrect video  frame reporting
-+-
 Reporter:  budman1  |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 cehoyos):

 Why??

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

Re: [FFmpeg-trac] #7702(undetermined:new): Incorrect video frame reporting

[FFmpeg]

#7702: Incorrect video  frame reporting
-+-
 Reporter:  budman1  |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 budman1):

 Uploaded 'FFmpeg log.rtf' (ffmpeg command line tested together with the
 complete, uncut console output to make this a valid ticket.)

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

Re: [FFmpeg-trac] #7637(undetermined:new): movenc.c does not properly handle subtitle durations (including pauses) exceeding INT_MAX - 1 microseconds

[FFmpeg]

#7637: movenc.c does not properly handle subtitle durations (including pauses)
exceeding INT_MAX - 1 microseconds
-+-
 Reporter:  erikbs   |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:  mov  |   Resolution:
  mov_text   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * keywords:   => mov mov_text
 * component:  avcodec => undetermined


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

Re: [FFmpeg-trac] #7051(undetermined:new): ffmpeg (libx264) skip frames

[FFmpeg]

#7051: ffmpeg (libx264) skip frames
-+-
 Reporter:  fireman10|Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  rtsp |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

 * keywords:  skip frames => rtsp


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

Re: [FFmpeg-trac] #7699(avcodec:closed): [regression] vaapi: Zero refs for a frame with P or B slices

[FFmpeg]

#7699: [regression] vaapi: Zero refs for a frame with P or B slices
-+-
 Reporter:  uartie   |Owner:
 Type:  defect   |   Status:  closed
 Priority:  important|Component:  avcodec
  Version:  git-master   |   Resolution:  fixed
 Keywords:  vaapi|   Blocked By:
  regression |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

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


Comment:

 Fixed in 44bcccb7f0c43cb40f1e61f6e1e19cf2ab266c57

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

Re: [FFmpeg-trac] #7151(avformat:closed): Incorrect duration and bitrate reported for mpegts stream

[FFmpeg]

#7151: Incorrect duration and bitrate reported for mpegts stream
+
 Reporter:  tmm1|Owner:
 Type:  defect  |   Status:  closed
 Priority:  normal  |Component:  avformat
  Version:  git-master  |   Resolution:  fixed
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+
Changes (by cehoyos):

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


Comment:

 Fixed in fd6e89586c01d068fc8d2cea24292bf8ae836f74

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

Re: [FFmpeg-trac] #7166(avformat:closed): HLS format with fmp4 creates empty init.mp4 file when there is a single m4s output segment

[FFmpeg]

#7166: HLS format with fmp4 creates empty init.mp4 file when there is a single 
m4s
output segment
+
 Reporter:  catbug  |Owner:
 Type:  defect  |   Status:  closed
 Priority:  normal  |Component:  avformat
  Version:  git-master  |   Resolution:  fixed
 Keywords:  hls |   Blocked By:
 Blocking:  |  Reproduced by developer:  1
Analyzed by developer:  0   |
+
Changes (by cehoyos):

 * status:  new => closed
 * resolution:   => fixed
 * version:  unspecified => git-master
 * component:  undetermined => avformat
 * reproduced:  0 => 1


Comment:

 Fixed in 76b8e42c1f0453215244c45114d5aa302e2add7b

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

Re: [FFmpeg-trac] #7210(avcodec:new): avcodec decoder error: existing hardware acceleration cannot be reused

[FFmpeg]

#7210: avcodec decoder error: existing hardware acceleration cannot be reused
-+-
 Reporter:  styxxx   |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avcodec
  Version:  unspecified  |   Resolution:
 Keywords:  vdpau|   Blocked By:
  videolan   |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * keywords:  vdpau => vdpau videolan
 * version:  3.4 => unspecified


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

Re: [FFmpeg-trac] #7217(ffprobe:new): ffprobe produces wrong XML; "data_hash" attribute sometimes in text

[FFmpeg]

#7217: ffprobe produces wrong XML; "data_hash" attribute sometimes in text
+---
 Reporter:  carlreinke  |Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  ffprobe
  Version:  git-master  |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+---
Changes (by cehoyos):

 * version:  3.2.4 => git-master


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

Re: [FFmpeg-trac] #7689(avformat:new): instance depth difference between external librtmp and builtin librtmp

[FFmpeg]

#7689: instance depth difference between external librtmp and builtin librtmp
+
 Reporter:  zermok  |Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  avformat
  Version:  git-master  |   Resolution:
 Keywords:  rtmp|   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+

Comment (by zermok):

 do you have enough 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] #7702(undetermined:new): Incorrect video frame reporting

[FFmpeg]

#7702: Incorrect video  frame reporting
-+-
 Reporter:  budman1  |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 cehoyos):

 Please provide the `ffmpeg` command line you tested together with the
 complete, uncut console output to make this a valid ticket.

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

Re: [FFmpeg-trac] #7037(avcodec:open): ffmpeg destroys HDR information when encoding

[FFmpeg]

#7037: ffmpeg destroys HDR information when encoding
-+---
 Reporter:  mario66  |Owner:  cehoyos
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  libx265 hdr  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by jamrial):

 Replying to [comment:10 mario66]:
 > This is why open source always fails because the glorified people who
 work in their spare time for this project just do things that make fun not
 things that are actually necessary.
 > Only if people get payed to fix bugs there is a chance that the project
 will become usable. That's the sad truth.
 You're chastising people for doing something fun and interesting in what
 you acknowledged is their spare time, and not what you think should be
 done instead. I hope you realize how absurd and entitled that sounds.

 > Libav was so right. It had much better developers with a much better
 mindset, too bad it was abandoned.
 Adding color information to the filter chain during format negotiation in
 encoding scenarios is a huge change that no one capable of implementing
 has felt like doing. And that includes every developer from ffmpeg and
 libav for the better part of the past two decades.


 This is a bug tracker, not a discussion forum. Stick to technical reports
 here, and criticize development elsewhere.

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

Re: [FFmpeg-trac] #7702(undetermined:new): Incorrect video frame reporting

[FFmpeg]

#7702: Incorrect video  frame reporting
-+-
 Reporter:  budman1  |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 budman1):

 Updating to ffmpeg version N-93022-g260f1960e7 solved player problem but
 still extracts wrong frame
 -
 create Blank clip, no sound:
 BlankClip(length=3600, width=640, height=480, fps=30, color=$00)

 create blank clip (GOP=50, FPS=30)with Frame type, Frame number and time
 embedded using Avisynth and FFMpeg:

 Avisynth script (test.avs):
 FFmpegSource2("C:\Users\Bud\Desktop\G50_30_Test
 Pattern.mp4").Crop(0,0,-0,-0).LanczosResize(640,480)
 ScriptClip(Last, """Subtitle("[ "+Chr(FFPICT_TYPE)+" ]",
 size=(Height*56.0/720), align=2)""", after_frame=true)
 Subtitle("Test_Pattern.mp4", x=295, y=240, font="Arial", size=24,
 text_color=$ff, align=3)
 ShowFrameNumber(scroll=true, x=10, y=27, font="Arial", size=24,
 text_color=$80)
 ShowTime(x=72, y=44, font="Arial", size=24, text_color=$80)
 ShowSMPTE(fps=25, x=68, y=61, font="Arial", size=24, text_color=$80)

 FFMpeg script:
 ffmpeg -i test.avs -an -c:v libx264 -crf 22 -g 50 -r 30
 "G50_30_Test_Pattern.mp4"

 Cut at frame 1848 (I-Frame with new file frame 0 dts 0.06616, 1st cut):
 ffmpeg -i "G50_30_Test_Pattern.mp4" -ss 61.60 -vframes 1750 -c:v copy
 -c:a copy -y "C:\Users\Bud\Desktop\1852\G50_30_Test_Pattern_First.mp4"

 check dts/pts (gives dts time 0.066016):
 ffprobe -i "C:\Users\Bud\Desktop\G50_30_Test_Pattern_First.mp4" -v quiet
 -select_streams v -show_frames -show_entries frame=pkt_pts_time
 -read_intervals %+6 -of csv

 In order to get 0.00 dts (dts * 0.667 = 0.044033)
 ffmpeg -nostats -loglevel 0 -ss 0.044033 -i
 "C:\Users\Bud\Desktop\G50_30_Test_Pattern_First.mp4" -vframes 1750 -c:v
 copy -c:a copy -y "C:\Users\Bud\Desktop\G50_30_Test_Pattern_Final.mp4"

 Check dts/pts (gives dts time 0.00):
 ffprobe -i "C:\Users\Bud\Desktop\G50_30_Test_Pattern_Final.mp4" -v quiet
 -select_streams v -show_frames -show_entries frame=pkt_pts_time
 -read_intervals %+6 -of csv

 ffplay script to view (see final_ffplay.jpg):
 
DirectShowSource("C:\Users\Bud\Desktop\1852\G50_30_Test_Pattern_Final.mp4").Crop(0,
 0, -0, -0)x = float(Width) / float(Height)
 last.LanczosResize(round(x * 480.0 / 4.0) * 4, 480).trim(0, -1750)
 ShowFrameNumber(offset=0,scroll=true, x=10, y=127, font="Arial", size=24,
 text_color=$80)
 ShowTime(offset_f=0,x=72, y=144, font="Arial", size=24,
 text_color=$80)

 extract first frame as xxx.jpg (final_1st_frame.jpg):
 ffmpeg -i "C:\Users\Bud\Desktop\1852\G50_30_Test_Pattern_Final.mp4" -ss
 0.00 -f image2 -q:v 1 -vf
 
scale=640:-2,"drawtext=fontfile=c:/Windows/Fonts/Arial.ttf:text='0.00':fontsize=30:box=1:x=(w-tw)/2:y=h-(2*lh),drawtext=fontfile=c:/Windows/Fonts/Arial.ttf:text='0:1':fontsize=30:box=1:x=(w-tw)/2:y=h-(2*lh)-30"
 -vframes 1 -y
 "C:\Users\Bud\Desktop\TrimNMerge\TrimNMerge\bin\Debug\work\Thumb_1.jpg

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

Re: [FFmpeg-trac] #7037(avcodec:open): ffmpeg destroys HDR information when encoding

[FFmpeg]

#7037: ffmpeg destroys HDR information when encoding
-+---
 Reporter:  mario66  |Owner:  cehoyos
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  libx265 hdr  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by cehoyos):

 Replying to [comment:14 mario66]:
 > Libav was focused on getting things right before working on fancy new
 stuff. This was the absolute correct thing to focus on. Unfortunately, it
 got abandoned because, like I said, doing things right doesn't attract
 developers. It's the fancy new stuff that attracts developers, because
 they just want to have fun while coding. This is how "open source
 development" always works. Libav was the rare exception but too few people
 followed them.

 Again: If any of this were true why did you report your issue here?

 > It's so sad. I would definitively use it if it was actively developed,
 this I can tell you.

 Why do you believe it is not actively developed?

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

Re: [FFmpeg-trac] #7037(avcodec:open): ffmpeg destroys HDR information when encoding

[FFmpeg]

#7037: ffmpeg destroys HDR information when encoding
-+---
 Reporter:  mario66  |Owner:  cehoyos
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  libx265 hdr  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by mario66):

 Libav was focused on getting things right before working on fancy new
 stuff. This was the absolute correct thing to focus on. Unfortunately, it
 got abandoned because, like I said, doing things right doesn't attract
 developers. It's the fancy new stuff that attracts developers, because
 they just want to have fun while coding. This is how "open source
 development" always works. Libav was the rare exception but too few people
 followed them. It's so sad. I would definitively use it if it was actively
 developed, this I can tell you.

 HDR is just not usable with ffmpeg because of this. It was not developed
 until the end. Probably something more fancy was on the way.

 "ffmpeg HDR metadata" is the among the top 4 (!) suggestions in Google if
 you type "ffmpeg HDR". Because everyone who wants to encode HDR will
 stumble across this. HDR is already in the mass marked. Even cheap TV
 supports it. I would consider this as a major drawback of ffmpeg that it
 cannot properly handle HDR. And I am sure some people haven't even noticed
 but they will screwed once they find out that in their media backup
 collection important metadata is missing.

 I'm just telling the truth.

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

Re: [FFmpeg-trac] #7644(undetermined:closed): print warning for "-c:v copy" + "-ss non-key-frame"

[FFmpeg]

#7644: print warning for "-c:v copy" + "-ss non-key-frame"
-+-
 Reporter:  hanshenrik   |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |  needs_more_info
Analyzed by developer:  0|   Blocked By:
 |  Reproduced by developer:  0
-+-

Comment (by hanshenrik):

 Replying to [comment:5 cehoyos]:
 > Without an example for ''black/random-color frames'' I don't think this
 is a valid ticket.
 > (There is at least one codec for which it does happen, but this is a
 known and reported bug for this codec, not something unavoidable.)

 there is a real example in #7640

 youtube-dl 'https://www.youtube.com/watch?v=PojTP32lE_o' -o in.mkv -q
 2>/dev/null

 ffmpeg -i "in.mkv" -c:v copy -c:a copy  -ss 00:11:32 -t 10.8 -y test.mkv

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

Re: [FFmpeg-trac] #7677(undetermined:closed): Some converted video files fail miserably with Apple video players

[FFmpeg]

#7677: Some converted video files fail miserably with Apple video players
-+-
 Reporter:  forthrin |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:  duplicate
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by forthrin):

 Resolving the issue is beyond even the ingenious FFmpeg developers? Must
 be a real nut, then. The suggestion in #5882 seemed so easy. Looks like
 we'll have to live with it until some brainiac has an eureka moment. Wish
 I could help, but video conversion isn't my forte. Thanks for clarifying.

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

Re: [FFmpeg-trac] #7677(undetermined:closed): Some converted video files fail miserably with Apple video players

[FFmpeg]

#7677: Some converted video files fail miserably with Apple video players
-+-
 Reporter:  forthrin |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:  duplicate
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by cehoyos):

 Several people failed, please send your patch - made with `git format-
 patch` - to the FFmpeg development mailing list if you succeed.

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

Re: [FFmpeg-trac] #7037(avcodec:open): ffmpeg destroys HDR information when encoding

[FFmpeg]

#7037: ffmpeg destroys HDR information when encoding
-+---
 Reporter:  mario66  |Owner:  cehoyos
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  libx265 hdr  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by cehoyos):

 Replying to [comment:10 mario66]:
 > Libav was so right. It had much better developers with a much better
 mindset, too bad it was abandoned.
 I am curious: So why did you report the issue here?

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

Re: [FFmpeg-trac] #6542(undetermined:closed): drawtext fails to render non-Latin characters

[FFmpeg]

#6542: drawtext fails to render non-Latin characters
-+-
 Reporter:  KenSharp |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:  drawtext |   Resolution:  invalid
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

 * keywords:  utf-8 => drawtext
 * status:  new => closed
 * resolution:   => invalid


Comment:

 You have to choose another font: !TrueType fonts never contain all UTF-8
 glyphs.

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

Re: [FFmpeg-trac] #7677(undetermined:closed): Some converted video files fail miserably with Apple video players

[FFmpeg]

#7677: Some converted video files fail miserably with Apple video players
-+-
 Reporter:  forthrin |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:  duplicate
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by forthrin):

 Can FFmpeg be changed so this issue is detected and fixed automatically?
 If not, could you explain why?

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

Re: [FFmpeg-trac] #7037(avcodec:open): ffmpeg destroys HDR information when encoding

[FFmpeg]

#7037: ffmpeg destroys HDR information when encoding
-+---
 Reporter:  mario66  |Owner:  cehoyos
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  libx265 hdr  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by mario66):

 cehoyos, so you are going to fix this bug now? Great!

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

Re: [FFmpeg-trac] #7037(avcodec:open): ffmpeg destroys HDR information when encoding

[FFmpeg]

#7037: ffmpeg destroys HDR information when encoding
-+---
 Reporter:  mario66  |Owner:  cehoyos
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  libx265 hdr  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---
Changes (by mario66):

 * owner:   => cehoyos
 * status:  new => open


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

Re: [FFmpeg-trac] #7037(avcodec:new): ffmpeg destroys HDR information when encoding

[FFmpeg]

#7037: ffmpeg destroys HDR information when encoding
-+---
 Reporter:  mario66  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  libx265 hdr  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by mario66):

 If you were as fast fixing this bug as you are to downplay the importance,
 we would have no issue here.

 I created a forum thread here
 https://forum.doom9.org/showthread.php?t=175278 and it got lots of
 attention. People wrote me personal messages because they had the exact
 same problem and asked me if I meanwhile found a solution. The truth is,
 however, that still no solution exists. I'm disappointed. ffmpeg is just
 another failing open source project where the developers only focus on
 integrating fancy cool stuff no one needs. If you read the changelog it
 mentions dozens of unnecessary filters you ''added'' but it never says
 that something was ''fixed''.

 This is why open source always fails because the glorified people who work
 in their spare time for this project just do things that make fun not
 things that are actually necessary.
 Only if people get payed to fix bugs there is a chance that the project
 will become usable. That's the sad truth.

 Libav was so right. It had much better developers with a much better
 mindset, too bad it was abandoned.

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

Re: [FFmpeg-trac] #7703(undetermined:closed): Dolby TrueHD: 100 buffers queued in out_0_0, something may be wrong

[FFmpeg]

#7703: Dolby TrueHD: 100 buffers queued in out_0_0, something may be wrong
-+-
 Reporter:  flx90|Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:  invalid
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

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


Comment:

 Thank you Hendrik, I wasn't sure if I remember the issue correctly.

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

Re: [FFmpeg-trac] #7037(avcodec:new): ffmpeg destroys HDR information when encoding

[FFmpeg]

#7037: ffmpeg destroys HDR information when encoding
-+---
 Reporter:  mario66  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  libx265 hdr  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---
Changes (by cehoyos):

 * priority:  important => normal


Comment:

 This is not a regression afaict.

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

Re: [FFmpeg-trac] #7037(avcodec:new): ffmpeg destroys HDR information when encoding

[FFmpeg]

#7037: ffmpeg destroys HDR information when encoding
-+---
 Reporter:  mario66  |Owner:
 Type:  defect   |   Status:  new
 Priority:  important|Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  libx265 hdr  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---
Changes (by mario66):

 * priority:  normal => important


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

Re: [FFmpeg-trac] #7037(avcodec:new): ffmpeg destroys HDR information when encoding

[FFmpeg]

#7037: ffmpeg destroys HDR information when encoding
-+---
 Reporter:  mario66  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  libx265 hdr  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by mario66):

 I don't understand. Why is no one working on this? There is clearly a
 demand for this. People have to write awfully long script for this to
 compensate this shortcoming. Here is one example:
 
https://forum.doom9.org/showthread.php?s=1e8582f9d692cbc7f04d205d05964122&p=1833683#post1833683

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

Re: [FFmpeg-trac] #7688(avcodec:closed): ARBC Codec

[FFmpeg]

#7688: ARBC Codec
-+---
 Reporter:  compn|Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:  fixed
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---
Changes (by cehoyos):

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


Comment:

 Implemented by Paul in 795af110f70bbd12b45ae2d3b08e7f45db5224a0

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

Re: [FFmpeg-trac] #7703(undetermined:new): Dolby TrueHD: 100 buffers queued in out_0_0, something may be wrong

[FFmpeg]

#7703: Dolby TrueHD: 100 buffers queued in out_0_0, something may be wrong
-+-
 Reporter:  flx90|Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by flx90):

 File is fine.

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

Re: [FFmpeg-trac] #7703(undetermined:new): Dolby TrueHD: 100 buffers queued in out_0_0, something may be wrong

[FFmpeg]

#7703: Dolby TrueHD: 100 buffers queued in out_0_0, something may be wrong
-+-
 Reporter:  flx90|Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by heleppkes):

 Is something actually wrong, or does the file come out fine?

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

[FFmpeg-trac] #7703(undetermined:new): Dolby TrueHD: 100 buffers queued in out_0_0, something may be wrong

[FFmpeg]

#7703: Dolby TrueHD: 100 buffers queued in out_0_0, something may be wrong
-+-
 Reporter:  flx90| Type:  defect
   Status:  new  | Priority:  normal
Component:   |  Version:  git-
  undetermined   |  master
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 I'm trying to convert Dolby TrueHD embedded in mkv container to alac and
 mux it into mp4(m4v)-container.
 I get the following message: [out_0_0 @ 0045a0c0] 100 buffers
 queued in out_0_0, something may be wrong.

 This can be replicated using one of those Dolby Trailers:
 https://thedigitaltheater.com/dolby-trailers/

 The message occurs with every output (alac, flac, wav, ...).


 Uncut console output:
 {{{
 ffmpeg -i Dolby_Bit_Harvest_Lossless-thedigitaltheater.mkv -map 0:1 -c:a
 alac Dolby_Bit_Harvest_Lossless-thedigitaltheater.m4v
 ffmpeg version N-93022-g260f1960e7 Copyright (c) 2000-2019 the FFmpeg
 developers
   built with gcc 8.2.1 (GCC) 20181201
   configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-
 fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-
 libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-
 amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus
 --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora
 --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp
 --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg
 --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-
 libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex
 --enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable-
 ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec
 --enable-dxva2 --enable-avisynth --enable-libopenmpt
   libavutil  56. 26.100 / 56. 26.100
   libavcodec 58. 44.100 / 58. 44.100
   libavformat58. 26.100 / 58. 26.100
   libavdevice58.  6.101 / 58.  6.101
   libavfilter 7. 48.100 /  7. 48.100
   libswscale  5.  4.100 /  5.  4.100
   libswresample   3.  4.100 /  3.  4.100
   libpostproc55.  4.100 / 55.  4.100
 Input #0, matroska,webm, from 'Dolby_Bit_Harvest_Lossless-
 thedigitaltheater.mkv':
   Metadata:
 encoder : libmakemkv v1.9.5 (1.3.0/1.4.1) win(x64-release)
 creation_time   : 2015-08-29T18:56:26.00Z
   Duration: 00:00:11.01, start: 0.00, bitrate: 12615 kb/s
 Stream #0:0(eng): Video: h264 (High), yuv420p(progressive), 1920x1080,
 SAR 1:1 DAR 16:9, 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc
 Stream #0:1(eng): Audio: truehd, 48000 Hz, 7.1, s32 (24 bit) (default)
 Metadata:
   title   : Surround 7.1
 Stream mapping:
   Stream #0:1 -> #0:0 (truehd (native) -> alac (native)) Press [q] to
 stop, [?] for help Output #0, ipod, to 'Dolby_Bit_Harvest_Lossless-
 thedigitaltheater.m4v':
   Metadata:
 encoder : Lavf58.26.100
 Stream #0:0(eng): Audio: alac (alac / 0x63616C61), 48000 Hz,
 6.1(back), s32p (24 bit), 128 kb/s (default)
 Metadata:
   title   : Surround 7.1
   encoder : Lavc58.44.100 alac
 [out_0_0 @ 0045a0c0] 100 buffers queued in out_0_0, something may
 be wrong.
 [truehd @ 02ff7640] End of stream indicated.
 size=5179kB time=00:00:11.09 bitrate=3824.1kbits/s speed=22.9x
 video:0kB audio:5177kB subtitle:0kB other streams:0kB global headers:0kB
 muxing overhead: 0.040051%
 }}}

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

Re: [FFmpeg-trac] #7637(avcodec:new): movenc.c does not properly handle subtitle durations (including pauses) exceeding INT_MAX - 1 microseconds

[FFmpeg]

#7637: movenc.c does not properly handle subtitle durations (including pauses)
exceeding INT_MAX - 1 microseconds
+---
 Reporter:  erikbs  |Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  avcodec
  Version:  git-master  |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+---

Comment (by flx90):

 I'm facing exactly the same problem.

 Currently putting  for 1 ms as a workaround between a long time of
 absence of subtitles.

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

Re: [FFmpeg-trac] #6304(undetermined:closed): Unable to parse some subtitles with a system ffmpeg compiled HandBrake

[FFmpeg]

#6304: Unable to parse some subtitles with a system ffmpeg compiled HandBrake
-+-
 Reporter:  slaanesh |Owner:
 Type:  defect   |   Status:  closed
 Priority:  important|Component:
  Version:  unspecified  |  undetermined
 Keywords:  handbrake|   Resolution:  invalid
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

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


Comment:

 !HandBrake has switched to FFmpeg some time ago, this should not be an
 issue anymore.

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

Re: [FFmpeg-trac] #7661(avformat:closed): SubViewer .sub files with UTF8 encoding are decoded incorrectly

[FFmpeg]

#7661: SubViewer .sub files with UTF8 encoding are decoded incorrectly
+
 Reporter:  lukasf  |Owner:
 Type:  defect  |   Status:  closed
 Priority:  normal  |Component:  avformat
  Version:  git-master  |   Resolution:  fixed
 Keywords:  SubViewer   |   Blocked By:
 Blocking:  |  Reproduced by developer:  1
Analyzed by developer:  0   |
+
Changes (by cehoyos):

 * status:  new => closed
 * resolution:   => fixed
 * reproduced:  0 => 1


Comment:

 Should be fixed in d3a69438049b481dd9db1af82fd22494d7560ee4

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

Re: [FFmpeg-trac] #7701(undetermined:new): [Parsed_deinterlace_qsv_2 Error during deinterlacing: -16

[FFmpeg]

#7701: [Parsed_deinterlace_qsv_2 Error during deinterlacing: -16
-+-
 Reporter:  kwsk |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  qsv  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by kwsk):

 Replying to [comment:3 cehoyos]:
 > Replying to [comment:2 kwsk]:
 >
 > > How Can I upload sample file?
 > Use https://streams.videolan.org/upload/ or a file hoster of your
 choice.

 I uploaded videolan.org with Trac Ticket #7701

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

Re: [FFmpeg-trac] #7701(undetermined:new): [Parsed_deinterlace_qsv_2 Error during deinterlacing: -16

[FFmpeg]

#7701: [Parsed_deinterlace_qsv_2 Error during deinterlacing: -16
-+-
 Reporter:  kwsk |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  qsv  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by cehoyos):

 Replying to [comment:2 kwsk]:

 > How Can I upload sample file?
 Use https://streams.videolan.org/upload/ or a file hoster of your choice.

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

Re: [FFmpeg-trac] #7702(undetermined:new): Incorrect video frame reporting

[FFmpeg]

#7702: Incorrect video  frame reporting
-+-
 Reporter:  budman1  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

 * keywords:  Key frame dts pts =>


Comment:

 Please test current FFmpeg git head and provide the command you tested
 together with the complete, uncut console output to make this a valid
 ticket.

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