Earlier quoted context omitted.
People rage about Electron being insecure and bloated, but by Jove it’s a godsend for consistency and portability.
Electron and consistency?? I get Electron being easier to develop for, but it achieves portability by ignoring platform native UI guidelines. There is no consistency at all between electron apps.
Show HN: CompressX, my FFmpeg wrapper for macOS
131–140 of 173 posts
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#132if anyone wants to do the same stuff for free on windows (except image resizing)
I use FFMPEGBatchAVConverter
https://ffmpeg-batch.sourceforge.io/
Batch FFMPEG conversion (I usually go from h264 to HEVC with my NVIDIA GPU 3060Ti)
> ffmpeg -i file.mp4 -c:v hevc_nvenc -rc vbr -cq 24 -qmin 24 -qmax 24 -profile:v main10 -pix_fmt p010le -b:v 0K -c:a aac -map 0
and LosslessCut
https://github.com/mifi/lossless-cut for ffmpeg cutting and splicing p0rn scenes.
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#133Earlier quoted context omitted.
It's because the user interface is actually consistent and normalised across the whole platform and the paradigms are well documented and understood by the developers producing software. On Windows and Linux one minute you're constantly poked in the eye by fucked up scaling issues, different toolkit weirdness and quirks, various layers of abandoned shit going back 25 years and people with the design ability of a thre…
but anyone can create an electron app these days with total control over the UI polish with way less effort. in fact electron seems like the perfect use case here for a ffmpeg UI wrapper. surprised no one has done it.
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#134How does your site know that “22 files compressed in the past hour”? Does the app collect this type of metrics from Desktop users, or is there some web-based function that’s being observed?
The app connects to telemetrydeck.com. Sadly, couldn't find any opt-out setting.
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#135How does your site know that “22 files compressed in the past hour”? Does the app collect this type of metrics from Desktop users, or is there some web-based function that’s being observed?
The app connects to telemetrydeck.com. Sadly, couldn't find any opt-out setting.
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#136How does your site know that “22 files compressed in the past hour”? Does the app collect this type of metrics from Desktop users, or is there some web-based function that’s being observed?
The app connects to telemetrydeck.com. Sadly, couldn't find any opt-out setting.
I would recommend removing this because it's against the GDPR... and even foreign companies have to comply (for the protection of European citizens, wherever they are) if they offer goods and/ or services to citizens in the EU in some way (European region of an app store, ad campaigns in Europe, etc.) I also think that the GDPR is pretty correct in requiring opt-in consent before tracking, so it's "the decent thing".
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#137Earlier quoted context omitted.
The app connects to telemetrydeck.com. Sadly, couldn't find any opt-out setting.
Block this domain with a firewall or DNS filter like NextDNS?
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#138Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#139Since ffmpeg has a wasm build, couldn't this be done client side?
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#140Looks cool but raises a bunch of questions :-). Maybe you could add these to your FAQ, I imagine picky users like me may want the answers to at least some of these: "up to 90% file size reduction" What's an example of an input video or image that would see its size reduced by 90% without loosing quality? Also, how do you come up with this percentage? I imagine median/average size reduction must be way lower than 90%…
The macOS integration on this app is impressive, but the technical compression bits are a combination of ffmpeg and off-the-shelf image compression libraries. The 90% number is a pretty typical (with lossy) image savings when taking a totally unoptimized jpeg out of a program like Photoshop. There's just a bunch of extra data that can be stripped out (EXIF for one), that doesn't affect how the image looks. For video,…