StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I've met this problem too with libx264-120. libx264-120 was built on <strong>MinGW</strong> and configuration option like below.</p> <p>$ ./configure --disable-cli --enable-shared --extra-ldflags=-Wl,--output-def=libx264-120.def --enable-debug --enable-win32thread</p> <pre><code>platform: X86 system: WINDOWS cli: no libx264: internal shared: yes static: no asm: yes interlaced: yes avs: yes lavf: no ffms: no gpac: no gpl: yes thread: win32 filters: crop select_every debug: yes gprof: no strip: no PIC: no visualize: no bit depth: 8 chroma format: all </code></pre> <p>$ make -j8</p> <p>lib /def:libx264-120.def /machine:x86</p> <pre><code>#include "stdafx.h" #include <iostream> #include <cassert> using namespace std; #include <stdint.h> extern "C"{ #include <x264.h> } int _tmain(int argc, _TCHAR* argv[]) { int width(640); int height(480); int err(-1); x264_param_t x264_param = {0}; //x264_param_default(&x264_param); err = x264_param_default_preset(&x264_param, "veryfast", "zerolatency"); assert(0==err); x264_param.i_threads = 8; x264_param.i_width = width; x264_param.i_height = height; x264_param.i_fps_num = 60;//fps; x264_param.i_fps_den = 1; // Intra refres: x264_param.i_keyint_max = 60;//fps; x264_param.b_intra_refresh = 1; //Rate control: x264_param.rc.i_rc_method = X264_RC_CRF; x264_param.rc.f_rf_constant = 25; x264_param.rc.f_rf_constant_max = 35; //For streaming: x264_param.b_repeat_headers = 1; x264_param.b_annexb = 1; err = x264_param_apply_profile(&x264_param, "baseline"); assert(0==err); x264_t *x264_encoder = x264_encoder_open(&x264_param); x264_encoder = x264_encoder; x264_encoder_close( x264_encoder ); getchar(); return 0; } </code></pre> <p>This program succeeds <em>sometime</em>. But will fail often on x264_encoder_open with the access violation. The information for this is not existing on Google. And how to initialize x264_param_t and how to use x264_encoder_open are unclear.</p> <p>It seems that behavior caused from x264's setting values, but I can't know these without reading some open source programs that using libx264.</p> <p><strong>And, this access violation seems doesn't occurs on FIRST TIME EXECUTION and on compilation with MinGW's gcc (e.g gcc -o test test.c -lx264;./test)</strong></p> <p>Since this behavior, I think that libx264 doing some strange processes of resources in DLL version of ilbx264 that was built on MinGW's gcc.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload