HandBrake

Just my opinion, but I'd like to see all releases compile cleanly (if not execute cleanly) on all "supported" platforms. It's going to be confusing to people to hear "OK, revision 71 is for Linux and PPC, revision 72 is for MacIntel, but otherwise there are no differences"...or, ...

The r69 x264 patches were by titer. The r70 x264 patches were upleveled and enhanced for x264 build 50 by Chris Long, but I believe were incomplete w.r.t. MacIntel.

Rodney

To help things along, I've put the Dec 9 snapshot (CVS internal build 604, external build 54) on my web server in ready-to-use form for editing the version and Jamfiles with. All that needs to be done beyond that is updating the x264 patchfile to match the new trunk - which should mostly apply as-is...

jbrjake, Baseline 3.0 doesn't have a hard requirement on vbv_buffer. In fact, there's much debate about what an appropriate value should be (since the potential target devices vary so widely). You were dead-on about the changes to ABR handling in x264 that led to the changes in the HandBrake core in...

I'd rather not integrate jbrjake's patches yet until everyone is satisfied that things are behaving as they should. Ideally, what I'd like to see happen (and I'm willing to assist with this) is the creation of a revision 71, based on the revision 70 trunk where the _only_ changes are the 'upgrade' o...

I don't know anything about the 604 branch, but basically what needs to happen (at a high level) is: - Fix the x264 patches (already in Handbrake Unofficial version 71) to match branch 604 of x264 - this has to be done by hand (and some trial-and-error) - Put the 604 branch source tarball on this si...

A word of caution on the "contrib" directory - you want to be careful about upsetting the delicate balance there, since many of the contributed sources are hand-patched for a specific version and, as you noted, are automatically downloaded by jam during compile time. My recommendation woul...

This forum, the informational site and the svn will stay available indefinitely (read: permanently unless titer's situation changes or someone would rather rehost it). Being on a home server, I can't guarantee 100% uptime, but I think it definitely exceeds 95% and should be suitable for ongoing deve...

I never got around to clarifying this, but it would appear the "memory leak" is in fact an artifact of the change to a multi-threaded model in HandBrake just after 0.7.0 was released. On slower machines, it is possible to have the audio thread "outrun" the video thread by a very ...

Responded via PM - unfortunately, this is part of the Chris code change I don't have yet.

Rodney

Having done full memory regression testing from all releases 33 (0.7.1 release) forward, I've found the following: - Release 40 increased memory usage by almost 50%. This is likely a result of the threading change, but the memory leak was NOT introduced here...just a lot more memory usage. - Release...

Chris is the resident MacOS X expert, but is there anything written between gcc -c -o libhb/encxvid.o -Wall -g -O3 -funroll-loops -I./contrib/include -DSYS_DARWIN -DHB_VERSION=\"0.7.1a1\" -DHB_BUILD=20060923 -D__LIBHB__ -Ilibhb libhb/encxvid.c and ...failed Cc libhb/encxvid.o ... ? This ma...

This forum is intended for use by current and potential developers of the HandBrake source code to exchange information, ideas, and solutions to problems with HandBrake. It is not intended for use as an end-user support forum - while consumers of HandBrake are welcome and encouraged to read the info...