Comskip Support Forum

Comskip is a free commercial detector, browse the forum for more information
It is currently Tue Aug 14, 2018 2:32 pm

All times are UTC [ DST ]




Post new topic Reply to topic  [ 3 posts ] 
Author Message
PostPosted: Wed Mar 14, 2018 8:17 pm 
Offline

Joined: Wed Mar 14, 2018 4:27 pm
Posts: 2
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).


Top
 Profile  
Reply with quote  
PostPosted: Thu Mar 15, 2018 8:27 am 
Offline
Site Admin

Joined: Sun Aug 21, 2005 3:49 pm
Posts: 3193
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


Top
 Profile  
Reply with quote  
PostPosted: Thu Mar 15, 2018 9:20 pm 
Offline

Joined: Wed Mar 14, 2018 4:27 pm
Posts: 2
Will do.
Thanks!!


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

All times are UTC [ DST ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group