Menu
  • HOME
  • TAGS

avconv complains “non monotonically increasing dts to muxer in stream” when piping from libx264 on 14.04

c,ubuntu,x264,avconv,ubuntu-14.04

In a moment of "I don't know why this should fix it, but does", changing -vcodec copy to -vcodec libx264 (even though the source codec was already libx264) fixed the dts error.

Windows: How to build X264.lib instead of .dll

c,video,encoding,h.264,x264

After the latest update of x264 you can build static library usable by MSVS project. For such library compilation you will need: MSYS and MSVS 2013 Update 2 (express version [for Windows Desktop] would also work if you install Update 2) run "VS2013 x86 Native Tools Command Prompt" or "VS2013...

X264: How to compile x264 with swscale support?

c,video-streaming,h.264,x264

A couple of things I would point to: MinGW can sometimes cause compilation issues (because of Windows-based compatibility requirements - I am not saying MinGW is not good). I try to compile on native UNIX system when ever possible. ffmpeg has built in support for swscale. If you cannot find...

C++ ffmpeg x264 encoding settings [duplicate]

c++,ffmpeg,x264

You're making the exact same mistake as this guy. And my answer is the same here as it was there: Don't pass c->priv_data to av_opt_set. Pass the context. As in: av_opt_set(c, "cabac", "0", 0); Internally, av_opt_set will cast the object to an AVClass* which is what holds all the options....

MP4 H264 VBR, How to get the bitrate for each second of video?

video-streaming,h.264,video-encoding,x264,adaptive-bitrate

I can't imagine possible methods other than actually process the MP4 format data. VBR means quality constraint encoding not bandwidth. There is no information about bitrate statistics. Reading MP4 format is not that difficult work to do (of course not trivial). Basically we only need sample size information and the...

Compiling x264 on a Mac: “No working C compiler found” and “arm-linux-androideabi-gcc: command not found”

android,gcc,android-ndk,x264,libx264

You shouldn't set --cross-prefix=$TOOLCHAIN/bin/arm-linux-androideabi-, you should add that directory to your path first, using export PATH=$TOOLCHAIN/bin:$PATH, and only specify --cross-prefix=arm-linux-androideabi- (just as in the post you linked to).

x264 fails to build using MacPorts

ffmpeg,macports,x264

..and to answer my own problem with a functional (but probably not recommended) hack, I consulted the config.log as suggested by the error message above. The problem, according to the log, was that clang does not support the -falign-loops option. x264 built successfully after commenting out the two configuration lines...

X264 : How to access NAL units from encoder?

c,video-streaming,h.264,x264,libx264

1) Yes. x264 includes the automatically. Its an SEI slice, and you can throw it away if you want. 2) set i_slice_max_size = 1390 3) Take a look at x264_param_t in x264.h. The settings are fairly self explanatory. As for setting the profile and preset call int x264_param_apply_profile( x264_param_t *,...

OpenCV: File Size of H.264 encoded videos

c++,opencv,video,h.264,x264

Even though it is kind of late, i figured it out...it seems it was just a bug of OpenCV. When I used the OpenCV method to use the h.264 encoder, the video file was corrupted. When I used FFmpeg instead everything worked fine.

Android JNI x264 as a library give relocation R_ARM_MOVW_ABS_NC; recompile with -fPIC

android,compilation,android-ndk,jni,x264

All the problematic object files (e.g. quant-a.o) come from assembly files (quant-a.S) Looking at the assembly sources from http://git.videolan.org/?p=x264.git;a=tree;f=common/arm;h=64e8990fc2043750599c45593f1bc7698d94048a;hb=refs/heads/master , it looks like you should have the PIC macro defined in your config.h Normally, this is done by the x264 script if you use "./configure --enable-pic ..." I'm guessing you're...

X264 Encoder API

c,video,encoding,h.264,x264

x264 can not encode BGR. You must convert the image to YUV 4:2:0p. I recommend using libswscale from the ffmpeg project to perform this operation. EDIT #2 No, a startcode is at least two 0x00 bytes followed by a 0x01. But it can have any number (But is usually two...