When exporting a film to a movie, Aleph One uses the FFMPEG API. This creates a burden on developers (because the API is not stable and frequently breaks the build), builders (because building FFMPEG often takes more than half of the compile time), and users (because only a very limited set of codecs and settings are available, and these settings result in very long encoding times and less-than-ideal quality).
We would like to rip out (nearly) all FFMPEG code from Aleph Bet, and replace it with a simple pipe to an external ffmpeg binary with command line arguments supplied by the user. Default arguments would be equivalent to the current settings, but could easily be customized to produce YUV444 output, use hardware encoding, or whatever else meets the user's needs. This would require users of the film export feature to install an ffmpeg binary on their system, but in my opinion, this burden is a small price to pay for the removal of all the aforementioned ones.
When exporting a film to a movie, Aleph One uses the FFMPEG API. This creates a burden on developers (because the API is not stable and frequently breaks the build), builders (because building FFMPEG often takes more than half of the compile time), and users (because only a very limited set of codecs and settings are available, and these settings result in very long encoding times and less-than-ideal quality).
We would like to rip out (nearly) all FFMPEG code from Aleph Bet, and replace it with a simple pipe to an external
ffmpegbinary with command line arguments supplied by the user. Default arguments would be equivalent to the current settings, but could easily be customized to produce YUV444 output, use hardware encoding, or whatever else meets the user's needs. This would require users of the film export feature to install anffmpegbinary on their system, but in my opinion, this burden is a small price to pay for the removal of all the aforementioned ones.