Recherche avancée

Sur d’autres sites (12536)

• Mix additional audio file with video(+audio) in ffmpeg

  21 mai 2019, par Serg

  I’m trying to mix additional audio file with video which has also audio within. But the problem is that I already have complex ffmpeg command and don’t know how to combine them together.

  This is my existing ffmpeg command which uses some offsets and replaces additional audio file with embedded one (audio inside video) and also overlays few gauges and watermark to the video.

  ffmpeg -y 
  
  -ss 00:00:01:213 -i videoFile.mp4 
  
  -ss 00:00:03:435 -i audioFile.wav 
  
  -i watermark.png 
  
  -framerate 6 -i gauge1_path/img-%04d.png 
  
  -framerate 1 -i gauge2_path/img-%04d.png 
  
  -framerate 2 -i gauge3_path/img-%04d.png 
  
  -framerate 2 -i gauge4_path/img-%04d.png 
  
  -framerate 2 -i gauge5_path/img-%04d.png 
  
  -framerate 2 -i gauge6_path/img-%04d.png 
  
  -filter_complex [0][2]overlay=(21):(H-h-21)[ovr0];
  
  [ovr0][3]overlay=(W-w-21):(H-h-21)[ovr1];
  
  [ovr1][4]overlay=(W-w-21):(H-h-333)[ovr2];
  
  [ovr2][5]overlay=(W-w-21):(H-h-418)[ovr3];
  
  [ovr3][6]overlay=(W-w-21):(H-h-503)[ovr4];
  
  [ovr4][7]overlay=(W-w-21):(H-h-588)[ovr5];
  
  [ovr5][8]overlay=(W-w-21):(H-h-673)
  
  -map 0:v -map 1:a -c:v libx264 -preset ultrafast -crf 23 -t 00:5:10:000 output.mp4

  Now I would like to use ffmpeg's amix in order to mix both audios instead of replacing them, if possible with ability to set volumes. But official documentation amix says nothing about volume.

  Separately both seems to work ok.

  ffmpeg -y -i video.mp4 -i audio.mp3 -filter_complex [0][1]amix=inputs=2[a] -map 0:v -map [a] -c:v copy output.mp4

  and

  ffmpeg -y -i video.mp4 -i audio.mp3 -i watermark.png -filter_complex [0][2]overlay=(21):(H-h-21)[ovr0] -map [ovr0]:v -map 1:a -c:v libx264 -preset ultrafast -crf 23 output.mp4

  but together

  ffmpeg -y -i video.mp4 -i audio.mp3 -i watermark.png -filter_complex [0][1]amix=inputs=2[a];[a][2]overlay=(21):(H-h-21)[ovr0] -map [ovr0]:v -map [a] -c:v libx264 -preset ultrafast -crf 23 output.mp4

  I’m getting an error :

  ffmpeg version N-93886-gfbdb3aa179 Copyright (c) 2000-2019 the FFmpeg developers
  
    built with gcc 8.3.1 (GCC) 20190414
  
    configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt
  
    libavutil      56. 28.100 / 56. 28.100
  
    libavcodec     58. 52.101 / 58. 52.101
  
    libavformat    58. 27.103 / 58. 27.103
  
    libavdevice    58.  7.100 / 58.  7.100
  
    libavfilter     7. 53.101 /  7. 53.101
  
    libswscale      5.  4.101 /  5.  4.101
  
    libswresample   3.  4.100 /  3.  4.100
  
    libpostproc    55.  4.100 / 55.  4.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'video.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      creation_time   : 1970-01-01T00:00:00.000000Z
  
      encoder         : Lavf53.24.2
  
    Duration: 00:00:29.57, start: 0.000000, bitrate: 1421 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 1032 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
  
      Metadata:
  
        creation_time   : 1970-01-01T00:00:00.000000Z
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, 5.1, fltp, 383 kb/s (default)
  
      Metadata:
  
        creation_time   : 1970-01-01T00:00:00.000000Z
  
        handler_name    : SoundHandler
  
  [mp3 @ 0000015e2f934ec0] Estimating duration from bitrate, this may be inaccurate
  
  Input #1, mp3, from 'audio.mp3':
  
    Duration: 00:00:45.33, start: 0.000000, bitrate: 128 kb/s
  
      Stream #1:0: Audio: mp3, 44100 Hz, stereo, fltp, 128 kb/s
  
  Input #2, png_pipe, from 'watermark.png':
  
    Duration: N/A, bitrate: N/A
  
      Stream #2:0: Video: png, rgb24(pc), 100x56 [SAR 3779:3779 DAR 25:14], 25 tbr, 25 tbn, 25 tbc
  
  [Parsed_amix_0 @ 0000015e2ff2e940] Media type mismatch between the 'Parsed_amix_0' filter output pad 0 (audio) and the 'Parsed_overlay_1' filter input pad 0 (video)
  
  [AVFilterGraph @ 0000015e2f91c600] Cannot create the link amix:0 -> overlay:0
  
  Error initializing complex filters.
  
  Invalid argument

  So my question : whether it’s possible to combine amix and overlay together and how and in which order they should be used ? Or should I look something different because amix unable to set volume levels ?

  Thanks in advance !

• Use Google Analytics and risk fines, after CJEU ruling on Privacy Shield

  27 août 2020, par Joselyn Khor — Privacy
  EU websites using Google Analytics and Facebook are being targeted by European privacy group noyb after the invalidation of the Privacy Shield. They filed a complaint against 101 websites for continuing to send data to the US. 

  “A quick analysis of the HTML source code of major EU webpages shows that many companies still use Google Analytics or Facebook Connect one month after a major judgment by the Court of Justice of the European Union (CJEU) - despite both companies clearly falling under US surveillance laws, such as FISA 702. Neither Facebook nor Google seem to have a legal basis for the data transfers.”

  

  The Privacy Shield previously allowed for EU data to be transferred to the US. However, this was invalidated by the Court of Justice of the European Union (CJEU) on July 16, 2020. The CJEU deemed it illegal for any websites to transfer the personal data of European citizens to the US. 

  They also made it clear in a press release that “data subjects can claim compensation for inadmissible data exports (marginal no. 143 of the judgment). This should in particular include non-material damage (“compensation for pain and suffering”) and must be of a deterrent amount under European law.” Which puts extra financial pressure on websites to take the new ruling seriously.

  Immediate action is required after Google Privacy Shield invalidation

  The Berlin Commissioner for Data Protection and Freedom of Information therefore calls on all those responsible under its supervision to observe the decision of the ECJ [CJEU]. Those responsible who transfer personal data to the USA - especially when using cloud services - are now required to immediately switch to service providers in the European Union or in a country with an adequate level of data protection.

  As the ruling is effective immediately, there’s a pressing need for websites using Google Analytics to act, or face getting fined.

  What does this mean for you ?

  If you’re using Google Analytics the safest bet is to stop using it immediately. 

  "Neither Google Analytics nor Facebook Connect are necessary for the operation of these websites and could therefore have been replaced or at least deactivated in the meantime."

  If you still need to use it, then you’ll need to inform your visitors via a clear consent screen. This banner needs to make clear their personal data will be sent to the US, and to educate them about any potential risk related to this. They will then need to explicitly agree to this. 

  Another downside of cookie consent screens is that you may also suffer a damaging loss of visitors. After implementing cookie consent best practices, the UK’s data regulator the Information Commissioner’s Office (ICO) found a 90% drop in traffic, “implying a ninety percent drop in opt-in rates.”

  With an acceptance rate for such consent screens being lower than 10% your analytics becomes guesswork rather than science. 

  Looking for a privacy-respecting alternative to Google Analytics ?

  Privacy compliant Matomo Analytics is one of the best Google Analytics alternatives availalble. 

  With Matomo you’re able to continue using analytics without facing the wrath of both the GDPR and the CJEU. Matomo On-Premise lets you choose where your data is stored, so you can ensure no data is processed in the US. 

  Matomo is privacy-friendly and can be tweaked to comply with all privacy laws. Including the GDPR, HIPAA, CCPA and PECR. The benefits of this include : not needing to use tracking or cookie consent screens (like with GA) ; and avoiding fines because no personal data is collected. You also get 100% accurate data and the ability to protect your user’s privacy.

  Download Matomo

  

  Is your EU business at risk of being fined for using Google Analytics ?

  Email

  Get our assessment guide

• How to compile a static FFmpeg binary on OS X

  29 juillet 2014, par Chitanda_Eru

  I want to compile a static ffmpeg binary by myself. I follow this guide, and then built one successfully.

  ./configure --extra-version=Chitanda_Eru --prefix=/Volumes/Chitanda_Eru/ --enable-gpl --enable-version3 --enable-nonfree --disable-shared --enable-static --enable-ffplay --disable-ffserver --enable-pthreads --enable-avisynth --enable-libvo-aacenc --enable-libfaac --enable-libfdk-aac --enable-libmp3lame --enable-libvorbis --enable-libx264 --enable-libx265 --enable-libxvid --enable-libbluray --enable-libtheora --enable-libcelt --enable-openssl --enable-libspeex --enable-postproc --enable-libvpx --enable-libgsm --enable-libopenjpeg --enable-libopus --enable-fontconfig --enable-libfreetype --enable-libass --enable-filters --disable-indev=qtkit --enable-runtime-cpudetect --enable-bzlib --enable-zlib --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-libtwolame --enable-openal --enable-libsoxr --enable-libwavpack --enable-libvidstab --enable-libilbc --enable-libschroedinger --enable-libcaca --enable-opengl --enable-frei0r --enable-libquvi

  But I come across a problem, the FFmpeg binary is only 15.5MB which is much smaller than the official builds, what’s more, it can’t work on my second Mac and with errors below.

  Library not loaded: /usr/local/lib/libx264.142.dylib
  
    Referenced from: /Applications/CLI/ffmpeg
  
    Reason: image not found
  
  Trace/BPT trap: 5

  And then I use otool command to see what the dynamic libraries ffmpeg rely on.

  otool -L /Applications/CLI/ffmpeg | grep local
  
  
  
      /usr/local/lib/libSDL-1.2.0.dylib (compatibility version 12.0.0, current version 12.4.0)
  
      /usr/local/lib/libx265.25.dylib (compatibility version 25.0.0, current version 1.2.0)
  
      /usr/local/lib/libx264.142.dylib (compatibility version 0.0.0, current version 0.0.0)
  
      /usr/local/lib/libvorbisenc.2.dylib (compatibility version 3.0.0, current version 3.10.0)
  
      /usr/local/lib/libvorbis.0.dylib (compatibility version 5.0.0, current version 5.7.0)
  
      /usr/local/lib/libogg.0.dylib (compatibility version 9.0.0, current version 9.2.0)
  
      /usr/local/lib/libvo-aacenc.0.dylib (compatibility version 1.0.0, current version 1.3.0)
  
      /usr/local/lib/libvidstab.0.9.dylib (compatibility version 0.9.0, current version 0.0.0)
  
      /usr/local/lib/libtheoraenc.1.dylib (compatibility version 3.0.0, current version 3.2.0)
  
      /usr/local/lib/libtheoradec.1.dylib (compatibility version 3.0.0, current version 3.4.0)
  
      /usr/local/lib/libspeex.1.dylib (compatibility version 7.0.0, current version 7.0.0)
  
      /usr/local/lib/libquvi.7.dylib (compatibility version 8.0.0, current version 8.1.0)
  
      /usr/local/lib/libopus.0.dylib (compatibility version 6.0.0, current version 6.0.0)
  
      /usr/local/lib/libopenjpeg.1.dylib (compatibility version 7.0.0, current version 7.0.0)
  
      /usr/local/lib/libopencore-amrwb.0.dylib (compatibility version 1.0.0, current version 1.3.0)
  
      /usr/local/lib/libopencore-amrnb.0.dylib (compatibility version 1.0.0, current version 1.3.0)
  
      /usr/local/lib/libmp3lame.0.dylib (compatibility version 1.0.0, current version 1.0.0)
  
      /usr/local/lib/libgsm.1.0.13.dylib (compatibility version 1.0.0, current version 1.0.13)
  
      /usr/local/lib/libfreetype.6.dylib (compatibility version 18.0.0, current version 18.2.0)
  
      /usr/local/lib/libfontconfig.1.dylib (compatibility version 10.0.0, current version 10.0.0)
  
      /usr/local/lib/libfdk-aac.0.dylib (compatibility version 1.0.0, current version 1.4.0)
  
      /usr/local/lib/libfaac.0.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
  
      /usr/local/lib/libcaca.0.dylib (compatibility version 100.0.0, current version 100.19.0)
  
      /usr/local/lib/libcelt0.2.dylib (compatibility version 3.0.0, current version 3.0.0)
  
      /usr/local/lib/libbluray.1.dylib (compatibility version 8.0.0, current version 8.0.0)
  
      /usr/local/lib/libass.5.dylib (compatibility version 6.0.0, current version 6.0.0)

  Most of my packages are installed by Homebrew, and Homebrew will install them with "—enable-static —enable-shared". And my guess is : when I compile ffmpeg, ffmpeg rather use the dynamic libraries than the static libraries, so the binary won’t work on other Macs.How can I build a static binary of ffmpeg ? Thanks.

  update : I successfully build static ffmpeg after moving all the dylibs which have static libraries as well to other dictionary and disable all the libraries that ./configure can’t find.

  ./configure --extra-version=Chitanda_Eru --prefix=/Volumes/Chitanda_Eru/ --enable-gpl --enable-version3 --enable-nonfree --disable-shared --enable-static --enable-ffplay --disable-ffserver --enable-pthreads --enable-avisynth --enable-libvo-aacenc --enable-libfaac --enable-libfdk-aac --enable-libmp3lame --enable-libvorbis --enable-libx264 --enable-libxvid --enable-libtheora --enable-libcelt --enable-openssl --enable-libspeex --enable-postproc --enable-libvpx --enable-libgsm --enable-libopenjpeg --enable-filters --disable-indev=qtkit --enable-runtime-cpudetect --enable-bzlib --enable-zlib --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-libtwolame --enable-libsoxr --enable-libwavpack --enable-libilbc --enable-opengl --enable-frei0r