Newest 'x264' Questions - Stack Overflow

Les articles publiés sur le site

• FFmpeg installation for x264 codec

  27 juillet 2019, par Kamila

  can anybody help me out in where can i find ffmpeg download for windows x264 codec , am developing a website which converts any file format to mp4h264 baseline format , everythng was fine with another wrap installer called MooO ffmpeg which i found in this link http://www.moo0.com/?top=http://www.moo0.com/software/FFmpeg/ evrythng is fine i can access the exe from my local system as the file is installed rather i could acess the same when its in remote as i knw the batch file location is different , any help related with ffmpeg x264 sourcecode or access batch file would be helpful.

  Thanks for your time

• How to find the Quantified transformed coefficients in encoder x264 and in decoder libavcodec ?

  8 juillet 2019, par Quentin CHARRIER

  I'm a student in computer science and I am working on h264 encoder and decoder.

  I decided to use x264 and libavcodec and I downloaded code of these open libraries. Then, I searched for a month on how to do it. I think the quantified transformed coefficients are in h->dct.luma8x8 and h->dct.luma4x4 but they are no luma16x16 so I'm disappointed.

  Now, I suppose that Intra 16x16 macroblock have their coefficients in luma4x4 or luma8x8 but I'm not sure. Is there someone who knows about it and could give answers?

  Furthermore, I have to find the same coefficients in decoder and I thought that they are in sl->mb but the coefficients in sl->mb are strange (there are a lot of 0s and values > 100 contrary to the encoder where values are close to 1-10..) I'm lost so I hope that someone have some advice to help me to continue my project.

  EDIT :

  I think the coefficients when the macroblock is encoded in 16x16IntraPrediction are in luma4x4. I always need help to understand how the decoder works.

  EDIT :

  I think the coefficients which are in sl->mb are always dequantized, maybe there is a variable who have the correct coefficient in decode_cabac_residual_internal but I didn't find it..

• libx264 compiled with MinGW - missing __umoddi3, __udivdi3, _fseeko64 and __chkstk_ms

  26 juin 2019, par Dan Tumaykin

  I'm willing to use x264 in my Windows project, so I've build the library from source using MinGW and gcc into a static library.

  The library and the header are included correctly, the only problem is that linker now complains, because __umoddi3, __udivdi3, _fseeko64 and __chkstk_ms. Looks like this functions are a part of some standard library, but where can I find it in Windows?

  Thanks.

• x264 static lib libx264.a occur an error : asm code, recompile with -fPIC [closed]

  20 juin 2019, par thunvan

  compile with static libs:

  yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/cabac-a.o common/x86/cabac-a.asm

  link the libx264.a to another so libs

  occur: (cabac-a.o): relocation R_X86_64_PC32 against symbol `x264_cabac_range_lps' can not be used when making a shared object; recompile with -fPIC

  used -DPIC with yasm, also have error.

  gcc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64  -Wall -I. -I. -std=gnu99 -D_GNU_SOURCE -mpreferred-stack-boundary=5  -I/usr/local/include  -I/usr/local/include -fPIC -fomit-frame-pointer -fno-tree-vectorize   -c -o encoder/cavlc.o encoder/cavlc.c
  gcc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64  -Wall -I. -I. -std=gnu99 -D_GNU_SOURCE -mpreferred-stack-boundary=5  -I/usr/local/include  -I/usr/local/include -fPIC -fomit-frame-pointer -fno-tree-vectorize   -c -o encoder/encoder.o encoder/encoder.c
  gcc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64  -Wall -I. -I. -std=gnu99 -D_GNU_SOURCE -mpreferred-stack-boundary=5  -I/usr/local/include  -I/usr/local/include -fPIC -fomit-frame-pointer -fno-tree-vectorize   -c -o encoder/lookahead.o encoder/lookahead.c
  gcc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64  -Wall -I. -I. -std=gnu99 -D_GNU_SOURCE -mpreferred-stack-boundary=5  -I/usr/local/include  -I/usr/local/include -fPIC -fomit-frame-pointer -fno-tree-vectorize   -c -o common/threadpool.o common/threadpool.c
  gcc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64  -Wall -I. -I. -std=gnu99 -D_GNU_SOURCE -mpreferred-stack-boundary=5  -I/usr/local/include  -I/usr/local/include -fPIC -fomit-frame-pointer -fno-tree-vectorize   -c -o common/x86/mc-c.o common/x86/mc-c.c
  gcc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64  -Wall -I. -I. -std=gnu99 -D_GNU_SOURCE -mpreferred-stack-boundary=5  -I/usr/local/include  -I/usr/local/include -fPIC -fomit-frame-pointer -fno-tree-vectorize   -c -o common/x86/predict-c.o common/x86/predict-c.c
  yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/const-a.o common/x86/const-a.asm
  yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/cabac-a.o common/x86/cabac-a.asm
  yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/dct-a.o common/x86/dct-a.asm
  yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/deblock-a.o common/x86/deblock-a.asm
  yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/mc-a.o common/x86/mc-a.asm
  yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/mc-a2.o common/x86/mc-a2.asm
  yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/pixel-a.o common/x86/pixel-a.asm
  yasm -I. -I. -DARCH_X86_64=1 -I./common/x86/ -f elf64 -Worphan-labels -DSTACK_ALIGNMENT=32 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/x86/predict-a.o common/x86/predict-a.asm
  

  how to compile asm code with yasm, and result to pic code successfully?

• How to transcode 50 H264 Streams with FFMPEG more efficient ?

  20 juin 2019, par Kevin

  i need to (Re-)Transcode ~ 50 Live-Streams. These streams are in H264 with 720p to 1080p and bitrates up to 10M. I just want to reduce the quality and bitrate of the streams to up to 720p with max. 2M Bitrate.

  That's what i'm doing right now:

  ffmpeg -re -i "http://domain.tld/path/file.ext" -vcodec libx264 -preset veryfast -vf scale=-2:720 -b:v 2M -maxrate 2M -bufsize 1M -acodec libfdk_aac -f flv "rtmp://127.0.0.1:1935/live/stream_xyz"
  

  My Server CPU (2 x Xeon E5-2630 v3) is already at 100% with just 12 streams. I will upgrade my server to 2 x Xeon Gold 5118 next month, but i don't think, that this will give me that much more power.

  Can someone help me, to do this more efficient?

  Would it be more efficient / cheaper to do this with GPUs?

  Or any other ideas, to do that as efficient and cheap as possible?

  Thanks