
Recherche avancée
Autres articles (62)
-
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 (4992)
-
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
-
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 ?
-
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 ?