Hi, thought I might be able to add another data point here, running PySceneDetect on a linux system. You mentioned this happens with different sources, do they all share the same framerate/codec? Have you noticed the doubling in framerate in the output? Generally issues like that can be caused by corrupted video files, although since you mentioned this happens with several sources, I'd like to dig a little further into that and see if there is any commonalities between those sources (specifically how they were encoded). I'll investigate if forcing the output framerate would be an acceptable workaround, since it seems like there is indeed duplicate frames in the output in this particular case, although why that is I'll need your help to solve. Thus, the frame length I would calculate would be completely wrong (since the output seems to have twice the number of frames). I was able to get frame-accurate cuts by manually specifying -frames to ffmpeg, but ffmpeg thinks the framerate is actually 47.9fps (twice the input), whereas both OpenCV and vlc indicate that the original framerate is 23.9-something FPS. I'm able to replicate this issue on my end, but not sure exactly how to proceed. Hey I did some further digging here, and noticed something interesting - when re-encoding the file with ffmpeg, the framerate seems to double for some reason? Also the framerate of the original video is a rather odd number, can you confirm that it is correct? Although I doubt it's related here, note that PySceneDetect doesn't work with variable-framerate videos.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |