Skip to content
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: Ability to have much less samples #41

Open
Joshfindit opened this issue May 15, 2016 · 3 comments
Open

Feature request: Ability to have much less samples #41

Joshfindit opened this issue May 15, 2016 · 3 comments

Comments

@Joshfindit
Copy link

I have files that are 60-500 minutes, and all I need are at most 900 samples.

An example file: 141482 frames, (61:35.856) 3695.856
Even --pixels-per-second 1 gives 22K of JSON data.
We can pre-calculate the desired 'pixels-per-second' value (in this example case, it would be roughly --pixels-per-second 0.2165. 500 minutes would be roughly .0267), but audiowaveform seems to only take an integer.

Blue-sky, it would be great to have a '--desired-samples` that uses the first frame, the last frame, and calculates the spacing needed to reach the right number of frames, but that feels like a complex ask. :)

@swordsreversed
Copy link

+1

@chrisn
Copy link
Member

chrisn commented Jul 28, 2016

audiowaveform computes the data you need in order to output PNG images, but I'd need to give some thought to the command-line interface for it to output JSON or binary data instead: --start, --end, and --width get us most of the way there...

@timobehrens
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants