Recherche avancée

Médias (91)

Autres articles (37)

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

  • Contribute to translation

    13 avril 2011

    You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
    To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
    MediaSPIP is currently available in French and English (...)

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

Sur d’autres sites (5014)

  • Error while installing ffmpeg on standalone computer

    10 juillet 2018, par newuser

    I am trying to install libx264 and ffmpeg on a computer without internet access
    My plan is to first download all required packages and dependencies on a laptop with internet and then copy them over
    To download the packages I used :

    apt-get download $(apt-rdepends <package>|grep -v "^ ")
    
</package>

    I was able to install yasm, libvpx and libx264 without issues this way.
    When I try to install ffmpeg, I get this error.

    The following packages have unmet dependencies:
    
 chromium-codecs-ffmpeg-extra-dbg : Depends: chromium-codecs-ffmpeg-extra (= 51.0.2704.79-0ubuntu0.16.04.1.1242) but 66.0.3359.181-0ubuntu0.16.04.1 is installed
    
 ffmpeg-dbg : Depends: ffmpeg (= 7:2.8.14-0ubuntu0.16.04.1)
    
 ffmpeg-doc : Depends: libjs-bootstrap but it is not installed
    
 ffmpeg2theora : Depends: liboggkate1 (>= 0.3.0) but it is not installed
    
 ffmpegthumbs : Depends: libkf5kiowidgets5 (>= 4.99.0) but it is not installed
    
 kffmpegthumbnailer : Depends: libkio5 (>= 4:4.3.4) but it is not installed
    
 moc-ffmpeg-plugin : Depends: moc (= 1:2.6.0~svn-r2788-1) but it is not installed

    where do I get these packages from ? I dont want apt-get to download them for me as I want to be able to get the package files.

  • SRT protocol not found - Raspbery Pi 4 via ffmpeg

    12 août 2021, par Tim Martin

    We tried to stream from a rasp Pi 4 via SRT, but we got a error : "protocol not found". Our command line is :

    &#xA;

    ffplay srt://127.0.0.1:9500?mode=listener&amp;latency=20000&#xA;

    &#xA;

    We tried the following guides :&#xA;https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu&#xA;how to compile ffmpeg with enabling libsrt&#xA;https://www.undergroundnews.dk/index.php/item/107-rtmp-eller-srt-streaming

    &#xA;

    Those guides worked so far and compiled but we still got the error message.

    &#xA;

    Do you have any ideas how to get the srt protocol working on a pi via ffmpeg ?

    &#xA;

  • Compiling FFMPEG on CentOS DigitalOcean

    29 juillet 2015, par coder_uk

    I set up a DigitalOcean instance running CentOS 6.5 and successfully followed the guide to compile FFMPEG (https://trac.ffmpeg.org/wiki/CompilationGuide/Centos). Hurrah !

    But of course I realised that by default, DigitalOcean creates a root user and so ffmpeg now lives in /root/bin/ffmpeg. Which isn’t ideal because when I want to exec the ffmpeg bin from nginx, I would have to run nginx as root for it to have permission.

    Questions ...

    1) Long-shot, but presumably if I change the owner of the ffmpeg binary to nginx, it still won’t work, because nginx won’t be able to access the /root folder it is in. Correct ?

    2) I could run nginx as root (’user root’). But this seems like a very bad idea. Correct ?

    3) Which leaves me with the option of creating a new user, and then compiling ffmpeg into its home folder. But : which user ? EC2 creates ’ec2-user’, so should I make my own equivalent for DO ? But then won’t I have to run nginx as that user, else I’ll run into the same problem ?

    Or should I compile ffmpeg into the ’nginx’ home folder, if indeed it has one ? Is that how it is supposed to be done ?

    Since compiling ffmpeg takes ages, I don’t want to keep doing it, and the static files all seem very out of date. Thanks

Navigation