Bug with comskip autoskip?

[erik]

Is it correct to assume its a Sage bug?
I don't hear any mention of this problem on other fora.
COuld be a timeline problem.
Or is it on all recordings?

[cslatt]

It appears to be a problem with the STVi import which adds the skipping functionality to Sage. The code seems to be in need of some TLC. There is this bug, the framerate issue that you added a workaround for and some other issues with the accuracy of the skips getting farther and farther off over time. Also ideally, the code would be updated to use the time code format for commerical skip files (like the edl files that SA outputs) as that would simplify things and help prevent a whole class of these bugs regarding mis-calculated times and such. Unfortunately, nobody has stepped up to the plate to try updating the code. I'm hoping to tackle it someday if nobody else does, but I haven't had the time yet to sit down with the Studio documentation and get familiar.

[erik]

Comskip can output other formats too, like edl.
Would another output format help?

[cslatt]

Not unless someone steps up and updates the comskip import code.

[scoful]

I'm afraid I don't know much about studio yet, but I did notice in the comskip section it looked like it would jump forward a predefined amount without checking to see if there was that much of the video left to play. I'll take a little closer look when I get a chance. I'm guessing it's trying to skip beyond the end of the clip, so Sage just sends it back to where it came from since the point requested doesn't exist. Then it hits the comskip mark again and tries to jump forward again, creating the perpetual loop.