-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
Better encoding defaults #9
Comments
There are some guidelines on settings for VP9. This codec might be a good default as it has better compression than VP8 and is already supported by all major browser. As not all browser support VP9, we should keep
|
Hello, I am a video compressionist and am able to help configure advanced encoding perameters. What I would like to also see is the ability to configure the encoding variables on the upload form. How can I do that? |
Hey @ajeema , the idea of the package is, to provide a simple way of video encoding for non-video-compression experts and the one video will automatically be encoded to all defined resolutions. That's why the whole configuration is hidden away in the Django settings. I am sure there is a way to provide a form to select different encoding methods, but this is not something I want to include in this package as most users will simply use the provided defaults. Anyway, I would be more than happy to accept a PR, which update the current defaults with some modern ones :) |
This was very nice as a new user, however, I'm wanting to customize this and I'm unable to really grok how to do so as of now. EDIT: Ok, so its in config.py. Probably worth providing this link in the README so it stands out more? shrug |
We currently have some default parameters (https://github.com/escaped/django-video-encoding/blob/master/video_encoding/config.py) to encode videos for the web. As I am not a video compression expert, I suspect that these values can be tweaked and optimized. Maybe there is someone with more experience and willing to contribute better defaults.
The text was updated successfully, but these errors were encountered: