Log in

View Full Version : Which Patches to get


horrormaster34
23rd July 2009, 22:46
I see the thread with the list of patches, but since it was last updated in 2007 I figure that most of them have already been applied and aren't needed anymore. I also see that the ones listed on http://mirror05.x264.nl/Cef/?dir=./patches haven't been updated in a month and are either useless now or outdated.

Basically, just looking for the right patches to get and where to get them from.

skystrife
24th July 2009, 01:34
Current Patches, Where to get them, How they affect speed/output (http://forum.doom9.org/showthread.php?t=130364).

On the front page of this forum. Look at the most recent builds by different people to see what they're using, and read the thread to find the sources for the patches.

Dark Shikari
24th July 2009, 01:35
Current Patches, Where to get them, How they affect speed/output (http://forum.doom9.org/showthread.php?t=130364).

On the front page of this forum. Look at the most recent builds by different people to see what they're using, and read the thread to find the sources for the patches.The start of the thread is rather outdated though...

Selur
24th July 2009, 10:46
yup, I normally start at the end of the thread look what the others are using and work my way back through the thread to find the downloadlinks for the patches. ;)

qyot27
25th July 2009, 20:53
Speaking of the commonly-used patches, I still haven't found an explanation of what the win_zone_parse_fix patch does. I looked all over the Current Patches thread and on Google and couldn't seem to put in the right search parameters or something. It's the 'win' part that confuses me - is the patch only relevant on Windows, or does 'win' refer to something else? Because I've been using it in my Linux builds anyway and if it's totally unnecessary on there I'd rather not keep bothering with it.

LoRd_MuldeR
25th July 2009, 21:02
Speaking of the commonly-used patches, I still haven't found an explanation of what the win_zone_parse_fix patch does. I looked all over the Current Patches thread and on Google and couldn't seem to put in the right search parameters or something. It's the 'win' part that confuses me - is the patch only relevant on Windows, or does 'win' refer to something else? Because I've been using it in my Linux builds anyway and if it's totally unnecessary on there I'd rather not keep bothering with it.

That patch fixes a problem when parsing the commandline and "zones" are used. And yes, I think the problem is specific to Windows.

kemuri-_9
26th July 2009, 01:10
That patch fixes a problem when parsing the commandline and "zones" are used. And yes, I think the problem is specific to Windows.

the name is slightly a misnomer...
the problem is specific to mingw; ICL (or whatever the name is for intel's c compiler for windows) and MSVC do not require the fix.

mingw is the only platform without a built in recursive (thread safe) string tokenizer, so the patch works around that lack.

qyot27
27th July 2009, 04:57
Thanks, that's been confusing me for a while. I'll have to keep that in mind if I ever decide to set up MinGW again, though.

Gokumon
27th July 2009, 22:19
Current Patches, Where to get them, How they affect speed/output (http://forum.doom9.org/showthread.php?t=130364).

On the front page of this forum. Look at the most recent builds by different people to see what they're using, and read the thread to find the sources for the patches.

Did you even read his post? He knows about the presence of that thread but was talking about how it was outdated.

I see the thread with the list of patches, but since it was last updated in 2007

LoRd_MuldeR
27th July 2009, 22:29
mingw is the only platform without a built in recursive (thread safe) string tokenizer, so the patch works around that lack.

Well, obviously MinGW does provide a "strtok_r" function (thread-safe strtok). Otherwise unpatched x264 wouldn't compile.

So is it broken or what exactly is the problem? :confused:

Dark Shikari
27th July 2009, 22:42
Well, obviously MinGW does provide a "strtok_r" function (thread-safe strtok). Otherwise unpatched x264 wouldn't compile.

So is it broken or what exactly is the problem? :confused:#ifdef _WIN32
#define rename(src,dst) (unlink(dst), rename(src,dst)) // POSIX says that rename() removes the destination, but win32 doesn't.
#ifndef strtok_r
#define strtok_r(str,delim,save) strtok(str,delim)
#endif
#endifhurr

LoRd_MuldeR
27th July 2009, 22:45
Hehe, I see :D