Recherche avancée

Médias (3)

Mot : - Tags -/pdf

Autres articles (111)

  • Gestion générale des documents

    13 mai 2011, par

    MédiaSPIP ne modifie jamais le document original mis en ligne.
    Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
    Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (12143)

  • Anomalie #3981 : Menu "Écrire une nouvelle traduction" non présent pour rédacteurs

    12 août 2017, par Franck D

    Bon alors, j’ai pas fait les tests correctement...
    En faite, le lien pour traduire un article n’est présent concernant les "rédacteurs" que concernant leur propre articles !
    Ce qui fait qu’il ne peuvent traduire les articles des autres rédacteurs !

    Par contre, une personne avec le statut d’admi peux traduire les articles des autres (logique)

    Donc,logiquement, il faudrait que les personnes ayant le statut de rédacteur puissent traduire et proposé leur traduction à la publication concernant les articles des autres.

  • Dealing with long conversion times on nginx, ffmpeg and Ruby on Rails

    19 avril 2013, par Graeme

    I have developed a Ruby on Rails-based app which allows users to upload videos to one of our local servers (Ubunto 10.04 LTS). The server uses nginx.

    Through the paperclip-ffmpeg gem, videos are converted to mp4 format using the ffmpeg library.

    Everything appears to be working fine in production, except Rails' own 500 page (not the customised version I have provided - but that's a different issue) is displayed whenever certain videos are uploaded. Otherwise, videos are being converted as expected.

    Having done a bit of investigation, I think the default 500 page is being displayed because a 502 error has occurred. I think what is happening, having uploaded the videos locally, is that some videos are taking an extensive amount of time to convert, and that an interruption is occurring on the server (I'm not a server expert by any means).

    Using the excellent Railscasts episode on deployment, I use Capistrano to deploy the app. Here's the unicorn.rb file :

    root = "XXXXXXX"
    working_directory root
    pid "#{root}/tmp/pids/unicorn.pid"
    stderr_path "#{root}/log/unicorn.log"
    stdout_path "#{root}/log/unicorn.log"

    listen "/tmp/unicorn.XXXXXXXXX.sock"
    worker_processes 2
    timeout 200

    And here's the nginx.conf file. Note that client_max_body_size has been set to a fairly hefty 4Gb ! :

    upstream unicorn {
     server unix:/tmp/unicorn.XXXXXXXXX.sock fail_timeout=0;
    }

    server {
     listen 80 default deferred;
     root XXXXXXXXX;


     location ^~ /assets/ {
       gzip_static on;
       expires max;
       add_header Cache-Control public;
     }

     try_files $uri/index.html $uri @unicorn;
     location @unicorn {
       proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
       proxy_set_header Host $http_host;
       proxy_read_timeout 600;
       proxy_redirect off;
       proxy_pass http://unicorn;
     }

     error_page 500 502 503 504 /500.html;
     client_max_body_size 4G;
     keepalive_timeout 10;

    }

    So, my question is...how could I edit (either of) the above two files to deal with the extensive time that certain videos take to convert through ffmpeg - possibly up to an hour, 2 hours or even more ?

    Should I extend timeout in the former and/or keepalive_timeout in the latter - or is there a more efficient way (given that I've no idea how long certain videos will take to convert) ?

    Or, is there possibly a more significant issue I should consider - e.g. the amount of memory in the server ?

    I'm not an nginx/server expert, so any advice would be useful (particularly where to put extra lines of code) - however, as the rest of the app just "works", I'm not keen to make a huge amount of changes !

  • FFMpeg : Webcam capture not fast enough. Ffmpeg dies half way (Linux)

    19 août 2013, par user763410

    I am trying to capture webcam output in liux/ubuntu. I have a chico webcam (lenovo laptop). I am running inside a VMWARE virtual machine. The capture is not proceeding beyond 10 seconds. can you please help.

    The command I used is :

    $ ffmpeg -y  -f video4linux2 -r 20 -s 160x120 -i /dev/video0 -acodec libfaac -ab 128k  /tmp/web.avi

    The most important message I am getting is :

    [video4linux2,v4l2 @ 0x9e43fa0] The v4l2 frame is 46448 bytes, but 153600 bytes are expected

    Complete message from ffmpeg :

    ffmpeg version N-55159-gf118b41 Copyright (c) 2000-2013 the FFmpeg developers
     built on Aug 18 2013 09:09:13 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5)
     configuration: --enable-libass --prefix=/opt/ffmpeg --enable-debug --enable-libfreetype
     libavutil      52. 40.100 / 52. 40.100
     libavcodec     55. 19.100 / 55. 19.100
     libavformat    55. 12.102 / 55. 12.102
     libavdevice    55.  3.100 / 55.  3.100
     libavfilter     3. 82.100 /  3. 82.100
     libswscale      2.  4.100 /  2.  4.100
     libswresample   0. 17.103 /  0. 17.103
    [video4linux2,v4l2 @ 0x9e43fa0] The V4L2 driver changed the video from 160x120 to 320x240
    [video4linux2,v4l2 @ 0x9e43fa0] The driver changed the time per frame from 1/20 to 1/15
    Input #0, video4linux2,v4l2, from '/dev/video0':
     Duration: N/A, start: 6424.338678, bitrate: 18432 kb/s
       Stream #0:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 320x240, 18432 kb/s, 15 fps, 15 tbr, 1000k tbn, 1000k tbc
    Codec AVOption ab (set bitrate (in bits/s)) specified for output file #0 (/tmp/web.avi) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.
    Output #0, avi, to '/tmp/web.avi':
     Metadata:
       ISFT            : Lavf55.12.102
       Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 320x240, q=2-31, 200 kb/s, 20 tbn, 20 tbc
    Stream mapping:
     Stream #0:0 -> #0:0 (rawvideo -> mpeg4)
    Press [q] to stop, [?] for help
    [video4linux2,v4l2 @ 0x9e43fa0] The v4l2 frame is 46448 bytes, but 153600 bytes are expected
    /dev/video0: Invalid data found when processing input
    frame=   29 fps= 14 q=3.5 Lsize=      87kB time=00:00:01.45 bitrate= 490.0kbits/s    
    video:80kB audio:0kB subtitle:0 global headers:0kB muxing overhead 7.760075%
    [video4linux2,v4l2 @ 0x9e43fa0] Some buffers are still owned by the caller on close.