[Feature] Transcode policy: accept open codecs (lpcm, flac, vp8) #10540
pyorot
started this conversation in
Feature Request
Replies: 1 comment 1 reply
-
I'm especially interested in flac as it is a web-safe codec. It is supported in every modern browser: https://caniuse.com/flac I have "original" files encoded with AV1 + flac that I would prefer not to generate thumbnails for. I just want to be able to add it to the Should be a fairly easy change to add it to the enum. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have searched the existing feature requests to make sure this is not a duplicate request.
The feature
It's caused me problems (excessive storage usage) that I've been unable to disable the transcoding of files that open normally in my clients, that is, ones that use fairly universal open formats. As part of making transcode policy more flexible, we can add more options to the lists of accepted formats. We don't need to offer the option to transcode into them, but generally speaking, I would like to see a more extensive lists of codecs and a doc page talking loosely about what is expected to work where.
One could argue accepting vp8 and flac is unnecessary insofar as there aren't any devices known to capture photos/videos in them, but lpcm is both universal on the web (the unique uncompressed audio format, stored in wav container usually) and used by iPhones as part of the mov part of live photos.
Platform
Beta Was this translation helpful? Give feedback.
All reactions