Comskip Detection off by Half (only in GBPVR)

[tweeknockr]

Well, I went back and a recording that I know was in 720p (Lost, on ABC) was correctly identified at 59.94 fps, and in GBPVR the commercial locations were dead on.

Further, I took the (what I'm fairly convinced was) 1080i video, and manually set the framerate to be 59.94 in the *.csv file generated by comskip. It then went through and reprocessed, and the .txt file said that it was processed at 59.94, but GBPVR still showed the incorrect commercial locations.

It seems odd that GBPVR is incorrectly identifying the framerate, but playback is fine (ie not at twice the speed)...?

[sub]

Further, I took the (what I'm fairly convinced was) 1080i video, and manually set the framerate to be 59.94 in the *.csv file generated by comskip. It then went through and reprocessed, and the .txt file said that it was processed at 59.94, but GBPVR still showed the incorrect commercial locations.

When comskip thought it was 30fps, and GB-PVR thought it was 60fps, then it was pretty clear that you'd get the results shown in your screenshot.

If the comskip file and GB-PVR both agreed that it was 60fps, then I cant seen any reason why it would not be showing in the correct locations. I have to assume you did something wrong in your attempt to test this.

[erik]

Comskip reads the framerate from the MPEG file, also from DVR-MS files
It disregards whatever value you set.
Just to make sure, remove any fps setting in you comskip.ini

Do you use the .edl file or the .txt file to transfer the results to GBPVR?
.txt files are independend from the frame rate because it is based on the frame count. The conversion between frame number and position on the timeline is done in GBPVR.
.edl files give the position of the commercials in second so the conversion between frame numers and seconds is done on Comskip.

Could you enable the .edl output (output_edl=1) so you can check consistency in the calculations done by comskip?

Make sure you do not set sage_framenumber_bug or sage_minute_bug to 1 because that will mess up the frame count.

[sub]

GB-PVR only supports the .txt files.

[sub]

If you have access to a web server and can make a 100MB or smaller sample file available, then I'll download it and take a look. Otherwise, I dont know....

[tweeknockr]

Sounds good... I'll work on it.

[tweeknockr]

Sub,

I've PM'd you a link with the download.

[erik]

Can you PM me also the details so I can also download and check?

[erik]

Sub,

Comskip sees this recording as 1407 frames and a large blackframe sequence around frame 950

Even if comskip makes a fps error that does not influence the output of the .txt file.

I checked, frame_period = 90900 meaning 29.97 fps.
Or am I wrong?

[sub]

Sub,

Comskip sees this recording as 1407 frames and a large blackframe sequence around frame 950

Even if comskip makes a fps error that does not influence the output of the .txt file.

I checked, frame_period = 90900 meaning 29.97 fps.
Or am I wrong?

I'm not really sure. I dont have any tools for analysing dvr-ms file.

The MPEG sequence header in the file indicates it is 59.94 fps, which is where GB-PVR is getting this from. The property page for the VMR renderer in graphedit also shows it delivering 59.94 fps.