Recherche avancée

Sur d’autres sites (11206)

• Building x264 with YASM : failing the ASM check

  11 janvier 2020, par radiofreemyourenji

  My question up front is, "I have new yasm, I think x264 is supposed to be cool with that, why is x264 not cool with that ?"

  


  For reasons, I am building a CentOS docker image (based on centos:latest) that contains a from-scratch ffmpeg build, following the guide here. It's a good guide, it's worked for me before, so I was feeling good about it.

  


  Today I'm hitting a choke point on the libx264 build point : specifically, I say

  


  PKG_CONFIG_PATH="/tmp/ffmpeg_build/lib/pkgconfig" \
  ./configure \
  --prefix="/tmp/ffmpeg_build" \
  --bindir="/tmp/bin" \
  --enable-static


  


  And I get a reply back

  


  


  Found no assembler

  


  Minimum version is nasm-2.13

  


  If you really want to compile without asm, configure with —disable-asm.

  


  


  That's unexpected. I have yasm, which I understand to be 1) there to do the things nasm does but better, and 2) to be the daisy-fresh most modern version given that I pulled it from its repo about an hour ago, and built it about fifty-nine minutes ago. For what it's worth, nasm is on the box too since the instructions request it, but it's below their stated version (i.e. it's "NASM version 2.10.07 compiled on Jun 9 2014")

  


  So it seems like yasm is not being found. There's another StackExchange question that mentions that problem, which came out to a pathing issue. So, I added yasm to my path like so :

  


  PATH=/tmp/ffmpeg_sources/yasm:$PATH \
  PKG_CONFIG_PATH="/tmp/ffmpeg_build/lib/pkgconfig" \
  ./configure
  ...etc


  


  That still gave the Found-no-assembler problem. As a last, confused resort, I told the script explicitly what I wanted to use for the variable $AS, because based on my quick look into configure, that looked like where yasm/nasm was meant to go. The command becomes :

  


  AS=`which yasm`
  PKG_CONFIG_PATH="/tmp/ffmpeg_build/lib/pkgconfig" \
  ./configure
  ...etc


  


  That at least gave

  


  


  Found yasm 1.3.0

  


  Minimum version is nasm-2.13

  


  If you really want to compile without asm, configure with —disable-asm.

  


  


  Looking in the config.log I see the following :

  


  checking whether /tmp/bin/yasm supports vmovdqa32 [eax]{k1}{z}, zmm0... no
Failed commandline was:
--------------------------------------------------
/tmp/bin/yasm conftest.asm  -I. -I$(SRCPATH) -DARCH_X86_64=1 -I$(SRCPATH)/common/x86/ -f elf64  -o conftest.o
conftest.asm:1: error: instruction expected after label
conftest.asm:1: warning: ignoring unrecognized character `{'
conftest.asm:1: warning: ignoring unrecognized character `}'
conftest.asm:1: warning: ignoring unrecognized character `{'
conftest.asm:1: warning: ignoring unrecognized character `}'
--------------------------------------------------
Failed program was:
--------------------------------------------------
vmovdqa32 [eax]{k1}{z}, zmm0
--------------------------------------------------


  


  So : what's the deal here ? Is my assumption that yasm drop-in replaces nasm bad ? Is yasm good for this purpose, but I'm not providing the right information to ./configure ? Are my instructions for building ffmpeg for CentOS simply out of date with respect to this prerequisite and I should just try harder to get a modern nasm ?

  


• Building x264 with YASM : failing the ASM check

  11 janvier 2020, par radiofreemyourenji

  My question up front is, "I have new yasm, I think x264 is supposed to be cool with that, why is x264 not cool with that ?"

  For reasons, I am building a CentOS docker image (based on centos:latest) that contains a from-scratch ffmpeg build, following the guide here. It’s a good guide, it’s worked for me before, so I was feeling good about it.

  Today I’m hitting a choke point on the libx264 build point : specifically, I say

  PKG_CONFIG_PATH="/tmp/ffmpeg_build/lib/pkgconfig" \
  
    ./configure \
  
    --prefix="/tmp/ffmpeg_build" \
  
    --bindir="/tmp/bin" \
  
    --enable-static

  And I get a reply back

  Found no assembler

  Minimum version is nasm-2.13

  If you really want to compile without asm, configure with —disable-asm.

  That’s unexpected. I have yasm, which I understand to be 1) there to do the things nasm does but better, and 2) to be the daisy-fresh most modern version given that I pulled it from its repo about an hour ago, and built it about fifty-nine minutes ago. For what it’s worth, nasm is on the box too since the instructions request it, but it’s below their stated version (i.e. it’s "NASM version 2.10.07 compiled on Jun 9 2014")

  So it seems like yasm is not being found. There’s another StackExchange question that mentions that problem, which came out to a pathing issue. So, I added yasm to my path like so :

  PATH=/tmp/ffmpeg_sources/yasm:$PATH \
  
    PKG_CONFIG_PATH="/tmp/ffmpeg_build/lib/pkgconfig" \
  
    ./configure
  
    ...etc

  That still gave the Found-no-assembler problem. As a last, confused resort, I told the script explicitly what I wanted to use for the variable $AS, because based on my quick look into configure, that looked like where yasm/nasm was meant to go. The command becomes :

  AS=`which yasm`
  
    PKG_CONFIG_PATH="/tmp/ffmpeg_build/lib/pkgconfig" \
  
    ./configure
  
    ...etc

  That at least gave

  Found yasm 1.3.0

  Minimum version is nasm-2.13

  If you really want to compile without asm, configure with —disable-asm.

  Looking in the config.log I see the following :

  checking whether /tmp/bin/yasm supports vmovdqa32 [eax]{k1}{z}, zmm0... no
  
  Failed commandline was:
  
  --------------------------------------------------
  
  /tmp/bin/yasm conftest.asm  -I. -I$(SRCPATH) -DARCH_X86_64=1 -I$(SRCPATH)/common/x86/ -f elf64  -o conftest.o
  
  conftest.asm:1: error: instruction expected after label
  
  conftest.asm:1: warning: ignoring unrecognized character `{'
  
  conftest.asm:1: warning: ignoring unrecognized character `}'
  
  conftest.asm:1: warning: ignoring unrecognized character `{'
  
  conftest.asm:1: warning: ignoring unrecognized character `}'
  
  --------------------------------------------------
  
  Failed program was:
  
  --------------------------------------------------
  
  vmovdqa32 [eax]{k1}{z}, zmm0
  
  --------------------------------------------------

  So : what’s the deal here ? Is my assumption that yasm drop-in replaces nasm bad ? Is yasm good for this purpose, but I’m not providing the right information to ./configure ? Are my instructions for building ffmpeg for CentOS simply out of date with respect to this prerequisite and I should just try harder to get a modern nasm ?

• FFMPEG CLI Language Metadata Tagging Output MP4 (Video + Audio) File

  12 juin 2017, par DMtd

  Can anyone help me understand why my attempts at tagging an audio track with language metadata using FFMPEG CLI is failing ? I’ve found various pieces of information on the correct syntax for the tag which I’m still not clear on (so part 1 of my question is what is the correct syntax), but even if I get it right (which I may or may not have), I am wondering if FFMPEG is failing to tag my audio track because my source is wrapped/muxed with a video essence. Does this preclude the ability to language tag ?

  Worth noting, attempts have been made from both MP4 and MKV sources (video and audio) to MP4 (video and audio) and M4A, MP4 and AAC audio only outputs with no success.

  Also worth noting, I’ve also tried using the -metadata title tag with no success.

  I am looking for the following metadata to show up in a mediainfo advanced mode check :

  Language : en
  Language : English

  Here is my command line :

  ffmpeg -i "input.mkv" -c:v libx264 -level:v 3.0 -b:v 5000k -bufsize 4300k -flags +ildct+ilme -top 1 -x264opts tff=1:colorprim=bt470bg:transfer=bt470m:colormatrix=bt470bg -vf crop=720:576:0:32 -pix_fmt yuv420p -c:a aac -b:a 128k -metadata language="eng" -aspect 4:3 -y "output.mp4"