Newest 'x264' Questions - Stack Overflow

Les articles publiés sur le site

• Usage of libx264.dll in C++ under windows

  19 janvier 2012, par Anuj

  I have been able to build the libx264 dll from source using hints from here. I am successfully able to load the Dll via my application using the LoadLibrary method. But when i try to get the address of the methods available via the x264.h header using GetProcAddress(), i always get back NULL.

  Has anyone worked with libx264.dll before in VS or are there any references to some sample code for the same.

• Mencoder Mp4(x264) Encoding

  17 janvier 2012, par Ahmet Kapıkıran

  I want to convert any video to mp4(x264).But codecs of videos which will be processed are different(x264,Xvid,etc.). I want that properties of video which I convert should be same with video which I will convert and I want to not raise video's size.

• Build FFMPEG with x264 error

  11 janvier 2012, par Kage

  I am trying to build FFMPEG with libx264.

  I can successfully build and use FFMPEG for Android but I realized that I need the ability to encode, therefore I am trying to build FFMPEG with x264.

  When trying to build FFMPEG I get an error:

  "ERROR: libx264 not found"

  And in my log it says:

  "/usr/local/lib/libx264.a: could not read symbols: Archive has no index; run ranlib to add one..."

  I have the latest versions of both FFMPEG and x264. I understand that FFMPEG looks for the header and libraries in usr/lib and usr/include, so in order to make it find x264 I use the cflags and ldflags:

  • --extra-cflags = " -I/usr/local/include "
  • --extra-ldflags = " -L/usr/local/lib "

  I have tried building x264 with many different options that other people on the internet have said that i need. eg. --enable-shared, --enable-static, --disable-pthreads etc. Some forums say enable this, others say no disable that.

  Any help would be much appreciated, Thanks

• pixelformat conversion in QTKit on mac os x

  10 janvier 2012, par saiffu

  I wanted to develop a mac application for streaming video over internet. Im using x264 for encoding captured video from camera and libavcodec for decoding.
  x264 takes yuv 420p as input. But im getting kCVPixelFormatType_422YpCbCr8 only from QTCaptureDecompressedVideoOutput. How can i convert the pixel format to yuv 420 ?

• libx264 in Visual Studios 2010 - Memory error in Release Build

  21 décembre 2011, par DeusAduro

  I am building an application and using the x264 library as an encoder. I have built the library for my windows system using MSys/MingW. The library works fine under debug build (note both debug and release builds are using the default VS2010 settings). However, under release an access violation error is thrown at the first call to the x264 library, specifically:

    Unhandled exception at 0x00905a4d in StreamTest.exe:
    0xC0000005: Access violation.
  

  The error is thrown at this line:

  x264_param_default_preset((params), "veryfast", "zerolatency");
  

  While I was figuring out how to compile the library I came across a lot of talk about memory alignment in Windows/Visual Studios and how it wasn't particularly compatible with the alignment expected by x264. For example when compiling in MSys I had to enable --enable-memalign-hack. I am wondering if the source of this error might stem from a memory alignment issue which only manifests itself through some setting in my release build. Unfortunately I know almost nothing about the specifics and so have come here.

  Can anyone give me some more information regarding the memory alignment issues and any Visual Studio settings which might cause this? Any other tips/pointers to fix this issue are very welcome.

  Thanks.

  Edit

  From answer below:

  1. From the linked SO question I get the impression he added "build with debugger info" to the OpenCV build? Since I'm building the x264 library through MSys with G++ I'm not sure I can do this. I have checked the build settings for my project, and under both release and debug it has debugger info. Not sure if I missed something in that post, please let me know.

  2. I tried the application verifier. It seems that x264 is trying to execute code from non-executable memory as per the App verifier output:

     VERIFIER STOP 0000000000000650: pid 0x1B18: 
     

     Attempt to execute code in non-executable memory (first chance).

     0000000000905A4D : Address being accessed.
     0000000000905A4D : Code performing invalid access.
     000000000021EA90 : Exception record. Use .exr to display it.
     000000000021E5A0 : Context record. Use .cxr to display it.
     

  Anything to be gathered from this output?

  Thanks again.