Recherche avancée

Sur d’autres sites (13479)

• Creating animated AVIF with FFmpeg

  17 septembre 2022, par Ollie Williams

  Edit : This did eventually complete, and the output file is fine. I am using a top-end MacBook M1 Pro computer. Is it normal for it to be this relentlessly slow ? It was

  


  My input file is an .mov. I used this command :

  


  ffmpeg -i Jellyfish.mov Jellyfish.avif

  


  I also tried converting an MP4/h264 file.
In both cases it took over 50 minutes.

  


  It's a 5 second long clip but it has taken about 20 minutes and the output file is still zero bytes.

  


  This is the output in my terminal :

  


  Output #0, avif, to 'Jellyfish.avif':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: mp42mp41isomavc1
    encoder         : Lavf59.27.100
  Stream #0:0(und): Video: av1 (av01 / 0x31307661), yuv420p(tv, bt709, progressive), 1280x720, q=2-31, 30 fps, 15360 tbn (default)
    Metadata:
      creation_time   : 2022-03-18T00:53:05.000000Z
      handler_name    : L-SMASH Video Handler
      vendor_id       : [0][0][0][0]
      encoder         : Lavc59.37.100 libaom-av1
    Side data:
      cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: N/A
frame=    1 fps=0.0 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   frame=   36 fps=1.4 q=0.0 size=       0kB time=00:00:00.03 bitrate=   0.0kbits/sframe=   37 fps=0.2 q=0.0 size=       0kB time=00:00:00.06 bitrate=   0.0kbits/sframe=   39 fps=0.2 q=0.0 size=       0kB time=00:00:00.13 bitrate=   0.0kbits/sframe=   41 fps=0.1 q=0.0 size=       0kB time=00:00:00.20 bitrate=   0.0kbits/sframe=   43 fps=0.1 q=0.0 size=       0kB time=00:00:00.26 bitrate=   0.0kbits/sframe=   45 fps=0.1 q=0.0 size=       0kB time=00:00:00.33 bitrate=   0.0kbits/sframe=   47 fps=0.1 q=0.0 size=       0kB time=00:00:00.40 bitrate=   0.0kbits/sframe=   49 fps=0.1 q=0.0 size=       0kB time=00:00:00.46 bitrate=   0.0kbits/sframe=   51 fps=0.1 q=0.0 size=       0kB time=00:00:00.53 bitrate=   0.0kbits/sframe=   53 fps=0.1 q=0.0 size=       0kB time=00:00:00.60 bitrate=   0.0kbits/sframe=   55 fps=0.1 q=0.0 size=       0kB time=00:00:00.66 bitrate=   0.0kbits/sframe=   57 fps=0.1 q=0.0 size=       0kB time=00:00:00.73 bitrate=   0.0kbits/sframe=   59 fps=0.1 q=0.0 size=       0kB time=00:00:00.80 bitrate=   0.0kbits/sframe=   61 fps=0.1 q=0.0 size=       0kB time=00:00:00.86 bitrate=   0.0kbits/sframe=   63 fps=0.1 q=0.0 size=       0kB time=00:00:00.93 bitrate=   0.0kbits/sframe=   65 fps=0.1 q=0.0 size=       0kB time=00:00:01.00 bitrate=   0.0kbits/sframe=   67 fps=0.1 q=0.0 size=       0kB time=00:00:01.06 bitrate=   0.0kbits/s speed=0.00103x


  


  I copied the command avif.io

  


• Ffmpeg x265 error : "Color Primaries must be", "ransfer Characteristics must be", "Matrix Coefficients must be" [closed]

  16 septembre 2022, par Mister Sir

  I'm trying to do the following conversion :

  


  ffmpeg -i video.mp4 -map 0 -c copy -c:v libx265 -crf 30 -vf "scale=-1:\'min(720,ih)\'" -c:a libopus -b:a 44k -map_metadata 0 -loglevel error -hide_banner video.mkv


  


  This works fine except for a specific video. I'm getting the following output :

  


  x265 [info]: HEVC encoder version 3.5+39-7c7ea0a4b
x265 [info]: build info [Windows][GCC 12.1.0][64 bit] 8bit+10bit+12bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
x265 [error]: Color Primaries must be unknown, bt709, bt470m, bt470bg, smpte170m, smpte240m, film, bt2020, smpte-st-428, smpte-rp-431 or smpte-eg-432
x265 [error]: Transfer Characteristics must be unknown, bt709, bt470m, bt470bg, smpte170m, smpte240m, linear, log100, log316, iec61966-2-4, bt1361e, iec61966-2-1, bt2020-10, bt2020-12, smpte-st-2084, smpte-st-428 or arib-std-b67
x265 [error]: Matrix Coefficients must be unknown, bt709, fcc, bt470bg, smpte170m, smpte240m, gbr, ycgco, bt2020nc, bt2020c, smpte-st-2085, chroma-nc, chroma-c or ictcp
[libx265 @ 00000000005a2940] Cannot open libx265 encoder.


  


  Can't find a single result when I google the first error text, ffmpeg "Color Primaries must be unknown"

  


  This is the verbose output :

  


  ffmpeg version 2022-06-16-git-5242ede48d-full_build-www.gyan.dev Copyright (c) 2000-2022 the FFmpeg developers
  built with gcc 11.3.0 (Rev1, Built by MSYS2 project)
  configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib --enable-lzma --enable-libsnappy --enable-zlib --enable-librist --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libdav1d --enable-libdavs2 --enable-libuavs3d --enable-libzvbi --enable-librav1e --enable-libsvtav1 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libaom --enable-libjxl --enable-libopenjpeg --enable-libvpx --enable-mediafoundation --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-liblensfun --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-libshaderc --enable-vulkan --enable-libplacebo --enable-opencl --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint
  libavutil      57. 27.100 / 57. 27.100
  libavcodec     59. 33.100 / 59. 33.100
  libavformat    59. 25.100 / 59. 25.100
  libavdevice    59.  6.100 / 59.  6.100
  libavfilter     8. 41.100 /  8. 41.100
  libswscale      6.  6.100 /  6.  6.100
  libswresample   4.  6.100 /  4.  6.100
  libpostproc    56.  5.100 / 56.  5.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'video_2022-07-22_10-01-25.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    creation_time   : 2022-07-04T13:14:36.000000Z
  Duration: 00:01:04.32, start: 0.000000, bitrate: 342 kb/s
  Stream #0:0[0x1](eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, reserved, progressive), 1280x720, 209 kb/s, 24.99 fps, 50 tbr, 90k tbn (default)
    Metadata:
      creation_time   : 2022-07-04T13:14:29.000000Z
      handler_name    : VideoHandle
      vendor_id       : [0][0][0][0]
  Stream #0:1[0x2](eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 127 kb/s (default)
    Metadata:
      creation_time   : 2022-07-04T13:14:29.000000Z
      handler_name    : SoundHandle
      vendor_id       : [0][0][0][0]
Multiple -c, -codec, -acodec, -vcodec, -scodec or -dcodec options specified for stream 0, only the last option '-c:v libx265' will be used.
Multiple -c, -codec, -acodec, -vcodec, -scodec or -dcodec options specified for stream 1, only the last option '-c:a libopus' will be used.
File 'C:\Users\Administrator\Downloads\delendum\New folder\testout.mkv' already exists. Overwrite? [y/N] Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> hevc (libx265))
  Stream #0:1 -> #0:1 (aac (native) -> opus (libopus))
Press [q] to stop, [?] for help
x265 [info]: HEVC encoder version 3.5+37-07b011400
x265 [info]: build info [Windows][GCC 11.2.0][64 bit] 8bit+10bit+12bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x265 [error]: Color Primaries must be unknown, bt709, bt470m, bt470bg, smpte170m, smpte240m, film, bt2020, smpte-st-428, smpte-rp-431 or smpte-eg-432
x265 [error]: Transfer Characteristics must be unknown, bt709, bt470m, bt470bg, smpte170m, smpte240m, linear, log100, log316, iec61966-2-4, bt1361e, iec61966-2-1, bt2020-10, bt2020-12, smpte-st-2084, smpte-st-428 or arib-std-b67
x265 [error]: Matrix Coefficients must be unknown, bt709, fcc, bt470bg, smpte170m, smpte240m, gbr, ycgco, bt2020nc, bt2020c, smpte-st-2085, chroma-nc, chroma-c or ictcp
[libx265 @ 0000000002e60340] Cannot open libx265 encoder.
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
[libopus @ 000000000056fe00] 1 frames left in the queue on closing
Conversion failed!


  


  I'm not an expert at video encoding, so I don't really know what this all means. Probably something with the source file. How to get around this ? Thanks in advance ! If I need to upload the video, let me know how I can do that.

  


• Introducing Improvements to the Opt-Out Form Feature

  18 septembre 2022, par Ben — About

  Matomo includes a built-in opt-out form that you can add to your website so you can provide your visitors with the choice to opt-out of Matomo tracking. Up until Matomo 4.12.0 the built-in opt-out form relied on iFrame technology which has become increasingly problematic due to browser changes and restrictions on setting third-party cookies.

  With our privacy-first approach, we’ve known for some time that we would eventually need a new way to provide this important opt-out functionality that would work most reliably in the myriad of contexts our users rely on it for.

  Embedding the opt-out form

  Matomo 4.12.0 introduces an improved opt-out. This provides two new options for embedding the opt-out on your website, either using the Matomo tracker code or as self-contained code.

  

  As with the iFrame method, the built-in opt-out code can be styled in Matomo to match your website, and provides a snippet which you can add to your website to show the opt-out feature to your users.

  Find out how to customise the opt-out form.

  Customising the opt-out form

  

  What does this mean for existing opt-out forms ?

  Although it is no longer possible to generate new iFrame embed code using the Matomo UI, the underlying opt-out feature is still fully supported and any existing iFrame opt-out form code embedded in websites will still work as before. It is recommended to migrate to one of the new opt-out form options as browser support for the iFrame opt-out will continue to decrease.

  To read more in depth information about the new opt-out functionality please refer to our new developer documentation for tracking opt-out.