I noticed an issue while using the parameter skip_b_frames=1 in comskip.ini while working to optimize performance on a x86_64 NAS (linux / celeron). comskip v82.005 This is also consistant with the regular donators comskip.exe v82.003 on Win10.

The resulting edl files show the same values as with/without skip_b_frames=0/1, however the calculated frame number values in the txt file are half of what they should be (6423 vs. 12846).

This is indeed a problem.The .txt output refers to frame numbers but when skipping b frames the frame number combined with frame rate is no longer consistent with timecode in the file.You are advised NOT to use .txt output when skipping frames but .edl output or any of the other time based outputs.In the future I may improve the dynamic calculation of the frame rate to prevent this from happening