61–70 of 181 posts
I ask as someone who uses ffmpeg regularly, what does Handbrake offer over ffmpeg?
How good is the ffmpeg AAC encoder these days? Ages ago when I started using HandBrake, it using Apple's CoreAudio codec on Macs for the AAC encoding was a big plus on the audio side.
I 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
Earlier quoted context omitted.
How good is the ffmpeg AAC encoder these days? Ages ago when I started using HandBrake, it using Apple's CoreAudio codec on Macs for the AAC encoding was a big plus on the audio side.
libfdk_aac is fast and good
There's a built-in ffmpeg AAC encoder too, but despite the author's claims it is not as good as libfdk_aac.
And libfdk_aac itself isn't as good as Apple's AAC codec either. There's a Hydrogenaudio listening test demonstrating that.
I often wonder if archivists are out there somewhere, armed with HandBrake, ripping every DVD they can find into a digital format for preservation beyond the life of the disc. I've been fascinated with some projects that have tried to recreate the original theater experience of the original Star Wars,[0] or groups trying to capture classics that influenced Chinese cinema but haven't been widely reproduced, like Red H…
Rest assured that there are archivists ripping their discs losslessly somewhere in the dark corners of the internet. Hidden because the copyright mafia will otherwise ruin their lives.
I often wonder if archivists are out there somewhere, armed with HandBrake, ripping every DVD they can find into a digital format for preservation beyond the life of the disc. I've been fascinated with some projects that have tried to recreate the original theater experience of the original Star Wars,[0] or groups trying to capture classics that influenced Chinese cinema but haven't been widely reproduced, like Red H…
DRM is dumb.
I ask as someone who uses ffmpeg regularly, what does Handbrake offer over ffmpeg?
How good is the ffmpeg AAC encoder these days? Ages ago when I started using HandBrake, it using Apple's CoreAudio codec on Macs for the AAC encoding was a big plus on the audio side.
Earlier quoted context omitted.
Yes, the absurd of piracy warnings is ridiculous Really makes me think twice about giving them my money
Nothing makes me want to go out and pirate something purely as an act of defiance than unskippable piracy warnings.
It is amazing to see software that is about 10 years old just hitting 1.0. Never really quite understood that. Is the developer just not confident in it that it is in beta for a while? or is it just a style of versioning? Anyways glad to see development on handbreak.Great software!
Versioning is generally arbitrary. I actually don't know why people pay so much attention to it. 1.0 for some people, is 0.1 for others. 1.0 might mean it's stable, or it could meant that it's feature complete. As you say it could also be used to convey the confidence the developers have in the software. The thing I find most important myself is conveying compatibility, i.e. semver. To me that tells me it will be eas…
Traditionally, version numbering has been used to signal the significance of the release. for version x.y.z, you could expect that
* x is incremented: Major new features, possibly incompatibilities
* y incremented but not x: Minor new features and bug fixes.
* z changed only: Bug fixes only.
Of cause there has always been a pressure from the marketing departments to have a new major release, while the engineers has been holding back, so you have always seen major releases that isn't that major, and sometimes incompatible changes sneaked into minor releases. The latter has generally been considered bad form.
Earlier quoted context omitted.
How is that even possible with virtual memory and paging? Why would the same video data or whatever go to the same physical location every time?
I can imagine bunches of possibilities. Paging can make things hard to predict, especially when multiple programs are allocating memory, but it doesn't make the system non-deterministic, nor does it make hitting the same physical address impossible. One possibility is that he didn't restart the program between retries, and the memory in question was already allocated. Another possibility is that he only ran handbrake…
What with Windows Update and the variety of other similar OS- and application-level auto-updaters, is getting the computer into a very similar state likely? I'm not sure but my gut says no.
That said, at first I was imagining a desktop computer with 4 or 8 memory modules, but given a machine with just 2 modules, maybe it follows that one module usually gets filled with "core stuff" and the second, defective module somewhat infrequently sees "big user stuff" after the first module is filled, and I guess that isn't too much of a head-scratcher when it comes to identifying the source of the problem.