Recherche avancée

Sur d’autres sites (9640)

• How do I configure ffmpeg to enable rtpdec.h or rtpdec_h264

  3 mai 2022, par mike

  I'd like to build ffmpeg libraries so I can use the functionality in rtpdec_h264.c.

  


  As far as I can tell, my current build is not including this, at least not in the headers. I can happily encode and decode h264 via AVFormat structs, but now I'm trying to decode rtp packets directly.

  


  I might be missing something but it seems like I might just need to turn on another option when building ffmpeg - if so, what is that option ?

  


  I can see rtpdec is listed in the configure script as part of CONFIG_EXTRA - it looks to me like that should be building by default, but again no sign of the functions when I dump the contents of the libavformat .lib or .dll (I'm on Windows).

  


  Should I expect rtpdec.h to be in the include/libavformat output ?

  


  Or - am I missing something and the rtpdec stuff is handled internally, and I should be going through some other interface ?

  


  Current configure string is ./configure --prefix=./../../build/ffmpeg --enable-nonfree --enable-gpl --enable-shared --enable-cuda-nvcc --enable-libx264 --enable-libx265 --enable-libnpp --extra-cflags="-I../../build/x264/include -I../x265_git/source -I../nv_sdk -I../build/nv-codec-headers/include/ffnvcodec" --extra-ldflags="-L../../build/x264/lib -L../nv_sdk -L../x265_git/build/vc16-x86_64/Release"

  


• lavu/tx : add an RDFT implementation

  21 janvier 2022, par Lynne

  lavu/tx : add an RDFT implementation
  RDFTs are full of conventions that vary between implementations.
  
  What I've gone for here is what's most common between
  
  both fftw, avcodec's rdft and what we use, the equivalent of
  
  which is DFT_R2C for forward and IDFT_C2R for inverse. The
  
  other 2 conventions (IDFT_R2C and DFT_C2R) were not used at
  
  all in our code, and their names are also not appropriate.
  
  If there's a use for either, we can easily add a flag which
  
  would just flip the sign on one exptab.
  For some unknown reason, possibly to allow reusing FFT's exp tables,
  
  av_rdft's C2R output is 0.5x lower than what it should be to ensure
  
  a proper back-and-forth conversion.
  
  This code outputs its real samples at the correct level, which
  
  matches FFTW's level, and allows the user to change the level
  
  and insert arbitrary multiplies for free by setting the scale option.
  

  • [DH] libavutil/tx.c
  • [DH] libavutil/tx.h
  • [DH] libavutil/tx_template.c

• electron ffmpeg mas build "Illegal instruction : 4"

  8 mars 2021, par Martin

  I am trying to release an electron app on the Mac Apple Store (mas), my electron app uses ffmpeg to render videos. In order to release my app on the mac apple store, It needs to be sandboxed, and by default ffmpeg makes calls to external libraries so I need to statically build ffmpeg and package it with my app. My code is on the 'mas-ffmpeg-fix' branch : https://github.com/MartinBarker/digify/tree/mas-ffmpeg-fix

  


  My static ffmpeg build works before I build my app, but after running electron-builder build --mac, the ffmpeg executable now fails with Illegal instruction: 4

  


  This is the full timeline of building/packaging/submitting my app to the mac apple store and where the error first appears :

  


  


  • In Digify repo :

    


  


  • clone, configure, and build static ffpmeg : “sudo rm -rf ffmpeg-mac/ && npm run download-ffmpeg”

    


  


  • download-ffmpeg command is inside package.json and runs this :
git clone https://git.ffmpeg.org/ffmpeg.git ffmpeg-mac && cd ffmpeg-mac && ./configure pkg_config='pkg-config --static' --pkg-config-flags='--static' --libdir=/usr/local/lib --extra-version=ntd_20150128 --disable-shared --disable-lzma --enable-gpl --enable-pthreads --enable-nonfree --enable-libass --enable-libfdk-aac  --enable-libmp3lame  --enable-libx264 --enable-static --enable-filters --enable-runtime-cpudetect && make && cd ..

    


  


  • Check if any dylibb files in the static ffmpeg build with command : “otool -L ffmpeg-mac/ffmpeg | grep /usr/local”

    


  


  • If there are any, move them to folder in desktop, run ‘otool’ again to ensure there are no dynamic libraries, rebuild static ffmpeg.

    


  


  • there will now be a folder 'ffmpeg-mac' which contains static versions of ffmpeg and ffprobe

    


  


  


  Using ffmpeg with electron UI : works
Using Ffmpeg with command-line command :
/Users/martinbarker/Documents/projects/digify-new/ffmpeg-mac/ffmpeg -h
Works

  


  

  • Build mac mass app with “npm run build-mas“

  


  • When this command finishes it will output two files inside the /dist/mas/ folder : Digify.app and Digify-01.20.pkg (or whatever version number it is)
Ffmpeg command-line check :
/Users/martinbarker/Documents/projects/digify-new/dist/mas/Digify.app/Contents/Resources/ffmpeg -h
Illegal instruction : 4

  


  


  This is the first place the error appears, after building my mac mac-apple-store app, ffmpeg fails with this err.

  


  

  • Sign built app with .sh file : “sh mas-sign-script.sh”
view .sh file here

    

    • the .sh file will output Digify-mac.pkg

    


    


  


  • Easier command to both build & sign : “sudo rm -rf dist/mas/ && npm run build-mas && sh mas-sign-script.sh”

  


  • Upload the outputted “Digify-mac.pkg” file & submit to apple for review

  


  


  Once this app gets published in the store, if you download it and try to run an ffmpeg command with the electron UI, it fails with this error :

  


  /Applications/Digify.app/Contents/Resources/app.asar/node_modules/execa/lib/error.js:59 Uncaught (in promise) Error: Command failed with exit code 1: /Applications/Digify.app/Contents/Resources/ffmpeg -i /Users/martinbarker/Downloads/Felix Lebarty - Bobo/01. Bobo.mp3 -y -filter_complex concat=n=1:v=0:a=1 -c:a libmp3lame -b:a 320k /Users/martinbarker/Downloads/Felix Lebarty - Bobo/output-064237.mp3
ffmpeg version N-101191-g51a9f487ae-ntd_20150128 Copyright (c) 2000-2021 the FFmpeg developers
  built with Apple LLVM version 10.0.1 (clang-1001.0.46.4)
  configuration: pkg_config='pkg-config --static' --pkg-config-flags=--static --libdir=/usr/local/lib --extra-version=ntd_20150128 --disable-shared --disable-lzma --enable-gpl --enable-pthreads --enable-nonfree --disable-libass --enable-libfdk-aac --enable-libmp3lame --enable-libx264 --enable-static --enable-filters --enable-runtime-cpudetect
  libavutil      56. 65.100 / 56. 65.100
  libavcodec     58.125.100 / 58.125.100
  libavformat    58. 68.100 / 58. 68.100
  libavdevice    58. 12.100 / 58. 12.100
  libavfilter     7.107.100 /  7.107.100
  libswscale      5.  8.100 /  5.  8.100
  libswresample   3.  8.100 /  3.  8.100
  libpostproc    55.  8.100 / 55.  8.100
[mp3 @ 0x7feeae809c00] Estimating duration from bitrate, this may be inaccurate
Input #0, mp3, from '/Users/martinbarker/Downloads/Felix Lebarty - Bobo/01. Bobo.mp3':
  Metadata:
    comment         : 
    album           : Bobo
    artist          : Felix Lebarty
    title           : Funkytown Eklablog
    genre           : Boogie
    date            : 1984
  Duration: 00:05:19.53, start: 0.000000, bitrate: 320 kb/s
  Stream #0:0: Audio: mp3, 44100 Hz, stereo, fltp, 320 kb/s
/Users/martinbarker/Downloads/Felix Lebarty - Bobo/output-064237.mp3: Operation not permitted
    at makeError (/Applications/Digify.app/Contents/Resources/app.asar/node_modules/execa/lib/error.js:59)
    at handlePromise (/Applications/Digify.app/Contents/Resources/app.asar/node_modules/execa/index.js:114)
    at async file:/Applications/Digify.app/Contents/Resources/app.asar/src/js/newindex.js:1162


  


  Command failed with exit code 1: Operation not permitted