Skip to content

Finalize video capabilities for EW 2.0 #116

Description

@michael

Currently missing:

  • Automatic video transcoding (e.g. drop a 400MB original .mov on a media placeholder, should be converted into a <50MB .mp4 file)
  • Ability to control initial autoplay (longer videos should not automatically start, to save bandwidth)
    • still undecided if users should control autoplay yes/no, maybe have all videos autoplay or at least autoplay all videos below a max-filesize-threshold makes sense
    • reasons is that people will engange / watch autoplayed videos, but likely skip the one that you have to manually start
  • video thumbnail extraction (there should be one good frame of the video as a placeholder, while the video is still loading or waiting to be played)

Solutions:

  • Probably MediaBunny is the right choice here

Specs:

If original video is stored at:
/assets/39c7952b6866b19581e6cd48c20da6b926a7f6e0c2e297f27bb705346b4d6761.mp4

Then store the cover in a folder

/assets/39c7952b6866b19581e6cd48c20da6b926a7f6e0c2e297f27bb705346b4d6761.mp4/cover.webp

Default is a maximum of 1280px for videos (for a 16:9 ratio that is equivalent to 720p).

I'd maybe leave some room for custom encoding of a video. So e.g. if you upload an .mp4 file that is < 20mb EW leaves it untouched. If it's bigger the resize/compression is performed.

Maybe there can be a smarter optimal compression detector. Goal is that it works for everything and videos are always web-optimized, but leaves room for manual tweaks.

H.264/MP4 is going to be the file format for all videos, it's the best regarding compatibility and interoperability.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions