New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: HTML export #17

Open
sheimend opened this Issue Aug 3, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@sheimend

sheimend commented Aug 3, 2016

I'd love a feature, similar to the existing CSV export, that saved each detected scene into a formatted HTML document that included the thumbnail frames that get saved out on scene detection change.

The HTML doc would contain a table with the same headers as the CSV currently has. However, there'd be a "Frame Image" column that includes one or more of the JPG frame grabs. Each scene would be represented by a row.

For folks who want to do further analysis (in Excel, for instance), it'd much easier to import an HTML table into Excel than it is to add images to a table without them - although that's also possible with an Excel macro.

You can construct the HTML file in the same section of code that currently builds the CSV, either using an HTML builder (I'm sure Python supports one?) or even just by hand by writing out the table markup.

Anyhow, super awesome piece of code you've got. Totally made my day yesterday!

@Breakthrough

This comment has been minimized.

Owner

Breakthrough commented Jan 16, 2017

Hey @sheimend;

I recently added integrated support for splitting videos to PySceneDetect (via mkvmerge), and will be adding HTML output to the list of features to tackle for the current revision series (v0.4.x). Feel I should mention this because in v0.4 and above the command line option -o defaults to the video output now, not the scene list output (the option is now -co, or --csv-output).

There's two approaches to implementing this that are reasonable. The first is changing the output option from --csv-output to --scene-list-output (-so), and making the output format selectable (and easy to customize). The second would be to simply add another flag -ho (--html-output) that outputs an HTML file, as well as any images to an img/ folder (if it exists).

I'm leaning towards the latter implementation, but am open to any suggestions you might have.

@Breakthrough

This comment has been minimized.

Owner

Breakthrough commented Aug 5, 2018

I apologize for the lack of progress on this issue, all my effort has been tied up with development of v0.5 (which is a complete refactor of both the CLI and Python API).

The integration of this feature should be significantly smoother now that the API has been rewritten for modularity first and foremost. I'm working on a feature to configure the number of output images.

In the meantime, if anyone has a suggestion for a template or how to format N images per scene, as well as the information about each scene's start/end/duration timecode, frame number, and in seconds, I would greatly appreciate it. I'm not much of an HTML/CSS person, so any help on how to format the output would be appreciated.

@qazqwezxc

This comment has been minimized.

qazqwezxc commented Dec 13, 2018

Hey @Breakthrough,

Has this been resolved? I'm a little new to this so if you've already completed the majority of the work here, I'll look for something else?

Regards,
Andrew H

@Breakthrough

This comment has been minimized.

Owner

Breakthrough commented Dec 13, 2018

Hi @qazqwezxc;

There hasn't been any progress on this actually, feel free to have a go at it!

I'm thinking there should be a new command like export-html or something, which should imply save-images, and functions roughly the same way (saves an HTML file with the same name as the video in the working directory, and an override is allowed like export-html --file "some_dir/my_html_file.html").

Also the command should reflect the global output directory flag (-o).

Thoughts? Thanks for your interest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment