Comskip Support Forum

I have added ATSC CC decoding to Comskip but before releasing I need some people to test.
Who is willing to receive a test version of Comskip, set verbose=10 and run Comskip on some recordings from various channels and see if the CC is decoded correctly?
The log file will contain the full CC transcript, it will also dump the XDS (such as V-Chip) data but not yet decode that data.
It should work on .mpg, .ts or dvr-ms files
Can not be combined with setting skip_b_frames != 0
It also contains test code to output a .srt file.

From the changelog

Changes in 0.79.133
- Added functionality to decode ATSC Close Captioning data. Will work on any file (mpg, ts, dvr-ms) that contains this information.
- Added the ability to generate a .srt file, Set output_srt=1 to enable. This is done by integrating ccextractorwin. Send me feedback on what other output formats of ccextractor are usefull.
- Added the ability to dump the user data stream from the mpeg recording. Set output_data=1 to enable. this will generate a .dmp file that could be compatible with ccextractor

Will this automatically try and use the dictionary along with the CC extracted to help in detection?? If that option is enabled in the .ini?

Yes

[quote="erik"]Yes[/quote]
Cool! I'll give this a try! That dictionary will need some updating now!

:)

Does logging need to remain at 10 for the use of CC in comskip detection, or can I set it back to 0???

No need to keep it at 10. Set at any value you like

[quote="erik"]No need to keep it at 10. Set at any value you like[/quote]
Terrific!

One more question.. I still see that the dictionary isn't being used.. I believe the exact wording in the log is: "Dictionary not processed successfully". The log does show all the CC data though...

My dictionary file is in the same folder as all the other comskip files. I call comskip using Dirmon..

Any idea why it isn't seeing/using the dictionary file?

Yes,

There is a big problem with dirmon as that it does not set the working directory to the directory where comskip.exe resides. Then comskip can not find its dictionary file
One possibility is to create a small batch file that contains something like

c:
cd \folder\where\comskip\can\be\found
comskip %1

and call that batch file instead of directly calling comskip

Normally comskip should be able to find from where its executed but due to some unknown reason this fails when comskip is invoked by dirmon.

[quote="erik"]call that batch file instead of directly calling comskip[/quote]
Worked perfectly!

Thanks!

Build 134 is available

From the changelog
Changes in 0.79.134
- Change the extension of the XDS dump file to .data
- When comskip is started with a .csv file the .data file containing the XDS dump will also be read when available.
- In ComskipGUI.exe the 'X' key can be used to show XDS data. Currently the Program Name, V_Chips, Program duration and Program position are displayed. Decoding of the XDS data is not yet complete
- A very thin grey vertical line at the very top of the debugbar timeline shows the location of the XDS data changes

Could someone set
output_framearray=1
output_data=1
and enable the Close Caption processing and upload for the a file with a lot of XDS both the generated .csv and .data to my ftp server?

I prefer a recording with V-Chip data that changes during show/commercial and that shows program position information.
This will allow me to test additional detection rules using the XDS data