Recherche avancée

Médias (2)

Mot : - Tags -/plugins

Autres articles (112)

  • La sauvegarde automatique de canaux SPIP

    1er avril 2010, par

    Dans le cadre de la mise en place d’une plateforme ouverte, il est important pour les hébergeurs de pouvoir disposer de sauvegardes assez régulières pour parer à tout problème éventuel.
    Pour réaliser cette tâche on se base sur deux plugins SPIP : Saveauto qui permet une sauvegarde régulière de la base de donnée sous la forme d’un dump mysql (utilisable dans phpmyadmin) mes_fichiers_2 qui permet de réaliser une archive au format zip des données importantes du site (les documents, les éléments (...)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

Sur d’autres sites (6424)

  • ffmpeg combining mp4 videos incorrectly

    9 juin 2018, par wdsfds

    i have a list of 20 mp4 files that I need to combine into one video. They are all 60 FPS, but range in size. In between each mp4 file I need to show its ’intro’, a 1.5 second clip about the file.

    Reference :

    • pics/i.png - intro for the nth mp4 file
    • clips/i_intro.mp4 - mp4 intro generated from i.png
    • clips/i.mp4 - original mp4
    • clips/i_resize.mp4 - 720p mp4

    Here is what I’ve done :

    Convert image to mp4 using this command (taken from this post) :

    ffmpeg -y -i pics/{i}.png -f lavfi -i anullsrc -r 60 -pix_fmt yuv420p -ac 2 -ar 44100 -video_track_timescale 90k -t 1.5 clips/{i}_intro.mp4

    Convert i.mp4 to 720p using this command (taken from this post) :

    ffmpeg -i clips/{i}.mp4 -c:v libx264 -crf 23 -preset medium -c:a aac -b:a 128k -vf scale=-2:720,format=yuv420p {i}_resize.mp4

    Created a file like this :

    file 1_intro.mp4
    
file 1_resize.mp4
    
file 2_intro.mp4
    
file 2_resize.mp4
    
...

    Combine all clips :

    ffmpeg -f concat -i {video_list} -c copy out.mp4

    This generates a file, but it is definitely messed up. When I combined the files I got a ton of warning messages like this :

    [mp4 @ 0x7f88fe01de00] Non-monotonous DTS in output stream 0:0;
    
previous: 48966232, current: 8826932; changing to 48966233. This may
    
result in incorrect timestamps in the output file.

    FFprobe for out.mp4

    ffprobe version 4.0 Copyright (c) 2007-2018 the FFmpeg developers
    
  built with Apple LLVM version 9.1.0 (clang-902.0.39.1)
    
  configuration: --prefix=/usr/local/Cellar/ffmpeg/4.0 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-gpl --enable-libmp3lame --enable-libx264 --enable-libxvid --enable-opencl --enable-videotoolbox --disable-lzma
    
  libavutil      56. 14.100 / 56. 14.100
    
  libavcodec     58. 18.100 / 58. 18.100
    
  libavformat    58. 12.100 / 58. 12.100
    
  libavdevice    58.  3.100 / 58.  3.100
    
  libavfilter     7. 16.100 /  7. 16.100
    
  libavresample   4.  0.  0 /  4.  0.  0
    
  libswscale      5.  1.100 /  5.  1.100
    
  libswresample   3.  1.100 /  3.  1.100
    
  libpostproc    55.  1.100 / 55.  1.100
    
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'out.mp4':
    
  Metadata:
    
    major_brand     : isom
    
    minor_version   : 512
    
    compatible_brands: isomiso2avc1mp41
    
    encoder         : Lavf58.12.100
    
  Duration: 00:09:35.56, start: 0.000000, bitrate: 4119 kb/s
    
    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 4221 kb/s, 59.98 fps, 351.56 tbr, 90k tbn, 120 tbc (default)
    
    Metadata:
    
      handler_name    : VideoHandler
    
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 122 kb/s (default)
    
    Metadata:
    
      handler_name    : SoundHandler

    FFprobe for 1.mp4

    ffprobe version 4.0 Copyright (c) 2007-2018 the FFmpeg developers
    
  built with Apple LLVM version 9.1.0 (clang-902.0.39.1)
    
  configuration: --prefix=/usr/local/Cellar/ffmpeg/4.0 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-gpl --enable-libmp3lame --enable-libx264 --enable-libxvid --enable-opencl --enable-videotoolbox --disable-lzma
    
  libavutil      56. 14.100 / 56. 14.100
    
  libavcodec     58. 18.100 / 58. 18.100
    
  libavformat    58. 12.100 / 58. 12.100
    
  libavdevice    58.  3.100 / 58.  3.100
    
  libavfilter     7. 16.100 /  7. 16.100
    
  libavresample   4.  0.  0 /  4.  0.  0
    
  libswscale      5.  1.100 /  5.  1.100
    
  libswresample   3.  1.100 /  3.  1.100
    
  libpostproc    55.  1.100 / 55.  1.100
    
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '1.mp4':
    
  Metadata:
    
    major_brand     : isom
    
    minor_version   : 512
    
    compatible_brands: isomiso2avc1mp41
    
    encoder         : Lavf57.71.100
    
  Duration: 00:00:40.94, start: 0.000000, bitrate: 7613 kb/s
    
    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuvj420p(pc, bt709/unknown/unknown), 1920x1080 [SAR 1:1 DAR 16:9], 7451 kb/s, 60 fps, 60 tbr, 90k tbn, 120 tbc (default)
    
    Metadata:
    
      handler_name    : VideoHandler
    
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 160 kb/s (default)
    
    Metadata:
    
      handler_name    : SoundHandler

    FFprobe for 1_resized.mp4

    ffprobe version 4.0 Copyright (c) 2007-2018 the FFmpeg developers
    
  built with Apple LLVM version 9.1.0 (clang-902.0.39.1)
    
  configuration: --prefix=/usr/local/Cellar/ffmpeg/4.0 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-gpl --enable-libmp3lame --enable-libx264 --enable-libxvid --enable-opencl --enable-videotoolbox --disable-lzma
    
  libavutil      56. 14.100 / 56. 14.100
    
  libavcodec     58. 18.100 / 58. 18.100
    
  libavformat    58. 12.100 / 58. 12.100
    
  libavdevice    58.  3.100 / 58.  3.100
    
  libavfilter     7. 16.100 /  7. 16.100
    
  libavresample   4.  0.  0 /  4.  0.  0
    
  libswscale      5.  1.100 /  5.  1.100
    
  libswresample   3.  1.100 /  3.  1.100
    
  libpostproc    55.  1.100 / 55.  1.100
    
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '1_resize.mp4':
    
  Metadata:
    
    major_brand     : isom
    
    minor_version   : 512
    
    compatible_brands: isomiso2avc1mp41
    
    encoder         : Lavf58.12.100
    
  Duration: 00:00:32.37, start: 0.000000, bitrate: 3266 kb/s
    
    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 3127 kb/s, 60 fps, 60 tbr, 15360 tbn, 120 tbc (default)
    
    Metadata:
    
      handler_name    : VideoHandler
    
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 129 kb/s (default)
    
    Metadata:
    
      handler_name    : SoundHandler

    FFprobe for 1_intro.mp4

    ffprobe version 4.0 Copyright (c) 2007-2018 the FFmpeg developers
    
  built with Apple LLVM version 9.1.0 (clang-902.0.39.1)
    
  configuration: --prefix=/usr/local/Cellar/ffmpeg/4.0 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-gpl --enable-libmp3lame --enable-libx264 --enable-libxvid --enable-opencl --enable-videotoolbox --disable-lzma
    
  libavutil      56. 14.100 / 56. 14.100
    
  libavcodec     58. 18.100 / 58. 18.100
    
  libavformat    58. 12.100 / 58. 12.100
    
  libavdevice    58.  3.100 / 58.  3.100
    
  libavfilter     7. 16.100 /  7. 16.100
    
  libavresample   4.  0.  0 /  4.  0.  0
    
  libswscale      5.  1.100 /  5.  1.100
    
  libswresample   3.  1.100 /  3.  1.100
    
  libpostproc    55.  1.100 / 55.  1.100
    
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '1_intro.mp4':
    
  Metadata:
    
    major_brand     : isom
    
    minor_version   : 512
    
    compatible_brands: isomiso2avc1mp41
    
    encoder         : Lavf58.12.100
    
  Duration: 00:00:01.52, start: 0.000000, bitrate: 113 kb/s
    
    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 4667 kb/s, 60 fps, 60 tbr, 90k tbn, 120 tbc (default)
    
    Metadata:
    
      handler_name    : VideoHandler
    
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 2 kb/s (default)
    
    Metadata:
    
      handler_name    : SoundHandler

    I noticed that the length of the files are different, and the tbn in different, but idk what that means. Thanks for helping !

  • ffmpeg QSV hardware encoder with x11grab screen capture

    11 janvier 2020, par Toby Eggitt

    I believe I have built ffmpeg with support for my motherboard’s Intel graphics processor chip, but I have not succeeded in showing this working in any way. My goal is to use it for screen capture (the ffmpeg I built does capture screen successfully using the software encoding, but this is far too slow to be useful—it manages about 12fps at a very modest quality).

    My main problem—I think—is that I don’t know how to use these encoders, the examples I found all fail, which makes me suspect that what I’ve built is broken in some way. However, I also have no idea how I can verify that I built this correctly, but the following are true :

    • The five components that I built to get to this all compiled without
      errors (they were libva, gmmlib, intel-media-driver, libmfx, and
      ffmpeg
    • The output of ffmpeg -encoders includes four encoders with _qsv in
      their names including h264_qsv
    • Most of the commands I have tried result in output of this form :
        [h264_qsv @ 0x55ef1dc72040] Low power mode is unsupported
    
    [h264_qsv @ 0x55ef1dc72040] Current frame rate is unsupported
    
    [h264_qsv @ 0x55ef1dc72040] Current picture structure is unsupported
    
    [h264_qsv @ 0x55ef1dc72040] Current resolution is unsupported
    
    [h264_qsv @ 0x55ef1dc72040] Current pixel format is unsupported
    
    [h264_qsv @ 0x55ef1dc72040] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.
    
    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

    I have the impression this thing might be fussy about many parameters of this sort but have no idea where to find out what it would like. Any suggestions at all, how to verify it, or better yet, how to issue a command that captures screen and encodes with the hardware, would be most welcome.

  • How to handle differing .mp4 file types from different sources ?

    10 octobre 2017, par Dave502619

    If I take a .mp4 recorded on my mobile (Samsung S5) and pass it through FFmpeg with the below command, the output file (fileX.avi) is a greyscale bitmap uncompressed video file.

    • The offset values in fileX.avi (output from FFmpeg) to allow me to locate the video frame data are always 5680 bytes for the file header.

    • And 62 bytes for the inter frame header.

    • The data is uncompressed RGB24 so i can easily calculate the size of a video frame from height x width x 3.

    So my C# application can access the video frames in fileX.avi always at these above offsets.
    (This works great).

    My FFmpeg Command is :

    ffmpeg.exe -i source.mp4 -b 1150 -r 20.97 -g 120 -an -vf format=gray -f rawvideo -pixfmt gray -s 384x216 -vcodec rawvideo -y fileX.avi

    However... I recently took an .mp4 file from a different source (produced by Power Director 14 instead of direct from my mobile phone) and used this as the input source.mp4. But now the structure of fileX.avi differs as the offset values of 5680 + 62 bytes from the start in fileX.avi do not land me at the start of the video data frames.

    There seems to be different file formats for .mp4 - and obviously if there are my crude offset approach will not work for them all. I suspected at the time I wrote the code my method was all too easy a solution !

    So can anyone advise on the approach I should take now ? Should I check the original .mp4 or the output file (fileX.avi) to determine a "file type" to which I can determine the different offsets ?

    At the very least I need to be able to identify the "type" of .mp4 file that works so I can declare the type that will work with my software.

Navigation