
Recherche avancée
Autres articles (51)
-
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette 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. -
Support audio et vidéo HTML5
10 avril 2011MediaSPIP 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 (...) -
HTML5 audio and video support
13 avril 2011, parMediaSPIP 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 (4345)
-
Invoke ffmpeg commands from javacv
18 janvier 2016, par human123I am trying to build a video capture application. As a reference I am using https://github.com/sourab-sharma/TouchToRecord. In this ffmpeg commands are run from "FFmpegInvoke" class. When this project is run without any modification it is working as expected.
But it is using older version of JavaCV. On using latest JavaCV(1.1), build fails saying that libffmpeginvoke could not be found. In "TouchToRecord" project he seems to be using libffmpeginvoke from vine.
So my question is, can we run ffmpeg commands directly using JavaCV ? Please note that in the reference project ffmpeg commands are invoked by creating an instance of FFmpegInvoke in Processor class and command is executed from process method of Processor class.
-
How to use ffmpeg.js in a ReactJS project
1er septembre 2021, par L3M0LMy react app is using ffmpeg.wasm (https://github.com/ffmpegwasm/ffmpeg.wasm) but because of the "recent" issues with
SharedArrayBuffer
I have to move the project to ffmpeg.js (https://github.com/Kagami/ffmpeg.js).

Here is my problem. I installed the library (
npm i ffmpeg.js
) and tried to use the simple code provided on the github page for the web workers to test if it's working :

const worker = new Worker("ffmpeg-worker-webm.js");
worker.onmessage = function(e) {
 const msg = e.data;
 switch (msg.type) {
 case "ready":
 worker.postMessage({type: "run", arguments: ["-version"]});
 break;
 case "stdout":
 console.log(msg.data);
 break;
 case "stderr":
 console.log(msg.data);
 break;
 case "done":
 console.log(msg.data);
 break;
 }
};



but the
onmessage
method never get's called, instead I get

GET https://localhost:3000/ffmpeg-worker-webm.js 403 (Forbidden)



I'm new to the web worker topic and I could not find enough articles about this problem to wrap my head around (in fact, most of the articles use the exact same code as I do and apparently it works for them). Is the problem localhost specific or is it a ReactJS problem and I'm not able to use the ffmpeg.js library at all ? Can someone guide me on how to solve this issue ?


-
Révision 22596 : Code mort : suppression du dernier paramètre de la fonction _image_creer_vignette...
25 novembre 2015, par marcimat@rezo.netdans la fonction, qui ne servent plus a priori depuis r8673 (https://github.com/spip/SPIP/commit/9fe35bd70d028)
$vignette valait tout le temps ’’.
Réindentation en conséquence.Je ne suis pas certain que le paramètre $force non plus soit très utile.