Recherche avancée

Médias (91)

Autres articles (62)

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

  • 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

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

Sur d’autres sites (12012)

  • Revision 9f76c1ec50 : Dual arf : Name changes. Cosmetic patch only in response to comments on previous

    25 juin 2014, par Paul Wilkins

    Changed Paths :
     Modify /vp9/encoder/vp9_encoder.c


     Modify /vp9/encoder/vp9_firstpass.c



    Dual arf : Name changes.

    Cosmetic patch only in response to comments on
    previous patches suggesting a couple of name changes
    for consistency and clarity.

    Change-Id : Ida3a359b0d5755345660d304a7697a3a3686b2a3

  • avcodec/rasc : Check that the number of moves is less than or equal the number of...

    15 décembre 2018, par Michael Niedermayer
    avcodec/rasc : Check that the number of moves is less than or equal the number of pixels

    Fixes : OOM
    
Fixes : 10307/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_RASC_fuzzer-5393974559244288
    

    Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
    
Reviewed-by : Paul B Mahol <onemda@gmail.com>
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavcodec/rasc.c

  • For converting video to frames, should I do client or server side processing ?

    23 mars 2024, par Tomas Marson

    Here is the thing, I have a Nodejs API that serves one video at a time when client request it.

    &#xA;

    The client (made in react) receives the video, which has no more than 15 seconds, watch it and decide if he wants to approve or deny it.&#xA;If he approves the video, it must be displayed in a sort of frames carousel, with one frame per second, so there is no more than 15 images/frames.

    &#xA;

    So the question is, should I do the conversion video-to-frames on client once he approves the video or should I do it on server-side and then request each frame (or streaming all frames with one request if possible) ?

    &#xA;

    Now, I'm doing the conversion on server with ffmpeg, but it seems tricky to send all the frames when the client already have them inside the video.

    &#xA;

Navigation