Recherche avancée

Médias (17)

Mot : - Tags -/wired

Autres articles (103)

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

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

  • Gestion de la ferme

    2 mars 2010, par

    La ferme est gérée dans son ensemble par des "super admins".
    Certains réglages peuvent être fais afin de réguler les besoins des différents canaux.
    Dans un premier temps il utilise le plugin "Gestion de mutualisation"

Sur d’autres sites (7646)

  • Converting DAV to MP4 and OGG

    27 mars 2015, par mackowiakp

    I want to prepare WEB page containing films from security camera recorders. Each recorder transmit video files in DAV format so each film is converted to MP4 format by script, using such syntax :

    ffmpeg -y -i movie.dav -vcodec libx264 -crf 24 movie.mp4

    So I included in HTMLv5 code such entry :

    <video width="320" height="240">
     <source src="movie.mp4" type="video/mp4">
    </source></video>

    It works correctly with Chrome but not with Firefox. For proper work in FF it is necessary add link to OGG file. So correct HTMLv5 syntax for both browsers should look like this :

    <video width="320" height="240">
     <source src="movie.mp4" type="video/mp4">
     <source src="movie.ogg" type="video/ogg">
    </source></source></video>

    Can anybody help me to pass correct ffmpeg syntax to create OGG file ?

    Output from console after using -movflags +faststart options

    [maciek@piotr MMM]$ ../ffmpeg-2.4.2-64bit-static/ffmpeg -movflags +faststart -y -i   04.24.23-04.24.38\[M\]\[@0\]\[0\].dav -vcodec libx264 -crf 24 10.mp4
    ffmpeg version 2.4.2-   http://johnvansickle.com/ffmpeg/    Copyright (c) 2000-2014 the FFmpeg developers
     built on Oct  9 2014 07:24:56 with gcc 4.8 (Debian 4.8.3-11)
     configuration: --enable-gpl --enable-version3 --disable-shared --disable-debug --enable-runtime-cpudetect --enable-libmp3lame --enable-libx264 --enable-libx265 --enable- libwebp --enable-libspeex --enable-libvorbis --enable-libvpx --enable-libfreetype --enable-fontconfig --enable-libxvid --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libtheora --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-gray --enable-libopenjpeg --enable-libopus --disable-ffserver --enable-libass --enable-gnutls --cc=gcc-4.8
     libavutil      54.  7.100 / 54.  7.100
     libavcodec     56.  1.100 / 56.  1.100
     libavformat    56.  4.101 / 56.  4.101
     libavdevice    56.  0.100 / 56.  0.100
     libavfilter     5.  1.100 /  5.  1.100
     libswscale      3.  0.100 /  3.  0.100
     libswresample   1.  1.100 /  1.  1.100
     libpostproc    53.  0.100 / 53.  0.100
    Option movflags not found.
  • It's possible to catch ffmpeg errors with python ?

    4 avril 2019, par Elros Romeo

    Hi I’m trying to make a video converter for django with python, I forked django-ffmpeg module which does almost everything I want, except that doesn’t catch error if conversion failed.

    Basically the module passes to the command line interface the ffmpeg command to make the conversion like this :

    /usr/bin/ffmpeg -hide_banner -nostats -i %(input_file)s -target
    film-dvd %(output_file)

    Module uses this method to pass the ffmpeg command to cli and get the output :

    def _cli(self, cmd, without_output=False):
       print 'cli'
       if os.name == 'posix':
           import commands
           return commands.getoutput(cmd)
       else:
           import subprocess
           if without_output:
               DEVNULL = open(os.devnull, 'wb')
               subprocess.Popen(cmd, stdout=DEVNULL, stderr=DEVNULL)
           else:
               p = subprocess.Popen(cmd, stdout=subprocess.PIPE)
               return p.stdout.read()

    But for example, I you upload an corrupted video file it only returns the ffmpeg message printed on the cli, but nothing is triggered to know that something failed

    This is an ffmpeg sample output when conversion failed :

    [mov,mp4,m4a,3gp,3g2,mj2 @ 0x237d500] Format mov,mp4,m4a,3gp,3g2,mj2
    detected only with low score of 1, misdetection possible !
    [mov,mp4,m4a,3gp,3g2,mj2 @ 0x237d500] moov atom not found
    /home/user/PycharmProjects/videotest/media/videos/orig/270f412927f3405aba041265725cdf6b.mp4 :
    Invalid data found when processing input

    I was wondering if there’s any way to make that an exception and how, so I can handle it easy.

    The only option that came to my mind is to search : "Invalid data found when processing input" in the cli output message string but I’m not shure that if this is the best approach. Anyone can help me and guide me with this please.

  • vulkan_decode : use a single execution pool

    3 décembre 2024, par Lynne
    vulkan_decode : use a single execution pool
    

    Originally, the decoder had a single execution pool, with one
    execution context per thread. Execution pools were always intended
    to be thread-safe, as long as there were enough execution contexts
    in the pool to satisfy all threads.

    Due to synchronization issues, the threading part was removed at some
    point, and, for decoding, each thread had its own execution pool.
    Having a single execution pool per context is hacky, not to mention
    wasteful.
    Most importantly, we *cannot* associate single shaders across multiple
    execution pools for a single application. This means that we cannot
    use shaders to either apply film grain, or use this framework for
    software-defined decoders.

    The recent commits added threading capabilities back to the execution
    pool, and the number of contexts in each pool was increased. This was
    done with the assumption that the execution pool was singular, which
    it was not. This led to increased parallelism and number of frames
    in flight, which is taxing on memory.

    This commit finally restores proper threading behaviour.
    The validation layer has isses that are reported and addressed in the
    earlier commit.

    • [DH] libavcodec/vulkan_decode.c
    • [DH] libavcodec/vulkan_decode.h