Recherche avancée

Médias (1)

Mot : - Tags -/artwork

Autres articles (37)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

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

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

  • Anomalie #3167 : redirection 301 d’anciennes URLs en .php3 ne fonctionne pas

    22 février 2014, par cedric -

    Aucun bug du côté de SPIP, mais une mauvaise compréhension des Rewrite Rules ici :
    - Les Règles de ré-écritures sont lues les une après les autre et s’enchainent pour modifier l’URL : donc ici la première, celle de SPIP, transforme rubrique.php3 en rubrique.php ce qui ne matche plus ta règle qui arrive après
    - La règle de ré-écriture porte sur l’URL, pas sur la query-string. Donc la partie ?id_(rubrique|article)=$ ne matchera jamais car cela fait partie de la query-string
    - dans ta règle complète le R=301 par un skip si tu veux éviter que les règles qui suivent ne s’appliquent aussi [R=301,skip=100] par exemple

    Une ressource utile pour s’y retrouver dans les RewriteRules : http://borkweb.com/story/apache-rewrite-cheatsheet
    Et aussi la base : https://httpd.apache.org/docs/current/mod/mod_rewrite.html

  • Node 18 or Node 20 break ffmpeg (in google cloud functions -> ffprobe was killed with signal SIGSEGV)

    10 janvier 2024, par user20206929

    Please see below, the code is working on node js 16, but not when upgrading to node 18 or 20.

    


    const ffmpeg = require("fluent-ffmpeg");

// Following is inside a .https.onRequest Google Cloud function with enough memory

try {
  const duration = new Promise((resolve, reject) => {
  ffmpeg.ffprobe(videoUrl, async (err, metadata) => {
    if (err) {
      if (res.headersSent) {
        console.error("Response already sent");
        return;
      } else {
        console.log("Metadata:", metadata);
        console.log("err: " + err);
        res.status(400).send("Error getting video metadata");
        return;
      }
    }
  const duration = metadata.format.duration;
  console.log("video duration in second: " + duration);
  resolve(duration);
  });
});
  videoDuration = await duration;
} catch (err) {
  console.log(err);
  throw err;
}


    


    When upgrading to node 18/20 (No other change than upgrading node), the error "ffprobe not found" appears.

    


    But setting the path manually using ffmpeg.setFfprobePath(ffprobePath) ;
trigger the error : Error : ffprobe was killed with signal SIGSEGV

    


    So it seem its a permissions issue.

    


    However, I tried a lot of different solutions, none of them made this work.
For instance i tried to download manually the ffprobe from the official website https://ffbinaries.com/downloads. Then manually add it to the code.

    


    I tried to use https://www.npmjs.com/package/@ffprobe-installer/ffprobe or others package like https://www.npmjs.com/package/ffprobe-static

    


    I also tried to download the ffprobe file to the temporary folder of google cloud, and change the permission of this folder.

    


    All of those was doing the same error.

    


    None of what i could think of made any difference.

    


    Please help because i need to update node 16 to 18 or 20 before google remove node 16 on january 31 2024 and for now i don't see a solution.

    


    I also looked for other solution to get this duration from a video file url, but using ffmpeg seem to be the only one that should work out of the box. As it is working on node 16.

    


    Thank you,

    


    UPDATE - 11/26/2023

    


    GCP Functions NodeJS 16 runtime uses Ubuntu 18.04 with FFMpeg installed.
NodeJS 18/20 use Ubuntu 22.04, and Google decided not to include FFMpeg.

    


    https://cloud.google.com/functions/docs/runtime-support#node.js
https://cloud.google.com/functions/docs/reference/system-packages

    


    No workaround or solutions found as of now

    


    UPDATE - 01/10/2024

    


    Google added back ffmpeg to latest version, this is working as before now.

    


  • FFMPEG Dash with tiles of thumbnail images

    31 juillet 2020, par martyn Gilbert

    As of DASH-IF IOP version 4.2, section 6.2.6 defines the notion of image-based tracks in DASH :
https://dashif.org/docs/DASH-IF-IOP-v4.3.pdf.

    



    This is the ability to have an adaption set made up of mime type images that themselves are a strip of low resolution thumbnails. 
A player will use these thumbnails when the user hovers their mouse over the video timeline and get a 
preview of the the frame at that approximate timecode.

    



    Theo player website has a page dedicated to this function for playback :
https://www.theoplayer.com/blog/in-stream-thumbnail-support-dvr-dash-streams

    



    I need to generate a dash stream (not live) using ffmpeg that also contains these thumbnails. 
I already have an ffmpeg command that will generate the film strip of jpgs which outputs a thumbnail every 5 seconds of input video and joins 5 of these together in a single jpg :

    



    ffmpeg -i INPUT -q:v 20 -vf "select=not(mod(n\,125)),scale=480:270,tile=5x1" -vsync vfr output%d.jpg

    



    and the mpeg dash itself :

    



    ffmpeg -i INPUT -y -map 0 -acodec aac -ac 2 -ar 48000 -s 960x540 -vcodec libx264 -f dash -preset veryfast -b:v:2 1500k -seg_duration 2 output.mpd

    



    But I cannot find a way in ffmpeg to include the thumbnails in the dash mpd file.