Skip to content

Latest commit

 

History

History
42 lines (32 loc) · 1.72 KB

README.md

File metadata and controls

42 lines (32 loc) · 1.72 KB

avpipe

"What if ffmpeg was a GUI application?" "I have no clue what I'm doing."

This project aims to become a GUI-based tool for basic editing of audio and video files and streams: (re-)encoding, (re-)muxing, cutting, splicing, basic mixing/compositing, filtering…

The name "avpipe" comes from ffmpeg filtergraphs forming a series of pipes that the streams go through. At some point, we might have a visual graph editor for this.

History

I started this for two reasons: modern NLEs require absurd amounts of resources and are overkill for most of the tasks I need them for, and building a ffmpeg command/script is time-consuming and sometimes an experience in frustration, especially for someone who doesn't do it on a frequent basis.

This started out as an idea for a GUI for building ffmpeg commands, but quickly became its own program to allow for useful features like live previewing.

A long-term goal (or pipe dream) would be feature-parity with ffmpeg.

Building

You'll need:

  • GCC 12 (currently under development), or
  • clang 7 (currently under development), or
  • CL 19.30 (Visual Studio 2022 v. 17)

Install the dev packages for Qt 5, then mkdir out && cmake -B out && cmake --build out
It'll download and build the rest of the dependencies, then build the project, with the resulting binary in the out directory. The project should also work in Visual Studio 2019 (this is what I use) and other IDEs.

You can also take a look at .github/workflows/build.yml. This is the build script that runs on every push.

We don't pull Qt on our own because it takes too much time and disk space to build. (We tried, it just broke our CI half the time.)

This is being developed on Windows, but should also run on Linux/BSD/macOS.