GSOC - File analysis funcionality about ccextractor HOT 7 CLOSED

I'm trying to assign this to both Ruslan and Willem but it looks like I can't.

Anyway:
Ruslan => Changes in CCExtractor
Willem => Consume the output in a way that is useful for the test code

from ccextractor.

Looks interesting, but would it be possible to clarify this a little?
The way I'm understanding it now is:

1. run CCExtractor just as normal, but add an extra parameter to it.
2. Instead of outputting the normal info, it shows the info you put in the first post
3. This data should go into a report

Did I understand this correctly, or did you have it envisioned in another way?

from ccextractor.

That's pretty much it. The idea is that since CCExtractor already figures
out most of the information we make it easy to make use of that stuff for
external programs that want the information but not the subtitles. I get
emails from time to time from people who needs to know if a file has
captions but don't care about the captions themselves, for example.

On Wed, May 28, 2014 at 9:54 PM, wforums [email protected] wrote:

Looks interesting, but would it be possible to clarify this a little?
The way I'm understanding it now is:

1. run CCExtractor just as normal, but add an extra parameter to it.
2. Instead of outputting the normal info, it shows the info you put in the
   first post
3. This data should go into a report

Did I understand this correctly, or did you have it envisioned in another
way?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-44456134
.

from ccextractor.

Ok, that looks good then. I assume I'll have to wait for Ruslan then, and after that I can alter the tester to implement it.

from ccextractor.

Yes. Just discuss with Ruslan the most convenient output format for you :-)

On Wed, May 28, 2014 at 10:18 PM, wforums [email protected] wrote:

Ok, that looks good then. I assume I'll have to wait for Ruslan then, and
after that I can alter the tester to implement it.

—
Reply to this email directly or view it on GitHub
#17 (comment)
.

from ccextractor.

I'll stick to time as a limit for now.
What parameter should I use to print reports? -out=report or --report or something else? There is -endate for time.
If we output report to stdout then we should mute other printed info, right? Maybe just leave file name as separator in case there are several input files.
As for report content: Some of useful data are in global variables, other in local. I'll create a global structure with variables holding current info for the report.

from ccextractor.

I think the out parameter is the most interesting, since that one clearly indicates that there will be no other output generated. If we'd use --report it might be unclear to others.

And yes, other info should be suppressed, only that info should be displayed. For multiple files I'd go with the file name as separator, or a blank line.

from ccextractor.