Recherche avancée

Médias (91)

Autres articles (61)

  • 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 (...)

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

Sur d’autres sites (11864)

  • Usage FFmpeg command to capture video from Apple device camera and to get 3 outputs with different resolutions (UHD, FHD, HD)

    12 décembre 2019, par Levon Gharibyan

    I use mobile-FFmpeg to execute FFmpeg commands (https://github.com/tanersener/mobile-ffmpeg).

    I am using AVFoundation, and trying to get 3 output files (3840x2160, 1920x1080 and 1280x720) from device camera.
    Here is the command :

    -f videotoolbox -f avfoundation -video_size 3840x2160 -r 30 -pixel_format nv12 -i "0:0"  -c:v h264_videotoolbox -b:v 8M -maxrate 8M -s 3840x2160 output1/path -c:v h264_videotoolbox -b:v 8M -maxrate 8M -s 1920x1080 output2/path -c:v h264_videotoolbox -b:v 8M -maxrate 8M -s 1280x720 output3/path

    But the encoding process is very slow (0.3x-0.4x speed) with that command and as a result, I can’t record realtime 30fps outputs. What am I doing wrong ? All my tests were done on the iPhone 7.

  • How can I stream video in swift using FFmpeg in real time ?

    13 novembre 2019, par rIn

    I want to make a real time video streaming app but I’m new to Swift and live streaming..

    Video input captured by AVCaptureSession is from iPhone and I want to encode the input from MPEG-4 to MPEG-2.
    I will use FFmpeg library to encode the video input in swift.

    Here’s my questions.

    1. I don’t know how to deliver video data to FFmpeg functions. Actually I’m not certain that I have to use FFmpeg library to encode video data from MPEG-4 to MPEG-2 transport stream. Is there any API that can encode video data in Swift by Apple ?

    2. How can I deal with video data from AVCaptureSession ? Are there frames or h.264 video in CMSampleBuffer ? I want to know what type of data is in CMSampleBuffer.

    I’m struggling to solve this problem. Please let me know anything if you have some experiences about this kind of project. Any ideas or advice for a better approach are welcome.

  • FFmpeg encoding slow for 4K HDR content

    1er mars 2023, par Geno Diaz

    When processing 4K input with the following configuration it is taking upwards of 2 minutes to process a 35s, 60fps, 4K HDR clip recorded from an iPhone. Is this the expected performance or is there an inefficiency within the configuration that is causing this ?

    


    In comparison, running this configuration on a 35s, 30fps, 4K non-HDR clip, only takes about 20 seconds.

    


    ffmpeg 
-i "input path" 
-y 
-filter:v scale=w=2160:h=3840 
-threads 4 
-r 59.94 
-c:v libx264 
-preset veryfast 
-vsync 1 
-tune film 
-maxrate 6000k 
-bufsize 5400k 
-g 60 
-x264opts no-scenecut 
-c:a aac 
-af aresample=async=1:min_hard_comp=0.100000:first_pts=0 
-ac 2 
-b:a 128k 
-ar 44100 
-vf zscale=transfer=linear:npl=100,
  format=gbrpf32le,
  zscale=primaries=bt709,
  tonemap=tonemap=hable:desat=0,
  zscale=transfer=bt709:matrix=bt709:range=tv,
  format=yuv420p 
-sws_flags full_chroma_int+full_chroma_inp 
-pix_fmt yuv420p 
"outputfile".mp4