FFMPEG libx264 processing maxes out

[rouftop]

Just created an account to say "me too" in hopes of getting some attention.

[rogerdpack]

working on it...

[rouftop]

working on it...

Sorry to nag... has this been addressed in recent builds? Getting to the end of a project and want to know if I need to spend the time rebuilding ffmpeg myself... not my area of expertise.

[rogerdpack]

Ok we're working on it, in the meantime maybe a work around will suffice:
http://betterlogic.com/roger/2012/08/ff ... rk-around/

[rogerdpack]

Next update: for me the dec 26th builds are "still broken" somewhat, for me (with -threads 6) unless I specify -threads 1 (but not entirely sure, yet...)

[DJX]

I created a bug report on the FFmpeg trac a while ago:
http://ffmpeg.org/trac/ffmpeg/ticket/1509

[arad85]

I created a bug report on the FFmpeg trac a while ago:
http://ffmpeg.org/trac/ffmpeg/ticket/1509

Just added something to that.

Roger: it's all gone quiet.......

[rogerdpack]

I've updated http://betterlogic.com/roger/2012/08/ff ... ork-around with the latest.
Basically I've got some builds there that "should" work around the problem--give them a shot. In the meantime we're trying to fix the pthreads build. There's even a script there if you want to build a local working version that has libfdk-aac included
-roger-

[arad85]

Thanks Roger,

Just for completeness, this is the link that shows the chatter on pthreads mailing list:

http://sourceforge.net/mailarchive/foru ... w64-public

[rogerdpack]

Ok the latest builds use straight win32threads until we can get this problem "fixed" so there's a workaround in place now, give it a go.