Recherche avancée

Médias (0)

Mot : - Tags -/gis

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

Autres articles (55)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

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

  • 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

Sur d’autres sites (9761)

  • Use FFMPEG without downloading full file

    19 août 2020, par servalex

    I'm generating thumbnails for a videos that are available from s3 and need to minimize traffic.
Frame is going to be from the first couple seconds of the video so the question : is there a way to get frame without passing the full file through network ?

    


    At the moment I'm passing video url to ffmpeg but seems like it downloads the whole file, not only first couple seconds.

    


    ffmpeg -ss 0 -noaccurate_seek -i {srcPresignedUrl} -vframes 1 -q:v 2 {outputFileName}

    


    I tried downloading first 10mb of the file and passing it, this works for some mp4 files, but fails on mov :

    


    ffmpeg.exe -ss 0 -i source.mov -vframes 1 -q:v 2 thumb.jpg
ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 10.2.1 (GCC) 20200726
  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libsrt --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libgsm --enable-librav1e --disable-w32threads --enable-libmfx --enable-ffnvcodec --enable-cuda-llvm --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt --enable-amf
  libavutil      56. 51.100 / 56. 51.100
  libavcodec     58. 91.100 / 58. 91.100
  libavformat    58. 45.100 / 58. 45.100
  libavdevice    58. 10.100 / 58. 10.100
  libavfilter     7. 85.100 /  7. 85.100
  libswscale      5.  7.100 /  5.  7.100
  libswresample   3.  7.100 /  3.  7.100
  libpostproc    55.  7.100 / 55.  7.100
[mov,mp4,m4a,3gp,3g2,mj2 @ 0000017582ffff40] moov atom not found
source.mov: Invalid data found when processing input



    


  • mp3enc : write full LAME frame

    12 avril 2014, par Anton Khirnov
    mp3enc : write full LAME frame

    Most importantly, it contains the encoder delay and replaygain info.
    • [DBH] doc/muxers.texi
    • [DBH] libavformat/mp3enc.c

  • rtmppkt : Repeat the full 32 bit timestamp for chunking continuation packets

    14 janvier 2015, par Martin Storsjö
    rtmppkt : Repeat the full 32 bit timestamp for chunking continuation packets

    This fixes sending chunked packets (packets larger than the output
    
chunk size, which often can be e.g. 4096 bytes) with a timestamp delta
    
(or absolute timstamp, if it’s a timestamp step backwards, or the
    
first packet of the stream) larger than 0xffffffff.
    

    The RTMP spec explicitly says (in section 5.3.1.3.) that packets of
    
type 3 (continuation packets) should include this field, if the
    
previous non-continuation packet had it included.
    

    The receiving code handles these packets correctly.
    

    Pointed out by Cheolho Park.
    

    CC : libav-stable@libav.org
    
Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DBH] libavformat/rtmppkt.c

Navigation