Closed sotelo closed 1 year ago
Maybe a simpler to implement intermediate solution would be to change the interpretation from seconds to milliseconds? That way you could keep the variable as an integer while giving significantly more flexibility. What do you think @rarzumanyan?
Hi @sotelo
It's a VPF bug. Thanks for bringing this up!
Actual seek function treats seek_frame
variable as double
despite it's uint64_t
:
https://github.com/NVIDIA/VideoProcessingFramework/blob/d8d5d1874c65ecfe6a82db2c282182e1b865452e/src/TC/src/FFmpegDemuxer.cpp#L295-L299
SeekContext
structure needs to be extended with double timestamp
.
@sotelo I've created a PR which shall fix this issue, could you please test it on your side? #497
@RomanArzumanyan not sure why I wasn't notified of your comment. Will check it out and report back! Thanks a lot for looking into this.
This is related to: https://github.com/NVIDIA/VideoProcessingFramework/issues/232
Describe the bug
nvc.SeekContext
expects an integer for theseek_frame
parameter. However, when we want to search by timestamp (because of a variable frame rate), we are limited to seeking for the frames at the integer second positions and can't seek for the frame at intermediate locations (i.e. 1.5 seconds).To Reproduce Steps to reproduce the behavior:
Expected behavior We should be able to specify floats as the seek location when seeking by timestamp.