Starting to test Comskip with h.264 support

[erik]

Could you mail me a log file created with
verbose=10
in your comskip.ini file?

[killervette]

Originally Posted by erik

Could you mail me a log file created with
verbose=10
in your comskip.ini file?

sure...im out of town today and tomorrow, so i will try wednesday. thanks

[killervette]

Originally Posted by erik

Could you mail me a log file created with
verbose=10
in your comskip.ini file?

log zip sent

[Chaos~Theory]

Hey Erik,

I am still receiving those errors with Comskip on nntdll.dll.

Faulting application comskip.exe, version 1.4.6.0, time stamp 0x48e51430, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a783, exception code 0xc0000005, fault offset 0x00023592, process id 0x1b4c, application start time 0x01c928c5cfb565dc.

I installed the Microsoft Visual C++ 2008 Redistributable Package that you recomended, but it doesn't seem to help. I can't for the life of me figure out what is going on because it seems to throw out the error, but it keeps going on the file. At least that is what it seems like is happening.

Any suggestions?

[erik]

Nope,

When all the output files are blank there must be a crash.
What do you use to start comskip?

[killervette]

well, i think i will have to discontinue using comskip until it gets alittle further along. 1 out of 3 shows are tagged correctly, the rest are not accurate. i got a little frustrated, so i will try it again in the future. thanks

[erik]

The h.264 decoder is crashing.
I tried a newer version but no luck. Crash at the same location.
Will look into a recovery strategy.

[Chaos~Theory]

Hey Erik...

Sorry for not getting back to you, but it looks like you found the same problem I did. Some of the TS files are crashing out right after it finds the Logo. That is why I wasn't finding any zeroed log files! I'm glad I wasn't going nuts! The wierd thing is that if you hit the same file over about 3 times.... it will go back to processing it. (not once.... or twice.... but the third time "really" does do the charm!) There are, though, about 2% of my files of (250+ TS files), that it does go over again on that it crashes on and doesn't recover. And since it doesn't recover, and crashes at the moment, it never creates an "edl" or "txt" file that most people for set there scripts to look for to know that file had been process for comercials.

I had a thought.... (which is always scary) I noticed that Comskip recognizes that it is re-processing a file by way of the "Second time" header I see in the log file. Well, what if you some how kept an actual count of how many times a file had been re-scanned and, say, put in a limit of (x) (say 4 times) that if Comskip reaches that limit, put in a 'kill operations' flag in the log file (or something) so that it doesn't get processed again. Maybe even a new file.... "title of show.error" or something that is noticeable. I know having that would make me very happy!

So, it only looks like about 2% of my files don't get processed! The rest are pretty much right on.... some 'are' off, but I don't know if it's because of Comskip or because of the tracking problem they are having with SageTV at the moment. (i.e. MpegDeMux.ax") That, to me, is awesome work!

I know that I'm not going to give up on Comskip over a few errors..... Keep up the great work!

-Chris

[abbott_m]

I'll admit I'm a relative newcomer to comskip but since I installed the PVR, I started testing the code. Right now it's working on about half my .ts files nicely (very accurate detection). The others it seems to be dying after getting through almost t lahe entire. I've setup everything to retain the logs (set to verbose 10) so my question is how do I go about giving these logs to someone who can understand what is broken and advise?

Mike

[erik]

Please make sure you disable the CC detect_method when you experience Comskip crashing
Do try
detect_method=11

[Chaos~Theory]

Originally Posted by erik

Please make sure you disable the CC detect_method when you experience Comskip crashing
Do try
detect_method=11

Do you mean only selecting:
(1) Black Frame
(2) Logo
(8) Fuzzy Logic
....and not the default of '111'?

Will try it! My CC isn't working anyways..... hasn't worked since I installed SageTV v6.4.

Thanks Eirk!

[erik]

detect_method=111 also has no CC
Some people use
detect_method=127
and that implies also CC processing which for the new digital broadcast has some "weaknesses"

[killervette]

tried the 04 release. i used it on a 30 minute jon and kate plus 8. the end result is a edl file, but it cuts the commercial to soon every time. a couple seconds into the show, then there is the end of a bit of a commercial before it comes back on

[erik]

Try
detect_method=11

[bialio]

Hows the speed of comskip these days on h264? I tried the initial release and it was SLOOOOOWWWW

[erik]

Comskip build 0.80.006, released today, has a major robustness improvement.

[Djc208]

Updated to 80.006 but no help. MPEG files come through fine but only one TS file made it through and its a 480p resolution file. All the 1080i files crash at some point in the file. The .log file doesn't show error messages, however I ran one through the GUI file and the text window that opens showed multiple errors before it crashed.

Is there a way to keep the window open or have comskip dump the output to a file so I can forward it along?

I'm using the .ini file from the 80.005 version as you recommended and comskip is being called by comskip monitor. I did re-run the setup to include the .ts files in the scan and cleanup exemption portions.

[erik]

Its most probably the h.264 decoder crashing and that is very difficult to debug.
The error message do not tell a lot because the error message only appear if the decoder is able to recover from a faulty input. SO corrupt input without error messages can lead to a crash.

Best is to find a small as possible recording that causes Comskip to crash and to upload it to my ftp site. I will PM you with the upload details when you have one to upload.
Then I may be able to reproduce the problem and can run the processing in debug mode (this takes hours!!!)

[gplasky]

Using build 80.006 with Dirmon2 on Windows Home Server. Appeared to be hung on 2 movie recordings. Just kept crashing comskip and requeueing the files. Also comskip kept crashing on reboot and sending diag logs to ms. Once it crashed 4 or 5 times after the server came up. One time it just kept crashing. It did work on 27 tv recordings and performance seemed to be better. Once I get rid of those 2 problem movies i'll test again. (Also saw a MS C++ error but I'm not sure if that came from Sage's latest beta or not.

Gerry

[erik]

Find the shortest possible recordings that cause comskip to crash and upload them to my ftp server and I will try to solve the crash.