#9814: time_scale / num_units_in_tick is not infinite precision
-------------------------------------+-------------------------------------
Reporter: Balling | Owner: (none)
Type: enhancement | Status: reopened
Priority: wish | Component:
| undetermined
Version: git-master | Resolution:
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 1
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Changes (by Balling):
* priority: normal => wish
* status: closed => reopened
* resolution: invalid =>
* type: defect => enhancement
Comment:
>Issue is that your timebase is generic one that can not reproduce your
fps perfectly
I need 30k tbn, '''not 1200k''' tbn BY DEFAULT. Nice that you understand.
Changing to feature request.
Why does it report
{{{
[mp4 @ 0000022d9775a040] Timestamps are unset in a packet for stream 0.
This is deprecated and will stop working in the future. Fix your code to
set the timestamps properly
}}}
That is just strange.
>and .h264 does not store pts or timebase at all.
It does have timing SEI, but not in my sample. Anyway, it sets
fixed_frame_rate_flag, yet after this genius remux it has CFR with a
different frame rate. Like how strange is that.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/9814#comment:4>
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".
