[FFmpeg-trac] #8620(avdevice:open): Fundamental bug in DirectShow capture - wrong timestamps

FFmpeg trac at avcodec.org
Wed Jun 2 19:03:32 EEST 2021


#8620: Fundamental bug in DirectShow capture - wrong timestamps
-------------------------------------+-------------------------------------
             Reporter:  Dmitry       |                    Owner:  (none)
  Sinitsyn                           |
                 Type:  defect       |                   Status:  open
             Priority:  normal       |                Component:  avdevice
              Version:  unspecified  |               Resolution:
             Keywords:  dshow dts    |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by Dmitry Sinitsyn):

 Replying to [comment:19 Balling]:
 > Replying to [comment:17 Dmitry Sinitsyn]:
 > > Replying to [comment:16 Diederick Niehorster]:
 > > > Ah, so is there a case missin? something like:
 > > Yes. I think so now. That patch was my first attempt to make ffmpeg
 >
 > Okay, but you still do not know what to do with big initial negative
 PTS?
 I did never see "big initial negative PTS". But current workaround for
 this case is OK for me.

 >
 > >those numbers do not relate to Media Sample PTS.
 >
 > Okay, but after that there will be two different ways to calculate
 framerate, is not it?
 I still do not understand why do you mention about framerate here. It is
 from a different place - from stream info.
 Timestamp generated by DirectShow source filter for each its media sample.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/8620#comment:20>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list