Frame is an open-source media conversion utility that wraps FFmpeg in a native Rust GUI for video, audio, image, subtitle, and metadata workflows.

From the article:

FFmpeg is a tool almost every Linux user has benefited from, even if they have never typed its name in a terminal. It powers countless media workflows, handling video, audio, image, subtitle, and metadata processing with great flexibility.

The problem is that using it directly usually means dealing with long commands, codec names, bitrate settings, filters, containers, and much trial and error. Frame tries to make that part less painful.

It is an open-source desktop application providing a graphical interface for FFmpeg. Instead of replacing FFmpeg, it wraps it in a native app and offers users a cleaner way to configure common media conversion tasks. The project describes itself as a native media conversion utility built in Rust, using FFmpeg and FFprobe underneath for media handling.

    • adarza@lemmy.caEnglish
      23·
      2 days ago

      the last sentence in the submission text might explain the ‘why’, at least from the project developer’s pov:

      built in Rust

    • terabyterex@lemmy.world
      5·
      2 days ago

      EDIT: i took the time to look and its not realky a gui for ffmpeg. it uses the same libraries but doesnt have the exact functionality as the ffmpeg program.

      i feel very silly. i always thought handbrake was an alternative. i never took the time to find out more but never knew it was a frontend for ffmpeg.

    • qupada@fedia.io
      10·
      2 days ago

      I’ve done some truly horrible things with it.

      Whenever we have big construction projects at work, I export footage from our CCTV system and time-lapse it.

      But then one time I wanted to put two videos side by side. Difficulty that they were both variable frame rate (a quirk of the NVR, but meant that played at constant rate they wouldn’t line up).

      It ended up with 5 copies of ffmpeg running at once. Because the most efficient way to create this monstrosity was 2 copies that stretched their input videos to 25fps (by duplicating frames), piped into two that ran the time lapsing, and both outputs into a 5th that assembled the video into one frame and encoded it.

      I think you’d struggle to represent that level of kerfuckery in a GUI, to be honest.

      • fuckwit_mcbumcrumble@lemmy.dbzer0.com
        6·
        2 days ago

        It’s not hard to remember the basics, but if you want to run some crazy encoding options/conversions then it’s annoying as hell. I made scripts for my most common options. But anything outside that and I can’t stand it.

        • Deebster@infosec.pub
          1·
          2 days ago

          I’d probably find more use in a TUI app that could help me with the more obscure options and give me the command. Then I could run it from the terminal and it would be in my history for next time. tldr but a wizard.