Earlier quoted context omitted.
The complaint that Chrome eats all your RAM is because it starts a new process for each tab, with all the overhead that entails. You’re not using multiple tabs in an Electron app.
The overheard prevents any one tab from taking out the entire browser though.
Show HN: CompressX, my FFmpeg wrapper for macOS
161–170 of 173 posts
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#162Is it just me or is it deceptive to say that a person saves 50% when buying the "standard" license? Both Claude and Gemini seem to come up with a savings of almost 24%. The only way I can reach the 50% mark is by phrasing it as "buy 1 license and get a second license 50% off." Also "testimonial" should be plural, and "spams" should be singular.
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#163Earlier quoted context omitted.
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,…
EXIF metadata accounts for so little of the overall file size it isn't even worth mentioning...
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#164Earlier quoted context omitted.
I agree with the GP here. Yes, you can do all this with just FFMPEG, but now you have to wade through all the docs, flags, values to craft your CLI args with a bit of trial and error. The value add here is a coherent front-end that abstracts away all the complexity and lets you cut right to what you want. Further, if it's something you do infrequently, or your workflow changes, you have to rerun the gaunlet of figuri…
I had to transcode some files recently. I’m extremely proficient with the ClI, but I would have loved to have a GUI version.
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#165Earlier quoted context omitted.
I highly disagree. I think the majority of people who would pay money for a barebones ffmpeg wrapper don't care about telemetry.
Privacy should be the default, not something that is done only when users care enough to fight back.
Similar to Windows forcing users to update because most of them keep putting it off forever, hurting their own security.
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#166Earlier quoted context omitted.
Privacy should be the default, not something that is done only when users care enough to fight back.
I agree with you to a point. The problem is that if most people turn it off, then developing the telemetry system was a huge waste of time and resources for not much gain. Valuable data that could have been used to improve the program without any extra work from others may be lost. Similar to Windows forcing users to update because most of them keep putting it off forever, hurting their own security.
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#167A lot of people would just go “look at this app I made by myself, it compresses files”
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#168Looks 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%…
Other low cost video devices (like dashcams) can use higher bitrates and lower compression modes simply because they don’t have the CPU power to use the most optimal settings while also being able to record real-time streams.
You can save a lot of space by re-encoding these types of files on a real computer.
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#169Earlier quoted context omitted.
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,…
EXIF metadata accounts for so little of the overall file size it isn't even worth mentioning...
Re: Show HN: CompressX, my FFmpeg wrapper for macOS
#170Earlier quoted context omitted.
Thought of this too, how do they know how many GB are being reduced? Hope the analytics can be opted out.
I will implement the option to opt-out anonymous telemetry this week. Thanks for the feedback