After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 601870 - deprecated use of x264 API
deprecated use of x264 API
Status: RESOLVED DUPLICATE of bug 599095
Product: GStreamer
Classification: Platform
Component: gst-plugins-ugly
0.10.13
Other Linux
: Normal major
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-11-14 05:18 UTC by alxgomz
Modified: 2009-11-14 11:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description alxgomz 2009-11-14 05:18:31 UTC
it seems like the lastest tarball i have tried have pb as it uses an old variable that has been removed from x264.
when trying to comile gstreamer-plugin-ugly with x264 i get the following error:

stx264enc.c: In function ‘gst_x264_enc_init_encoder’:
gstx264enc.c:585: error: ‘x264_param_t’ has no member named ‘b_bframe_pyramid’
make[3]: *** [libgstx264_la-gstx264enc.lo] Erreur 1

I contacted videolan dev on irc channel and they told me b_bframe_pyramid has been replaced with i_bframe_pyramid.
Then I patched the file ext/x264/gstx264enc.c and compilation worked fine.

here is the very simple diff

--- /tmp/gstx264enc.c	2009-11-13 19:16:37.335487579 -1000
+++ ext/x264/gstx264enc.c	2009-11-13 19:01:05.615494630 -1000
@@ -582,7 +582,7 @@
   encoder->x264param.analyse.i_noise_reduction = encoder->noise_reduction;
   encoder->x264param.i_frame_reference = encoder->ref;
   encoder->x264param.i_bframe = encoder->bframes;
-  encoder->x264param.b_bframe_pyramid = encoder->b_pyramid;
+  encoder->x264param.i_bframe_pyramid = encoder->b_pyramid;
 #if X264_BUILD < 63
   encoder->x264param.b_bframe_adaptive = encoder->b_adapt;
 #else

Can you consider adding this upstream?

thanks
Comment 1 Sebastian Dröge (slomo) 2009-11-14 11:13:19 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 599095 ***