-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync with ffmpeg #1554
Comments
Hi, sorry for the delay, the differences you are seeing may be because ffmpeg uses the "presentation time" (PTS), while this module uses the "decoding time" (DTS). You can check the DTS/PTS values of the frames using ffprobe, e.g. |
Many thanks for the answer! No problem for the delay it was a busy month for me too.
|
The question is about thumb? because you didn't mention it in the original post... |
Yeap, I am talking for the thumb grabber mainly, as this is the point of reference. So do you suggest to try to emulate the nginx-pckg-module thumb grabber into the vod module and then check what happens? I did not mention the thumbs in the beginning because by changing the configuration, I found a way to have video + thumbs synced, so I thought it was the same "seeking" mechanism. |
Yes, I think the thumb logic nginx-pckg-module is much more accurate. But it may require additional changes, because in the live framework, the packager (nginx-pckg-module) sends a param in the request to the segmenter (nginx-live-module) that returns only the frames of the relevant GOP (NGX_KSMP_FLAG_MEDIA_MIN_GOP). A similar logic will need to be added here. |
OK, I will try to give it a look in the next two weeks! Untill then, the mjpeg produced from ffmpeg will do the job :) |
If I try to cut from ffmpeg using time input from the playback,
e.g bring me the 10second to 25second part of the video
ffmpeg -ss 10 -i test.mp4 -t 15 -c copy out.mp4
there are sometimes small time differences, which is propably normal!
Do you know if its possible to emulate the timings of ffmpeg to that of the module?
Thanks a lot!
The text was updated successfully, but these errors were encountered: