Recherche avancée

Médias (91)

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

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

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

Sur d’autres sites (5255)

  • Heroku buildpack FFMpeg

    1er juin 2015, par user1107201

    I would like to setup FFMpeg for use with my rails app on Heroku and am trying to follow seemingly simple instructions. But I don’t understand the instructions. Would really appreciate if someone could help me interpret them.

    $ ls
    .buildpacks
    ...

    I assume this is working from my local application root folder of my rails app. But I don’t have a .buildpacks file. So, I try to create one using touch .buildpacks. That doesn’t create anything - I am using a mac with yosemite

    $ cat .buildpacks
    https://github.com/shunjikonishi/heroku-buildpack-ffmpeg
    https://github.com/heroku/heroku-buildpack-play

    I believe this will pull the contents of those two github build packs into my `.buildpacks’ file.

    $ heroku create --buildpack https://github.com/ddollar/heroku-buildpack-multi

    The above command take my newly create .buildpacks file, combines into build-pack-multi

    $ git push heroku master

    Push the changes created above to heroku.

    Thanks !

  • Monitoring ffmpeg two-passes encoding

    31 décembre 2024, par Hodol

    I'm new in FFMPEG.

    


    According to the official guide, https://trac.ffmpeg.org/wiki/Encode/VP9 I use the following command to convert a large h.264 file :

    


    ffmpeg -i input.mp4 -c:v libvpx-vp9 -b:v 0 -crf 30 -pass 1 -an -f null /dev/null
ffmpeg -i input.mp4 -c:v libvpx-vp9 -b:v 0 -crf 30 -pass 2 -c:a libopus output.webm


    


    However, the pass-1 takes too long time and it does not log progress. With -report option I can see something is in progress but I don't know how long I should wait.

    


    Here's questions :

    


      

    1. Is there any way to see the progress of 1-pass ?
    2. 


    3. Is there any way to speed up the process ?
    4. 


    


    Thank you,

    


  • ffmpeg and grep not working to extract mean_volume value

    31 octobre 2019, par Json

    I have a list of mp3 files and i want to set all mean_volume to the same db value using a script, so I enter the command for detecting the value (https://trac.ffmpeg.org/wiki/AudioVolume) and I try to grep the value but it fails and instead prints all the output from the ffmpeg command. Any thoughts ?
    Also tried tr instead of grep. The command I used is :

    ffmpeg -i sample.mp3 -filter:a volumedetect -f null /dev/null | grep 'mean_volume'