Recherche avancée

Sur d’autres sites (9179)

• Can you reuse an init.mp4 file for two separate FMP4 videos if they are encoded to the same specification ?

  19 février 2024, par TCR

  I have two separate FMP4 (Fragmented MP4) videos that I need to encode. Both videos will be encoded to the same specifications, including resolution, bitrate, and codec settings. I understand that each FMP4 video typically includes an init.mp4 file containing initialization data.

  


  My question is : can I reuse the same init.mp4 file for both videos since they are encoded to the same spec ? Would this cause any issues with playback compatibility or any other potential problems ?

  


  Since the moov atom contains general info and timing information meta-data, and both videos are encoded to the same specification, my thought is you could reference one init file for playback of both videos. If I could guarantee that encoding specifications are the same, what would be the consequence of such an approach ?

  


• Revision 38898 : L’action de récupération de logo passe par la fonction idoine (évite de ...

  19 juin 2010, par kent1@… — Log

  L’action de récupération de logo passe par la fonction idoine (évite de dupliquer du code)
  Cette fonction retourne le nouvel id_document lié à la vignette
  Pour les documents dont le son est en codé via le codes vorbis ou libvorbis, on utilise un niveau de qualité plutôt qu’un bit rate (Vorbis étant toujours en VBR)
  Le cron ne fonctionne que si le chemin vers ffmpeg n’est pas cassé (méta)
  Si un document original n’existe plus ses occurrences sont enlevées de la file d’attente via le cron
  Amélioration du script d’encodage prenant en compte la qualité des fichiers utilisant vorbis
  On augmente le numéro de version du plugin

• ffmpeg amix filter on mp3 with image

  20 novembre 2018, par cutoffurmind

  I use ffmpeg to concatenate 2 mp3 files with amix filter (see full log).

  It works fine for mp3 files without any meta but it fails with mp3 files with cover image in meta, result file length is less then 1 second.

  How could I fix it in same command ?

  Here is full log :

  localhost:Music user$ ffmpeg -i input.mp3 -i /opt/docker/tag_long.mp3 -filter_complex amix=inputs=2:duration=shortest,volume=2 -codec:a libmp3lame -q:a 5  out.mp3 -report
  
  ffmpeg started on 2018-11-11 at 13:19:50
  
  Report written to "ffmpeg-20181111-131950.log"
  
  ffmpeg version 4.1 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with Apple LLVM version 10.0.0 (clang-1000.11.45.5)
  
    configuration: --prefix=/usr/local/Cellar/ffmpeg/4.1 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-ffplay --enable-gpl --enable-libmp3lame --enable-libopus --enable-libsnappy --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid --enable-lzma --enable-opencl --enable-videotoolbox
  
    libavutil      56. 22.100 / 56. 22.100
  
    libavcodec     58. 35.100 / 58. 35.100
  
    libavformat    58. 20.100 / 58. 20.100
  
    libavdevice    58.  5.100 / 58.  5.100
  
    libavfilter     7. 40.101 /  7. 40.101
  
    libavresample   4.  0.  0 /  4.  0.  0
  
    libswscale      5.  3.100 /  5.  3.100
  
    libswresample   3.  3.100 /  3.  3.100
  
    libpostproc    55.  3.100 / 55.  3.100
  
  [mp3 @ 0x7fe506000000] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, mp3, from 'input.mp3':
  
    Metadata:
  
      artist          : Paul
  
      album           : Underground Vol. 17
  
      title           : Crazy
  
      track           : 11/20
  
      date            : 2017
  
    Duration: 00:04:46.23, start: 0.000000, bitrate: 324 kb/s
  
      Stream #0:0: Audio: mp3, 44100 Hz, stereo, fltp, 320 kb/s
  
      Stream #0:1: Video: mjpeg, yuvj420p(pc, bt470bg/unknown/unknown), 500x500 [SAR 1:1 DAR 1:1], 90k tbr, 90k tbn, 90k tbc
  
      Metadata:
  
        comment         : Cover (front)
  
  [mp3 @ 0x7fe50601aa00] Estimating duration from bitrate, this may be inaccurate
  
  Input #1, mp3, from '/opt/docker/tag_long.mp3':
  
    Metadata:
  
      genre           : Blues
  
      id3v2_priv.XMP  : &lt;?xpacket begin="\xef\xbb\xbf" id="W5M0MpCehiHzreSzNTczkc9d"?>\x0a\x0a \x0a  <rdf 128="128" kb="kb"></rdf>s
  
      Stream #1:0: Audio: mp3, 44100 Hz, stereo, fltp, 128 kb/s
  
  File 'out.mp3' already exists. Overwrite ? [y/N] Y
  
  Stream mapping:
  
    Stream #0:0 (mp3float) -> amix:input0 (graph 0)
  
    Stream #1:0 (mp3float) -> amix:input1 (graph 0)
  
    volume (graph 0) -> Stream #0:0 (libmp3lame)
  
    Stream #0:1 -> #0:1 (mjpeg (native) -> png (native))
  
  Press [q] to stop, [?] for help
  
  [swscaler @ 0x7fe506045000] deprecated pixel format used, make sure you did set range correctly
  
  [mp3 @ 0x7fe507810000] Frame rate very high for a muxer not efficiently supporting it.
  
  Please consider specifying a lower framerate, a different muxer or -vsync 2
  
  Output #0, mp3, to 'out.mp3':
  
    Metadata:
  
      TPE1            : Paul
  
      TALB            : Underground Vol. 17
  
      TIT2            : Crazy
  
      TRCK            : 11/20
  
      TDRC            : 2017
  
      TSSE            : Lavf58.20.100
  
      Stream #0:0: Audio: mp3 (libmp3lame), 44100 Hz, stereo, fltp (default)
  
      Metadata:
  
        encoder         : Lavc58.35.100 libmp3lame
  
      Stream #0:1: Video: png, rgb24(progressive), 500x500 [SAR 1:1 DAR 1:1], q=2-31, 200 kb/s, 90k fps, 90k tbn, 90k tbc
  
      Metadata:
  
        comment         : Cover (front)
  
        encoder         : Lavc58.35.100 png
  
  frame=    1 fps=0.0 q=-0.0 Lsize=     496kB time=00:00:00.26 bitrate=15501.4kbits/s speed=0.336x    
  
  video:495kB audio:1kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.084876%