Recherche avancée

Médias (0)

Mot : - Tags -/clipboard

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (45)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

Sur d’autres sites (7167)

  • Compile ffmpeg with x264 shows : ERROR : libx264 not found in docker building image

    3 mai 2019, par NKam

    Trying to install ffmpeg from source with libx264 package. When I compile ffmpeg can’t find x264 because it is not installed.
    I followed ffmpeg installation guide.

    Before intention to compile ffmpeg in building docker image I tried to install locally and found out in folder ffmpeg_build/include I don’t have x264 files installed.

    To compile libx264 I used :

    cd /ffmpeg_sources &&

    git -C x264 pull 2> /dev/null || git clone —depth 1 https://code.videolan.org/videolan/x264.git &&

    cd x264 &&

    PATH="$HOME/bin :$PATH"

    PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig" ./configure —prefix="$HOME/ffmpeg_build" —bindir="$HOME/bin" —enable-static —enable-pic &&

    PATH="$HOME/bin :$PATH" make &&

    make install

    I changed url to https://code.videolan.org/videolan/x264.git, because this url https://git.videolan.org/git/x264 from guide not working

    I want to know what I missed. I want ffmpeg to find x264, if it is not installed how can I find way to install.

  • Compile ffmpeg with x264 shows : ERROR : libx264 not found in docker building image

    3 mai 2019, par NKam

    Trying to install ffmpeg from source with libx264 package. When I compile ffmpeg can’t find x264 because it is not installed.
    I followed ffmpeg installation guide.

    Before intention to compile ffmpeg in building docker image I tried to install locally and found out in folder ffmpeg_build/include I don’t have x264 files installed.

    To compile libx264 I used :

    cd /ffmpeg_sources &&

    git -C x264 pull 2> /dev/null || git clone —depth 1 https://code.videolan.org/videolan/x264.git &&

    cd x264 &&

    PATH="$HOME/bin :$PATH"

    PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig" ./configure —prefix="$HOME/ffmpeg_build" —bindir="$HOME/bin" —enable-static —enable-pic &&

    PATH="$HOME/bin :$PATH" make &&

    make install

    I changed url to https://code.videolan.org/videolan/x264.git, because this url https://git.videolan.org/git/x264 from guide not working

    I want to know what I missed. I want ffmpeg to find x264, if it is not installed how can I find way to install.

  • ffmpeg outputs that the first frame of a 25fps video shows for only 1ms

    13 avril 2019, par Chubacca

    I’m using ffmpeg to split up a video by frames. For a video that is 25fps, my expectation would be that it would show frame 0 for 40ms, and then it would show frame 1 for 40ms, etc. However, when I use ffmepg to analyze the video, this is not what I get.

    I pulled frames out of the video using the following commands :

    ffmpeg -i original.mp4 -ss 00:00:00.000 -vframes 1 0.000.png
    ffmpeg -i original.mp4 -ss 00:00:00.001 -vframes 1 0.001.png
    ffmpeg -i original.mp4 -ss 00:00:00.040 -vframes 1 0.040.png
    ffmpeg -i original.mp4 -ss 00:00:00.041 -vframes 1 0.041.png

    In this, I would expect 0.000.png and 0.001.png to be the same frame, but the resulting pngs are different. However, on the flipside, 0.001.png and 0.040.png ARE the same frame, while 0.040.png and 0.041.png are different frames. It seems as though the frame at 0.000.png is only showing for 1ms. I’ve tested this on multiple different videos, with consistent results. Can anybody explain why this is or why my expectations are potentially incorrect ?

    As a side note, when I load the same video into an HTML5 video tag in the browsers, when I play the video the first frame shows for 64 milliseconds, and all other frames show for 40 milliseconds. I can test this by comparing frames for the following commands :

    player.currentTime = 0
    player.currentTime = .063 // same frame as 0
    player.currentTime = .064 // different frame than .063
    player.currentTime = .103 // same frame as .064
    player.currentTime = .104 // different frame than .103

    This also defies expectations, and makes matching up frames/times for the video between ffmpeg and html5 video even more annoying. Does anyone know what’s going on here ?

    If it’s helpful, here is the metadata from the video :

    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'original.mp4':
     Metadata:
       major_brand     : isom
       minor_version   : 512
       compatible_brands: isomiso2avc1mp41
       encoder         : Lavf58.17.101
     Duration: 01:36:16.20, start: 0.000000, bitrate: 2301 kb/s
       Stream #0:0(und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 2200 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
       Metadata:
         handler_name    : VideoHandler
       Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 96 kb/s (default)
       Metadata:
         handler_name    : SoundHandler