search

HomeOfAviSynthPlusEvolution / L-SMASH-Works

Forked from VFR-maniac/L-SMASH-Works; hydra3333/L-SMASH-Works; l33tmeatwad/L-SMASH-Works; HolyWu/L-SMASH-Works; AkarinVS/L-SMASH-Works.
89 stars 15 forks source link

Report on _AbsoluteTime #44

Closed Mr-Z-2697 closed 1 year ago

Mr-Z-2697 commented 1 year ago

This stream->start_time is pts and it should be devided by 1/time_base I think (should I just say multiply?), and It's meaningless for raw bitstream input because the pts of every frame will be AV_NOPTS_VALUE, which is interpreted as -9223372036854775808, since stream->start_time is pts of first frame, this will send the calculated _AbsoluteTime straight to even before the beginning of the universe (based on the estimated age of the universe) (if it's multiplied by time_base then probably not😜).

The parsed FPS of raw bitstreams is inaccurate by the way, it's always 25, it has been like this since release 20230430, but it's accurate when I built with official ffmpeg branch release/5.1 last time. The reason is likely ffmpeg changed the underlying mechanism of FPS parsing, a quick ffprobe test between recent git and 5.1.2 shows different fps value reported.

>ffprobe -hide_banner Desktop\onimai\01_fin.hevc
Input #0, hevc, from 'Desktop\onimai\01_fin.hevc':
  Duration: N/A, bitrate: N/A
  Stream #0:0: Video: hevc (Main 10), yuv420p10le(tv, bt709), 1920x1080, 25 fps, 23.98 tbr, 1200k tbn

>ffprobe-5.1.2 -hide_banner Desktop\onimai\01_fin.hevc
Input #0, hevc, from 'Desktop\onimai\01_fin.hevc':
  Duration: N/A, bitrate: N/A
  Stream #0:0: Video: hevc (Main 10), yuv420p10le(tv, bt709), 1920x1080, 23.98 fps, 23.98 tbr, 1200k tbn

(I only tested h264 and h265 bitstream)