GNOME Bugzilla – Bug 619776
[x264enc] is unable to do Baseline with recent x264
Last modified: 2010-08-23 19:10:21 UTC
Created attachment 162069 [details] [review] x264enc: Disable I weighted pred Recent versions of x264 have added a "i_weighted_pred" parameter. If it is not 0, it will set the profile to main. So that means that x264enc will never produce baseline streams. That causes interoperability issues with many decoders that only support baseline. Including the decoder on the N900 and the decoder that is used by Google Talk's video calling thing (bug #612338). My simple solution for this release is to just disable that thing entirely (although I have no idea what it does, so I added Jason in CC). I guess it would be a better solution to fix bug #607798..
As listed in the documentation, i_weighted_pred controls P-frame explicit weighted prediction. Given that x264enc is already completely broken, it couldn't really hurt much to make it just a bit worse by forcing weighted prediction off. But it would rather be better to fix the whole thing properly, as you mentioned.
We want to release today or tomorrow. I don't really want to drop in an untested x264enc rewrite at this point, even more so since it didn't really seem quite ready yet. So the less invasive any fix is, the better.
commit d6df52f99a82bc79d91aa229e379cfdf25c174d9 Author: Olivier Crête <tester@tester.ca> Date: Wed May 26 23:16:46 2010 -0400 x264enc: disable I weighted pred If it is enabled, then it will be main profile instead of baseline. This ensures maximum compatibility of the output stream until the encoder configuration interface gets an overhaul with explicit output profile selection. Fixes #619776.
Created attachment 162406 [details] [review] x264enc: Only set i_weighted_pred on versions where it exists Arg, seems like we have to ifdev this on older versions...
Comment on attachment 162406 [details] [review] x264enc: Only set i_weighted_pred on versions where it exists Yes, please push this :)
*** Bug 620233 has been marked as a duplicate of this bug. ***
This was pushed at some point..
*** Bug 627753 has been marked as a duplicate of this bug. ***