Recherche avancée

Médias (0)

Mot : - Tags -/gis

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

Autres articles (86)

  • 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"

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • Personnaliser les catégories

    21 juin 2013, par

    Formulaire de création d’une catégorie
    Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
    Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire.
    Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
    Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)

Sur d’autres sites (11614)

  • How to use ffmpeg encode video in H.264 ?

    7 mai 2016, par seaguest

    I have installed ffmpeg 3.0 from https://github.com/FFmpeg/FFmpeg, I am trying to convert a video coded with mepeg4 part 2 to H264, but I got Unknown encoder 'libx264'
    error

    Here is my comannd : (I tried h264, x264, libx264, none of them worked)

    ffmpeg -i Fashion.divx -acodec aac -vcodec libx264  out.mp4

    I checked the list of supported codec

    Codecs:
    D..... = Decoding supported
    .E.... = Encoding supported
    ..V... = Video codec
    ..A... = Audio codec
    ..S... = Subtitle codec
    ...I.. = Intra frame-only codec
    ....L. = Lossy compression
    .....S = Lossless compression
    -------
    D.VI.. 012v                 Uncompressed 4:2:2 10-bit

    Here is h264 :

    D.V.LS h264                 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (decoders: h264 h264_vdpau)

    I am using ffmpeg 3.0, from that list, it seems that encoding with h264 is not supported, only decoding h264 is supported, right ?

    I tried to enable h.264 with this guide
    How to quickly compile FFmpeg with libx264 (x264, H.264)

    ./configure --enable-gpl --enable-libx264

    bu I get
    ./configure —enable-gpl —enable-libx264

    ERROR: libx264 not found

    If you think configure made a mistake, make sure you are using the latest
    version from Git.  If the latest version fails, report the problem to the
    ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
    Include the log file "config.log" produced by configure as this will help
    solve the problem.

    what should I do to make encode video in h.264 work ?

  • python ffmpeg subprocess not working on heroku

    21 septembre 2018, par Liam

    I’ve made a bot that deals with gif files and I tried uploading it on heroku.

    So I’ve installed this buildpack https://elements.heroku.com/buildpacks/jonathanong/heroku-buildpack-ffmpeg-latest

    And I run this code as a subprocess :

    id_name = "je4d" (is actually randomized bc it downloads different gifs)
    path = "./media/%s.gif" % (id_name)
    subprocess.run('ffmpeg -y -ignore_loop 0 -i %s -movflags faststart -pix_fmt yuv420p -vf "scale=trunc(iw/2)*2:trunc(ih/2)*2" -t 15 %s' % (path, path.replace(".gif", ".mp4")), shell=True)

    So if I run this on my computer, it will transform je4d.gif into an .mp4 and it works fine

    If I try to test ffmpeg on heroku by doing heroku run bash
    and then inputing the command ffmpeg -y -ignore_loop 0 -i ./media/je4d.gif -movflags faststart -pix_fmt yuv420p -vf "scale=trunc(iw/2)*2:trunc(ih/2)*2" -t 15 ./media/je4d.mp4
    It also works fine and makes a .mp4

    However if I run the code on heroku from python it does this :
    [Errno 2] No such file or directory: 'ffmpeg -y -i ./media/3s1m8cw09sl11.gif -movflags faststart -pix_fmt yuv420p -vf "scale=trunc(iw/2)*2:trunc(ih/2)*2" ./media/3s1m8cw09sl11.mp4': 'ffmpeg -y -i ./media/3s1m8cw09sl11.gif -movflags faststart -pix_fmt yuv420p -vf "scale=trunc(iw/2)*2:trunc(ih/2)*2" ./media/3s1m8cw09sl11.mp4'

    So I thought maybe there’s an error with the download, so I change path to a static file on the server, and it still gives me the same error.
    Any tips ?

  • Compiling ffmpeg with an output device (decklink)

    18 avril 2018, par ddibiase

    I’ve gone through the ffmpeg compile tutorial and have managed to get it working as expected. The build looks stable and usable. However now I need to include the Blackmagick Decklink SDK in the build using the —enable-decklink flag.

    cd ~/ffmpeg_sources && \
    wget -O ffmpeg-snapshot.tar.bz2 https://ffmpeg.org/releases/ffmpeg-snapshot.tar.bz2 && \
    tar xjvf ffmpeg-snapshot.tar.bz2 && \
    cd ffmpeg && \
    PATH="$HOME/bin:$PATH" PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig" ./configure \
     --prefix="$HOME/ffmpeg_build" \
     --pkg-config-flags="--static" \
     --extra-cflags="-I$HOME/ffmpeg_build/include" \
     --extra-ldflags="-L$HOME/ffmpeg_build/lib" \
     --extra-libs="-lpthread -lm" \
     --bindir="$HOME/bin" \
     --enable-gpl \
     --enable-libass \
     --enable-libfdk-aac \
     --enable-libfreetype \
     --enable-libmp3lame \
     --enable-libopus \
     --enable-libtheora \
     --enable-libvorbis \
     --enable-libvpx \
     --enable-libx264 \
     --enable-libx265 \
     --enable-decklink \
     --enable-nonfree && \
    PATH="$HOME/bin:$PATH" make && \
    make install && \
    hash -r

    However after a few seconds it fails and reports that it cannot find the decklink libs :

    ERROR: DeckLinkAPI.h not found

    If you think configure made a mistake, make sure you are using the latest
    version from Git.  If the latest version fails, report the problem to the
    ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
    Include the log file "ffbuild/config.log" produced by configure as this will help
    solve the problem.

    I’ve placed the libraries in the same folder specified by extra-cflags and in the ldflags. So basically the Decklink SDK is available here and here :

    ~/ffmpeg_build/include/decklink
    ~/ffmpeg_build/lib/decklink

    That’s not apparently how you do it though. I’m wondering where I should be putting the SDK source to ensure the compiler can read it.