
Recherche avancée
Médias (1)
-
La conservation du net art au musée. Les stratégies à l’œuvre
26 mai 2011
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (95)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
Multilang : améliorer l’interface pour les blocs multilingues
18 février 2011, parMultilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela. -
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
Sur d’autres sites (9928)
-
using ffmpeg in C : system() or C api ?
5 décembre 2018, par toastedDeliI want to use ffmpeg’s transcoding features multiple times in my program. This can be achieved by doing
ffmpeg -i input output
in a terminal. I believe I can use some shell or C code to execute these commands programmatically.
I could also directly use ffmpeg’s c libraries to do this. My question is, will there be a noticeable performance difference between the 2 approaches ? Obviously the first will be simpler to implement, but will I pay a big performance cost ?
-
Xcode with ffmpeg support
5 octobre 2013, par user2741735I wanted to know the procedure for compiling the xcode project with ffmpeg with special ./configure options and the gas-processor. I'm using direct input from IP Camera and storing it on my hard drive. However I'm doing this on terminal with ffmpeg. I want to do the same operations using code on xcode. Need help for that.
I have heard that Apple doesn't support ffmpeg for ios apps on AppStore. Is it true ?
-
Trouble Executing ffprobe Binary in Node.js on Local Machine
19 août 2023, par dzul.stellarI'm facing an issue executing the
ffprobe
binary within a Node.js script on my local machine. I have a Node.js script that uses thefluent-ffmpeg
library to extract video metadata usingffprobe
. While I can execute theffprobe
binary directly from my terminal and retrieve the expected output, I'm encountering issues when attempting to run it within my Node.js script.

Project Structure :


project-root/
├── assets/
│ └── video.mp4
├── node_modules/
├── src/
│ └── index.js
├── layers/
│ └── ffmpeg/
│ └── ffprobe <-- This is the binary I'm trying to execute
├── package.json
├── package-lock.json



Example Code :


const { exec } = require('child_process');
const binaryPath = './layers/ffmpeg/ffprobe';

exec(binaryPath, (error, stdout, stderr) => {
 if (error) {
 console.error(`Error: ${error.message}`);
 return;
 }

 console.log('Command executed successfully');
 console.log('stdout:', stdout);
 console.error('stderr:', stderr);
});



Error Message :


Error: Command failed: ./layers/ffmpeg/ffprobe
./layers/ffmpeg/ffprobe: ./layers/ffmpeg/ffprobe: cannot execute binary file



Troubleshooting :


- 

- Ensured that the
ffprobe
binary has executable permissions usingchmod +x
. - Verified that the architecture of the
ffprobe
binary is arm64, which matches my local system. - Checked that the path to the binary is correct and doesn't contain special characters.
- Tested the basic execution of
ffprobe
using theexec
function, but it still fails.











I've tried various troubleshooting steps, including verifying permissions, checking the architecture, and testing basic execution. Despite these efforts, I'm still unable to execute the
ffprobe
binary within the Node.js environment. I expected the script to successfully run theffprobe
binary and provide the expected output, just like when I run the binary directly from the terminal.

Could anyone provide insights into why the
ffprobe
binary fails to execute within the Node.js environment, even though it works perfectly when executed from the terminal ? Are there any additional considerations I might be missing ?

Thank you for your help !


- Ensured that the