Just interested, how do you manage licensing tarpits around certain video codecs supported by ffmpeg?
FFmpeg is not bundled with the app. User will have to install it separately and link it with CompressX. Hope this explains
Yup, all clear, thanks!
Show HN: CompressX, my FFmpeg wrapper for macOS
171–173 of 173 posts
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#172Earlier quoted context omitted.
I actually think VSCode is one of the best use cases for Electron. It enables a robust and well-documented set of APIs for extension and theme developers, which IMO is why it has one of the most thriving extension ecosystems out there. Disclaimer: I work at Microsoft, but not in Developer Division.
> It enables a robust and well-documented set of APIs for extension and theme developers Didn't VIM and Emacs have that for ages? Look at https://vimawesome.com/ . I think the remote development extension is nice, but most people would just SSH and run their editor on the server or sync their project's files.
The Emacs APIs aren't exactly robust in the modern sense. They don't have the security and privilege isolation that VS Code's TypeScript APIs have.
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#173Earlier quoted context omitted.
Supports hundreds of file formats both new and ancient, ability to control every aspect of encoding, uses libx264/x265 which are much better than the libraries available in AVFoundation etc.. What does AVFoundation do that ffmpeg cannot? Probably streaming libraries, Dolby Vision support, hardware accelerated encoding. AVFoundation is great for what it is, an OS embedded library.
> …uses libx264/x265 which are much better than the libraries available in AVFoundation etc. Citations? As a counter-example, AVFoundation's AAC encoder trounces anything in ffmpeg, which ffmpeg thankfully exposes suffixed "_at". ffmpeg -i input.wav -c:a aac_at -profile:a aac_he -b:a 64k output.m4a https://wiki.hydrogenaud.io/index.php?title=Apple_AAC
Oh I thought we were talking about AVFoundation which is more for video than audio.
It's well known[1] that x264 is the best h.264 encoding library and produces the highest quality at the lowest bitrate (obviously at the expense of encoding speed). Software encoders for any codec are generally going to get better quality results at lower bitrates because of their ability to use more complex features.
OS library encoders are generally more focused on streaming and bitrate stability than quality. And to be honest, QAAC (Apple Core Media's AAC encoder) is kind of an anomaly that I'd chalk up to the absolute amazing amount of engineering that went into the ipod/iphone era.
[1] https://www.compression.ru/video/codec_comparison/h264_2012/