Recherche avancée

Médias (91)

Autres articles (74)

  • Gestion des droits de création et d’édition des objets

    8 février 2011, par

    Par défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;

  • Dépôt de média et thèmes par FTP

    31 mai 2013, par

    L’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
    Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)

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

Sur d’autres sites (8941)

  • How do I install ffmpeg on one EC2 Amazon Linux instance that can stream a mp4 ? [closed]

    12 septembre 2020, par starpebble

    Good day. How can I install ffmpeg on an EC2 amazon linux machine that can stream a mp4 ?

    


    The goal : an ffmpeg install on EC2 Amazon Linux that can stream one mp4 to one rtmps endpoint. Then, create an integration test suite with it.

    


    Is it just me or is ffmpeg a little crippled on EC2 Amazon Linux ?

    


    Example :

    


    ffmpeg -re -i input.mp4 -c:v libx264 -b:v 6000K -maxrate 6000K -pix_fmt yuv420p -s 1920x1080 -profile:v main -preset veryfast -g 120 -x264opts "nal-hrd=cbr:no-scenecut” -acodec aac -ab 160k -ar 44100 -f flv rtmps:///app/


    


    Linux OS :

    


    Linux version 4.14.193-113.317.amzn1.x86_64 (mockbuild@koji-pdx-corp-builder-60005) (gcc version 7.2.1 20170915 (Red Hat 7.2.1-2) (GCC)) #1 SMP Thu Sep 3 19:08:08 UTC 2020


    


    The stackoverflow answer to similar questions fail to install a ffmpeg that can stream.

    


    An installation script such as Install FFMPEG Library on EC2 Server fail this year.

    


    The static downloads referenced on John Van Sickle-FFmpeg Static Builds fail to stream to IVS. I tried the i686 release, my first guess for an x86_64 instance.

    


    The git source tree compiled binary fails to stream. Example : The tip of the tree isn't what I expected because the binary fails to recognize switches like -preset.

    


    I'd love to be able to explain streaming to anyone. Thanks.

    


  • ffmpeg capturing image from rtmp stream

    14 juin 2020, par Lewis Day

    I am passing this command via ssh ;

    



        $rtmp_address = 'rtmp://198.251.69.110/live/';
    $stream_link = "" . $rtmp_address . "" . $stream_key . "";
echo $ssh->exec('ffmpeg -i "' . $stream_link . ' live=1" -f image2 -vcodec png -vframes 1 -s 180x145 -compression_level 100 /var/www/vhosts/flamingocams.net/httpdocs/images/' . $username . '.png -y');


    



    however getting this response ;

    



    


    ffmpeg version N-53084-gd29aaf12f4-static
 https://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2020 the FFmpeg
 developers built with gcc 8 (Debian 8.3.0-6) configuration :
 —enable-gpl —enable-version3 —enable-static —disable-debug —disable-ffplay —disable-indev=sndio —disable-outdev=sndio —cc=gcc —enable-fontconfig —enable-frei0r —enable-gnutls —enable-gmp —enable-libgme —enable-gray —enable-libaom —enable-libfribidi —enable-libass —enable-libvmaf —enable-libfreetype —enable-libmp3lame —enable-libopencore-amrnb —enable-libopencore-amrwb —enable-libopenjpeg —enable-librubberband —enable-libsoxr —enable-libspeex —enable-libsrt —enable-libvorbis —enable-libopus —enable-libtheora —enable-libvidstab —enable-libvo-amrwbenc —enable-libvpx —enable-libwebp —enable-libx264 —enable-libx265 —enable-libxml2 —enable-libdav1d —enable-libxvid —enable-libzvbi —enable-libzimg libavutil 56. 50.100 / 56. 50.100 libavcodec 58. 90.100 / 58. 90.100 libavformat 58. 44.100 / 58. 44.100 libavdevice 58. 9.103 / 58. 9.103 libavfilter 7. 84.100 / 7. 84.100 libswscale 5. 6.101 / 5. 6.101 libswresample 3. 6.100 / 3. 6.100 libpostproc 55. 6.100 / 55. 6.100 [rtmp @ 0x730fe40] Detected librtmp style URL parameters, these aren't supported by the
 libavformat internal RTMP handler currently enabled. See the
 documentation for the correct way to pass parameters.

    


    



    could anyone help with what is going wrong.

    


  • Problems with ffmpeg input filenames when using bash script

    25 septembre 2020, par Nick Styles

    I'm trying to use ffmpeg to convert some .m4a audio files to .mp3, and have come across something that has me stumped. I'd like to create the .mp3 in the same location and with the same filename as the .m4a, and so I'm using a combination of find/exec and a bash script to do this, as follows :

    


    find /Volumes/Untitled/ -name '[!.]*' -name '*.m4a' -exec ./m4atomp3.sh {} \;


    


    where m4atomp3.sh looks like :

    


    #!/usr/bin/env bash
[[ -f "$1" ]] || { echo "$1 not found" ; exit 1 ; }
P="$1"
echo "$P is the full filename"
filename=${P%.*}
echo "$filename is the stripped filename"
m4afilename=\"$filename.m4a\"
echo "$m4afilename is the input filename"
mp3filename=\"$filename.mp3\"
echo "$mp3filename is the output filename"
mycmd="/Users/nickstyles/Downloads/ffmpeg -i "$m4afilename" -codec:a libmp3lame -qscale:a 2  -nostdin "$mp3filename
echo $mycmd
$mycmd


    


    Whenever I try this, it fails because ffmpeg doesn't find the file, seemingly because of the whitespace in the filename, e.g if the file was called /Volumes/Untitled/My M4As/My M4A.m4a I would see :

    


    ffmpeg version N-99346-g003b5c800f-tessus  https://evermeet.cx/ffmpeg/  Copyright (c) 2000-2020 the FFmpeg developers
  built with Apple clang version 11.0.0 (clang-1100.0.33.17)

[configuration details]

"/Volumes/Untitled/My: No such file or directory


    


    However, if I just paste what is returned by echo $mycmd into the command line, e.g :

    


    /Users/nickstyles/Downloads/ffmpeg -i "/Volumes/Untitled/My M4As/My M4A.m4a" -codec:a libmp3lame -qscale:a 2 -nostdin "/Volumes/Untitled/My M4As/My M4A.mp3"


    


    then it works absolutely fine. I'm sure I'm missing something very obvious, which hopefully someone can spot !