HandBrake found me a defective RAM module on my PC: it freezed in the middle of video conversion - every single time on exactly the same video position. After further investigation I found the "bug" in my RAM...
Amazing. These are like Bill Brasky stories or Schneier facts. If Handbrake fails, it's only because your hardware is broken.
HandBrake 1.0.0 Released
91–100 of 181 posts
Re: HandBrake 1.0.0 Released
#92I just downloaded it for the first time in a while 3 days ago and noticed that H.265 exists and compresses twice as well at the same quality level... how in the hell did I miss that? (VLC will play them). I did a test on a full-rez MKV and worked great
Most hardware video players (like Raspberry pi etc) can't decode H.265 using hardware acceleration, a RPi 2 (haven't testen RPi3) does not have enough computational power to play a FHD H.265 at 24FPS. Until hardware H.265 decoding is introduced to the popular media center hardware, H.264 will remain the codec of choice for most people.
Might never happen, thanks to netvc.
Re: HandBrake 1.0.0 Released
#93Earlier quoted context omitted.
Streaming doesn't stop it, you just record your screen. It's not perfect, but it works. DRM is dumb.
Yes, but it stops easy copying. Don't let good be the enemy of perfect.
Re: HandBrake 1.0.0 Released
#94Re: HandBrake 1.0.0 Released
#95HandBrake found me a defective RAM module on my PC: it freezed in the middle of video conversion - every single time on exactly the same video position. After further investigation I found the "bug" in my RAM...
Re: HandBrake 1.0.0 Released
#96Re: HandBrake 1.0.0 Released
#97Re: HandBrake 1.0.0 Released
#98I'm a little surprised they aren't signing their MacOS releases. It's even documented on the download page, "We are not currently able to sign the HandBrake downloads". I wonder if it's a philosophical choice or a legal one? It seems like a failure of Apple's Gatekeeper though: either because such a popular app is not able to be signed, or because it's not signed and yet so many people run it anyway.
Do any small developers actually do this? It seems entirely useless from a security prospective. You go through an expensive process so that at the end it can "verify" that the binary was signed by an individual the user has never met who may not even live in the same country and for all anyone knows is perfectly willing to sign ransomware, or who has stolen some arbitrary third party's signing key.
If you don't actually know and trust the party who makes the software then the signature is worse than useless because it makes people think signed=trustworthy when in reality it only means signed=signed. And if you do know and trust the authors you don't need a CA to verify anything more, at great expense, when you can already just download via HTTPS from the domain you trust.
Apple should eliminate practice entirely, and in the meantime no one should use it.
Re: HandBrake 1.0.0 Released
#99Re: HandBrake 1.0.0 Released
#100I haven't used either in a long time and would appreciate the input.